I am doing some test flights into JFK. When trying the ILS for 4R 109.50/45, the VORLOC switch will not light. If I then select APP, it switches to BCS 222.

 

I did an ILS 31L flight no problem. Does any one have any ideas.

 

 

Thanks

 

Bill

Just tried ILS 4L. Again VORLOC not selectable, but APP worked correctly. There are no duplicate AFCADS and I am using lastest Navigraph version.

 

Bill

I have just completed all tes5/

 

ILS 4L. No vornav selection. APP ok

 

ILS 13L good

 

ILS 31R. No vorloc selection. APP goes to Bcs 222 landing ok

 

ILS 22R/L. Ok

 

ILS 31L Ok

 

ILS 4R. No vornav selection. APP goes to Bcs 222 IJOC. Lines up between the 4's

 

Any ideas? No duplicate afcads found. Reinstalled fast

 

Thanks

 

The NGX doesn't do anything special with ILSes - they have to be there properly in the FSX world, it's tuning them just like any other aircraft does (aside from if you have SET FSX LOC CRS enabled, in which case it pulls the course from the local BGL file). I've also never heard of any issues specific to FSDT airports - I have many of them myself and haven't experienced any issues (I don't have JFK though).

Ryan, removed FSDT JFK and used the stock airport. ILS 4R still goes to B/CRS 222 and shows IJOC/45 which is 22L and not IJFK/45

 

Could this be a Navigraph issue?

 

Bill

I think it is. Revision 1 of the latest Airac for the PMDG aircraft has been upgraded to revision 2 due to sid/star errors. So, Rev 2 is available now.

I found a response in another forum on this exact problem (see below). I am going to turn off backcourse tonight and give it a try.

 

Bill

 

 

Your problem is the way Microsoft setup the default ILS in FS2004 and FSX.

 

Rwy 4R and 22R share a frequency (109.50), Rwy 4L and 22L share a frequency (110.90) and Rwy 13L and 31R share a frequency (111.50) at KJFK. And every one of those ILS is set to enable the backcourse.

 

Which means that if you are not exactly on ILS course, your aircraft will 'capture' the backcourse from the wrong runway. Of course there are not actual transmissions in FS - just a simlation of the effects of radio transmissions.

 

This in not a problem in the real world because none of those ILS transmits a back course, and the ILS for the runways not in use will be turned off to not transmit. But because Microsoft chose to Enable Back Course for every localizer in the entire world - several airports have this issue.

 

There are two options which should relieve your problems, but both require the airport to be edited.

1) Edit the airport to uncheck the default setting of Enable Backcourse on those six ILS at KFJK, or,

 

2) Change the frequencies of one of each pair of shared frequencies.

 

Nr 1 works most of the time for most folks. Nr 2 has the disadvantage of making it harder for you to find the new frequencies if you forget.

 

Something else is that you need to be able to recognize the identifier of the localizer your aircraft 'locks' onto. Some FS aircraft have a HSI gauge which will display that identifier, some will require you to listen to the morse code to recognize the ident.

 

Of course, you have to do your homework and know which is the correct ident, and what are the other idents for the airport should you 'lock' onto a wrong one.