Learn why a flight simulator autopilot engages but will not steer or hold altitude, and fix mode, trim, nav-source, power and controller issues.
An autopilot can indicate ENGAGED yet fail to steer or hold altitude because the AP master confirms that the system is connected; the intended lateral and vertical modes may still be inactive or merely armed. Check the flight-mode annunciator, then verify selected targets, navigation source, trim, aircraft systems and controller inputs.
What does autopilot engaged actually mean?
In Microsoft Flight Simulator, X-Plane, FSX, Prepar3D and most other flight simulators, engaging the autopilot does not automatically make it follow the flight plan, selected heading and chosen altitude. It connects the autopilot, but the selected aircraft must also have appropriate lateral and vertical modes active.
Some basic systems enter roll and pitch hold when engaged. Others retain the present attitude or use aircraft-specific default modes. The aircraft may therefore be controlling something, just not the route or altitude you expected. Our explanation of simulated autopilot servos and flight modes covers this distinction in more detail.
Do not confuse the flight director with the autopilot. Flight-director bars provide commands for the pilot to follow; they do not move the controls unless AP or CMD is genuinely engaged. A lit mode button can also mean selected or armed rather than active, so the flight-mode annunciator is a better guide than the switch position.
How do I fix an engaged autopilot that is not controlling?
- Stabilise and trim the aircraft. Hand-fly it to a normal attitude, speed and configuration before engaging the autopilot. A badly out-of-trim aircraft can exceed the simulated servos' authority even though the AP indication remains on.
- Confirm AP or CMD is engaged. Look for the aircraft's actual autopilot-status annunciation, not just FD, NAV or ALT button illumination. If the AP annunciation disappears, the system is disconnecting rather than remaining engaged without guidance.
- Select one lateral and one vertical mode. For a simple test, use heading mode with the heading bug near the present heading, then use altitude hold or another appropriate vertical mode. Setting a heading bug or altitude selector alone does not command the aircraft to follow it.
- Read the active mode annunciations. Modes such as ROL, PTCH, HDG, NAV, ALT, VS or FLC show what the system is actually commanding. Active and armed modes often use different colours, but the convention varies between aircraft. An armed ALT mode is waiting for altitude capture; it is not necessarily holding the present altitude.
- Check the navigation source. NAV and APP need valid guidance from the selected GPS/FMS, VOR or localiser source. Confirm that the correct CDI source is selected, the route has an active leg and the aircraft is positioned to intercept the course. Our guide to NAV and APP capture logic explains why an armed mode may not take control immediately.
- Remove conflicting control inputs. Centre the yoke or stick and check for duplicate pitch, roll and trim assignments across every connected controller. A noisy axis, held key, manual trim wheel or assistance feature can make the autopilot fight the controls, override its commands or disconnect. For MSFS and X-Plane, use our trim sensitivity and trim-axis conflict checks to isolate this problem.
- Verify aircraft systems and failures. The required electrical, avionics and, where modelled, hydraulic systems must be operating. Check for an autopilot failure, tripped circuit breaker or incomplete aircraft start-up, especially in complex add-ons.
- Perform a controlled reset. Disconnect the autopilot, return to normal simulation speed, trim the aircraft manually and cancel unwanted modes. Select a straightforward heading and vertical mode, then reconnect the autopilot and watch the annunciations rather than repeatedly pressing every mode button.
What does each autopilot symptom reveal?
The pattern of what works and what does not usually identifies the missing mode or conflicting input.
| Symptom | Likely cause |
|---|---|
| Flight-director bars move, but the aircraft does not | The flight director is on, but the autopilot servos are not engaged. |
| Heading works, but altitude does not | No vertical mode is active, ALT is only armed, or a trim input is fighting the system. |
| Altitude works, but the aircraft ignores the route | NAV has not captured, the wrong navigation source is selected, or the route has no valid active leg. |
| NAV is armed while HDG or ROL remains active | The autopilot is waiting to intercept valid course guidance. |
| The aircraft pitches up while losing speed | The autopilot is controlling pitch, but engine power is insufficient or autothrottle is not engaged. |
| The aircraft wanders or oscillates | Look for duplicate axes, poor calibration, trim conflicts, excessive simulation rate or conditions beyond the modelled autopilot's capability. |
Why does autopilot steer but not hold altitude or airspeed?
Lateral, vertical and throttle automation are separate functions, so success on one axis does not prove the others are configured correctly. HDG or NAV can steer the aircraft while no vertical mode is active, and an altitude preselector will not normally initiate a climb by itself.
Vertical-speed mode commands a climb or descent rate. FLC or IAS mode generally changes pitch to maintain speed, while ALT holds or captures altitude according to the aircraft's logic. Unless the aircraft has autothrottle, the pilot must still set suitable engine power; our guide to pitch-based speed modes and autothrottle explains why an engaged autopilot can still overspeed or stall.
When is the simulator or aircraft add-on likely at fault?
A configuration or aircraft-specific fault becomes likely when correct modes are shown as active, the aircraft is trimmed and within its normal operating envelope, all required systems are powered, and no controller input is overriding the autopilot.
Test the same controller profile with a default aircraft in a clean flight at normal simulation speed. If every aircraft has the problem, inspect global bindings, assistance options, external control software and failure settings. If only one add-on is affected, check its documented engagement procedure and required systems because complex aircraft often replace the simulator's standard autopilot logic with their own.