How do I calibrate FlyByWire A32NX throttles in MSFS?

To calibrate FlyByWire A32NX throttles in Microsoft Flight Simulator, bind each lever to the correct analogue axis, remove duplicate assignments, then use the flyPad EFB to capture IDLE, CL/CLB, FLX/MCT, TOGA and any physical reverse detents. Save the calibration and check that 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 for a single physical lever.

1. Create an A32NX control profile. A dedicated profile prevents conventional-aircraft bindings from interfering with Airbus detents. MSFS 2020 and 2024 organise profiles differently, so confirm that the intended profile is active after reconnecting a controller.
2. Assign the analogue axes. Bind the left lever to THROTTLE 1 AXIS (0 TO 100%) and the right lever to THROTTLE 2 AXIS (0 TO 100%), or their equivalent names in your simulator version. With one lever, use THROTTLE AXIS (0 TO 100%).
3. Remove conflicting inputs. Clear legacy or full-range throttle axes, the combined axis when using separate levers, digital increase/decrease commands and unwanted assignments on gamepads or joysticks. One physical lever bound to both a combined and individual engine axis is a common cause of jumping.
4. Check direction and travel. Each input indicator should move smoothly from minimum to maximum. Invert an axis only if its cockpit lever moves backwards, and invert it in one place rather than in both device software and MSFS.
5. Begin with a linear response. Avoid copied sensitivity curves and large extremity dead zones. Use only enough central or endpoint adjustment to correct a demonstrated hardware problem.

Our A32NX axis and keybinding walkthrough covers profile selection, separate engine inputs and duplicate-binding removal in more detail. If the raw input misses an endpoint or jitters before the aircraft is loaded, complete the hardware and base MSFS throttle checks first.

Thrustmaster Airbus quadrant owners should use the same layered approach, but the physical detent and reverse arrangement needs device-specific handling; see our TCA Airbus calibration steps.

Should I calibrate the hardware, MSFS or the flyPad?

Use all three layers, but give each one a separate job.

• Hardware calibration corrects missing endpoints and irregular raw movement.
• MSFS controls handle axis assignments, direction, conflicts and small dead zones for genuine sensor noise.
• A32NX flyPad calibration maps that clean signal to Airbus thrust detents and reverse travel.

Repeat the flyPad calibration after changing hardware calibration, axis inversion, sensitivity, dead zones or controller assignments.

How do I calibrate A32NX detents in the flyPad?

Open the throttle-calibration or throttle-configuration page in the FlyByWire flyPad and record each physical gate in order.

1. Load the correct aircraft. Park the FlyByWire A32NX with the engines shut down, open the flyPad and look under its settings or aircraft area. The exact tab and button names vary between flyPad builds. If the page is absent, make sure the loaded aircraft is the FlyByWire model rather than the stock A320neo.
2. Select the axis arrangement. Choose independent or separate calibration for two individually bound levers. Keep the inputs linked when one physical axis controls both engines.
3. Inspect the live input. Move every lever slowly through its complete travel. Stop if a value jumps, travels backwards or cannot reach an endpoint; flyPad calibration cannot repair a missing, duplicated or unstable simulator input.
4. Configure reverse thrust. Enable reverse on axis only when the hardware has a real section below its idle gate. Otherwise leave it disabled and use a separate hold or toggle reverse command.
5. Capture every detent. Place the levers firmly at IDLE, CL or CLB, FLX/MCT and TOGA, then record the displayed position for each gate. With independent axes enabled, calibrate both engines separately.
6. Set usable ranges. If the flyPad requests lower and upper values, capture the edges of each physical notch rather than entering the same value twice. Allow enough width for minor sensor noise without overlapping adjacent ranges, especially CL and FLX/MCT.
7. Save and verify. Apply the settings, sweep the throttles slowly through their full travel and confirm that both virtual levers enter each named gate together without flickering, lagging or stopping short.

Do not copy another simmer’s raw calibration values. Endpoints and notch positions can differ even between two quadrants of the same model.

How should reverse thrust be calibrated?

Match the A32NX reverse setting to how the hardware physically reports its below-idle movement.

Use the A32NX 0–100% bindings by default, including for quadrants whose physical travel extends below idle; the flyPad maps that travel to reverse. Do not create an axis-based reverse section on a forward-only lever, as this compresses the usable range and often makes IDLE unreliable.

How can I tell whether the calibration is correct?

A correct calibration makes both cockpit levers track smoothly and settle positively in each gate.

• Physical idle must not produce reverse thrust.
• Both levers should remain in CL/CLB without flickering towards manual thrust or MCT.
• FLX/MCT should be recognised correctly when a valid flex take-off is configured.
• TOGA must be reached before the hardware runs out of travel.
• Reverse should begin only below idle and reach its calibrated maximum during a ground check.

Airbus autothrust does not motor the physical or cockpit thrust levers. In normal two-engine flight, the levers can remain in CL while autothrust varies engine output; that is normal. If the flight-mode annunciator still requests LVR CLB while the hardware is in the CL notch, its captured range is misplaced or too narrow.

Why do A32NX throttle detents jump or disagree?

Jumping, mismatched or missing detents usually indicate duplicate bindings, narrow calibration bands, axis noise or different endpoints between the two levers.

If the problem affects other aircraft or no throttle signal appears at all, follow our systematic MSFS throttle-input checks before recalibrating the A32NX. Aircraft-side detent mapping cannot fix an inactive, duplicated or unstable simulator axis.