MSFS autopilot not working: why won’t it engage?

If Microsoft Flight Simulator autopilot will not engage, confirm electrical and avionics power, stabilise and trim the aircraft, select valid lateral and vertical modes, then use the cockpit AP button. If it still will not turn on, inspect the mode annunciator, navigation source, controller bindings, assistance settings and aircraft-specific engagement limits.

These checks apply to MSFS 2020 and MSFS 2024, but switch labels, mode logic and engagement limits differ between aircraft. An illuminated button alone does not prove that a mode is active: the flight-mode annunciator on the primary flight display is the final authority.

Aircraft-specific autopilot quick checks

Start with the row for your aircraft before changing simulator-wide settings.

How do you use autopilot in MSFS?

To use autopilot in Microsoft Flight Simulator, establish safe flight, set the targets and navigation source, select appropriate guidance modes, engage AP from the cockpit and verify the active modes on the flight display.

1. Confirm that the aircraft has an autopilot. Some basic, vintage and bush variants do not. Look for controls labelled AP, A/P, CMD, AP1 or AP2, with modes such as HDG, NAV, ALT, VS or FLC.
2. Supply full electrical and avionics power. Battery power alone may not energise every avionics or autopilot bus. Bring the alternator, generator, external power or APU generator online as appropriate and let the displays and navigation equipment initialise.
3. Hand-fly into a stable, trimmed condition. Level the wings, establish a safe airspeed and remove sustained control pressure. Autopilot is not intended to recover a stall, overspeed, extreme attitude or badly out-of-trim aircraft.
4. Set the targets and navigation source. Position the heading bug before selecting HDG and set the required altitude. For NAV, use GPS/FMS for a programmed route or the appropriate radio source for a VOR or localiser.
5. Select lateral and vertical modes. HDG follows the heading bug; NAV follows valid navigation guidance. Use VS, FLC or the aircraft’s managed climb or descent modes as appropriate. Selecting a new altitude alone does not necessarily command the aircraft to climb or descend.
6. Engage with the cockpit AP button. This provides a cleaner test than a generic keyboard or controller command, especially in aircraft with custom systems.
7. Read the annunciations. Confirm which modes are active and which are merely armed. NAV may remain armed until the route is intercepted, while altitude capture normally arms before becoming active near the selected altitude.

Autopilot does not control engine power unless the aircraft also has autothrottle or autothrust. In FLC, pitch normally controls speed while available power determines climb or descent performance. In VS, an excessive climb rate can let airspeed decay even though the autopilot is following the selected vertical speed.

Airliner users can follow our more detailed workflow for setting flight directors, FMS guidance and airliner autopilot modes.

Why can’t I activate the autopilot?

If the autopilot will not turn on, its exact failure behaviour usually reveals whether the cause is power, engagement logic, control input or incorrect mode selection.

Cessna 172: autopilot will not engage

A Cessna 172 autopilot will not engage if the fitted panel lacks autopilot power, the aeroplane is unstable or the G1000/GNS navigation source and modes are not configured correctly.

First identify the variant. A G1000 display does not guarantee that every C172 variant uses identical autopilot hardware, while a GNS navigator may feed a separate autopilot controller. Some basic C172 variants have no autopilot at all.

1. Confirm electrical and avionics power. Check the battery, alternator and avionics master or buses appropriate to the aircraft. On a GNS-equipped panel, a powered navigator does not by itself prove that the separate autopilot controller has power.
2. Establish stable airborne flight. Use a safe airspeed, level the wings and trim until little control force is required. Do not diagnose AP while parked or while demanding recovery from a steep or badly trimmed condition.
3. Set an uncomplicated test. Move the heading bug to the present heading and select a sensible altitude. Begin with heading and altitude-related guidance rather than attempting a difficult NAV capture.
4. Use the panel AP control. Press the dedicated autopilot button on the fitted controller instead of a generic simulator shortcut.
5. Verify the annunciator. Confirm that AP is shown and check both the lateral mode, such as ROL, HDG or NAV, and the vertical mode, such as PIT, ALT, VS or FLC. Exact labels depend on the fitted system.

For route tracking, a G1000-equipped aircraft must have the intended GPS or radio source selected on the PFD. With a GNS installation, check the GPS/VLOC source and the separate autopilot mode. If HDG works but NAV does not, the servos are functioning; concentrate on the navigation source, active leg and intercept geometry.

Fenix A320: why AP1/AP2 will not engage

The Fenix A320 is a distinct aircraft simulation, so diagnose it through its own cockpit logic rather than applying A32NX-specific timing or assumptions.

• Test the virtual-cockpit buttons. Press AP1 or AP2 on the FCU. If a keyboard or controller command fails but the cockpit button works, the problem is the simulator binding rather than the Fenix autopilot.
• Confirm normal airborne engagement conditions. Complete the take-off, establish a safe attitude and airspeed, and avoid trying to engage during an abnormal flight condition or active protection response.
• Centre the controls. Release the sidestick, centre the rudder pedals and check for noisy or drifting axes. Persistent manual input can inhibit engagement or cause an immediate disconnect.
• Check the flight directors and FMA. The FMA should show valid lateral and vertical guidance. Test a selected heading and a straightforward vertical mode before blaming managed navigation.
• Use one autopilot in normal flight. AP2 is not simply a spare button to press when AP1 refuses. Dual-autopilot operation is associated with the appropriate approach configuration; a common engagement problem can prevent both channels.
• Isolate conflicting bindings. Look for duplicate assignments to autopilot toggle, disconnect, sidestick, elevator, aileron and trim commands. Test with unnecessary controllers disconnected or a clean control profile.

If selected heading and vertical guidance work but managed flight does not, inspect the MCDU route, active leg and FMA. Do not apply the A32NX five-second engagement rule to the Fenix as if both products used the same simulation logic.

How do you use autopilot in the A320neo and A32NX?

In the A320neo workflow, prepare the route and targets, enable the flight directors, hand-fly the take-off, engage AP1 under valid airborne conditions and verify every selected or managed mode on the FMA.

For the FlyByWire A32NX, normal logic prevents engagement on the ground and requires at least five seconds after lift-off. Release the sidestick, centre the rudder, press the virtual AP1 button and use one autopilot for ordinary climb and cruise. AP1 and AP2 together are intended for a qualifying approach configuration, not routine en-route flight.

If AP1 engages in selected heading but the aircraft will not follow the flight plan, the likely fault is the MCDU route, an active discontinuity or managed NAV not becoming active. Our A320 autopilot and autothrust checks cover FCU modes, sidestick input and managed guidance in more depth.

MSFS 2024 A330 autopilot not working

When the MSFS 2024 A330 autopilot is not working, use the A330’s own FCU controls, confirm the FMS route and read the FMA to distinguish a failed engagement from the wrong guidance mode.

1. Test AP1 from the cockpit. Establish normal airborne flight, centre the controls and press the virtual AP1 button. A generic simulator command is not a reliable diagnostic for a cockpit with aircraft-specific logic.
2. Confirm the route inside the FMS. The route drawn on the simulator map is not proof that the cockpit FMS has a valid active leg. Remove unintended discontinuities and check that the next waypoint is sensible.
3. Read the FMA. Verify AP engagement plus active lateral and vertical modes. An armed mode is waiting for capture and is not yet controlling the aircraft.
4. Distinguish selected from managed guidance. Selected heading, track or vertical speed follows FCU values chosen by the pilot. Managed navigation and climb or descent rely on valid FMS guidance. Use the FCU push or pull action required by the cockpit, then confirm the resulting FMA rather than assuming the mouse input registered.
5. Try a simple selected-mode test. If the A330 follows selected heading and vertical speed but not managed NAV, the autopilot is operating; troubleshoot the FMS route, active leg and managed-mode selection.
6. Check bindings and packages. If the cockpit button still fails, isolate duplicate disconnect or axis assignments. On PC, temporarily remove unrelated packages from the Community folder; on console, disable optional add-ons through the available package controls and retest the unmodified aircraft.

MSFS 2024 autopilot not following flight plan: what should I check?

An autopilot that holds heading or altitude but does not follow the flight plan is usually engaged correctly and receiving the wrong navigation source, route leg or lateral mode.

1. Confirm the cockpit flight plan. Check that the FMS or GPS contains the intended route, the correct leg is active and no discontinuity blocks sequencing.
2. Select the correct source where applicable. Use FMS or GPS for the programmed route. Select NAV1, NAV2 or VLOC only when tracking the corresponding radio aid or localiser.
3. Approach the route in HDG mode. Use the heading bug to create a sensible intercept rather than expecting NAV to recover from a distant, parallel or badly angled position.
4. Arm NAV and watch the annunciator. NAV armed is not NAV active. The aeroplane remains under the existing lateral mode until valid guidance is captured and NAV moves into the active field.
5. Check the next commanded leg. If NAV becomes active but turns the wrong way, inspect a stale direct-to, an unexpected procedure leg or the wrong active waypoint.

A mistake we see constantly is treating the magenta map line as proof that the aircraft is following FMS guidance. The PFD’s flight-mode annunciator and the FMS active-leg page are the useful evidence.

Why does autopilot hold heading but ignore the selected altitude?

Selecting an altitude usually sets a target; it does not always initiate a climb or descent. Choose VS, FLC, selected climb or the aircraft’s managed vertical mode, apply suitable power and confirm that altitude capture is armed.

If using VS, monitor airspeed because the autopilot will prioritise the commanded vertical rate. If using FLC, set appropriate power because pitch controls speed while thrust determines whether the aircraft can climb or descend as intended.

Why does autopilot engage and disconnect straight away?

An immediate disconnect means that the engagement command reached the aircraft, but another control input, protection or system condition cancelled it.

• Noisy controls: a drifting yoke, joystick, sidestick or rudder axis can fight the servos.
• Duplicate commands: another device may have Autopilot Disconnect or Toggle Autopilot assigned, sometimes to a held or bouncing button.
• Bad trim: severe out-of-trim forces can exceed what the simulated system accepts.
• Unsafe flight condition: stall warning, overspeed, excessive angle of attack or extreme attitude may inhibit or disconnect AP.
• Interrupted power: an incorrectly configured generator, alternator or avionics bus can drop the system after engine start.
• Assistance interference: AI piloting and assisted-control features may issue commands that conflict with the cockpit system.

Stabilise the aeroplane, centre and release the controls briefly, then engage AP with its cockpit button while watching the annunciator. If it now remains engaged, follow our autopilot-disconnection diagnosis for trim, axes and duplicate bindings.

Does the flight director need to be on?

The flight director should normally be enabled before autopilot engagement where the aircraft provides an FD control, although some systems switch it on automatically when AP or a guidance mode is selected.

The decisive evidence is not the FD switch light but the FMA. It must show valid active lateral and vertical guidance. Flight-director bars can also be displayed while hand-flying, so their presence does not mean that the autopilot servos are engaged.

What should I do if it is still not working?

If autopilot is still not working after the cockpit checks, run a controlled test that separates an aircraft fault from a simulator setting, controller problem or package conflict.

1. Load a stock aircraft with a known autopilot. Use clear weather, a safe altitude and a simple HDG plus ALT or VS test.
2. Use only cockpit controls. Avoid keyboard and controller autopilot commands during the first test.
3. Disconnect unnecessary hardware. If AP now works, reconnect devices one at a time and inspect their axes and autopilot assignments.
4. Try a clean control profile. Check especially for duplicate toggle, disconnect, trim, elevator and aileron inputs.
5. Disable piloting assistance. Retest without AI control or assisted handling features issuing competing commands.
6. Isolate add-ons. On PC, move unrelated packages out of the Community folder temporarily. On console, disable optional packages where the simulator permits it. Restore add-ons individually after the clean test.

If every aircraft fails, concentrate on controls, assistance settings, power-up procedure and simulator configuration. If only one aircraft fails, its setup, compatibility or custom logic is the more likely cause. If HDG works but NAV does not, stop troubleshooting the AP servos and inspect the route, source and active mode instead.

For a broader platform-level sequence, use our MSFS 2024 checks for bindings, navigation sources and add-on isolation.