Fix MSFS 2024 autopilot problems on PS5: restore cockpit input, remove DualSense conflicts, engage AP correctly and make NAV follow the route.
In Microsoft Flight Simulator 2024 on PS5, autopilot usually fails because the aircraft is not configured for engagement, the DualSense has a conflicting or drifting input, or the wrong lateral or vertical mode is selected. Restore controller focus, clear duplicate bindings, stabilise the aircraft, then verify the active flight-guidance modes.
How do I fix the MSFS 2024 autopilot on PS5?
The fastest reliable fix is to separate a cockpit-input fault from an autopilot-configuration fault.
- Confirm that the aircraft has an autopilot. Some aircraft have only basic stability assistance, while others lack an autopilot entirely. Test with a default aircraft whose panel includes AP, HDG, NAV and ALT controls.
- Prepare the aircraft correctly. Switch on the required electrical and avionics systems, complete any aircraft-specific alignment, enable the flight director where required and stabilise the aircraft in normal flight. An autopilot is not intended to recover a stall, extreme bank or badly out-of-trim condition.
- Test the cockpit AP button. If it highlights but will not operate, return focus to the cockpit cursor, close any EFB or toolbar interaction and check the selected cockpit interaction method. Our PS5 cockpit-focus and interaction-mode fixes cover this input problem.
- Inspect the DualSense bindings. Search the controls options for
autopilot,AP disconnect,trim,pitchandroll. Remove duplicate assignments, check that no disconnect command is permanently active and add a small stick dead zone if the input display does not return to centre. - Disconnect other controllers temporarily. A keyboard, mouse, flight stick or throttle can send an unnoticed trim or control-axis input. Reconnect each device separately after the autopilot works.
- Engage AP in steady flight. Release the stick, press the cockpit AP or CMD control and watch the flight-mode annunciator. If the aircraft-specific control works but a mapped DualSense button does not, the problem is the binding rather than the autopilot.
- Select an active guidance mode. Use HDG for the heading bug, NAV for an interceptable route and VS or FLC to climb or descend towards a selected altitude. The correct PS5 autopilot and flight-mode sequence explains how those modes work together.
What does each autopilot symptom mean?
The exact symptom usually identifies whether the fault is controller input, engagement conditions or flight-plan guidance.
| Symptom | Likely cause | What to check |
|---|---|---|
| AP button cannot be pressed | Cockpit cursor or interaction focus | Close overlays, restore cockpit focus and test another panel switch |
| AP will not engage | Missing power, unsafe flight condition or aircraft-specific requirement | Avionics, flight director, trim, airspeed and failure settings |
| AP engages and immediately disconnects | Stick drift, manual trim input or duplicate disconnect binding | Input indicators, dead zones and every connected device |
| AP stays on but ignores the route | NAV is armed but not captured, or the wrong navigation source is selected | Flight-mode annunciator, active flight-plan leg and GPS/FMS source |
| Aircraft holds altitude instead of climbing | ALT hold is active without a climb mode | Select the target altitude, then use VS, FLC or the aircraft's equivalent mode |
Why does the autopilot engage and immediately disconnect?
An autopilot that engages and drops out is usually reacting to a continuous controller command, excessive trim or an aircraft limit. A small DualSense stick drift can be enough, even when the aircraft appears to fly straight by hand.
Watch the pitch, roll and trim input indicators without touching the controller. Increase the relevant dead zone only enough to centre the input, remove duplicate AP-disconnect assignments and temporarily disable piloting assistance while testing. If the warning repeats, use our autopilot disconnect diagnosis to distinguish controller drift from trim and flight-condition problems.
Why is autopilot on but not following the flight plan?
If AP remains engaged but the aircraft ignores the magenta route, the problem is navigation-mode capture rather than the autopilot master. The flight-mode annunciator is the deciding evidence: an armed mode is waiting to capture, while an active mode is controlling the aircraft.
- Confirm that the intended flight-plan leg is active and not behind the aircraft.
- Select the correct GPS, FMS or navigation source for that aircraft.
- Approach the route at a reasonable intercept angle before arming NAV.
- Use HDG to intercept if NAV will not capture from the present position.
- Remember that preselecting an altitude alone does not command a climb in most aircraft; select VS, FLC or the applicable managed mode.
Complex airliners may require their cockpit AP1 or CMD control rather than a generic controller command. Our complete MSFS 2024 engagement workflow covers power, trim, mode selection and flight-plan tracking in more depth.
Is this a PS5 problem or an aircraft problem?
A failure affecting one aircraft is normally aircraft-specific, while the same failure across several default aircraft points to a PS5 control profile or simulator setting.
Start a fresh flight in a default aircraft, use a clean DualSense preset and operate AP directly from the cockpit. If that works, rebuild the custom binding or check the original aircraft's checklist and available guidance modes. If it fails everywhere, restart the simulator, verify that the simulator and installed aircraft content are updated, and reset only the affected controller preset after recording any custom assignments.
Reinstallation should be the last step. It rarely corrects a drifting axis, duplicate binding or incorrect navigation mode, which are the faults we see most often behind an MSFS 2024 autopilot not working on PS5.