Why is my Thrustmaster TCA Airbus not working in MSFS?
If a Thrustmaster TCA Airbus sidestick or throttle quadrant does not work in Microsoft Flight Simulator, first check that Windows sees live axis movement, then create a device-specific MSFS control profile and bind the correct axes. Most failures come from USB detection, an empty profile, duplicate assignments, or incorrect throttle-axis and detent calibration.
Find where the TCA input stops
The result of one Windows input test usually identifies whether the fault is outside Microsoft Flight Simulator or inside its control settings.
| What you see | Likely cause | Next action |
|---|---|---|
| The TCA is absent from Windows | USB, firmware, mode or hardware problem | Reconnect it directly and check its platform selector |
| Axes move in Windows but not MSFS | Wrong or empty control profile | Select the TCA device and bind its axes |
| MSFS detects movement but the aircraft ignores it | Duplicate binding, assistance setting or aircraft-specific profile | Remove conflicts and test a stock aircraft |
| The control works but has the wrong range | Axis polarity, sensitivity or detent calibration | Correct the axis type before calibrating detents |
How do I fix a TCA device that Windows cannot detect?
On PC, Microsoft Flight Simulator cannot use a controller that Windows does not recognise reliably.
- Close MSFS completely. Reconnecting a controller while the simulator is running can leave the old device state or profile loaded.
- Connect the controller directly. Use a known-good USB port rather than an unpowered hub, extension or monitor port. If the cable is detachable, reseat both ends.
- Check the mode selector. If your particular TCA model has PC and console modes, select the mode matching your platform. A quadrant with an engine-pair selector should normally be on 1&2 when it is the only quadrant.
- Open the Windows controller panel. Press the Windows key, enter
joy.cpl, open the TCA device and move every lever and axis. Our guide to checking controller axes and buttons in Windows explains what a healthy input should show. Use this panel for testing; do not start recalibrating until the basic signal is confirmed. - Update the correct driver and firmware. Use the software intended for the exact TCA model and follow its connection prompts. Restart Windows afterwards, especially if the device name or mode has changed.
The sidestick and throttle quadrant are separate USB controllers on most PC arrangements, so each directly connected unit should appear separately. If one appears and the other does not, concentrate on the missing unit's cable, USB port, mode and firmware rather than changing MSFS bindings.
Intermittent disconnections point to USB power management, a weak hub or a damaged connection. Test another direct port with other non-essential controllers disconnected before assuming that the profile is corrupt.
How do I bind the TCA sidestick and throttle correctly?
Once Windows shows live input, select the physical TCA device in MSFS and save the axes to the profile that is active for the aircraft being flown.
- Open Controls. In MSFS 2020, select the TCA device and its control preset. MSFS 2024 can apply device and aircraft-specific profiles, so confirm that the profile you edit is also assigned to the aircraft you load.
- Display all assignments. An “assigned” filter can hide unbound commands and make the controller appear unsupported. Use the input-search or scan function where available.
- Bind the sidestick axes. Assign the stick to Ailerons Axis and Elevator Axis. Assign its twist to Rudder Axis only when you intend to use twist rudder; remove that assignment when using separate pedals.
- Bind each throttle lever separately. For a twin-engine aircraft, the left lever normally uses Throttle 1 Axis and the right lever uses Throttle 2 Axis. Do not substitute digital commands such as throttle increase and decrease.
- Save and test. Apply the profile, load a stock aircraft on a runway with its engines running, and confirm that the cockpit controls follow the hardware.
Use a full-range throttle axis when reverse thrust occupies part of the lever travel. Use a 0-to-100-percent axis when reverse is operated through a separate button or aircraft-specific system. Binding both methods at once commonly causes jumps around idle. For the full profile procedure, see our detailed TCA axis and detent setup for MSFS 2024.
Why does MSFS detect the controller but the aircraft ignore it?
If the MSFS input indicator moves but the cockpit control does not, another assignment or an aircraft system is usually overriding the TCA input.
- Duplicate axes: search by input and inspect every connected device. A gamepad stick, joystick slider or old quadrant profile assigned to the same axis can make the control freeze, jump or snap back.
- Assisted control: disable AI piloting and any assistance option that takes over flight or throttle control while testing.
- Extreme sensitivity: a very large dead zone or incorrect extremity setting can suppress most of an axis. Return the axis response close to its default shape for diagnosis.
- Aircraft-specific mappings: an add-on aircraft may use its own throttle calibration or commands. If the TCA works in a stock aircraft, the USB device and general binding are sound; inspect that aircraft's profile and calibration instead.
- Autopilot and autothrust: these systems can make the aircraft respond differently from a conventional aeroplane. In an Airbus, the thrust levers select detents while autothrust controls engine output, so engine thrust need not vary continuously with lever movement.
A mistake we see constantly is editing one controller tile while testing another, or saving a new preset without making it active. Disconnecting other controllers temporarily is the quickest way to expose this.
When a clean profile is the quickest fix
A fresh profile is appropriate when assignments are duplicated, inexplicable or inherited from older hardware. Create a clean preset and bind only aileron, elevator, rudder and the two throttle axes; add buttons and switches only after those work.
If even a clean preset behaves incorrectly, follow our steps for clearing or rebuilding MSFS controller bindings. Resetting should come after the Windows test, because it cannot repair a missing USB device.
Why are the Airbus throttle detents or reverse thrust wrong?
Detent and reverse-thrust faults require axis calibration, not another driver installation, provided both levers already move through their full range.
| Symptom | Check |
|---|---|
| Both levers operate engine 1 | Remove the duplicate assignment and bind the right lever to Throttle 2 Axis |
| Idle produces reverse thrust | Check axis polarity and recalibrate the idle and reverse zones |
| Full forward gives only partial thrust | Restore sensitivity and extremity settings, then verify the chosen axis range |
| CL, FLX/MCT or TOGA does not align | Use the aircraft's own throttle-calibration page when it provides one |
| Reverse engages twice or jumps | Choose either axis-based reverse or a separate reverse command, not both |
The MSFS Reverse Axis option changes input polarity; it does not itself enable reverse thrust. Calibrate the basic forward range first, then define Airbus detents through the aircraft's tablet, EFB or cockpit calibration tool if one is supplied.
Console compatibility
Console support depends on the exact TCA model, not merely the Airbus branding. Xbox requires an Xbox-compatible version, while a PC-only or Xbox-labelled controller should not be assumed to work on PlayStation 5. MSFS 2020 has no PlayStation version; MSFS 2024 does, but the connected controller still needs explicit PS5 compatibility.
On Xbox, fully quit Microsoft Flight Simulator rather than resuming a suspended session, connect the supported controller, and then restart the simulator. Console profiles cannot compensate for hardware that was not designed for that platform.