How do I set up a Thrustmaster T.16000M joystick?

For general PC flight simulation, connect the Thrustmaster T.16000M directly to the computer, verify every axis in Windows, then create a dedicated simulator profile. Assign X to ailerons, Y to elevators, twist to rudder and the base slider to throttle; clear duplicate bindings, check direction, and add only the smallest dead zone needed.

This method applies to both the original T.16000M and the T.16000M FCS, although button labels and the displayed device name can differ. It is designed as a PC USB controller; plugging it into an Xbox or PlayStation does not make it a supported console joystick.

Set up the T.16000M in the right order

A reliable setup begins with clean Windows input and ends with testing inside the aircraft.

1. Prepare the grip: Install the supplied left- or right-handed thumb-rest pieces as required, place the base on a stable surface and make sure nothing presses against the stick. The twist grip should return to centre without catching.
2. Connect it directly: Use a computer USB port rather than an unpowered hub during initial configuration. Leave the stick centred while Windows detects it, and temporarily disconnect controllers that could be mistaken for the T.16000M.
3. Test it in Windows: Press the Windows key, run joy.cpl, select the joystick and open its properties. Move the stick, twist grip and slider through their complete ranges, then press every button and POV-hat direction. Our Windows controller testing checklist explains what to check when an axis or button does not register.
4. Create a simulator profile: Make a separate T.16000M profile instead of modifying an unknown default mapping. Simulator-specific menus differ; follow the profile and binding procedure for Microsoft Flight Simulator 2020 and 2024 or the calibration process used by X-Plane 12.
5. Clear automatic assignments: Remove unwanted mappings before adding your own. A mistake we see constantly is the twist grip controlling both rudder and cockpit view, or the slider being assigned to throttle while another device also controls the same axis.
6. Bind analogue axes: Select commands labelled Axis, not digital commands such as “Aileron Left”, “Rudder Right” or “Throttle Increase”. Move the physical control when the simulator asks for an input rather than relying on button numbers.
7. Validate the profile: Load a simple aircraft, keep the engine off and watch the cockpit controls or external control surfaces. Confirm smooth movement, correct direction, a neutral centre and full travel before taxiing.

If an axis moves backwards, use the simulator's Reverse Axis option rather than remapping it as two buttons. With only one slider, use a combined throttle command for multi-engine aircraft unless you deliberately want to control one engine at a time.

Which T.16000M buttons should I assign?

Put flight-critical controls on the grip and less urgent functions on the base buttons.

• POV hat: Cockpit view panning if you do not use head tracking.
• Trigger: Wheel brakes, push-to-talk or another frequently held command.
• Grip buttons: Elevator trim up and down, autopilot disconnect, view reset or weapon controls in a combat profile.
• Base buttons: Flaps, landing gear, parking brake, airbrake, mixture presets and engine functions.

Create separate profiles for airliners, light aircraft, helicopters and combat aircraft instead of forcing one button layout onto everything. Keep commands needed during a landing on the grip because reaching for a base button can disturb the stick.

If you have a TWCS throttle, bind its main lever to throttle and remove the T.16000M base slider's duplicate throttle assignment. With rudder pedals, bind the pedal yaw axis and unbind joystick twist from rudder; otherwise tiny twist inputs can fight the pedals.

Do I need Thrustmaster TARGET software?

No, TARGET is unnecessary for an ordinary T.16000M flight-simulator setup because modern PC simulators can bind the joystick directly.

Use TARGET only when you need advanced modifiers, macros or a virtual combined controller. If you do use it, run the chosen TARGET profile before opening the simulator and bind the resulting virtual device. Binding both the virtual controller and the physical T.16000M can produce doubled inputs, unexplained full deflection or controls that stop working when TARGET is closed.

Adding TARGET to fix a basic axis problem usually makes diagnosis harder. Confirm that the raw joystick behaves correctly in Windows before introducing another software layer.

What sensitivity and dead-zone settings work best?

Start with a linear response and no dead zone, then change only what the aircraft and hardware actually require.

• Pitch and roll: The Hall-sensor X and Y axes should normally need little or no dead zone. Add the smallest amount that prevents unwanted movement while the stick is released.
• Twist rudder: Use a slightly larger dead zone only if resting your hand on the grip causes accidental yaw. A dead zone can hide small centre noise, but it cannot repair severe spikes.
• Response curve: Soften the centre modestly for airliners and general aviation if precise corrections are difficult. Aerobatic and combat aircraft generally benefit from a more linear response.
• Endpoints: Make sure every axis can still reach full output. Excessive curve or range reduction can prevent full elevator, aileron, rudder or throttle travel.

Change curves in either the simulator or controller software, not both. For a fuller explanation of dead zones, reversed axes and conflicting inputs, use our simulator-agnostic joystick calibration guidance.

Why is the T.16000M drifting or not working correctly?

Most T.16000M problems come from duplicate assignments, an incorrect axis type, USB detection or noise on the twist axis.

Do not compensate for a genuine hardware spike with an enormous dead zone or extreme curve. If the same erratic movement appears in the Windows test panel, the fault exists before the simulator processes the input.