Why does autopilot stop working in FSX?

In FSX and FSX: Steam Edition, autopilot usually stops because the master is being toggled by a duplicate control assignment, electrical or avionics power has failed, the aircraft is outside a safe capture condition, or the selected mode never captured. First determine whether AP disengaged or stayed on but stopped following commands.

Is the FSX autopilot disengaging or just missing a mode?

An extinguished AP master indication means a real disconnect; an illuminated master with the aircraft ignoring its route usually means the wrong mode or navigation source is selected, or the mode is still waiting to capture.

“Ja, beides”: what if it disconnects and also ignores modes?

If your answer is ja beides — “yes, both” — treat the behaviour as two symptoms. Diagnose each event by watching the AP master and active-mode indications at the moment the problem occurs.

A noisy controller or duplicate AP command can cause genuine disconnects while also disturbing heading, pitch or trim control. Unstable electrical power can make the panel behave inconsistently before the autopilot finally drops offline. Do not assume both symptoms have one navigation-setting fix.

FSX autopilot: what should I test when nothing works?

If the only report is “it dont work” or “nothing works”, a fresh default-aircraft test will separate an autopilot fault from a bad flight plan, add-on state or hardware input.

1. Start a clean flight. Use a default FSX aircraft whose panel visibly includes an autopilot. Choose ordinary weather, use normal 1× simulation rate and avoid loading the saved flight in which the fault appeared.
2. Stabilise before engagement. Fly at a normal airspeed and attitude, then trim the aircraft so that it needs little control pressure. Stock FSX systems are generally permissive, but sophisticated add-ons may reject or disconnect autopilot during excessive bank, pitch, overspeed, stall warning or strong manual input.
3. Confirm electrical power. Start the engine correctly and turn on the battery, generator or alternator and required avionics switches. A panel may work from the battery at first and then fail several minutes later because no engine-driven electrical source is online.
4. Inspect the AP master assignment. The default Z key toggles the FSX autopilot master; it is not a dedicated “on” command. Check for a stuck key, a joystick button assigned to the same event, or controller software sending that command separately from FSX.
5. Remove duplicate and noisy inputs. One button programmed in both FSX and the device’s own software can send two presses, making AP appear to engage and instantly disengage. Also inspect assignments for autopilot disconnect, elevator trim, aileron trim and the primary control axes. Temporarily unplugging the controller is a useful proof test; persistent input problems can be traced with our FSX joystick, throttle and axis checks.
6. Test heading mode by itself. Set the heading bug to the present heading, engage the AP master and select HDG. Move the bug by a modest amount and watch for a controlled turn. Once level, test altitude hold according to that panel’s operating logic.
7. Check failures and saved state. Disable deliberate or scheduled failures and start another new flight. Reloading the same saved situation may restore the failed component, depleted battery or incorrect panel state.
8. Interpret the result. If HDG and altitude hold work, the autopilot servos are functioning and the remaining problem is probably route, radio or approach configuration. If you are unsure about the normal engagement sequence, use our practical guide to engaging and operating FSX autopilot modes.

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

The AP master only enables the system; the required lateral and vertical modes must also be selected, armed and captured.

• Heading mode: Select HDG and move the heading bug to the desired heading. If NAV or APR is active, it may replace HDG rather than operate alongside it.
• GPS flight plan: On panels using the default FSX navigation logic, choose GPS as the navigation source, make sure a valid flight-plan leg is active and select NAV. Approach the route at a sensible intercept angle. If NAV remains armed or turns towards the wrong leg, follow our GPS, VOR and NAV-source troubleshooting sequence.
• VOR navigation: Select NAV rather than GPS, tune the correct NAV receiver, set the required course and intercept the radial while within reception range. Tuning a station does not by itself command the autopilot to follow it.
• Altitude: Rotating an altitude selector does not initiate a climb or descent in every FSX aircraft. Some panels hold the altitude at which ALT is pressed; others combine a preselected altitude with vertical-speed, pitch or altitude-arm modes. Read the mode indications rather than assuming all stock and add-on panels use identical logic.
• Airspeed and power: A conventional FSX autopilot controls direction and pitch, not necessarily the throttle. Unless the aircraft has a functioning autothrottle, you remain responsible for power. An aircraft that becomes too slow, overspeeds or reaches its pitch limit may appear unable to hold altitude.

An armed mode is waiting for its capture conditions; it is not yet controlling the aircraft. A vertical-speed mode changing automatically to altitude hold at the target altitude is normal. An illuminated flight director is also not proof that the autopilot servos are engaged.

Why does FSX autopilot stop after a few minutes?

An autopilot that initially works and then dies with the radios, navigation equipment or glass displays is usually running from a discharging battery without an operating generator or alternator.

If the other avionics remain powered, look for a repeating controller command, a drifting trim or control axis, an add-on protection event, or a scheduled failure. High simulation rates can also destabilise older FSX autopilots and complex custom systems, so reproduce the flight at 1× before changing the aircraft installation.

Why does the autopilot fail only during an ILS approach?

An autopilot that works en route but not on final usually has an ILS capture problem rather than a failed AP system.

NAV1 must be tuned to the correct localiser frequency, the appropriate navigation source must be selected, APR must be armed, and the aircraft should capture the localiser before intercepting the glideslope from below. Being above the glideslope or approaching at a severe angle can leave the mode armed indefinitely. Our ILS localiser and glideslope capture checklist covers the complete setup.

How can I tell whether an add-on aircraft is causing the problem?

Run the same heading-and-altitude test in a fresh flight with a default FSX aircraft equipped with a conventional autopilot.

• The default aircraft works: Check the add-on’s supplied procedures for custom electrical buses, flight directors, hydraulic requirements, engagement limits and panel-state logic. Some advanced aircraft intercept or ignore the default Z command.
• Every aircraft fails: Concentrate on global FSX control assignments, external controller software, electrical procedure and simulator failures.
• Only one saved flight fails: Create a new flight. The saved situation may contain an exhausted battery, deliberate failure, invalid route or corrupted custom panel state.

Reinstalling FSX should be the last step. It rarely fixes a duplicate binding, an unpowered avionics bus or an aircraft-specific operating requirement.

MSFS 2024 A330 autopilot not working

The MSFS 2024 A330 uses Airbus-style managed and selected modes, so the FSX GPS/NAV switch instructions above do not apply directly. These checks also apply to Microsoft Flight Simulator 2024 Sim Update 5.

1. Read the PFD flight-mode annunciator. AP1 or AP2 confirms that an autopilot is engaged. The lateral and vertical FMA columns show what is active and what is merely armed; the flight director bars alone do not confirm AP engagement.
2. Engage from a stable condition. Centre the sidestick, establish a normal flight attitude and press AP1. If it immediately disconnects, check for a held autopilot-disconnect command, noisy pitch or roll axes, duplicate controller bindings and active aircraft warnings or protections.
3. Check managed versus selected heading. For Airbus-style controls, pushing the heading control requests managed NAV guidance while pulling it selects a heading. Managed NAV also needs a valid flight-plan path without an unresolved discontinuity or manual-vector segment. Confirm the result on the FMA rather than relying only on the knob position.
4. Command the altitude change. Selecting a new altitude does not always start the climb or descent by itself. Push for managed guidance or pull for an open climb or descent, then verify the active vertical mode on the FMA. Managed mode may respect programmed altitude constraints, which can make the aircraft level earlier than expected.
5. Test a clean aircraft state. Start a new flight with the included A330, a standard controller profile and no third-party aircraft-system modifications. On PC, temporarily removing relevant packages from the Community folder is a useful conflict test. If a clean flight works, restore modifications individually rather than reinstalling the whole simulator.