Why won’t the autopilot engage in Microsoft Flight Simulator?
If autopilot will not engage in Microsoft Flight Simulator, the usual cause is not a sim bug but a condition the aircraft is refusing: no avionics power, the wrong flight mode setup, being too low or too fast, continuous control input from hardware, or a binding that instantly disconnects it again. The fix is to check power, trim, mode logic and controller assignments in that order.
Why autopilot will not engage in Microsoft Flight Simulator
Autopilot in MSFS is aircraft-specific. The button may be labelled AP, A/P, CMD or similar, but the logic behind it is not the same in every aeroplane. A Cessna with a simple autopilot does not behave like an Airbus, and a third-party add-on often uses its own custom systems.
In practice, we see the same handful of causes over and over:
- No electrical or avionics power to the autopilot and flight instruments.
- The aircraft is outside engagement limits, such as too low after take-off, too steeply banked, badly out of trim, too slow or too fast.
- The flight director or source setup is wrong for that aircraft.
- A controller binding is fighting the autopilot or sending a constant disconnect command.
- You are holding the yoke or stick off-centre, or a noisy axis is doing it for you.
- A custom add-on aircraft has its own procedures and will ignore the generic button until those are met.
How do we fix autopilot that will not engage?
Confirm the aircraft actually has a usable autopilot. Not every aircraft is fitted with one, and some vintage or bush aircraft either do not have autopilot at all or simulate failures and inoperative equipment. If you are unsure, look for an autopilot panel, mode buttons such as HDG, NAV, ALT, or an FMA annunciation on the primary flight display.
Check electrical and avionics power. Battery alone is not always enough for long, and some systems need the alternator or generator online. Make sure the avionics master is on where applicable, the main screens are powered, and any necessary alignment or initialisation has completed in more complex aircraft.
Get the aeroplane stable first. Most autopilots will not engage happily if you are hand-flying at an extreme pitch angle, in a steep turn, close to a stall, overspeeding, or badly out of trim. Level the wings, set a sensible climb or cruise attitude, trim the aircraft, and then try again.
Wait until you are high enough after take-off. Many aircraft inhibit autopilot engagement on the ground and during the first part of the climb. We recommend hand-flying until safely airborne and settled, then engaging it once the aircraft is clean, trimmed and within normal flight parameters.
Set the basic modes before pressing AP. In many GA aircraft, turning on FD first and selecting HDG, NAV or VS/FLC gives the autopilot something valid to follow. In airliners, make sure the flight directors are on and the aircraft has a sensible lateral and vertical mode available rather than an empty or conflicting setup.
Release manual pressure on the controls. If you are holding the stick, yoke or rudder pedals with force, the sim may interpret that as a disconnect condition or immediately overpower the servos. Centre the controls and briefly take your hands off after pressing the autopilot button.
Check for duplicate or bad controller bindings. This is one of the biggest hidden causes. A yoke, joystick, throttle quadrant or gamepad may have Autopilot Disconnect, Toggle Autopilot, trim commands or even pitch/roll axes assigned in a way that constantly cancels the autopilot. Review every connected device, not just the one you think you are using.
Try the cockpit switch instead of a keyboard shortcut. Some add-on aircraft do not always respond correctly to generic control assignments. Clicking the actual autopilot button or using the aircraft's own EFB or systems panel can rule out an input-mapping issue.
Test in a default aircraft. If autopilot works in a stock Cessna or airliner but not in one specific add-on, the problem is likely aircraft-specific rather than a global MSFS fault. That narrows the troubleshooting quickly.
Temporarily remove conflicts from your setup. If you use mods, utilities or older aircraft packages, test with a clean configuration. A conflicting add-on in the Community folder, outdated avionics package or external hardware profile can interfere with autopilot behaviour.
Does autopilot need the flight director to be on?
Sometimes yes, sometimes no. In many Garmin-equipped GA aircraft and most airliners, the flight director should be on because the autopilot follows the flight director commands. In simpler legacy GA systems, autopilot may engage without a visible flight director, but it still needs valid pitch and roll logic.
If in doubt, we suggest this sequence:
Set heading or navigation source.
Turn on the flight director if the aircraft has one.
Select a lateral mode such as HDG or NAV.
Select a vertical mode such as ALT, VS or FLC if appropriate.
Press AP.
That order works far more reliably than pressing AP first and hoping the aircraft decides what to do.
Why does the autopilot engage and then disconnect straight away?
If the autopilot lights up and then drops out immediately, we usually look at control conflict or aircraft state rather than the autopilot button itself.
- Continuous yoke or stick input from your hand or a drifting axis.
- Trim badly out of range, creating too much servo force.
- A mapped disconnect button on a throttle, yoke or joystick firing by mistake.
- Unstable airspeed, near-stall or overspeed protection.
- Mode conflict, such as arming one source while another source is selected.
- Electrical interruption, especially after engine start or configuration changes.
A good test is to pause, centre all hardware controls, confirm trim is reasonable, and engage AP using the on-screen cockpit button.
Common aircraft-specific autopilot gotchas in MSFS
| Aircraft type | What usually stops AP engaging | What to check |
|---|---|---|
| Garmin-equipped GA aircraft | Flight director off, no active mode, unstable hand-flying | Power, FD, HDG/NAV selection, trim and airspeed |
| Steam-gauge GA aircraft | Old-style autopilot logic, no valid heading/nav source, poor trim | Avionics master, heading bug, NAV source, wings level |
| Airbus and Boeing | Take-off inhibition, incomplete setup, invalid mode state | Flight directors, navigation setup, safe altitude, stable climb |
| Third-party complex add-ons | Custom systems ignore generic bindings | Use cockpit controls and follow the aircraft's normal procedure |
What if autopilot works in one aircraft but not another?
That usually means the issue is not your sim installation. It is either:
- Different autopilot logic in that aircraft.
- A missing setup step unique to that cockpit.
- An outdated add-on after a sim update.
- A control profile conflict exposed by that aircraft's systems.
We would first test the aircraft with no external hardware profile changes, then with the cockpit button, then with add-ons temporarily disabled. If the problem only exists in one add-on aircraft, that is the most useful clue you can get.
Quick checklist: autopilot will not engage
- Avionics powered
- Aircraft airborne and stable
- Not too slow, too fast, or badly out of trim
- Flight director on if required
- Heading, NAV or vertical mode selected
- No pressure on yoke or stick
- No duplicate AP disconnect or trim bindings
- Tested with the cockpit button
- Tested in a default aircraft
- Tested without conflicting mods
If nothing fixes it
If autopilot still will not engage after the checks above, the most likely causes are a corrupted control profile, a conflicting mod, or an aircraft-specific issue introduced by a sim update. At that point we would clear or rebuild the relevant controller bindings, test with an empty Community folder, and verify the problem in a stock aircraft before blaming the simulator itself.
If you need aircraft files, liveries or freeware packages while testing a clean setup, our MSFS library is here: https://flyawaysimulation.com/downloads/.