How do I fix a Thrustmaster TCA Airbus flap axis?

If your Thrustmaster TCA Airbus flap lever does not work, check whether Windows sees its axis. No Windows input indicates module, cable, driver, firmware or USB trouble; Windows input but no simulator movement means bindings; reversed travel needs axis reversal; add-on-only detent errors need aircraft calibration. The lever requires the TCA Quadrant Add-On Airbus Edition.

This is a general PC flight-simulator diagnosis. The base TCA Quadrant Airbus Edition does not have a flap lever unless the add-on module is fitted; some larger TCA bundles include that module.

Thrustmaster Airbus flaps not working: symptoms and next actions

The Windows controller test separates a hardware fault from a simulator or aircraft configuration problem.

Fix the TCA Airbus flap lever in the right order

Start with the raw signal and work towards the aircraft, because sensitivity settings cannot repair an axis that Windows never receives.

1. Confirm that the flap module is present. The physical lever belongs to the TCA Quadrant Add-On Airbus Edition, not the base throttle quadrant by itself.
2. Reseat the add-on connection. Close the simulator, disconnect the quadrant from USB and reseat the cable between the flap module and the main quadrant. Reconnect it directly to the PC while testing, rather than through an unpowered hub.
3. Test it in Windows. Press Windows+R, enter joy.cpl, choose the TCA quadrant and open its properties. Move the lever slowly from UP to FULL and identify the indicator that follows it.
4. Interpret the result. No movement means the simulator is not yet relevant. If the main throttle axes work but the flap axis does not, concentrate on the add-on cable and flap module. If the entire quadrant is absent, concentrate on USB, the main unit, driver and firmware.
5. Repair detection before binding. Power-cycle the unit, try another direct USB port and install only the driver, firmware and calibration procedure intended for the exact TCA model. Our PC setup and firmware checklist for the TCA Airbus quadrant covers the full detection process.
6. Continue only after Windows is smooth. A complete, steady Windows range means the hardware is producing usable input; the remaining work is in the simulator profile or aircraft.

The TCA Boeing quadrant and Winwing panels use different hardware and calibration methods. The same Windows-versus-simulator diagnosis applies, but do not use an Airbus add-on cable check or a TCA Airbus calibration sequence on those products.

MSFS 2020 and MSFS 2024 Controls Options workflow

In Microsoft Flight Simulator 2020 or 2024, select the TCA quadrant itself and assign exactly one continuous flap axis.

1. Open Controls Options. Enter the controls screen from the simulator's main Options or Settings area, then select the TCA quadrant rather than the sidestick, keyboard or another throttle.
2. Choose a clean profile or preset. Create an editable test profile if the active one contains inherited assignments. Confirm that this is the profile active for the aircraft being tested.
3. Show all flap assignments. Set the control filter to display all commands and search for flap. Also use the search-by-input function, where available, while moving the physical lever.
4. Clear conflicts everywhere. Inspect every connected controller, including the joystick, throttle, quadrant, keyboard and any virtual controller. Remove other flap axes and the commands Increment Flaps, Decrease Flaps, Flaps Up and Flaps Down while testing.
5. Bind the first analogue option. Assign the lever to FLAPS AXIS (-100 TO 100%), save the profile and test the complete range in a default aircraft.
6. Try the alternative when necessary. If the first command gives half travel, a compressed range or no useful response, remove it and bind FLAPS AXIS (0 TO 100%) instead. Never keep both flap-axis variants assigned together.
7. Correct the direction. If UP commands FULL, use the Reverse Axis or equivalent invert option for that binding. Do not repeatedly swap endpoints or create an extreme sensitivity curve merely to reverse it.
8. Check each position. Move the lever through UP, 1, 2, 3 and FULL while watching the cockpit lever. Start with a linear response and little or no dead zone; adjust only after the correct command and direction are established.

A mistake we see constantly is leaving a flap button on the joystick while adding the analogue axis to the quadrant. The button can override the lever, making an otherwise healthy axis jump or appear not to work. If the entire TCA unit is missing from the controls screen, use our MSFS checklist for missing TCA input and controller profiles before editing sensitivity.

Fenix A320 flaps axis not working

If the Fenix A320 flap axis is not working, prove the native MSFS input first and use the aircraft's own control calibration only after that test passes.

1. Verify the lever in Windows. Open joy.cpl and confirm smooth movement from both endpoints. Stop here if the axis is missing or erratic.
2. Test the same profile in a default MSFS aircraft. Do not change the binding between tests. If the cockpit flap lever moves correctly there, the TCA module, USB input and MSFS axis are functioning.
3. Keep one native MSFS axis. Use either FLAPS AXIS (-100 TO 100%) or FLAPS AXIS (0 TO 100%), whichever gave full travel in the default aircraft. Do not bind both.
4. Remove every competing flap control. Search all physical and virtual devices for other flap axes, incremental flap commands and UP/DOWN buttons. Controller software that creates a virtual device can otherwise send the same lever twice.
5. Use the Fenix calibration provided by the installed version. If the aircraft or EFB exposes a flap control, hardware or detent calibration, place the physical lever in each requested position and save it there.
6. Avoid forcing detents with sensitivity curves. Curves alter the whole axis and can make one detent work while breaking another. If the default aircraft still works but Fenix does not after aircraft calibration, the problem is confined to the Fenix control configuration rather than the quadrant.

Setting the Thrustmaster flap lever in the FBW A320

The FBW A320 should first be tested with the same single native MSFS flap axis used in a default aircraft.

Bind either of the two MSFS analogue alternatives, remove all digital flap commands and check UP through FULL in the cockpit. Do not assign separate buttons for each mechanical detent or use throttle-detent calibration for the flap lever; they are different controls.

If the default aircraft responds but the FBW A320 does not, retain the known-good MSFS profile and inspect the aircraft's own control options for an override or calibration feature. A cockpit indication of 1+F after selecting lever position 1 can be normal Airbus logic based on flight phase and speed; it does not by itself prove that the TCA detent is wrong.

How do I configure the flap axis in X-Plane 12?

In X-Plane 12, calibrate the controller first, assign the physical lever to Flaps, and reverse it only if cockpit movement runs in the wrong direction.

1. Open the joystick settings. Go to X-Plane 12's Settings and select the Joystick page, then choose the TCA quadrant if more than one controller is connected.
2. Run joystick calibration. Move the flap lever through its entire travel when prompted, along with any other axes required by the calibration screen. Complete and accept the calibration before adding curves.
3. Identify the moving axis. Move only the flap lever and watch which axis bar responds. Assign that axis to Flaps.
4. Reverse it when needed. Load an aircraft and compare the physical and cockpit levers. Enable the axis reverse option if UP and FULL are exchanged.
5. Remove duplicate assignments. Check the remaining axes on every connected controller for another Flaps assignment. Also remove conflicting flap buttons while diagnosing the problem.
6. Test a stock aircraft. If the stock aircraft follows the full axis but a third-party Airbus does not, the add-on's custom input handling or detent configuration is responsible. Do not recalibrate healthy hardware merely for one aircraft.

What about FSX and Prepar3D v5?

FSX and Prepar3D v5 should use their analogue Flaps Axis assignment rather than incremental flap buttons.

Open the simulator's controls or axis-assignment page, select the TCA quadrant and bind the moving lever to the flaps axis. Remove old flap assignments from other controllers, then test the endpoints and direction in a default aircraft before loading an Airbus add-on.

If FSUIPC manages the lever, choose one input path: assign and calibrate it through FSUIPC, or assign it directly in the simulator, but not both. Our guide to checking raw movement, endpoints and flap-axis calibration in FSUIPC explains that method. A double assignment through FSUIPC and the simulator can cause flickering, delayed movement or an axis that immediately returns to another position.

Why do the Airbus flap detents not line up?

Misaligned UP, 1, 2, 3 and FULL positions mean the axis is detected, but its usable range or detent bands do not match the aircraft.

Check the Windows endpoints before touching sensitivity. If Windows cannot reach both ends, use only the model-specific hardware calibration procedure; calibration sequences differ between TCA products. If Windows reaches both ends, select the correct simulator axis variant, use a linear response and keep the dead zone small.

Detailed aircraft may divide the axis into their own detent zones. Use an aircraft or EFB calibration tool when one is provided. Large dead zones and steep sensitivity curves are poor substitutes because they can collapse two physical positions into one commanded flap setting.

How can I tell whether the flap module is faulty?

The flap module, cable, firmware or USB connection is the likely fault only when the input is also absent, incomplete or unstable in Windows.

• No flap movement but the throttles work: reseat the add-on interconnection cable and suspect the flap module or its connection if the fault remains.
• The whole quadrant is missing: test another direct USB port, the main USB connection, driver and model-specific firmware.
• The axis spikes in Windows: disconnect hubs and retest with the cable firmly seated. Persistent spikes indicate a connection or module fault rather than an aircraft profile.
• Windows shows only part of the range: run the official calibration intended for that exact model. If the endpoint remains missing, the module or connection is suspect.
• Windows movement is full and smooth: do not replace the module. Return to the active simulator profile, analogue axis choice, reverse option and duplicate bindings.
• Every default aircraft works: the hardware is serviceable; configure the affected add-on's custom controls or detent calibration.