-
Operating System: Windows 10
-
FS Version: X-Plane 12.4b2
-
Add-on: Zibo 737-800 (v4.05.15)
-
AIRAC Update No: 2513 rev 1
Flying into EGSS this morning with ILS approach on Rwy 22 - localiser ID is listed as ISX. As per the charts, I tuned Nav 1 and Nav 2 to the frequency (110.5) and the course (222). I double checked this on both the Navigraph chart (EGSS 31-2) and on the FMC (AIRAC 2513 rev 1) and confirmed that the radios and MCP were correctly configured.
When the localiser was picked up, it was shown on the PFD in yellow text and strikethrough with the localiser ID listed as ISED rather than ISX. I understand this to mean that the course selected is incorrect for ISED. Looking at the EGSS charts, ISED is the localiser for the opposite runway 04 (but on course 042).
This means that the ILS approach using localiser ISX on Rwy 22 cannot be flown.
Hi,
ILS04 and ILS22 use the same frequency (110.50), so you should select the correct approach in the FMC. Only turning the frequency is not enough.
I hope that helps
Richard
Correct approach was also selected in the FMC. ILS Rwy 22.
I’ve just run another test. Departing EGSS and landing EGSS at ILS Rwy 22. This time I was able to get the ISX localiser on 222. Very strange that it didn’t work when departing from another airport. Perhaps I did something wrong somewhere. I will do another test later.
Hello AutomatedWing755,
When opposite runway ends share the same ILS frequency, correct acquisition may depend on the approach sector while tuning the frequency on the VOR/ILS receiver. At least it is the case with Microsoft simulators. I have no experience regarding X-Plane. However, you may give it a try. On MS simulators a 30° beam (60° full angle) from selected runway axe is usually OK. As Richard pointed out, it has nothing to do with selection of the correct approach on the FMC
Regards
Hervé