Fix the A330 autopilot not working in MSFS 2024: check ADIRS, AP1, CL detent, managed modes, FMA indications and controller conflicts.
To fix the iniBuilds A330 autopilot in Microsoft Flight Simulator 2024, complete the aircraft’s electrical and ADIRS setup, engage AP1 only after take-off, move the thrust levers to CL when prompted, and check the Flight Mode Annunciator. If it disconnects immediately, remove duplicate autopilot bindings and add controller deadzones.
First establish what “not working” means. If AP1 never appears on the Primary Flight Display, it is an engagement problem. If AP1 remains displayed but the aircraft flies the wrong heading, altitude or speed, the autopilot is engaged and the fault is usually an FCU mode, flight-plan or autothrust issue.
Use this quick A330 autopilot test
A clean airborne test separates an aircraft setup error from a controller or simulator problem.
- Confirm the aircraft is properly powered. From a cold cockpit, complete the electrical and engine start sequence, set all three inertial-reference selectors to NAV and allow alignment to finish. The PFD must show valid attitude, airspeed and heading data without red ADIRS or flight-control warnings. Our A330 power-up, MCDU and managed-mode walkthrough covers the complete preparation sequence.
- Check the control profile. Temporarily unplug spare controllers and disable assisted piloting. Search every active profile for autopilot disconnect, autopilot toggle, pitch, roll and trim assignments. Remove duplicate button assignments and add a small deadzone to noisy axes.
- Establish a stable climb. Use normal simulation rate, retract the gear, centre the controls and trim the aircraft. For diagnosis, wait until roughly 1,000 feet above the ground rather than trying to engage the autopilot immediately after lift-off.
- Set an achievable target. Select an altitude above the aircraft and either establish a selected heading or ensure that a valid route leg is active. Turn both flight directors on, then press AP1 once. A programmed flight plan is required for NAV guidance, but it is not required merely to engage the autopilot.
- Set the thrust levers correctly. When the PFD requests LVR CLB, move the levers into the CL detent. Check that autothrust remains active. Incorrect detent calibration usually causes speed or thrust problems rather than blocking AP1, but it often makes the whole system appear faulty.
- Read the FMA. The Flight Mode Annunciator across the top of the PFD is authoritative. Confirm that AP1 is shown and identify the active lateral and vertical modes instead of relying only on illuminated FCU buttons.
What should the A330 Flight Mode Annunciator show?
The FMA should show AP1 together with active lateral and vertical modes; green modes are active, while blue modes are armed and waiting for capture.
| FMA indication | Meaning | What to do |
|---|---|---|
| AP1 not shown | The autopilot did not engage or disconnected | Check ADIRS, flight-control warnings and controller inputs |
| HDG green | The aircraft is following the selected heading | Push the heading selector for managed NAV when a valid route is available |
| NAV blue | Route guidance is armed but not yet captured | Intercept the active leg or use DIR in the MCDU |
| ALT green | The aircraft is holding its present selected altitude | Select a different altitude and command CLB, DES, OP CLB or OP DES |
| ALT* | Altitude capture is in progress | Allow the capture to complete without changing modes |
| LOC or G/S blue | Localiser or glideslope capture is armed | Continue towards a valid intercept and check the ILS signal |
Airbus FCU knobs have different push and pull actions. Broadly, push selects managed guidance from the MCDU and pull selects a pilot-commanded value. The interaction gesture varies with the chosen cockpit interaction system, so use the control tooltip to confirm which action MSFS 2024 is sending. Our Airbus FCU managed-versus-selected explanation covers these modes in more detail.
Why does AP1 engage but not follow the flight plan?
The A330 will not follow the magenta route while HDG is the active lateral mode, when the next leg is discontinuous or when the active waypoint is behind the aircraft.
- Look for NAV in green on the FMA. NAV shown in blue is only armed.
- Push the heading selector to request managed NAV. Pulling it commands selected heading instead.
- Check the MCDU flight plan for a discontinuity, vectors leg or incorrect active waypoint. Do not automatically delete a deliberate vectors segment used by an arrival or approach.
- If the aircraft is too far from the route to capture it cleanly, use the MCDU’s direct-to function or fly an intercept heading first.
- Check that the flight plan has not started sequencing from the wrong departure runway or an earlier waypoint.
Why will the A330 not climb or descend on autopilot?
The autopilot needs a new selected altitude and an active vertical mode; turning the altitude knob alone does not always command the aircraft to leave ALT hold.
Push the altitude selector when you want managed CLB or DES and the MCDU route contains suitable vertical guidance. Pull it for OP CLB or OP DES when you want to climb or descend directly towards the FCU altitude without observing intermediate managed constraints. Choose open climb or descent carefully because it can bypass planned altitude restrictions.
If AP1 controls pitch but airspeed runs away, troubleshoot autothrust rather than the autopilot. Place the hardware levers accurately in CL, confirm that A/THR is active and recalibrate the throttle detents if the virtual levers flicker between positions.
Why does the A330 autopilot disconnect immediately?
An immediate disconnect is most often caused by a continuing sidestick input, a duplicated disconnect command or an unstable aircraft state.
- Release and centre the pitch and roll axes before pressing AP1.
- Increase deadzones if the cockpit sidestick moves while the physical controller is untouched.
- Remove repeated or duplicated assignments for autopilot disconnect, AP master and trim.
- Check throttles, yokes, gamepads and button boxes rather than editing only the device used to fly.
- Return time acceleration to normal and recover manually from excessive bank, pitch or speed before trying again.
If the aircraft still rejects AP1, follow our broader MSFS engagement and immediate-disconnect checklist, which covers control conflicts, trim and aircraft-state failures.
Why will the A330 not capture the ILS?
APPR mode cannot capture an ILS unless the approach is correctly loaded or tuned and the aircraft reaches the localiser and glideslope from a usable intercept.
Confirm that the correct runway approach is active, the ILS ident and deviation scales are present, and LOC and G/S appear armed on the FMA. Intercept the localiser at a modest angle and approach the glideslope from below. Pressing APPR does not make the aircraft return to a localiser already behind it or descend onto a glideslope from above.
Use one autopilot for normal flight. A second channel is associated with approach capability when the aircraft and selected approach support it; pressing both AP buttons is not a general fix for faulty route or altitude guidance.
What if the stock A330 still fails the test?
If both autopilot channels fail in a stable, ready-to-fly aircraft with centred controls, test for a damaged aircraft state or conflicting add-on.
- Start a new flight rather than reloading the same saved flight.
- Use the default A330 without avionics modifications or non-default aircraft packages.
- Temporarily disable Community-folder modifications on PC and optional third-party packages on other platforms.
- Create a clean controller profile with only the essential flight axes and one AP disconnect assignment.
- Install any available simulator and aircraft-package updates, then restart Microsoft Flight Simulator 2024.
If the clean test works, restore controllers and add-ons one at a time. The item after which AP1 fails is the conflict; reinstalling or resetting everything at once hides that evidence.