Help! I've suddenly fallen foul of the reversed ILS syndrome with at least two airports.At LGAV and HEGN the ILS frequency is the same for both ends of the runway, i.e 03R/21L share the same frequency as do 16/34 at HEGN.When approaching either airport I lose both LOC and g/s and have only just realised it is because the aircraft is picking up the opposite end ILS beam.EGCC is the same in that 24R/06L share the same frequency but strangely I still get a correct ILS & g/s indication even though the PMDG 737 shows "INN/237" crossed through on the PFD but that is the correct ILS for 24R.I know this problem has cropped up before but I cannot remember the solution and a search threw up 180 pages of matches, I don't think I'll be searching through that lot!The 3 airports mentiooned all have AFCAD2 files asscociated with them.TIA

If available on your aircraft, use the "backcourse" mode. This mode is specially for intercepting the back of an ILS beam and interpreting it in the correct sense. IRL it is a legal in the US, not for JAA countries.

Hi,If you have addon scenery for these airports (not AFCAD2 files), then remove the navaids bgl file. Old style navaids files will cause this behavior.The other thing to try is to remove the AFCAD2 files for these airports and try it again. They may be incorrectly coded.Hope this helps,--Tom GibsonCal Classic Propliner Page: http://www.calclassic.comFreeflight Design Shop: http://www.freeflightdesign.comDrop by! ___x_x_(")_x_x___

Apparently FS9 does not like ILS frequencies that are the same at both ends of the runway. I believe this problem occurs when the ILS components have been moved from their default positions. With the latest version of AfCad 2, try changing the frequency of one end only (try each end in turn to see which works best) of the ILS to some frequency that does not exist elsewhere locally. I did this and found that the changed frequency end still works at the original frequency! I don't know of any other cure, having tried everything else I can think of. Hoping some AfCad designers might benefit from this too.

Tom & Charlie,Thanks for the suggestions.Before I get into the grrrr.... factor do AFCAD2 files have to be at a specific layer in the scenery library? Currently I have a whole lot of these files in addon sceneryscenery.After a little experiment I have just done (won't go into details yet) I wonder if the placement of the AFCAD2 files is my problem?Thanks

Vulcan, I'm not aware of exact placement issues with AfCad files. I had tried moving them around when I had the same problem and it made no difference. I usually like to install them in the same folder as the add on sceneries they relate to. Some sceneries install them in a separate folder which then usually means having to install those files in the scenery add on menu. As I said, the only way I know to fix it is to change the frequency of one of the ILS, I would suggest to begin with changing the one that is currently not working.

I get this at KMSP but when I am at the correct interecept altitude and with a few degrees of interecepting the correct localizer I have seen the correctly ID'd navaid pop-up on the EHSI just before it is needed.I am using for KMSP an FS2K scenery version (with upgrade) from Ron Ackerly and perhaps that might have something to do with things but so far I have had success at other single frequency locations.In another thread here it was also suggested that using AFCAD2 in the localizer properties section to insure that the back-course is disabled on opposing localizers on a shared frequency since they would interfere with each other.

I agree with Ronzie."I get this at KMSP but when I am at the correct interecept altitude and with a few degrees of interecepting the correct localizer I have seen the correctly ID'd navaid pop-up on the EHSI just before it is needed."But not limited to KMSP. Especially if I am approaching the runway from one side or the other, NAV1 often acquires the "wrong" localizer. If I grit my teeth and follow ATC's vectors the "right" localizer will capture before it is needed but sometimes it is just barely in time. R-

Hi Charlie,I can confirm that both LGAV & HEGN ILS work correctly with the default scenery and no extra AFCAD files.Staying with HEGN this what I found.Looking in AFCAD at the stock airport there is one ILS for Rwy34 (HIL), frquency 110.30.If I position my aircraft on approach to Rwy 34 with 110.30 set on NAV1 I get no indication at all, ame thing if I approach Rwy16.Looking at the AFCAD file I recently installed there are ILS beams for Rwy16 & 34. 34 is the same as stock (HIL, 110.30). ILS for rwy16 is IABC on 110.70.Now if I set 110.70 in the aircraft I get a correct indication approaching 16 and a back course approaching Rwy 34 but no indication at either end if I set 110.30 in NAV1??Back couse is enabled for both.

Vulcan, "Staying with HEGN this what I found.Looking in AFCAD at the stock airport there is one ILS for Rwy34 (HIL), frquency 110.30.If I position my aircraft on approach to Rwy 34 with 110.30 set on NAV1 I get no indication at all, ame thing if I approach Rwy16.Looking at the AFCAD file I recently installed there are ILS beams for Rwy16 & 34. 34 is the same as stock (HIL, 110.30). ILS for rwy16 is IABC on 110.70.Now if I set 110.70 in the aircraft I get a correct indication approaching 16 and a back course approaching Rwy 34 but no indication at either end if I set 110.30 in NAV1??Back couse is enabled for both."First make a backup of the add on AfCad file and move it to a folder that can't be read by FS9. Then try your preferred option from one of the three below. If you would rather the new AfCad to work as the default you should delete the ILS for Rwy 16. I think then Rwy34 should work. If you want to keep the new ILS at 110.70 for Rwy 16, just change the frequency for Rwy 34, say to 110.35 or if that is used locally, to another frequency to see what happens. Note that I would still expect it to work on 110.30! More logically, it should also work at the new frequency. If you want both Rwy16 and Rwy34 to work on 110.30, change Rwy16 to 110.30 and change Rwy34 as above. Both ends should then work on 110.30. You could try moving the plane in slew mode to speed up testing. Please let us know what happens. If it works OK then we can look at the other airport.

Many thanks Charlie, hugs and kisses, if I was that way inclined :-lol Deleted the ILS for Rwy 16, still no indication on 110.30 for Rwy 34.However using the AFCAD2 file as was and reassigning Rwy 34 ILS to 110.35 I get a correct indication, still no idea why 110.30 would not work?As I don't have charts for HEGN I have no idea if it should have an ILS for Rwy16/34 so I have emailed the person who wrote the AFCAD file to see if he can provide that info and I also explained the problem with using 110.30.Don't worry about LGAV Charlie as the add-on I'm using is for FS2002 and I am hoping the Hellas scenery guys will be producing a version for FS9 in the near future.Many thanks for your help.

Vulcan, Glad to be of help. When you say you get a correct indication for Rwy34, was that on 110.30 or 110.35 or both?

>Vulcan, >>Glad to be of help. When you say you get a correct indication>for Rwy34, was that on 110.30 or 110.35 or both? >Sorry Charlie, only when I changed the frequency to 110.35. No indication at all with 110.30 either with the stock file or the new AFCAD file.

Vulcan, In that case I'm kind of disappointed it won't work on the original intended frequency. But the main thing is that you're happy with the result.

One thing to insure is that when you open an airport in afcad2 there is no more than one showing up besides the default. If there is proceed to open it and get the full file name from the title bar and decide if you wish to keep it. Do the same for any other "layer".Move the layers you do not want to an out of the way folder that FS9 can't get to.More than one layer besides default can cause weird things to occur.