Hi all,In FS9, when approaching an airport for landing and tune the ILS frequency and set up course, sometimes on the ND I get the reverse behaviour from the CDI example :Tuned frequency xxx.xx and set up course 090 for the runway.When loc and gs are sensed and shown on the ND I will get reverse direction of the CDI and so if say I am on a 30deg right intercept the CDI will show that I have to turn left in order to get on the localiser. In general when this is the case I will also not get any GS indication on the ND.This happens randomly on no scenery in particular and no aircraft in particular either.Anyone encountered this before and knows how to solve it?THanks a lotFlylux

Hi,what you describe is a back course approach. When the runway you are attempting to land on doesn

Thanks a lot for that information and the thread you directed me to is quite informative.However the thing is that this issue happens on runways which are ils equipped and not for backcourse ie maybe today I fly into an airport and the ils behaves correctly and the next day the course behaves just oppositely. This I cannot reproduce any time that I want and it just happens at its own will. So I gather that there must be something more to it.The explanation of the backcourse was good indeed.So any other inputs please??ThanksFlylux

I have noticed that as I approach a runway with ILS, I often see this phenomenon when I first acquire the localizer signal (the vertical needle moves the wrong way and the horizontal needle does not move). If I am sure that my course is correct and I'm sure that the airport has a full ILS for my intended runway, then I just continue my approach. Within a few minutes, the localizer needle will correct itself and shortly afterward the glideslope will be acquired and the horizontal needle will deflect. R-

this was not the case for me ron because when I leave the aircraft to continue the approach it just follows the needle and turns the wrong side for a complete intercept of the localiser...I still cannot reproduce it often enough to nail down what triggers this...but i m sure that it is a bug somewhere....thanks the same mate...

Some autopilots are equipped with a "BC" button to handle backcourse approaches. Use it instead of the "APR" approach button, and it should correctly handle a backcourse approach.

Are these runways that indicate a shared frequency for localizer/ils in both directions? This is a known problem in FS9 since withiun FS9 both directions are simultaneously active, not a real world situation.I find that (by checking out the identifier code on audio or the display on the EHSI) that the opposite localizer has been acquired. I fly in heading mode an appropriate intercept and usually when close enough in the vertical and horizontal profile, the correct one pops in. It is very sensitive to distance from the navaid and intercept angle.I am not talking back course here, but (in FS9) active opposite facing navaids on the same frequency. In TRW only one would be active controlled by ATC.Some people have gone in to some airports with AFCAD2 and reassigned one of the frequencies - don't recall the procedure.Two checks when doing this is:1. Check out the navaid id (audio or display) to insure you've acquired the correct one.2. Check that your OBI course is set correctly for inbound at the appropriate time.During approach vectoring or self-navigation, I always use heading mode on the A/P with an eye on a GPS map and the GPS bearing to the runway. I manually intercept and only then activate the approach mode of the A/P after identifying again the navaid ID.