How to tune ILS with same frequency

[CapP 0]

Today a flew from Aberdeen to Liverpool. At liverpool the ILS frequencies of runway 09 and 27 are the same (111.75). ID of 09 is ILVR and ID of 27 is ILQ. ATC ordered me to land on 27, so I tuned 111.75 on NAV1 and set course selector to 269 degrees. Unfortunately the ID shown was ILVR and not ILQ! I saw this when the aircraft started to take strange angles to try to catch up with ILVR, so I had to go around. Second time i did a backcourse landing on ILVR and that worked. But my question is: is there a way to tune to ILQ instead of ILVR. I remember I had the same issue during the tutorial with runway 01R at KIAD. Hope someone is willing to help me with this. I think it's no error but just because I have always flown the MD11 which tuned the ILS frequencies itself. But those lazy days are gone now ;-)

[Yoda967 23]

Pieter,This is an age-old MSFS problem, I think. If memory serves, the solution is to wait until you're past the mid-point of the field to tune your NAV radio to the ILS. So, you're inbound from the west and are being vectored to RWY 27, you'd wait until you were east of the field before dialling in the ILS frequency. Let us know if that helps.

[CapP 0]

Thanks for your answer. I'm a bit relieved it was not me doing something very stupid. I will try next time when I'm heading to Liverpool. Although I'm afraid it won't work because during my go around i switched frequencies very often to try to tune ILQ but with no success :(

[ronzie 21]

This error is caused by all ILSs in FS9 ( and maybe X) default airports have the back course enabled. Open up in AFCAD (for FS9) the AFCAD layer or if none stock layer to create one and go to Lists/Navaids. Click on one of the two ILSs with the same frequency at opposite ends of the runway, click Properties, and uncheck Enable back course. Do the same for the other ILS and then save the file.In AFCAD be careful that any layer you open shows a taxi and runway diagram. It is not safe to modify and save any layers that do not show them as they are special. The top layer that shows runways, etc., is the one to modify.For FSX you can probably use the payware AEX.For both you should be able to use this released freeware ADEX9 available here. I have not used it yet but it should have that functionality. It is available here:http://www.scruffyduck.org.uk/filemanager/...rrent%20Version

[CapP 0]

Thanks for the info. Unfortunately the link doesn't work :(

[Andydigital 93]

Go via the official webpage rather than directly to the download area, then it will work.http://www.airportdesigneditor.co.uk/

[Nick Dobda 24]

Reviving this topic, I see it hasn't really been discussed since 2009. Has a solution to this problem (other then the one above) come about?

Departing Newark (KEWR) on the Liberty 3 requires DME from ILS approaches. Unfortunately, the wrong ILS comes in when tuning. Moving the plane to the opposite side of the center of the RW (slew) tunes in the correct one, but it switches halfway down the runway, so departing correctly on the Liberty 3 is impossible unless theres a fix... or a FIX way of doing it I guess with range circles or something.

​

I know its an FSX issue, as the program makes an assumption (that's mostly correct most of the time), but how does it work in real life? There must be a way in real life to do it... Tell the radio which to choose?

[pcubine 143]

Departing Newark (KEWR) on the Liberty 3 requires DME from ILS approaches.

I don't see any indication that any ILS frequency are required by a LIBERTY3 SID. The whole SID is by ATC vectors.

[JRBarrett 3,070]

Reviving this topic, I see it hasn't really been discussed since 2009. Has a solution to this problem (other then the one above) come about?

 

Departing Newark (KEWR) on the Liberty 3 requires DME from ILS approaches. Unfortunately, the wrong ILS comes in when tuning. Moving the plane to the opposite side of the center of the RW (slew) tunes in the correct one, but it switches halfway down the runway, so departing correctly on the Liberty 3 is impossible unless theres a fix... or a FIX way of doing it I guess with range circles or something.

​

I know its an FSX issue, as the program makes an assumption (that's mostly correct most of the time), but how does it work in real life? There must be a way in real life to do it... Tell the radio which to choose?

In a real life airport where the ILS systems at opposite ends of a particular runway both have the same frequency, the tower controls which transmitter is active. The controllers have the ability to remotely switch the equipment on or off. In addition, there is normally remote indication and monitoring equipment in the tower to alert the controllers if any part of the active ILS is malfunctioning , or if the radiated signal is out of tolerance, which might make the ILS unusable for an aircraft to make a safe approach.

 

The ability of ATC to control which ILS transmitter is active solves the problem of aircraft receiving the wrong one. In the sim, unfortunately, such switching is not possible, so the only practical solution is the one which currently exists - in which the "active" ILS depends on the relative position of your aircraft in relation to the runway. Not sure if there is any way in FSX or P3D to programmatically control whether a given nav aid is "on" or "off", since the nav aids are baked into various .bgl files.

 

Perhaps a scenery expert or someone like Pete Dowson might know if such a thing is possible.

 

While there are many r/w SIDS that use the DME associated with a specific runway's ILS as part of the procedure - the LIBERTY3 departure at Newark appears to be purely an ATC vectored departure. Not sure where you are seeing the DME requirement for this SID.

[Nick Dobda 24]

Sorry guys, I did the flight last night, and initially was going to do the Liberty 3, so I had that in my head. Ended up on the Newark Two departure for 22R. There you will find the problem at hand.

 

Its the first time I've come across it in my travels around the country. I thought someone might have created some sort of band aid type fix... something not in the real plane, but a gauge that might solve that issue.

 

Not a biggie, thanks for your help and insight..

[scandinavian13 5,192]

Sorry guys, I did the flight last night, and initially was going to do the Liberty 3, so I had that in my head. Ended up on the Newark Two departure for 22R. There you will find the problem at hand.

 

Its the first time I've come across it in my travels around the country. I thought someone might have created some sort of band aid type fix... something not in the real plane, but a gauge that might solve that issue.

 

Not a biggie, thanks for your help and insight..

 

The issue referenced in this thread is actually discussed in the J41 tutorial (which I'm guessing is what is referred to in this thread, at least in the 6 year old part of it). There is a workaround to make sure it doesn't catch the wrong side, and a workaround to force it to take the correct side when you get there, discussed in that tutorial.

 

What aircraft are you flying here? The NGX? If so, just use the FIX page. That's usually a lot easier. Note that the LOC names are different, despite the same frequencies. In your case, despite the north side using 110.75 as well, it has a name of I-EWR, while the south side has a name of I-JNN. I haven't flown this departure in a while, so my recollection of how to get it into the FIX page is a bit shaky, but I think you can just use IJNN (no dashes) and it'll pull the LOC. I know you can do it, though, because I'd do it any time I flew the EWR or LGA SIDs using DME.

[Nick Dobda 24]

Kyle,

 

Yes I'm in the NGX. I figured going to the FIX page with two range circles would work just fine too. I tried typing in just the last three letters as the fix but it didn't work. I'll try putting the I in front. If it works (I'm guessing it will), problem solved.

[downscc 1,327]

From what I've seen in the navigation data from FAA NASR, when both localizers share the same frequency and both use a DME there is only one DME and it is noted in the data as "also used by..."

 

Not sure how the MS default airports are set up, rarely is the DME in the right location... in fact, I've never seen the DME in the right location. The default usually puts it at the Localizer. Add on sceneries vary in their accuracy, usually overlooked.

 

Get a copy of ADE and learn to use it if you want to have accurate navaid placement at your airport. The data from the FAA is free and updated every 58 days: https://nfdc.faa.gov/xwiki/bin/view/NFDC/56+Day+NASR+Subscription