Anyone else getting random disconnects of the autopilot? IS this being worked on?Also, is somebody working on the new Airtran paint job of t heir frsh 737-700s, they look pretty sweet.

Sir- If you do not sign your name according to the rules of this forum it is unlikely anyone will answer your questions, thank you. There is nothing wrong with the Autopilot disconnecting, what I believe (and no disrepect intended) needs to be worked on is your knowledge of the AFDS systems on this aircraft. If you touch the controls at anytime while the AP is engaged the AFDS will revert to active CWS modes depending. If you are not doing a number of other things correctly like not setting the MCP altitude to your crz altitude etc etc. So, tell us exactly what YOU are doing the moment the AP disconnects and then we can be 100% in an answer for you. Best Wishes,[h4]Randy J. Smith[/h4][h3]P M D G's 747-400[/h3][h4]coming to a runway near you[/h4][/font color]Caution! Not a real pilot, but do play one on TV ;-)AMD 64 3200+ | ASUS KV8 DELUXE | GFORCE 5700 ULTRA @535/1000 | Maxtor 6Y080M0 SATA 80 GIG | 512 DDR 400 | Windows Xp Pro | Windows Xp Pro 64 |

Can I follow with a few questions on this topic as I too have seen autopilot discos.Without touching the controls.On a short flight, say a approach test, climbing out to a waypoint, then turning in for the procedure, the FMC will not engage at all in VNAV hold. It always says, Unable CRZ ALT. The MCP was set to 10,000ft and so was the FMC crz alt. I was at 8,000ft about 20 miles from the waypoint.On long flights I have seen both VNAV and LNAV just disco randomly. No error, nothing. Clicking both again and they come work again, no errors.END OF ROUTE, when there are waypoints for missed approach left to fly.NO ACTIVE ROUTE, when there are more waypoints and one is set current and active.VNAV DISCONNECT, repeatedly, with no error to say why.No ability to add more waypoints or alternative to the FMC after you have touched tarmac once. This happened to me landing when I couldn't see the runway, autoland got it down to 100ft and I still couldn't see the runway, so, I thought I would simulate a missed approach and divert to alternate. The FMC would not allow me to do this. It constantly said, "END OF ROUTE", when I flew around in circles for a while and attempted to reprogramme it, I added the new destination, new waypoints to get to it, new arrivals and procedures / transtions and set the first one active, it said, "NO ACTIVE ROUTE". The course remained Blue. I even climbed to 10,00ft and reboot the plane. All power off, engines, gens APUs battery and restarted, no joy.I have also seen it say, "UNABLE NEXT ALT" when the next ALT is 8,000ft say, the MCP alt is set to 8,000ft and there is plenty of time to descend. To correct this I have to set the MCP alt "below" the FMC alt. (Before you say, "Did you set your altimeter to the ATC settings?" the answer is NO, the transition ALT was 6,000ft for the airport.In all to sum up, if you fly the plan perfectly all is well with the FMC, if you need to deviate a little or extend your route, it's fiddly and impossible to control the thing, it just ignores you.

Not to sound rude or anything, but are you sure you filled everything out right in the FMC? I've never had either one of those happen to me.Nick B.Continental Airlines 737NG Pilothttp://www.precisionmanuals.com/images/forum/800driver.jpg--AMD Athlon XP 3200+ @ 2.2 Ghz (Equal to 2.8 ghz)400W Power supply3x 80 mm Case FansSoyo VIA KT600 Dragon PlusnVidia GeForce FX 5200 128 mb2 x 512 PC400100 GB Western DigitalMicrosoft Sidewinder Precision 2

Check you controls sensitivity. I should think a control spike would be sufficient to lead to disengagin autopilot. Even though I have a spikey joystick however I have never had any prolems with the AP unless I really gave the controller a good touch.Cheers,Terence

I will not get into every item you mention here but would like to comment on a few things,First, VNAV never just disconnects WITHOUT giving a FMC scratchpad message.Second, UNABLE NEXT ALT is programmed exactly like the real deal which ONLY happens when"Due to an undershoot on climb or an overshoot on descent, the next descent constraint cannot be achieved."If one programs the FMC with a wpt that exceeds 7 degress above 10000' you will get VNAV DISCONIf one programs the FMC with a wpt that exceeds 6 degrees below 10000' you will get a VNAV DISCON."On a short flight, say a approach test, climbing out to a waypoint, then turning in for the procedure, the FMC will not engage at all in VNAV hold. It always says, Unable CRZ ALT. The MCP was set to 10,000ft and so was the FMC crz alt. I was at 8,000ft about 20 miles from the waypoint." How can one be in a climb on final? What do you expect the FMC do do here? Are you trying a VNAV APP and landing? I think you need to give detailed information that helps us to understand, things like your route, altitude what exactly you were trying to do etc for us to judge correctly here."On long flights I have seen both VNAV and LNAV just disco randomly. No error, nothing. Clicking both again and they come work again, no errors." How do you expect us to know if you just make more general statements like this? You were doing something, you were flying right? What altitude? What route? What aircraft? Any weather? What modes etc I can think of many things to give us information in this very situation. VNAV and LNAV don't just disconnect without a reason. Always look at the cdu's scratchpad OR your Pilot's Flight Display for information on MODE REVERSIONS. Trust me it will be there. If you seriously believe there are issues in these areas then be serious in your posts otherwise there is no way to test what you say. Best Wishes,[h4]Randy J. Smith[/h4][h3]P M D G's 747-400[/h3][h4]coming to a runway near you[/h4][/font color]Caution! Not a real pilot, but do play one on TV ;-)AMD 64 3200+ | ASUS KV8 DELUXE | GFORCE 5700 ULTRA @535/1000 | Maxtor 6Y080M0 SATA 80 GIG | 512 DDR 400 | Windows Xp Pro | Windows Xp Pro 64 |

Ok Randy, thank you for your response. I will say that I am very familiar with the AFDS on the 737Ng as I am an actual airline pilot but do not play one one TV, and I am sure that the AP disconnect is not user error as I get no CWS P or CWS R indication when it happens. It just randomly disconnects with no other indication.Peter Gee

You fly a 737 NG Peter? What, when, where does it disconnect for you Peter and lets see if we can do a test setup.What version of FS are you runningWhat version of windows are you runningwhat version of the NG are you flyingwhat is your route, any weather? I will say that while not being an actual pilot, I am an actually tester of this aircraft since day one and I do know all about it and certainly know this AFDS and how it works ;-)Best Wishes,[h4]Randy J. Smith[/h4][h3]P M D G's 747-400[/h3][h4]coming to a runway near you[/h4][/font color]Caution! Not a real pilot, but do play one on TV ;-)AMD 64 3200+ | ASUS KV8 DELUXE | GFORCE 5700 ULTRA @535/1000 | Maxtor 6Y080M0 SATA 80 GIG | 512 DDR 400 | Windows Xp Pro | Windows Xp Pro 64 |

One other note, not sure if this is your guys' issue but I had an issue with the AP when my forcefeedback was enabled, so turning this feature off at least helped me in one area of AP disconnect..Best Wishes,[h4]Randy J. Smith[/h4][h3]P M D G's 747-400[/h3][h4]coming to a runway near you[/h4][/font color]Caution! Not a real pilot, but do play one on TV ;-)AMD 64 3200+ | ASUS KV8 DELUXE | GFORCE 5700 ULTRA @535/1000 | Maxtor 6Y080M0 SATA 80 GIG | 512 DDR 400 | Windows Xp Pro | Windows Xp Pro 64 |