How do I calibrate a Thrustmaster TCA Airbus throttle?

Calibrate a Thrustmaster TCA Airbus throttle in three layers: confirm both lever axes reach their full range in Windows, assign each engine axis only once in the flight simulator, then teach the Airbus aircraft its REV, IDLE, CL, FLEX/MCT and TOGA detents. Keep the response linear before adding small dead zones.

This general workflow applies to Microsoft Flight Simulator 2020 and 2024, X-Plane, Prepar3D and FSX. Control names differ slightly, but the distinction between hardware, simulator and aircraft calibration remains the same.

What has to be calibrated?

The TCA throttle can be correct at the hardware level yet still have incorrect detents inside a particular Airbus add-on.

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

1. Connect the quadrant directly. Use a direct USB connection while troubleshooting and install any driver or firmware offered specifically for your TCA model. Avoid changing firmware or hardware calibration while the simulator is running.
2. Test both raw axes in Windows. Open joy.cpl, select the throttle and inspect its test page. Move one lever at a time from full reverse to TOGA. Each lever should operate a separate axis, reach both endpoints and remain steady when untouched. Our Windows controller input test procedure explains what to check before changing simulator settings.
3. Create a clean simulator profile. Remove any combined throttle assignment, duplicate engine axes and throttle increase/decrease button bindings. For a twin-engine Airbus, bind the left lever to the engine 1 throttle axis and the right lever to engine 2. Use a combined throttle axis only for aircraft where both engines are deliberately controlled together.
4. Check direction and full travel. Advance each physical lever and watch its cockpit counterpart. Enable the simulator's reverse-axis option only if forward movement produces decreasing thrust. Do not use a sensitivity curve to hide an axis that fails to reach its raw endpoints.
5. Start with a linear response. Set sensitivity or response curves to neutral and use the smallest dead zone that stops genuine jitter. Large dead zones and curved responses compress the travel between Airbus detents, making accurate alignment harder.
6. Calibrate the aircraft detents. Open the aircraft's EFB, MCDU, tablet or throttle-calibration page if one is provided. Record each position in the order requested, normally including reverse, idle, CL, FLEX/MCT and TOGA. Some aircraft also let you set a tolerance around each detent so minor hardware variation does not make the annunciation flicker.
7. Verify the result in the cockpit. Move one lever at a time through every gate. Confirm that the displayed detent changes at the physical notch, both engines agree and reverse appears only after lifting the reverse levers. Airbus autothrust does not normally move the physical throttle levers; during flight they usually remain in the selected detent.

Microsoft Flight Simulator 2024 users can follow our complete TCA profile, axis and detent setup for the simulator-specific controls workflow.

Why do the Airbus throttle detents not line up?

Misaligned detents usually mean the aircraft has not been calibrated separately, or a simulator curve is altering the axis after calibration.

• One lever is correct and the other is not: check that engine 1 and engine 2 use separate axes, then recalibrate both sides independently.
• CL or FLEX/MCT flickers: add a small detent tolerance in the aircraft calibration page, or a minimal dead zone if the raw signal itself jitters.
• TOGA arrives too early: return the simulator response to linear and remove excessive extremity or saturation adjustments.
• Both cockpit levers move from one physical lever: delete the combined throttle assignment or another controller's duplicate binding.
• The cockpit lever moves backwards: reverse that axis in the simulator; do not recalibrate the physical detents backwards.

A mistake we see constantly is calibrating the Airbus add-on first and then changing the simulator sensitivity. Any subsequent curve or endpoint adjustment invalidates the aircraft's saved detent values, so repeat the aircraft calibration after changing axis response.

Why is reverse thrust not working?

Reverse thrust fails when the simulator or aircraft expects a different control method from the one assigned to the TCA's below-idle range.

Some aircraft accept a continuous axis extending below idle. Others expect a reverse toggle or hold command, followed by forward movement of the throttle axis. Use one method unless the aircraft's control instructions explicitly require both; combining them can produce stuck reverse thrust or an unexpected jump to maximum reverse.

In Microsoft Flight Simulator, our TCA reverse-range configuration guide covers split engine axes, the idle gate and the alternative button-based method.

Do I need to recalibrate for every aircraft?

Hardware calibration is normally done once, but simulator profiles and Airbus detent calibration may need to be saved separately.

• Repeat the hardware check only after a firmware change, a Windows calibration change or evidence that the raw endpoints have moved.
• Create a profile per simulator because MSFS, X-Plane, Prepar3D and FSX interpret axis ranges and reverse thrust differently.
• Calibrate each complex Airbus add-on through its own cockpit or tablet utility. One aircraft's saved CL and FLEX/MCT values are not guaranteed to suit another.

Do not run the legacy Windows calibration wizard merely because the detents are wrong in one aircraft. If the Windows test already shows smooth, complete travel, leave the raw hardware calibration alone and correct the simulator profile or aircraft-specific detent settings instead.