Set up FlyByWire A32NX keybindings in MSFS with the right axes, device profiles, throttle detents and fixes for ignored or conflicting inputs.
To set up FlyByWire A32NX keybindings in Microsoft Flight Simulator, create a dedicated control preset for each device, use axis commands for analogue controls, clear conflicting assignments, and save the preset. Bind both engine throttles, then calibrate their Airbus detents in the flyPad; use the mouse for unsupported custom cockpit controls.
This workflow applies to MSFS 2020 and MSFS 2024 on PC. FlyByWire A32NX is a PC add-on, so it cannot be loaded or configured on the Xbox or PlayStation editions.
How do I create an A32NX control preset?
Create one dedicated A32NX preset for every device shown in the simulator's Controls settings. Keyboard, joystick, throttle quadrant and pedals each keep their own assignments; changing the keyboard preset does not change the joystick preset.
- Load the FlyByWire aircraft. Confirm that you selected the A32NX rather than another A320neo. The flyPad is an obvious cockpit check; if it is missing, review the A32NX package and installation guidance before altering controls.
- Open Controls settings. MSFS 2020 and MSFS 2024 arrange their menus differently, but both provide device-specific profiles or presets.
- Duplicate the existing preset. Give the copy a clear name such as
A32NX. Repeat this for every device you intend to use. - Show all available commands. An Assigned-only filter hides commands you have not yet configured. Search by command name for new bindings and by input when checking what a key, button or axis already operates.
- Remove conflicts. Clear unwanted stock-aircraft, camera and assistance assignments from the same input. Do not leave both an axis and directional button commands attached to one joystick movement.
- Save and verify the preset. Move each control while parked and check the cockpit animation. After changing aircraft or reconnecting hardware, confirm that MSFS retained the intended preset.
For keyboard-only flying, use increase/decrease or toggle commands rather than axis entries. Our references show the baseline MSFS 2020 keyboard assignments and the corresponding MSFS 2024 keyboard profiles, which helps identify a default shortcut before replacing it.
Which FlyByWire A32NX controls should I bind?
Use analogue axis bindings for controls that move continuously and button commands for discrete Airbus positions. Command labels can differ slightly between MSFS versions, but the required control type remains the same.
| Aircraft function | Preferred binding | Practical detail |
|---|---|---|
| Pitch and roll | Elevator Axis and Ailerons Axis | Set only enough dead zone to stop sensor jitter. Reverse an axis if the cockpit control moves the wrong way. |
| Yaw | Rudder Axis | Leave nose-wheel steering linked to rudder unless you deliberately enable the A32NX separate-tiller option and bind a dedicated steering axis. |
| Thrust | Separate throttle axes for engines 1 and 2 | With one physical lever, assign that lever to both engine axes intentionally. With two levers, bind them separately. |
| Wheel brakes | Left and right brake axes | Use a combined brake button only when no toe-brake axes are available. Reverse the axes if the brakes are applied when released. |
| Flaps | Flaps increase/decrease, or a suitable flap axis | Increment and decrement commands are usually simpler for a keyboard or ordinary buttons; a detented quadrant can use an axis. |
| Speed brake | Spoilers axis and, where required, a separate arm command | Check the cockpit lever reaches retracted, armed and full extension without flickering. |
| Landing gear | Gear toggle or explicit up/down commands | A toggle saves a button; separate commands suit labelled hardware switches. |
| FCU and overhead controls | Mouse, unless the exact function has been verified | Generic autopilot commands do not represent every Airbus push, pull and managed-mode action. |
A common mistake is binding a joystick axis to both Aileron Axis and an aileron-left/right command. The axis then supplies a continuous value while the button-style assignment adds another input. The same conflict occurs when a throttle lever is attached to a generic all-engine axis as well as the separate engine axes.
How do I set up the A32NX throttle detents?
A32NX throttle detents require both correct MSFS axis assignments and a separate calibration in the flyPad. Bind throttle 1 and throttle 2 first, remove unintended duplicate and reverse-thrust assignments, then record the reverse, idle, CL, MCT/FLX and TOGA regions in the aircraft.
The exact calibration depends on the quadrant and whether reverse thrust occupies part of the lever travel. Follow our full A32NX throttle-axis and detent calibration procedure rather than copying another user's sensitivity or detent values. Keyboard users operating throttle increase/decrease commands do not need to calibrate a physical axis.
Why are my A32NX keybindings not working?
Most failed A32NX bindings come from an inactive device preset, duplicate assignments or a generic MSFS command that the aircraft's custom systems do not use.
- The command is missing: change the control filter from Assigned to All and confirm that the correct keyboard or controller is selected.
- A key performs two actions: search by input, press the key and remove its unwanted camera, view or aircraft assignment.
- Only one engine responds: the lever is bound to one engine axis only. Bind both engine axes, or one lever to each axis when using a combined throttle.
- The throttle skips or flickers between detents: clear competing bindings, correct any reversed axis and repeat flyPad calibration.
- The aircraft rolls, yaws or brakes without input: check for duplicate axes, increase the relevant dead zone slightly and disable assistance features that are taking control.
- The autopilot disconnects after engagement: inspect the pitch and roll axes for jitter or a second device sending control input.
- A stock A320 command does nothing: the A32NX may use a custom local variable or event instead of the similarly named generic command. If Controls settings do not expose the required action, operate it with the cockpit mouse rather than assigning an unrelated command.
- Bindings changed between flights: verify the active preset for every connected device. MSFS can select a different profile after hardware is reconnected or another aircraft has been used.