How do I set up FlyByWire A32NX keybindings in MSFS?
Set up FlyByWire A32NX keybindings in MSFS 2020/2024, configure Logitech throttles, calibrate flyPad detents and fix missing controls.
To set up FlyByWire A32NX keybindings in Microsoft Flight Simulator, create a dedicated A32NX profile for each connected device, assign analogue axes for flight controls and each engine throttle, remove duplicate bindings, and calibrate the Airbus throttle detents in the flyPad. Test every axis, key and button while parked before flight.
This applies to the PC editions of MSFS 2020 and MSFS 2024. Although MSFS 2024 is also available on Xbox and PlayStation, and MSFS 2020 on Xbox, the FlyByWire A32NX add-on and its flyPad configuration covered here are PC-only. A20N is the ICAO type designator for the A320neo, not a separate aircraft or control profile.
Wie genau geht das? The exact A32NX keybinding workflow
The exact sequence is to load the A32NX, select each physical device in Controls settings, create its profile, expose all commands, assign the required inputs and remove conflicts.
- Load the FlyByWire A32NX. Check for the flyPad in the cockpit and confirm that you did not select the default Microsoft A320neo.
- Open Controls settings. MSFS 2020 and MSFS 2024 organise this screen differently, but both let you select a keyboard, joystick, pedals or throttle quadrant and manage its profile.
- Create a dedicated profile for each device. Duplicate a working preset and give it a clear name such as
A32NX. A keyboard profile does not alter the profile assigned to a joystick or throttle quadrant. - Change the filter from Assigned to All. Assigned hides every command that has not yet been bound. Select the affected device before searching.
- Assign the correct command type. Use analogue axis commands for controls that move continuously and button, toggle, increase or decrease commands for discrete actions.
- Search by input for conflicts. Press the key or button, or move the axis, to reveal everything attached to it. Remove unwanted camera, assistance and stock-aircraft assignments.
- Save and activate the profile. Verify the selected profile again after reconnecting hardware or changing aircraft.
- Test while parked. Move every axis through its full travel and operate each button while watching the corresponding cockpit control or aircraft system.
If the basic device profile, sensitivity or reversed-axis setup is unclear, our MSFS device-profile and axis setup guide covers those simulator-wide settings before you add A32NX-specific bindings.
Which FlyByWire A32NX controls should I bind?
Bind axes for continuous movement and button or switch commands for discrete actions. Exact command labels vary between MSFS 2020, MSFS 2024 and connected hardware, so search for the command type below rather than choosing a superficially similar stock-A320 command.
| Aircraft function | Command type to use | What to check |
|---|---|---|
| Pitch and roll | Elevator and aileron axes | The sidestick moves in the same direction as the hardware, without jitter near neutral. |
| Yaw | Rudder axis | Reverse it if the pedals move the cockpit rudder input in the wrong direction. |
| Engine thrust | Separate Engine 1 and Engine 2 throttle axes | Do not retain a generic all-engines throttle axis on the same lever. |
| Toe brakes | Separate left and right brake axes | Released pedals must show released brakes; many pedal sets require axis reversal. |
| Flaps | Increase/decrease commands or a suitable flap axis | Buttons are simpler unless the hardware has useful physical flap positions. |
| Speed brake | Spoiler axis, plus an arm command if needed | Check retracted, armed and extended positions without flickering. |
| Landing gear | Gear toggle or explicit up/down commands | Use separate commands for a labelled two-position switch. |
| Autopilot disconnect | Verified disconnect command | Avoid an unsuitable generic autopilot master toggle. Our A32NX autopilot-disconnect binding procedure explains the distinction. |
| FCU and overhead functions | Mouse unless the exact event is exposed | Airbus push, pull and managed-mode actions are not all represented by generic MSFS commands. |
Keyboard users should choose increase, decrease, set or toggle commands rather than axis entries. A mistake we see constantly is assigning the same joystick movement to both an axis and left/right button commands; the two inputs then fight each other.
Logitech throttle quadrant with the FlyByWire A320
With one Logitech throttle lever, intentionally bind that lever to both engine throttle axes; with two levers, assign one independently to Engine 1 and the other to Engine 2.
| Physical arrangement | Correct assignment | Do not retain |
|---|---|---|
| One lever for both engines | The same physical axis assigned separately to Engine 1 and Engine 2 | A generic all-engines throttle axis on that lever |
| Two independent levers | Left lever to Engine 1 and right lever to Engine 2 | Either lever assigned to both engines |
If advancing a lever reduces thrust, reverse that axis in the active MSFS device profile. Apply reversal in one place only; reversing it in both the simulator and another hardware layer restores the wrong direction.
- Remove generic throttle duplicates. Clear any all-engines throttle binding once the separate engine axes are assigned.
- Remove conflicting reverse commands. A detent switch bound to throttle decrease or reverse thrust can fight a reverse range already included on the axis.
- Check sensitivity. Confirm that movement is smooth and reaches both endpoints. Large response-curve changes can compress the usable space around Airbus detents.
- Use only enough dead zone to stop jitter. Excessive dead zone wastes lever travel and makes detent capture less precise.
- Recalibrate after a change. Repeat flyPad calibration whenever you alter lever travel, reverse behaviour, sensitivity, dead zones or the active Logitech profile.
How do I calibrate FlyByWire A32NX throttle detents?
Calibrate the A32NX only after assigning separate Engine 1 and Engine 2 throttle axes and clearing generic throttle or reverse-thrust duplicates.
- Park the aircraft safely. Set the parking brake and keep the aircraft stationary while configuring the levers.
- Assign both engine axes. With two levers, assign one to each engine. With a single Logitech lever, intentionally assign the same lever input to both engine axes so the engines move together.
- Open the flyPad throttle page. Use
Settings (cog) > Realism > Throttle Configurationand start the calibration function. - Capture reverse. Move the hardware into its reverse position or range and use the displayed capture control. If the page separates reverse idle and full reverse, record both before continuing. If the lever has no reverse travel, use the supported no-reverse-on-axis arrangement rather than inventing a reverse zone.
- Capture idle. Place the lever firmly at idle and record the requested position or range.
- Capture CL. Move it into the climb detent and capture that position without holding it between physical notches.
- Capture FLX/MCT. Set the lever to the FLX/MCT detent and record it.
- Capture TOGA. Move the lever to its maximum take-off position and record the final detent.
- Save or apply the calibration. Do not leave the throttle-configuration page without committing the captured values.
- Test every detent while parked. Move slowly through reverse, idle, CL, FLX/MCT and TOGA. Both virtual thrust levers should settle in the same detent without jumping or flickering.
If the tablet is dark or the settings pages are unfamiliar, our guide to accessing and using the flyPad explains its power and menu controls. For reverse-range choices and hardware-specific details, see our full A32NX throttle-axis calibration notes.
Why are my A32NX keybinds not working?
Most failed A32NX bindings come from the wrong active device profile, hidden commands, duplicate axes or a generic simulator command that the aircraft’s custom systems do not support.
I couldn’t find it — where is the command?
Select the affected keyboard, joystick or quadrant first, change the Controls filter from Assigned to All, then search both ways: by command name to locate an unassigned action and by input to see what a key, button or axis already controls. Also verify that the loaded aircraft is the FlyByWire A32NX, not the default A320neo.
If no suitable action appears under All, the function may not be exposed through the standard MSFS controls system. Do not bind a similarly named stock-A320 command and assume it performs the same Airbus push, pull or managed-mode action.
My controls do not move / no se mueven
Use the symptom to separate a profile or input problem from a missing cockpit animation or unsupported custom control.
| Symptom | Likely cause | Fix |
|---|---|---|
| The device responds in Controls settings but nothing moves in the A32NX | An inactive or wrong aircraft profile | Select the intended A32NX profile for that specific device and test again in the cockpit. |
| The command is absent from search results | The Assigned-only filter is hiding unbound commands | Switch to All and make sure the affected device, rather than another controller, is selected. |
| The control jumps, snaps back or moves without being touched | Duplicate axes or another connected device sending input | Search by input and remove every competing assignment, including generic all-engines throttle and button-style direction commands. |
| All controls appear to stop responding | The simulator is paused, an input field has focus or control input has been suspended | Return to the live cockpit, leave pause, close control-search fields and verify that no simulator command or assistance mode has disabled input. |
| The aircraft responds but the cockpit control does not animate | The input is reaching the aircraft, but the visual control is out of sync or that command has no matching animation | Check the actual aircraft or system response before remapping. Reload the aircraft if a primary flight-control animation remains out of sync. |
| Flight axes work, but an FCU or overhead control does nothing | An unsupported custom Airbus control | Use the cockpit mouse unless the exact A32NX-compatible event is available; a generic stock command is not a safe substitute. |
Why does only one engine throttle move?
Only one engine moves when the physical lever is assigned to one engine axis instead of both. For a single-lever quadrant, bind that same lever intentionally to Engine 1 and Engine 2; for a two-lever quadrant, check that each lever has one separate engine assignment and neither also carries a generic throttle axis.