Since switching to FS9 I have noted some problems with the autopilot, mostly it involves the ALT HOLD turning off when the ILS is first intercepted - most times I can just turn it back on and everything os fine. However in isolated cases the autopilot will never pick up the G/S or the aircraft will want to 'dive' unless I turn off the autopilot and 'hand land'. I am wondering if others have the same problem and/or if it is simply a airport based problem like 2002 had some airports that had messed up ILS runways or a model problem with certain aircraft. Of course if someone figured it out and has a solution that would be great. I know how to edit the aircraft.cfg to make sure the radio has a glideslope and all that and also know that G/S will not work if the aircraft is left in GPS mode so those things are not the problem. I also have a file to make the md_83 flyable but it is one of the aircraft that will simply dive into the ground if the autopilot is used anytime after initial decent?? Any help or suggestion here would be appreciated.On another note I am ready for initial beta testing of some of my version 9 purple/black panels and was wondering how I would go about finding a few beta testers to help me in making the panel package as small as possible by working with me to not only fine tune any problems but mostly to find out what sounds and such need to be included with the file by 'trail and error' ( meaning I will send what I KNOW goes with the panel and will need someone to tell me what is missing ect so I do not have to include my entire sound folder or gauges that are not being used from nested folders (seems panel studio is not that good at figuring out which gauges are used in nested folders so I have had to include the entire folder in the past...

I have had the exact same thing happen to me. I also wonder if it is just at some airports. I have not seen much wrote about it. I thought maybe it was just me. keith

>I have had the exact same thing happen to me. I also wonder>if it is just at some airports. I have not seen much wrote>about it. I thought maybe it was just me.> keithI have the same problem, I saw a post where someone mentioned that the AutoPilot was a little buggy.I also have been experiencing the same problem with the FSD Seneca V using the new service pack for FS2002 when I intercept the localizer. and have the Altitude locked on the approach will not activate and I have to manually disengage the Alt. Lock for Approach to intercept GS and Localizer in both FS2002 & FS.2004.Kenny G.

Since making that initial post I have noticed this: At some airports FS9 appears to be giving its last set of instructions at some distance from the airport, occasionally so far away that you will not catch the ILS at all, but far more often you will catch the ILS before the G/S has become active. This appears to cause the ALT hold to disengage anyway, allowing uncontrolled decent. What I now do is monitor the approach distance and angle to intercept (I am no pilot so these may not be the proper terms) along with a gauge that will indicate that a G/S is active (many gauges including the collins eadi here on avsim will show the G/S) - additionally if you have a bit of knowledge of XML and panel.cfg you can add a 'indicator' to your panel by using code something like this:%((A:NAV1 GLIDE SLOPE, number) 0 > (A:TRAILING EDGE FLAPS0 RIGHT ANGLE, degree) 10 > && )%{if}%((A:RADIO HEIGHT, feet) 3000 < (A:RADIO HEIGHT, feet) 25 > && )%{case}%{:1}ILS G/S%{end}%((A:NAV1 HAS GLIDE SLOPE, number) -0.5 > (A:RADIO HEIGHT, feet) 50 > && )%{if}%((A:TRAILING EDGE FLAPS0 RIGHT ANGLE, degree) 17 > (A:Design Speed VS1, knots) 37 + < && )%{case}%{:1}G/S NA%{end}(Not 100% sure you can just paste this as word wrap is on and that may mess the gauge up, but if you know xml the parameters you use are there)...Back to solving the problem, now that you can monitor that G/S simply make any minor adjustments needed in your flight path to stay in a position to intercept or sort of make a 'sawtooth' approach along the ILS until you are sure the G/S is active before you engage the APPR mode (normally if you are farther than say 20nm from the airport you are not ready to turn on APPR and must verify these things before just assuming ATC has you ready to land...I have also noticed that some aircraft models just have messed up autopilots and are not going to work but this should at least help you out some - also be aware that you can only catch the G/S from below (you cannot really dive into it) so if you noticed you missed it you can either do a manual pattern or 'go around' using ATC but trying to position correctly late in your approach won't generally work...

I've had this happening in FS9 since installing FSNavigator 4.6. Sometihng in the `fly to here` command within FSNav is screwing up the ILS in FS9 - I get the exact same problem with the ILS and Alt Hold unless I switch each and every a/p function off, then re-engage. This means autopilot nd aitothrottle in the case of the big birds.If ou don't actually use Fly To Here from the FSNav map, it's no problem. Normal flight plans fly fine.Allcott

You may want to look at a manual for the king autopilot which I believe is what fs models. Although I have never used a king personally-at least my make of autopilot-you would turn off the alt button and choose app-not alt- when starting the approach. On my autopilot you also have to be pretty closely established before using it to follow the approach-it looks like the king does also.I didn't have time to find the particular model right now-but here is a king autopilot manual-there are several others on this site-it appears that this model works in a similar fashion.:http://www.bendixking.com/static/bk_club/p...8035-0000_0.pdfRead the following section on app mode vs. alt....http://forums.avsim.net/user_files/48800.jpg

Hi Digtek, I posted a similar question a while back on these boards, and no-one seemed able to give a definitive answer...judging by your experiences and those of your respondants, it would appear that there IS a problem in the ATC/ILS system, that manifests itself at certain airports, and maybe with certain aircraft. I'm not sure which is the culprit...I lean more towards airports, as ILS behaviour is erratic. For instance, Charles DeGaule, Paris, and London Heathrow will both frequently send me miles off course and tell me to fly straight in....you have no chance of getting established on the localiser and the Nav1 radio has only just started picking up a signal from the ILS marker....a quick check on the map screen shows that I'm aprox 30 miles out and flying at a severe angle straight past the chosen airport. If I restart the flight, after a couple of extra attempts, I might actualy get guided corectly, and I have noticed that some aircraft seem to respond better....some of the default Boeings just won't, whereas the Project Airbus A320 will be spot-on....Paris will even break-off ILS for no reason whatsoever at times...you follow their instructions to the letter, and suddenly you are told that ILS is cancelled....#####????!!!!It's terribly frustrating when it happens, but I guess we should expect a few 'oddities' when dealing with this sort of programme that tries to cover so much - proper beta testing not always being one of Microsofts' strongest points...!!!