I wonder if anyone can kindly help me sort out my ILS approaches?! At airports where there is a glidescope associated with the end of the runway on which I am supposed to be landing, then usually everything is OK. (That said, far too often FS9 tries to bring me down well short of the runway when I approach on IFR (the plane is not stalling, I should add!): I have to switch off AP and bring the nose up manually to get to the threshold. This seems to happen if I set flaps much over 15 degrees, even though in theory I should have more than that. Whatever...... The real frustration is something else):When I land at a runway which has the same ILS frequency both ends but a glidescope at only one of them, things go wrong. For example, FS9 shows no ILS frequency information at all for runway 11 at Darwin Intl., Australia. FSNavigator 4.6, however, gives the same ILS frequency for runway 11 as for its opposite end (I forget the number!) but indicates no glidescope for it. So what do I do to land by instruments on runway 11? If I set NAV1 to the given frequency, and click 'APP' as usual, when the plane intercepts the ILS beam, it always veers off in the opposite direction - steering, maybe, for the other end of the runway?? If I set Back Course, then I don't get any response from the autopilot at all and unless I disengage it I'd fly right over the airport.Doubtless I am doing something wrong, but even so, it is VERY annoying, having flown for several hours, to mess up the landing! (IT must be even more so in real life!!). As I say, assuming the above is vaguely intelligible, I'd appreciate some help from anyone with time and patience on how to land on instruments on Darwin's runway 11 (and all the thousands of similar!).Thanks!Martin

ILS consists of localizer and GS (glide slope).Sounds like Darwin's rwy 29 has full ILS but rwy 11 has Back Course only. So you have to manually control vertical part of approach to rwy 11. In other words your approach to 11 is localizer only.A few things can work 'against' you in FS9.First, in real life only one side would be working - 11 or 29 but not both. In FS9 all sides are always working ("ON"). The software can get confused if you start approaching on the 29 'side' but ultimately end up flying approach to 11. So it is important to stay on one side only.Your Back Course should work OK. However autopilots are not very well done in default FS aircraft so there mey be some bug somewhere.Michael J.http://www.reality-xp.com/community/nr/rsc/rxp-higher.jpg

Best advice is give yourself plenty of miles before touchdown.In Jets allow about 20 miles at least of ILS interception with your approach approximatley in line with beam.I engage just below glideslope, and it usually(?) picks up OK. However I take over manually at 500 feet call out, watching that joystick throttle is at zero and that speed a/p is switched off.On default A/P airspeed keeps active even when A/P is switched off!Generally I land where I am told by ATC! However, the ATC instructions can sometimes be 'mince' and what starts out as a textbook approach can go to hell!Hope this helps.

Here is a good ILS tutorial :http://www.flightsim.com/cgi/kds?$=main/howto/ilstutor.htmhttp://www.hifisim.com/images/as2004betateam.jpgPatrick/EBBR

Thanks for the information. I'd seen the artcile you refer to before Patrick, then forgot about it, so thanks for reminding me! I'll download the zip files and work through it. My son says 'get a life' - or thinks it - but when I've flown half way across the world and then the landing messes up, it spoils the rest of my day - what's left of it!!I do approach the 'non-glidescope' end of the runway directly, not via its opposite end, so FS9 shouldn't get confused. I think that you are right about there being a bug - I have flown the big jets almost every day since FS9 came out and sort of feel I am orpetty competent, so failures are hard to take; less hard if I can blame Microsoft!Also, FS9, when on IFR, always wants to begin my descent much later than FSNavigator. Again, I think you are right Ronald about an earlier descent. (Though I have to cancel my flight plan or ATC tells me I am below my assigned altitude of course). The FS9 default descent point (is there any way to alter this, globally? Probably not - buried in the code somewhere) is too late and not as realistic as that given in FSNav..... I take over at about 500ft too.....Thanks again for the replies folks.Martin