How do I calibrate the Thrustmaster TCA Airbus throttle quadrant?

To calibrate a Thrustmaster TCA Airbus throttle, first verify each lever’s full, smooth range in Windows, then bind the left and right levers once to engine 1 and engine 2 in your simulator. Keep both axes linear, then calibrate REV, IDLE, CL, FLEX/MCT and TOGA inside the Airbus aircraft.

This general PC workflow applies to Microsoft Flight Simulator 2020 and 2024, X-Plane, Prepar3D and FSX. The Windows checks are PC-only; console support and calibration options depend on the exact TCA package and connection method.

Which part of the TCA Airbus throttle needs calibrating?

The location of the fault tells you whether to correct the hardware, simulator profile or aircraft-specific detents.

If the problem exists in only one Airbus add-on, do not disturb otherwise correct Windows calibration. That aircraft almost certainly needs its own detent values.

How do you calibrate the TCA Airbus throttle step by step?

Calibrate the quadrant in hardware-to-aircraft order so that later settings are based on a clean, stable input.

1. Connect and initialise the quadrant. While troubleshooting, connect it directly to the PC rather than through an unpowered hub. Move both levers slowly through their complete travel once, including the below-idle range unlocked by the reverse levers. Complete the relevant driver, firmware and first-connection checks for the Airbus Quadrant before opening the simulator.
2. Inspect both raw axes in Windows. Press the Windows key, run joy.cpl, select the TCA quadrant and open its properties or test page. Move one thrust lever at a time from full reverse to TOGA. Each lever should control a separate indicator, cover the available range and remain steady when untouched. The two raw values do not have to be numerically identical.
3. Create a clean simulator profile. Assign the left lever to engine 1 throttle and the right lever to engine 2 throttle. Search all connected controllers for competing assignments and remove any combined throttle axis, duplicate engine axes or throttle increase/decrease command that acts on the same levers. Keep a combined axis only when you deliberately want one lever to control every engine.
4. Choose one reverse-thrust method. Use a full-range axis when the aircraft accepts continuous movement below idle and provides reverse detent calibration. Use a forward-only or 0–100% axis plus a reverse hold or toggle command when that aircraft expects button-controlled reverse. Do not configure both methods at once.
5. Check direction and response. Advancing a physical lever must advance the corresponding cockpit lever. Reverse the axis once in the simulator if it moves backwards. Start with a linear response, no saturation or extremity adjustment, and only enough dead zone to suppress confirmed raw jitter.
6. Record the aircraft detents. Open the Airbus add-on’s throttle calibration page and follow its requested order. This commonly includes full reverse, reverse idle, idle, CL, FLEX/MCT and TOGA. Calibrate both levers independently if separate engine values are offered, and use narrow, non-overlapping tolerance bands around each notch.
7. Test every gate in the cockpit. Move one lever at a time and confirm that its virtual lever reaches the correct detent at the physical notch. Then move both together and check that their indications agree, reverse begins only below idle, and neither engine jumps when a lever is released.

Microsoft Flight Simulator 2024 has its own profile and binding interface. Our exact MSFS 2024 axis, detent and reverse-thrust workflow covers those simulator-specific choices.

X-Plane users should run its built-in joystick calibration after confirming that Windows receives both axes. In Prepar3D and FSX, choose either the simulator’s native axis system or FSUIPC rather than assigning the same lever through both.

Why do the Thrustmaster Airbus throttle detents not line up?

Detents usually fail to align because the aircraft was not calibrated separately, the wrong axis type is assigned, or a response curve changed the values reaching the aircraft.

• One lever is correct and the other is not: confirm that the levers use separate engine 1 and engine 2 axes. Recalibrate each side independently rather than copying one lever’s raw values to the other.
• Both cockpit levers move from one physical lever: remove the combined throttle assignment or a duplicate binding on another controller.
• CL or FLEX/MCT flickers: use the aircraft’s detent tolerance or range setting. Add a simulator dead zone only when the Windows test shows genuine signal jitter.
• TOGA appears before the physical stop: remove sensitivity curves, saturation and extremity dead zones, then repeat the aircraft calibration.
• The cockpit lever moves backwards: reverse the simulator axis. Do not record the aircraft’s detents in reverse order to compensate.
• Idle enters reverse unexpectedly: narrow the idle and reverse-idle ranges so they do not overlap, then verify that the reverse lock is fully down at idle.

A mistake we see constantly is calibrating the aircraft first and then altering the simulator response. Any curve, endpoint or axis-type change alters the values saved for the detents, so the aircraft calibration must be repeated afterwards.

Some stock or simpler aircraft have no dedicated detent page. In that case, use the simulator’s intended TCA profile with a linear axis. If the endpoints are right but an intermediate notch remains wrong, a Windows recalibration will not fix an aircraft that lacks adjustable detent mapping.

Why is reverse thrust not working after calibration?

Reverse thrust fails when the selected axis type does not match the method expected by the aircraft.

If reverse works on only one engine, inspect that engine’s axis assignment and reverse calibration separately. If it activates before the physical reverse levers are lifted, correct the idle boundary rather than adding a large general dead zone.

Should I use Windows to calibrate the Thrustmaster throttle quadrant?

No, not routinely: use joy.cpl as a diagnostic test rather than automatically running the legacy Windows calibration wizard.

The TCA quadrant should normally report a complete raw range without Windows remapping it. Use a model-specific hardware recalibration process only when an axis also misses endpoints or behaves incorrectly on the Windows test page. Button combinations and reset procedures can differ by TCA model and firmware, so do not apply an unverified sequence intended for another Thrustmaster device.

If the raw input is faulty, reconnect directly, move each lever through its full range, confirm the correct device is selected, and check the driver and firmware. Curves and large dead zones can hide symptoms, but they cannot restore range that the hardware is not reporting.

Do I need to recalibrate the TCA throttle for every aircraft?

Hardware calibration is normally done once, but simulator profiles and Airbus detent values may need to be stored separately for each control system or aircraft.

• Repeat the hardware check after a firmware change, USB recognition problem or visible movement of the raw endpoints.
• Keep separate simulator profiles when aircraft use different axis types or reverse-thrust methods.
• Calibrate each complex Airbus add-on through its own EFB, tablet or MCDU because its saved detent ranges may not be shared with another aircraft.
• Use only one assignment system. If you configure the axes through FSUIPC’s separate throttle and reverse ranges, remove the equivalent native simulator assignments.

If calibration appears to vanish after every restart, first check that the intended controller profile is active and that no duplicate device has taken over the axes. Our guide to profiles, USB faults and recurring calibration loss covers the next checks without repeatedly changing good detent values.