LAST EDITED ON Oct-16-03 AT 08:31 PM (EDT) Don't know whether this is just another short between the ears, an error specific to my setup, or a general fault in FS9. I have been just adjusting and complying any time my vertical crosshair was on the wrong side and the horizontal was dead. (Obviously backcourse) Just completed a flight from KIAD to KORD, landing ILS on Runway 9R.To my surprise, it turned out to be a backcourse approach. Guidance was perfect for localizer accuracy, reversed, and no glideslope.If I read the approach plate correctly, this should have been a frontcourse ILS approach including Glideslope capability. FS Navigator and the GPS indicate this to be frontcourse if I read them correctly.In contrast, some plates specify backsourse approaches, for example, KBTR "LOC BC Rwy 4L".(i.e.AeorPlanner.com plates) Unfortunately, my Jeppeson plates do not include KORD ILS approaches.There have been numerous other approaches of which I was suspicious, but have not really investigated them. I am pretty sure at least one of the KIAD runways has this problem, but I don't remember which one.First, being that I was useing SimFlyer airports, I killed this and went to the FS9 default scenery. Same thing.Then being that I was useing the Iron Knuckles DC9, I thought maybe that was the problem. Switched to FS9 default aircraft. Even slowed down to the 172 to see everything in slow motion. Same thing. First time I have used a default aircraft since before FS2000. Now I remember why!Am I missing something here, or is my analysis correct, and are some of the approaches corrupt?Thanks:RTH

OK Gang, I found it! Last night luckyly I turned off my computer to give it, and me a rest, which is unusual as I virtually leave it running almost 100% of the time (not me, the computer). When I got up this morning, I cranked up FS9, went to KORD Rwy 9R, and wouldn't you know it, the problem was gone. I fear I made one mistake in my initial troubleshooting, and therefore; my initial post. When I unchecked the SimFlyers KORD scenery in the library, I went ahead and continued the startup in FS9. In big bold RED writing, Mr. Gates told me that I had to restart FS9 (TOO obvious). When I continued, I am assuming that the SimFlyers scenery was retained unbeknown to me rather than reverting back to the default FS9 Scenery. I sure do wish you could do this on the run like FS2002 without having to restart FS9. This morning thanks to shutting everything down last night, when I started up FS9 again, it rebuilt my scenery library without the SimFlyers KORD and replaced it with the default KORD location. I will copy Wolfgang at SimFlyers with this post and see what he thinks. Looks like a problem exclusive to that scenery to me. In fact, it seems like they have a statement concerning runways useing the same frequency for both directions on the same runway if memory serves me correctly, but I am not sure with my senior momments. I will try to check this out in their documentation. I'm willing to bet that the other runways in which I saw this problem were probably SimFlyers scenery as well. (Not bad mouthing SimFlyers. I will gladly accept a substituted backcourse in place of a standard ILS approach on some runways for their great airports.) It looks like some third party adaptations have converted ILS to Backcourse approaches, probably on common runways. May be the nature of the beast. RTH