ILS glide path wrong

[Andreas Guther]

The ILS glideslopes are not correctly aligned. Target is to cross the runway threshold at 50 ft RA, as visible in the screenshot the actual glideslope is much higher. I checked all ILS approaches in eastern direction, and they are all wrong. Therefore, the others should be checked as well.

IMHO, the correctness of such things is much more important than eye candy inside the airport...

Edited April 5 by Andreas Guther

[richboy2307]

On 4/6/2025 at 4:43 AM, Andreas Guther said:

IMHO, the correctness of such things is much more important than eye candy inside the airport...

Absolutely agreed, which is why we do run tests for these with autolands to try to get best co-incidence for the glideslopes and PAPIs. There are certain sim limitations that prevent this being perfect (ie matching real life 1:1), for example although the runways have slopes/terrain following, in the sim data, each runway still only has a single height value calculated at the centroid. This results in a slight difference between the PAPI GS (which sit at the 'physical' ground height) and the ILS GS position. Sometimes there's other limitations such as discrepancies between datasets (e.g. at OMDB between Navigraph vs Sim Default Navdata).

The scenery editor tools available for such adjustments are also fairly imprecise with a lot of trial and error required in the placement of these.

Anyways, in relation to your query below are screenshots from a video recorded during earlier test builds using Sim default navdata on the A330 on 24/25 Runways. Its not 100% co-incident with PAPIs at 50ft due to aforementioned issue but the glideslope does intercept 50ft AGL at about the the start of runway threshold as we observed in testing. Its not perfect but we believe it to be within margin of error for whatever precision the sim allows us to achieve.

24L
  
24R

25L
|
25R

Just for checking your report, tried with latest Navigraph navdata (2503 rev3) as well in the A321neo and cannot reproduce the Glideslope being *above* the user at 50ft RA at the threshold. If you are simply testing by slewing, do note the instruments (particularly GlideSlope) may not update until aircraft is released and as such not reflect the proper values in slew.

Thanks!