Bind the A32NX autopilot disconnect button in MSFS, choose the correct command, clear conflicts and silence the Airbus disconnect warning.
In Microsoft Flight Simulator, open the controls settings for your joystick, yoke or keyboard, create an A32NX-specific profile, set the filter to All, and bind your chosen button to Autopilot Off. Do not use Toggle Autopilot Master; another press could re-engage the autopilot. Save the profile and clear any conflicting assignment.
How do I assign the A32NX autopilot disconnect button?
The menu layout differs between MSFS 2020 and MSFS 2024, but the required control command is Autopilot Off.
- Select the controller: Open the simulator’s controls settings and choose the joystick, sidestick, yoke or keyboard containing the button you want to use.
- Create an aircraft profile: Duplicate the device’s existing preset and give the copy an A32NX-specific name. This prevents the Airbus assignment from changing controls used by other aircraft.
- Show every command: Change the assignment filter from Assigned or Essential to All, then search for
Autopilot Off. - Capture the input: Select the command’s input box, press the desired physical button, validate the assignment and apply the changes.
- Check for conflicts: Search by input using the same button. Remove unintended assignments, particularly
Toggle Autopilot Master,Autopilot Onor another cockpit function that would activate simultaneously. - Confirm the active preset: Ensure MSFS has retained the new profile for that device before returning to the flight.
For device profiles, modifiers and commands that are not exposed cleanly by MSFS, see our guidance on building a clean A32NX control profile and removing duplicate inputs.
Test the binding at a safe altitude with AP1 engaged. Pressing the button should remove the AP1 or AP2 indication from the Flight Mode Annunciator and hand control back to the pilot. Avoid making the first test during take-off, landing or close to terrain.
Which autopilot command should I bind?
Autopilot Off is the correct choice for a dedicated Airbus-style disconnect button because it can command disconnection without requesting engagement.
| MSFS command | Use for the A32NX disconnect button? | Reason |
|---|---|---|
Autopilot Off | Yes | Disconnects the active autopilot channel without acting as an on/off toggle. |
Toggle Autopilot Master | No | Alternates between states, so a second press while disconnected can request autopilot engagement. |
Autopilot On | No | Provides an engagement command rather than a dedicated disconnect action. |
The off command disconnects the A32NX autopilot as a system rather than requiring separate hardware buttons for AP1 and AP2. It does not disconnect autothrust or switch off the flight directors; those are separate Airbus functions. Our Airbus FCU and autopilot mode explanation covers how those systems interact.
Why does the A32NX disconnect binding not work?
An unresponsive A32NX autopilot disconnect button usually comes from the wrong profile, a hidden command filter or a conflicting assignment.
- The command is missing: Set the controls filter to All. Assigned-only views hide commands that have not yet been mapped.
- The wrong device is selected: MSFS stores separate presets for each controller. Assigning the command under Keyboard will not bind a joystick button.
- The wrong preset loaded: Check that the A32NX profile remains active after loading the aircraft or reconnecting the controller.
- The button has two assignments: Use search-by-input and remove any AP master toggle, assistance or unrelated cockpit command that fires with it.
- The hardware uses a maintained switch: A momentary pushbutton is the best match for the sidestick takeover button. A latching switch or repeating input can generate unexpected commands.
- A hardware panel sends its own event: If an ordinary joystick button works but a panel button does not, configure the panel to send
Autopilot Offrather than a generic AP master toggle, where its software permits.
If the autopilot disconnects without you pressing the button, inspect duplicated pitch and roll axes, noisy controller inputs and unintended AP commands using our diagnostic checklist for repeated autopilot disconnects.
How do I silence the A32NX autopilot disconnect warning?
If the cavalry-charge warning continues after the autopilot has disconnected, press the mapped Autopilot Off button again to acknowledge it.
A brief disconnect alert is normal after a deliberate takeover. The autopilot indication should already be absent from the FMA; the second press acknowledges the warning rather than reconnecting the system. This is another reason to avoid Toggle Autopilot Master, which can send an engagement request when the autopilot is off.