Fix MSFS 2024 autopilot problems: failed engagement, disconnects, wrong NAV source, missed altitude capture, controller conflicts and add-on faults.
Microsoft Flight Simulator 2024’s autopilot usually fails because the aircraft lacks electrical power, the wrong lateral or vertical mode is active, the navigation source is incorrect, or a controller input disconnects it. Restore power, stabilise and trim the aircraft, verify bindings, then engage the required mode and check its annunciation.
Pressing the AP button alone does not guarantee that the aircraft will follow a route or climb to the selected altitude. The flight director displays guidance, the autopilot moves the flight controls, and autothrottle or autothrust manages power; these are separate systems. Our guide to the correct engagement sequence for HDG, NAV, ALT, VS and FLC explains the basic mode logic.
What does the autopilot symptom tell you?
The way the autopilot fails usually identifies the system or setting responsible.
| Symptom | Likely cause | Check first |
|---|---|---|
| AP will not engage | Missing electrical power, aircraft outside engagement limits, or a disconnect command is active | Avionics buses, trim, airspeed, attitude and bindings |
| AP engages, then drops out | Noisy control axis, duplicate assignment, trim limit or aircraft protection | Every connected controller and the mode annunciator |
| Aircraft holds a heading but ignores the route | HDG or ROL remains active, NAV is only armed, or the wrong navigation source is selected | Active lateral mode, GPS/FMS source and active flight-plan leg |
| Aircraft holds its present altitude | ALT was engaged without a climb or descent mode | Selected altitude and VS or FLC mode |
| NAV or APR stays armed | The aircraft has not met capture conditions | Intercept angle, signal, source and approach geometry |
| Pitch changes but speed is wrong | Power is not being managed, especially with FLC in light aircraft | Throttle setting and whether the aircraft has autothrottle |
How do I fix MSFS 2024 autopilot problems?
Work from the aircraft state to the active modes, then isolate controllers and add-ons rather than changing unrelated settings.
- Read the mode annunciator. Look at the autopilot status or flight mode annunciator rather than relying on illuminated panel buttons. Confirm which lateral and vertical modes are active and which are merely armed.
- Check electrical and aircraft systems. Verify battery, alternator or generators, avionics buses and any required hydraulic or flight-control systems. In complex aircraft, incomplete inertial-system alignment or an unfinished start-up can inhibit the autopilot.
- Stabilise the aircraft manually. Establish a safe airspeed and moderate attitude, release control pressure and trim the aircraft. An autopilot may reject engagement during a stall, overspeed, extreme bank or badly out-of-trim condition.
- Remove control conflicts. Search every keyboard, yoke, joystick, throttle and gamepad profile for autopilot-disconnect, AP master, trim and flight-control assignments. Remove duplicates, disable piloting assistance that can control the aircraft, and add only enough dead zone to stop a genuinely noisy axis.
- Select the required modes. Use HDG to follow the heading bug, NAV to intercept an active route, and VS or FLC to climb or descend towards a selected altitude. Use ALT for level flight or altitude capture. Some aircraft require the flight director before AP engagement; others enable it automatically.
- Return to normal simulation rate. High simulation rates, severe turbulence and large control inputs can produce oscillations or exceed the authority of the simulated servos.
If the AP button still refuses to remain engaged, use our focused engagement checks for power, trim, bindings and immediate dropouts.
Why won’t the autopilot follow the flight plan?
An autopilot that holds a heading but ignores the magenta route is usually working; its navigation mode, source or active flight-plan leg is wrong.
Select GPS or FMS as the navigation source for a programmed route. Use VLOC for a conventional VOR or ILS signal where applicable. Confirm that the intended leg is active and that the flight plan has no discontinuity; use Direct-To or activate the next leg if the aircraft has no usable course to intercept.
HDG may remain active while NAV is armed. The aircraft will continue on the selected heading until it reaches the route at a suitable interception angle, at which point NAV should become active. For glass-cockpit input problems, inactive legs and CDI-source mistakes, see our G1000 and FMS navigation troubleshooting.
Why does approach mode stay armed?
APR remains armed when no valid lateral or vertical guidance meets the capture conditions. For an ILS, tune the correct frequency where manual tuning is required, select VLOC, intercept the localiser at a sensible angle and approach the glideslope from below.
GPS approaches require a compatible procedure, GPS source and usable vertical guidance. Not every aircraft can capture every approach type, and an ordinary approach-capable autopilot is not necessarily capable of autoland.
Why won’t the autopilot climb or descend?
Selecting a new altitude sets a target but does not, by itself, command a climb or descent.
Choose VS and set a vertical speed, or choose FLC and set an appropriate airspeed. In many light aircraft, FLC controls pitch to maintain speed while the pilot controls power. With VS, insufficient power can let the airspeed decay towards a stall even though the autopilot maintains the requested vertical speed.
If ALT is already active, the aircraft will normally hold its present altitude until another vertical mode is selected. Airliner VNAV also requires a valid FMS route, suitable altitude constraints and the correct selected or managed mode; setting an altitude on the panel is not enough in every aircraft.
Why does the autopilot keep disconnecting?
Repeated disconnects are commonly caused by a mapped command, analogue-axis noise, manual control input, loss of power or an aircraft-specific operating limit.
A mistake we see constantly is checking only the main joystick while a throttle, gamepad or keyboard has the same disconnect command assigned. Watch for moving control indicators with the hardware untouched, and do not fight the autopilot with the yoke or trim. Our disconnect and controller-noise diagnostic covers this symptom in more depth.
How can I tell whether this is an MSFS 2024 bug?
A clean test with a default aircraft separates a simulator fault from an aircraft, controller or add-on problem.
- Start a new free flight with a default autopilot-equipped aircraft, clear weather, no simulated failures and normal simulation rate. Avoid a saved flight because it may restore an incomplete avionics state.
- Create a clean control profile or disconnect optional controllers. Operate the autopilot from the cockpit so that an unseen AP binding cannot interfere.
- Disable third-party content. On PC, temporarily move add-ons out of the Community folder. On other platforms, disable optional third-party packages through the simulator’s content management tools where available.
- Restart and retest. Install pending simulator and aircraft-package updates before restoring add-ons in small batches.
If the default aircraft works, the core autopilot is not the cause. An add-on aircraft may use custom autopilot logic, enforce engagement limits or require its own start-up and FMS procedure. If several default aircraft fail under clean conditions, the control profile, assistance settings or simulator installation becomes the more likely source.