MSFS 2020 current (and recent) AIRACs
The start of the ILS glideslopes for all runways are at 5000’ at a named waypoint. The FI waypoint, for example FI08L, is some way down the glideslope where the chart shows GS 2700’. However, in the coding which is imported (presumably) into the aircraft there is an altitude restriction of At or Above 5000’, clearly wrong.
Hi,
Are you so friendly as to tell us which addon/aircraft you use? The reason for this not unimportant question is that I can´t reproduce it with the default aircraft, nor with PMDG, Fenix, or Maddog …
So, a few more background information could be helpful.
Cheers,
Richard
1 Like
FI08L on the ILS08L approach has a “H” altitude restriction, meaning the glideslope crossing altitude (2700 in this case) is in the second altitude field. Your aircraft seems to be reading the first field instead. That’s a problem of the aircraft, not the data.
1 Like
Philipp is absolutely right here. Thank you for the visual explanation. Therefore, it is essential to know which add-on you use because I assume that this add-on uses the wrong altitude values.
Cheers
Richard
Thanks for this explanation. It happens in the Inibuilds A359 (MSFS2020) so I’ll forward your reply to them.
Nic Cox
The Rowans, Buckworth, PE28 5AN
The A350 can use either the MSFS navigation data or Navigraph data (enabled via the EFB), so it would be useful to know which database exhibits the issue (default, Navigraph or both).
Regards,
Tim
It’s the MSFS2020 version of the A350 (A359 specifically) if you can give them the heads up!
Thanks
Nic
I use the import from Simbrief so Navigraph (presumably) data, which I’ve always had set in the EFB.
Nic
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.