How do I calibrate the A32NX throttle in MSFS?

To calibrate a throttle for the FlyByWire A32NX in Microsoft Flight Simulator, bind each lever to the correct analogue axis, remove duplicate assignments, then use the EFB’s throttle-calibration page to capture IDLE, CL, FLX/MCT, TOGA and reverse detents. Save the profile and confirm both cockpit levers track smoothly.

How do you calibrate the FlyByWire A32NX throttle?

The A32NX calibration works only after Microsoft Flight Simulator is supplying a clean, correctly directed axis signal. Perform the simulator assignment first, then teach the aircraft where each Airbus detent sits.

1. Load the FlyByWire A32NX. Park at a stand with the engines shut down. The tablet calibration belongs to the FlyByWire aircraft, not the stock A320neo; if the page is missing, confirm the A32NX package and installation.
2. Create or select the correct controls profile. Microsoft Flight Simulator 2020 and 2024 organise profiles differently, so check that the active profile belongs to the throttle device and aircraft you are using.
3. Assign analogue throttle axes. For two levers, bind them separately to THROTTLE 1 AXIS and THROTTLE 2 AXIS, using the equivalent names presented by your simulator version. A single lever should use the combined analogue throttle axis that drives both engines.
4. Remove conflicting bindings. Search by input and clear duplicate throttle axes, increase/decrease commands and unwanted reverse-thrust assignments. A mistake we see constantly is one physical lever being bound to both a combined axis and an individual engine axis.
5. Check direction and travel. Move each lever slowly from minimum to maximum in the controls screen. The indicator must travel smoothly through its full range. Invert the axis once if necessary, then leave inversion unchanged for the rest of the calibration.
6. Open the A32NX throttle-calibration page. On the flyPad EFB, open Settings and select the throttle-calibration section. The tab arrangement or button wording may vary between A32NX builds.
7. Choose the axis arrangement. Enable independent or separate axes when two physical levers supply two different inputs. Keep the levers linked when using one throttle axis for both engines.
8. Configure reverse thrust. Enable the reverser-on-axis option only when the physical lever actually travels below idle into a reverse range. Otherwise disable it and use a separate hold or toggle reverse command.
9. Capture every detent. Move the hardware to each marked position and use the EFB’s capture or set-from-throttle control for IDLE, CL, FLX/MCT and TOGA. Capture reverse idle and full reverse as well when reverse is on the axis.
10. Set usable detent ranges. If the EFB requests upper and lower limits, record the two edges of the physical detent rather than the same exact value twice. Keep neighbouring ranges separate; CL must not overlap FLX/MCT.
11. Save and verify. Use the page’s save or apply control, then move through the complete range. Both virtual thrust levers should enter each labelled detent without jumping, lagging or stopping short.

Which throttle axis should I bind?

Use a combined analogue axis for one physical lever and separate engine axes for a dual-lever quadrant. Whether reverse belongs on that axis depends on how the hardware reports its reverse section.

When both full-range and 0–100% axis variants are available, use the full-range form if reverse is physically part of the axis travel. A forward-only axis is appropriate when reverse is controlled separately. The decisive check is the live input shown by the EFB: it must move continuously across every position you intend to capture.

Should I calibrate the hardware, MSFS or the EFB?

Use all three calibration layers, but only for the job each layer performs. Hardware calibration fixes missing endpoints, MSFS controls handle assignments and inversion, and the A32NX EFB maps the resulting signal to Airbus detents.

• Hardware layer: Recalibrate the device using its own supported method if the raw axis cannot reach both endpoints or moves irregularly outside the simulator.
• Microsoft Flight Simulator layer: Assign axes, remove conflicts and apply only enough dead zone to suppress genuine sensor jitter. Start with a linear response rather than copying another user’s sensitivity values.
• A32NX layer: Capture the aircraft’s detents and reverse range. Repeat this step after changing inversion, sensitivity, dead zones or the physical hardware calibration.

Thrustmaster TCA owners can follow our three-layer TCA Airbus calibration workflow for the hardware-specific part before recording A32NX detents.

How can I tell whether the calibration is correct?

A correct calibration makes the virtual levers settle positively into every detent while both engines remain synchronised. Check the cockpit levers and Airbus indications rather than relying only on the physical markings.

• At physical idle, neither virtual lever should enter reverse.
• At CL, both cockpit levers should sit exactly in the CL gate without flickering towards MCT.
• FLX/MCT should produce the expected manual thrust mode when a flex take-off is configured.
• TOGA should reach the top detent without running out of physical travel.
• Reverse should begin only after the lever crosses below idle and should reach its calibrated maximum on the ground.

During normal two-engine flight with autothrust, the levers usually remain in CL. If the flight-mode annunciator continues to request LVR CLB while the hardware is physically in the CL notch, the captured CL range is misplaced or too narrow.

Why does the A32NX throttle jump or miss detents?

Most A32NX throttle faults come from overlapping assignments, an unstable axis or detent ranges that are too narrow. Match the symptom to the likely cause before recalibrating everything.

If the problem is not confined to A32NX detents, use our systematic MSFS throttle-input checks before returning to the EFB. Aircraft-side calibration cannot repair an axis that is missing, duplicated or unstable at simulator level.