FALE ILS 24 missaligned

Please add the following corrected data to your datasets. I received this from FSDG after complaining on their forum about the misalignment of RW24. I currently have this data in my user_nav.dat file in XP11

4 -29.627369971 31.105589685 294 10970 18 87697.800 TGI FALE FA 24 ILS-cat-II
6 -29.601522222 31.129791667 294 10970 18 300217.121 TGI FALE FA 24 GS
12 -29.601516667 31.129800000 294 10970 25 0.000 TGI FALE FA KING SHAKA INTL DME-ILS
4 -29.596163297 31.133428466 290 11130 18 22357.800 TNI FALE FA 06 ILS-cat-II
6 -29.623461111 31.110688889 290 11130 18 300037.121 TNI FALE FA 06 GS
12 -29.623469444 31.110683333 290 11130 25 0.000 TNI FALE FA KING SHAKA INTL DME-ILS

these coordinates are exactly the same what we use in the MSFS data too …

I don´t have found any FSDG FALE scenery for MSFS …

Here are the coordinates from MSFS
LOC antenna -29.62738611, 31.10571389
GS antenna -29.60152222, 31.12979167
DME antenna -29.60151667, 31.12980000

You see nearly exactly! the same position (there is a rounding of course but that doesn´t make any difference). Both are centerlined to the runway 24

… and here, because the original posting is quite old - FALE 24 approach stock data with the stock Airbus A320neo, AIRAC 2205 installed:

short final:

As you see, no misalignment here - the data are correct. By the way all data will be created from one and the same data-source, so it would be strange when a LOC position is differ in one sim as in the other one. In this case, all coordinates are the same (excluding a small rounding):

All these data are absolutely correct and will be used in the MSFS as you see in my screenshots, which I have made now with the latest MSFS version.


Hi Richard,

Apologies, I did not realize at the time that the thread was sim specific. The data I gave you earlier was specific for XP11.50+. Without me using the “fix” as shown the FSDG scenery does not work in XP11. RW24 is way off.

So what I understand now, is that it is fixed in MSFS2020 but definitely not in XP11


Hi Nico,
no problem, but again as you see in the google maps screenshot, the loc antenna is on the correct position in the XP11 data.

I haven’t test it now with the stock XP scenery but I will do this as a reference because I’m pretty sure that this is a 3rd party scenery issue. Possible the runway coordinates are not correct … I don’t have this XP scenery therefore it’s only a assumption. The coordinates in XP11 are correct too, thats for sure and you see this on the google maps screenshot above.


Can confirm ILS24 in msfs is spot on. Just landed the fenix.
But atc all over the place - not sure if this is a random event or the result of wu10

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.

Hi there, I am back as this has still not been resolved yet.

I have asked FSDG to submit their missing data to Navigraph, to be added to the AIRAC for X plane 11.50+ will include the link to this post in forum post on their side.

I see no point in asking users to put it in to the user_nav.dat when it can be permanently added to the Navigraph database.

If you will be so kind as to assist them to complete this task when they contact you, I will be very grateful and so will every XP user of the scenery.

I´m not sure, what you expect now? The data are correct and when you use it with the stock scenery, you see no offset/missalignment

XP11 - AIRAC 2207 installed - default B737:

Absolutely aligned … As I wrote before and as you see in the screenshots before, the localizer coordinates are correct on the real-world position. So, when you use a 3rd party scenery, than something is not 100% correct in the scenery - I´m not a scenery designer, I can only speak for the data and here, I don´t see any issue. Sorry.

… by the way, all our datasets are from the same source, so when something is wrong it´s nearly impossible that it´s ok in MSFS but not in XP11 and also in MSFS, no offset - you see the confirmation from @richardharrisxx


Good morning Richard,

I went and tested the information you provided and you are correct!
Apologies for the misunderstanding BUT it was driven by FSDG pointing here every time.

Thanks for your help, I will take it back to them now again.

No need to apologies you, we try to help where we can - when FSDG needs any help from us, they should contact us directly via the developer-support (dev@navigraph.com)


Appreciate it, i will relay the message