See the Thrustmaster T16000M button layout, recommended axis and button mappings, plus fixes for reversed, drifting or duplicate controls.
The Thrustmaster T.16000M FCS provides X/Y stick movement, twist rudder, a throttle slider, an eight-way POV hat and 16 buttons. For general PC flight simulators, map X to ailerons, Y to elevator, twist to rudder and the slider to a combined throttle axis; assign buttons by reach and frequency of use.
What is the T16000M button layout?
The standalone joystick exposes four analogue axes, one POV hat and 16 numbered buttons; the hat is normally reported separately rather than as eight additional buttons.
| Physical control | Reported input | Recommended assignment |
|---|---|---|
| Stick left and right | X axis | Ailerons or roll axis |
| Stick forwards and backwards | Y axis | Elevator or pitch axis |
| Twist grip | Rotation or rudder axis | Rudder or yaw axis |
| Base slider | Slider or throttle axis | Combined throttle axis |
| Eight-way hat | POV hat | View panning or trim |
| Button 1 | Trigger | Wheel brakes, push-to-talk or weapons |
| Buttons 2–4 | Three grip buttons | Trim, view reset or autopilot disconnect |
| Buttons 5–10 | Left base bank | Flaps, gear and other secondary controls |
| Buttons 11–16 | Right base bank | Lights, parking brake and secondary controls |
That numbering describes the normal unmodified DirectInput layout. The base numbers run around each six-button cluster rather than in simple reading order, while TARGET profiles or virtual-controller software can present different identifiers. The POV diagonals are hat directions, not eight independent push-buttons.
Set the right- or left-handed selector and fit the appropriate thumb rest before creating profiles. This description covers the joystick itself; a TWCS throttle or separate pedals introduce additional axes and buttons that must be mapped independently.
How do I map the T16000M in a flight simulator?
Build a clean device profile and assign each analogue control before touching the buttons. If Windows or the simulator does not detect the stick correctly, use our Windows and profile setup for the T.16000M before attempting to map it.
- Connect and identify the joystick. Move the stick, twist grip and slider in the simulator's control screen to confirm which input responds. Use the simulator's input-scanning function where available rather than relying entirely on displayed axis names.
- Create a fresh device preset. Keep the original default preset intact, then remove unwanted automatic assignments from the new profile. Do not clear profiles belonging to unrelated controllers.
- Assign analogue commands. Bind X to aileron axis, Y to elevator axis, twist to rudder axis and the slider to the combined throttle axis. Choose commands containing Axis, not digital commands such as aileron left, throttle increase or rudder right.
- Check direction and full travel. Pulling the stick back must command nose-up elevator, twisting right must command right rudder, and pushing the slider forwards should increase power. Reverse only the affected axis when one moves backwards.
- Remove competing axes. If rudder pedals are fitted, unbind the joystick twist from rudder. Likewise, remove throttle from the slider when a separate throttle quadrant controls power.
- Set sensitivity conservatively. Begin with a linear response and little or no dead zone. Add only enough centre dead zone to stop genuine drift; excessive dead zone makes small corrections difficult.
- Assign and save the buttons. Map essential grip controls first, test them in the aircraft, then add base commands. Save separate general aviation, airliner or combat profiles where the simulator supports them.
Microsoft Flight Simulator handles presets and duplicate assignments differently from some older simulators. Our MSFS 2020 and 2024 joystick profile workflow covers the simulator-specific process without requiring TARGET.
Which T16000M button assignments work best?
Keep time-critical commands on the grip and place infrequent aircraft systems on the base.
- POV hat: use it for cockpit views when flying without head tracking. With head tracking, it can handle elevator trim and any other trim commands the aircraft actually supports.
- Trigger: combined wheel brakes are practical for civilian aircraft without toe-brake pedals. Combat profiles normally reserve it for the primary weapon.
- Grip buttons 2–4: good choices include elevator trim up and down, push-to-talk, autopilot disconnect and view reset.
- Base buttons 5–16: use paired buttons for flaps up/down, spoilers extend/retract or lighting controls. Landing gear, parking brake and pause also suit the base because they are not adjusted continuously.
- Throttle slider: map it to the combined throttle command when flying multi-engine aircraft with one physical lever. Binding it only to Engine 1 leaves the other engines unchanged.
If a dedicated throttle is installed, the slider can instead control mixture, propeller pitch or another analogue function appropriate to the aircraft. Avoid assigning a control merely to fill every button; unused inputs are safer than commands that can be triggered accidentally.
Why are the controls reversed, drifting or duplicated?
Most T16000M mapping faults come from the wrong command type, a reversed axis or two devices controlling the same function.
| Symptom | Likely cause and fix |
|---|---|
| Control surface snaps to full deflection | A digital left/right or up/down command was used. Replace it with the corresponding analogue axis command. |
| Aircraft rolls, yaws or changes power by itself | Another controller has the same axis assigned. Search every connected device and keep only the intended binding. |
| Pitch or throttle moves backwards | Enable the simulator's reverse-axis option for that input only. |
| Only one engine responds | The slider is bound to an individual engine. Use the combined or all-engines throttle axis. |
| Rudder jitters near the centre | Check the twist axis outside the flight, add the smallest effective dead zone and recalibrate if necessary. Our hardware calibration and in-simulator dead-zone checks explain how to separate sensor drift from a sensitivity problem. |
| Button numbers do not match the physical labels | A TARGET virtual device or old custom profile may be renumbering them. Scan each physical button and bind the identifier the simulator actually detects. |
Do I need Thrustmaster TARGET software?
No. Normal axis and button mapping is simpler through the flight simulator's own control system.
TARGET is useful when a profile needs shifted button layers, macros or a virtual combined controller. Once such a profile is running, the simulator may see a virtual device instead of, or alongside, the physical T16000M. Bind only one of those paths; mapping both is a common cause of duplicate inputs and unexplained button numbers.
The T16000M should be treated primarily as a PC DirectInput joystick. A standard USB connection does not guarantee operation on Xbox or PlayStation, where flight simulators require explicitly supported console peripherals.