Why won’t the autopilot engage in Microsoft Flight Simulator?

If autopilot will not engage in Microsoft Flight Simulator, check electrical and avionics power, stabilise and trim the aircraft, then verify the selected modes and navigation source. If it still refuses or disconnects immediately, look for control-axis movement, duplicate bindings, assistance features or aircraft-specific engagement limits.

These checks apply broadly to MSFS 2020 and MSFS 2024, although switch labels, mode logic and engagement limits differ between aircraft.

How do you use autopilot in MSFS?

To use autopilot in MSFS, establish stable flight, set the targets and navigation source, select the required flight-director modes, then engage AP and confirm the active modes on the flight display.

1. Confirm that the aircraft has an autopilot. Some vintage, bush and basic variants do not. Look for controls labelled AP, A/P, CMD, AP1 or AP2, together with modes such as HDG, NAV, ALT, VS or FLC.

2. Supply full electrical and avionics power. Depending on the aircraft, battery power alone may not energise every avionics bus. Bring the generator, alternator, external power or APU generator online as appropriate and check that the primary flight display and navigation equipment have completed initialisation. Resolve dark avionics screens and missing panel power before testing AP.

3. Hand-fly into a stable, trimmed condition. Level the wings, establish a safe airspeed and remove excessive pitch pressure. Follow the aircraft’s normal engagement limitations rather than asking AP to recover a stall, overspeed or steep attitude. If trim moves by itself or returns to centre, diagnose the trim input conflict before using autopilot.

4. Set the targets and navigation source. Move the heading bug before selecting HDG and set the desired altitude in the altitude selector. For NAV mode, choose GPS/FMS when following the programmed route or the appropriate radio source when tracking a VOR or localiser.

5. Select suitable lateral and vertical modes. HDG commands the heading bug; NAV follows a valid navigation path. To climb or descend, use VS or FLC as the aircraft permits. Pressing ALT normally holds or captures an altitude—it does not necessarily command a climb merely because a different altitude has been selected.

6. Engage with the cockpit AP button. This is more reliable for diagnosis than a generic keyboard or controller command, especially in add-on aircraft with custom systems.

7. Read the flight-mode annunciations. Confirm which modes are active and which are only armed. NAV may remain armed until the aircraft intercepts the route, while altitude capture may not occur until the selected altitude is approached. Colours and labels vary, so read the annunciations rather than relying only on illuminated buttons.

Autopilot does not automatically control engine power unless the aircraft also has autothrottle or autothrust. In FLC, the autopilot normally pitches for the selected speed while power determines climb or descent performance. In VS, it pitches for vertical rate, so an excessive climb rate can allow airspeed to decay.

What does the autopilot failure symptom mean?

The way the autopilot fails usually identifies whether the fault is power, engagement logic, control input or mode selection.

Why does autopilot engage and then disconnect straight away?

An immediate disconnect means the engagement command worked, but another input, protection or system condition cancelled it.

• Stick or yoke movement: a hand-held input, drifting axis or insufficient dead zone can fight the servo.
• Duplicate commands: another yoke, throttle, joystick, controller or keyboard may have Autopilot Disconnect or Toggle Autopilot assigned.
• Bad trim: a severely out-of-trim aircraft can exceed what the simulated autopilot will accept.
• Unsafe flight condition: stall warning, excessive angle of attack, overspeed or extreme attitude may inhibit or disconnect AP.
• Interrupted power: an incorrectly configured generator or avionics bus can drop the system after engine start.
• Assistance interference: AI piloting or assisted control features can issue commands that conflict with the cockpit system.

With the aeroplane stable, centre the controls, release them briefly and press the cockpit AP button while watching the mode annunciations. If AP now stays engaged, inspect every connected device. Our procedure for clearing duplicate MSFS controller bindings explains how to isolate and rebuild a faulty profile.

Why is autopilot on but not following the route or altitude?

An engaged AP that flies the wrong path is normally working; it has been given the wrong mode, source or target.

• NAV is armed rather than active. Intercept the route at a sensible angle or use HDG to bring the aircraft towards it.
• The CDI source is wrong. Use GPS/FMS for the programmed flight plan and the relevant radio source for VOR or localiser tracking.
• The flight plan has a discontinuity or missing leg. The autopilot cannot follow guidance the FMS is not generating.
• ALT is holding the present altitude. Select the new altitude, then command VS or FLC and verify that altitude capture is armed.
• APPR was selected too early or for the wrong signal. Approach mode is for capturing valid approach guidance, not ordinary en-route navigation.

Does the flight director need to be on?

Not always, because some aircraft switch the flight director on automatically when AP or a guidance mode is selected; other implementations expect FD to be enabled first.

Where an FD control is provided, the clearest workflow is to turn it on, set the heading or navigation source, select lateral and vertical modes, then engage AP. The decisive evidence is the flight-mode annunciator: it must show valid active guidance, not merely an illuminated FD switch.

A320 FBW: why won’t AP1 or AP2 engage?

In the FlyByWire A32NX—often searched for as the A320 FBW—AP1 or AP2 is commonly inhibited by engagement conditions, control input or incomplete guidance setup rather than a broken button.

• Wait until the aircraft is properly airborne. Normal A32NX logic does not permit autopilot engagement on the ground and requires at least five seconds after lift-off.
• Release the sidestick and centre the rudder. Large manual inputs, excessive attitude or active flight-envelope protection can prevent engagement or cause a disconnect.
• Use the virtual cockpit AP1 or AP2 button. Generic simulator bindings are not a reliable test of a custom Airbus implementation.
• Use one autopilot for normal flight. Dual AP engagement is associated with a qualifying ILS approach configuration, not ordinary climb or cruise.
• Test selected modes first. Choose a selected heading and a straightforward vertical mode. If those work but managed NAV does not, inspect the MCDU route and flight-mode annunciator.
• Do not treat the flight director switch as the whole diagnosis. It should normally be on for the expected Airbus workflow, but valid guidance, flight conditions and control position still determine whether AP remains engaged.

If the A320 hand-flies normally but will not follow managed navigation, correct the route and performance setup using our A320 MCDU and FMS programming steps for MSFS.

What if autopilot works in one aircraft but not another?

If AP works in a stock aircraft but fails in only one add-on, Microsoft Flight Simulator’s core autopilot and your basic controls are probably functioning.

Use the affected aircraft’s cockpit controls, check that its systems have finished initialising and verify that it is compatible with the installed simulator build. For a clean test, close MSFS, move unrelated packages out of the Community folder temporarily, then load a stock aircraft before restoring the suspect add-on by itself. This separates an aircraft-specific fault from a package conflict without permanently deleting anything.