I’m experiencing an issue with the ILS 25 at EGSY (St Athan) using the PMDG 737. When I tune in the CRS and frequency in the plane, there’s neither an LOC nor a G/S coming up on my PFD. I tried other airports and tuning the ILS works fine (tested in EGLL and EHAM). It definitely worked before (I flew into EGSY with the 737 in February, and the ILS worked fine). I also tried the Fenix A320, and the ILS worked normally. So I assume there’s something fishy going on with the PMDG navdata.
Hi Dorian,
First of all, welcome to Navigraph. Thank you for your report.
Unfortunately, this is an ASOBO/MS issue because ASOBO uses an outdated ICAO code for St. Athan, and therefore, the overlay doesn´t work.
Here from the WorldMap - you see EGSY (St. Athan), which comes from us, and the EGDX (St. Athan AB) from ASOBO/MS, which is outdated. The internal logic is now that normally the ASOBO airports have a higher layer and “overwrite” our data (when the airport-position is equal):
With the default data, EGDX has no ILS for 25. Because the ASOBO layer is higher in this case, you can´t receive the ILS even when you have it in your data (MSFS and also in the PMDG).
Here, the stock MSFS data (wrong ICAO code, no ILS on 25):
I’m sorry, but in this case, we have no chance to fix this. ASOBO/MS used many old/unknown ICAO codes in 2020 and 2024, but there is no possibility to “overwrite” ICAO codes, runway idents, etc. In other words, please report this to ASOBO/MS so that they can change the ICAO to the correct one. You will immediately see and receive the ILS 25 when it’s done.
Thank you for your reply. I know about the issue regarding EGSY/EGDX. I actually created a scenery for myself which uses the EGSY code and disables EGDX since I couldn’t use it with BeyondATC otherwise. I thought the issue was the scenery at first, but even when I disable my custom airport, it doesn’t seem to work. At least not in the PMDG 737.
But still: I definitely used the ILS back in February in the 737, and it still works without problems in the Fenix. I’m gonna try the iFly 737 and PMDG 777 in the evening to see if the ILS works with them.
Hi Dorian,
Fenix doesn´t use any MSFS data; it is completely independent of the MSFS data, which avoids many such issues—it only uses its (our) database for the whole navigation. That´s not the case in iFly, PMDG, Maddog, etc.; they need the BGLs from the MSFS to work correctly, and therefore, you see a difference between Fenix and all the other add-ons.
Have you tried to determine whether you received the ILS with any stock aircraft, like the C172 with the G1000, or any other aircraft? I would try this first to see if you can generally receive the ILS.
Hi Dorian,
But where did you set the ILS frequency, 111.15? You have tried to select the approach, which has nothing to do with the signal. Can you tune the frequency in NAV1 and switch to the APP mode? I miss the LOC and GS on all screenshots.
Exactly, Dorian. I´m not a scenery designer, but you must add the ILS to your scenery. To see if the ILS is working, checking it first via any default stock aircraft is essential. When it is working, you can be sure that the PMDG also works
Good luck and let me know, whenever you need any more assistance, please
