Find why a flight simulator autopilot keeps disconnecting, with practical fixes for noisy controls, trim, mode errors, power loss and add-ons.
An autopilot in a flight simulator usually disconnects because it detects pilot control input, excessive trim or an unsafe flight condition, loses electrical or hydraulic power, or receives a mapped disconnect command. It may also remain engaged but appear to fail because the selected lateral or vertical mode is wrong.
Is the autopilot really disconnecting?
A true disconnect removes the AP annunciation and usually produces a warning tone, message or flashing light. If AP remains displayed while NAV changes to HDG or ROL, or ALT changes to VS or PIT, the autopilot is still operating but has reverted to another mode.
Read the flight-mode annunciator or autopilot status display rather than judging from the aircraft's movement. Flight-director bars also do not prove that the autopilot servos are engaged; they provide guidance commands that can remain visible during manual flight. Our guide to selecting and checking basic autopilot modes explains these distinctions.
Common causes of repeated autopilot disconnects
Most repeated disconnects can be narrowed down from when they happen.
| Symptom | Likely cause | What to check |
|---|---|---|
| Disconnects immediately after engagement | Control pressure, an off-centre axis, poor trim, excessive bank or pitch, or unmet engagement conditions | Stabilise and trim manually with AP off, release the controls and check the aircraft's engagement requirements |
| Disconnects at random | Noisy controller axis, duplicate button assignment, USB interruption, assistance input or a power interruption | Test one controller at a time, inspect bindings and disable automated control assistance while diagnosing |
| Disconnects when trim or the yoke is moved | Normal manual-override behaviour | Do not apply manual trim or sustained control input while AP is engaged unless that aircraft permits it |
| AP stays displayed but the aircraft turns away | Wrong active mode, navigation source, route leg or flight-plan discontinuity | Check the annunciated mode, CDI source and active flight-plan leg |
| Altitude begins oscillating | Low airspeed, excessive vertical demand, poor loading, trim limits or turbulence | Disconnect, recover stable flight, reduce the climb or descent demand and re-engage only when balanced |
| Only one add-on aircraft is affected | Aircraft-specific logic, a saved panel state, controller conflict or add-on compatibility problem | Compare it with a stock aircraft in a fresh flight using a clean control profile |
How do I stop the autopilot disconnecting?
The quickest fix is to separate an aircraft-state problem from a controller or navigation-mode problem.
- Record the exact indication. Note the warning, chime and active flight modes at the moment of failure. Do not assume every unexpected turn or descent is a disconnect.
- Disconnect and stabilise manually. Establish a safe airspeed, moderate attitude and sensible bank angle. Trim the aircraft with AP off; repeatedly engaging it during an oscillation usually makes diagnosis harder.
- Test simple hold modes. In straight-and-level flight, try a basic heading or wings-level mode and altitude hold. If these work, the servos are probably functioning and the fault is more likely in NAV, APP, the navigation source or capture conditions.
- Remove unintended control input. Take your hands off the controls and inspect the simulator's input indicators. Unplug controllers one at a time; if the problem stops, recalibrate the affected device and add only enough dead zone to remove genuine axis flicker.
- Audit every binding. Keep one assignment for each pitch and roll axis. Search all connected keyboards, gamepads, throttles and flight controls for autopilot master, autopilot disconnect, pitch trim and roll trim commands, then clear duplicates.
- Check the aircraft systems. Confirm that the required electrical, avionics, trim and, where modelled, hydraulic systems are powered. Disable random failures during testing and make sure the aircraft is inside its permitted autopilot envelope.
- Run a clean comparison flight. Use a stock aircraft, calm weather, a fresh cockpit state and no AI or co-pilot control. Reintroduce add-ons, weather and controller profiles individually until the fault returns.
Microsoft Flight Simulator has several additional causes, including assistance features, duplicated controller profiles and aircraft-specific engagement logic. Use our MSFS autopilot engagement and disconnect checklist when the problem occurs there.
Why does autopilot fail only on approach or altitude capture?
Approach and altitude-capture problems are usually capture or energy-management errors rather than random autopilot failures.
- Wrong navigation source: the aircraft may be following GPS when the intended approach requires a radio navigation source, or vice versa.
- Unsuitable intercept: a localiser or vertical path may not capture from an excessive angle, from above the path or before the correct approach mode is armed.
- Flight-plan discontinuity: NAV mode cannot follow a missing or inactive route leg.
- Excessive vertical demand: a large selected climb or descent rate at low airspeed can lead to trim saturation, altitude overshoot or a stall.
- Late configuration changes: deploying flaps or landing gear abruptly changes drag and pitch requirements, sometimes exceeding what a basic autopilot can correct comfortably.
If the aircraft repeatedly climbs and descends around the selected altitude, follow our focused steps for correcting autopilot altitude oscillation and trim problems. There is no universal autopilot disconnect height: some aircraft support coupled approaches or autoland, while others require manual disconnection according to their operating limitations.
Aircraft-specific autopilot logic and add-ons
Autopilot engagement rules and override thresholds belong to the aircraft, not to the simulator as a whole.
A light general-aviation aircraft may have only basic roll, heading and altitude functions, with no autothrottle. An airliner may require valid flight-management data, functioning sensors and the correct mode-control selections. Helicopter stability augmentation can also be mistaken for a full route-following autopilot.
Airbus logic deserves particular care because autopilot and autothrust are separate systems, and sidestick input, flight-mode selections or controller conflicts can affect them differently. Our A320 autopilot and autothrust troubleshooting guide covers those cases.
Complex add-ons may use custom autopilot code and may not respond exactly like the simulator's default aircraft. If a stock aircraft works in the same flight but the add-on does not, use the add-on's cockpit controls, reset its saved state and test with a clean controller profile before changing the simulator globally.