Assign separate throttle controls to each engine, remove conflicting axes, calibrate every lever and fix throttles that still move together.
To assign separate engine throttles in a general flight simulator, bind each physical lever to its matching numbered axis—such as Throttle 1 Axis and Throttle 2 Axis—rather than the unnumbered combined throttle axis. Clear duplicate assignments, calibrate every lever, check its direction, then test each engine independently.
Assigning one throttle axis per engine
The clean setup is one physical analogue axis mapped to one numbered engine axis. Microsoft Flight Simulator, X-Plane, FSX, Prepar3D and DCS use different labels, but the principle is the same.
- Check that each lever is an independent axis. Move the levers separately while watching the controller input display. If two levers produce the same input, change the quadrant's hardware mode or configuration first; the simulator cannot split a single reported axis into two independent controls. On a console, the quadrant must also be supported by the platform and simulator.
- Open the correct controller profile. If the simulator supports aircraft-specific profiles, select or create one for the aircraft being configured. A twin-engine profile should not automatically be reused for a four-engine aircraft without checking every assignment.
- Remove conflicting throttle bindings. Search every connected controller for throttle assignments. Clear the generic, unnumbered throttle axis and any unwanted numbered axes, including assignments on joystick sliders or unused levers. A mistake we see constantly is clearing the quadrant while leaving another controller bound to all engines.
- Assign the numbered axes. Bind the left lever to engine 1, the next lever to engine 2, and continue in order. Engine numbering normally runs from the aircraft's left to right: on a four-engine aircraft, engine 1 is outer left and engine 4 is outer right. Choose an axis command, not throttle increase and decrease buttons. For platform-specific screens and command choices, follow our detailed MSFS throttle-axis procedure or the multi-engine mapping steps for X-Plane 11 and 12.
- Calibrate each lever. Move it through its full range, set a small dead zone only if the input flickers, and confirm that idle and maximum power are reached. Avoid applying conflicting calibration or inversion in both a hardware utility and the simulator.
- Test one engine at a time. With the aircraft parked and its brakes set, move only the first lever. Confirm that the matching cockpit lever and engine indication respond while the others remain still, then repeat for every engine.
How many throttle axes do I need?
True per-engine control requires one independent physical axis for every engine you want to control separately.
| Available axes | Practical assignment | Result |
|---|---|---|
| One | Generic throttle axis | All engines move together |
| Two | Engines 1 and 2 | Independent control of a twin |
| Two on a four-engine aircraft | First lever to engines 1 and 2; second to engines 3 and 4 | Left and right engine pairs, not true per-engine control |
| Four | Throttle axes 1 through 4 | Independent control of all four engines |
Many simulators permit one lever to be assigned to several numbered engines, which is useful for grouped four-engine control. Do not also bind those levers to the generic all-engine axis.
Why do all engine throttles still move together?
The usual cause is a combined throttle assignment that remains active alongside the numbered engine axes.
- Use the controls screen's assigned-input filter and inspect every connected device, not just the quadrant.
- Remove the generic throttle axis from joystick sliders, gamepads and duplicate controller profiles.
- Check that one physical lever has not accidentally been bound to several numbered throttle axes.
- Confirm that the hardware exposes separate axes rather than a combined mode.
- For aircraft with their own electronic flight bag or throttle calibration page, calibrate there as well as in the simulator when the aircraft documentation requires it.
Detented quadrants are particularly prone to duplicate combined and per-engine bindings. Our TCA Airbus Quadrant setup guidance explains how those conflicting assignments produce linked or erratic levers.
Why is one throttle reversed or responding differently?
A reversed or mismatched lever normally has its own inversion, dead-zone or response-curve setting.
Correct the affected axis individually and compare its calibration with the other levers. If the cockpit levers move together correctly but one engine's thrust indication differs, the binding may be fine: check whether that engine is fully started, has fuel, has suffered a simulated failure, or is being limited by an aircraft-specific control system. Jet engines also spool at a different rate from the cockpit lever's movement.
How should reverse thrust and detents be configured?
Reverse travel must be calibrated separately for each lever and matched to the type of axis the aircraft supports. Use a full-range axis when the hardware provides reverse travel and the simulator or aircraft recognises it; otherwise use a forward-only throttle axis with a separate reverse hold or toggle command.
If one engine enters reverse before another, first match the lever curves and detent positions. Do not compensate by adding a large dead zone unless the physical input is genuinely noisy, because that shortens usable throttle travel and makes matched thrust harder to set.