How do I calibrate FlyByWire A32NX throttles?

Bind each physical lever to the matching 0–100% throttle axis in Microsoft Flight Simulator, remove duplicate bindings, then open the FlyByWire A32NX flyPad’s throttle-calibration page. Capture IDLE, CLB, FLX/MCT and TOGA—plus reverse detents if used—save the calibration, and verify both cockpit levers settle cleanly in every gate.

Which MSFS throttle bindings should I use?

Use separate 0–100% engine axes for a two-lever quadrant, or one combined 0–100% throttle axis if the controller has a single lever.

1. Create an A32NX control profile. A dedicated profile prevents bindings intended for conventional aircraft from interfering with the Airbus detents.
2. Assign the axes. Bind the left lever to THROTTLE 1 AXIS (0 TO 100%) and the right lever to THROTTLE 2 AXIS (0 TO 100%). For one physical lever, use the combined THROTTLE AXIS (0 TO 100%) control where available.
3. Remove conflicting assignments. Clear the legacy throttle axes, combined axis when using separate levers, and unwanted throttle bindings on gamepads, joysticks or other connected devices. A duplicate assignment is the most common cause of levers that jump or fight each other.
4. Start with a linear response. Avoid large sensitivity curves and extremity dead zones before calibrating. If the raw input cannot reach both endpoints or moves erratically, complete the relevant hardware and controller calibration checks first.

Invert an axis only if its cockpit lever moves backwards, and invert it in one place rather than both the device software and MSFS. Owners of the Thrustmaster Airbus quadrant can also follow our TCA Airbus axis and detent setup for device-specific binding guidance.

How do I calibrate A32NX detents in flyPad?

Calibrate the Airbus gates from the A32NX flyPad after confirming that its live input moves smoothly across the complete throttle range.

1. Load the FlyByWire A32NX. Open the flyPad and find its throttle-calibration page under the aircraft or settings area. The exact wording can vary between flyPad builds.
2. Check lever direction and range. Move each physical lever from minimum to maximum. Stop here if the displayed value jumps, travels backwards or fails to reach an endpoint; aircraft calibration will not repair a bad hardware signal.
3. Select the correct axis arrangement. Use independent calibration for two separately bound levers. Use the combined option for a single lever controlling both engines, if that choice is shown.
4. Capture each detent. Place the levers firmly at IDLE, CLB, FLX/MCT and TOGA, then use the flyPad control to record the live position for each gate. Calibrate the two engines separately when independent axes are enabled.
5. Set sensible detent ranges. Some flyPad versions capture lower and upper limits; others capture a position with tolerance. Give each physical notch enough width to absorb minor electrical noise, but do not let neighbouring ranges overlap.
6. Save and verify. Apply the calibration, move through the full range slowly, and confirm that both virtual levers enter the same named gate together and remain there without flickering.

Do not copy raw calibration numbers from another simmer. Even two quadrants of the same model can report different endpoints and detent positions.

How should reverse thrust be calibrated?

Enable reverse-on-axis only when the hardware has a genuine reverse section below the idle gate.

Trying to create an axis-based reverse range on hardware that physically stops at idle usually compresses the forward range and makes IDLE unreliable. Conversely, a quadrant with integrated reverse travel must have both reverse endpoints captured or it may jump directly from idle to excessive reverse.

Why do A32NX throttle detents jump or disagree?

Jumping or mismatched detents usually come from duplicate bindings, narrow calibration bands, axis noise or different endpoint values between the two levers.

• One lever moves both engines: remove the combined throttle axis if separate engine axes are also assigned.
• CLB alternates with manual thrust: recapture CLB and widen its flyPad calibration range slightly without overlapping FLX/MCT or IDLE.
• One engine reaches TOGA first: calibrate each lever independently rather than copying values from engine one to engine two.
• The levers move backwards: change the MSFS reverse-axis option once, then recalibrate all detents.
• IDLE or TOGA cannot be reached: check the device’s physical calibration, MSFS sensitivity endpoints and extremity dead-zone settings.
• The flyPad calibration page is missing: confirm that the loaded aircraft is the FlyByWire model rather than the default Airbus. Our FlyByWire A32NX aircraft page helps identify the correct package.
• Settings appear to have vanished: check that MSFS has not switched to another controller profile after reconnecting the device.

If no throttle input appears at all, follow our throttle-input troubleshooting sequence before repeating the A32NX calibration.

Finally, Airbus autothrust does not motor the physical or cockpit thrust levers. During normal flight the levers can remain in CLB while the system varies engine thrust; that behaviour is normal and is not evidence of failed calibration.