Fix a throttle not working in a flight simulator: test detection, correct axis bindings, remove conflicts, calibrate travel and check autothrottle.
Across flight simulators generally, a throttle fails because the controller is not detected, the lever is bound to buttons instead of a continuous axis, another device has a duplicate assignment, or calibration or autothrottle is overriding it. Test the hardware first, then create one clean throttle-axis binding in the simulator.
How do I find out whether the throttle or simulator is at fault?
Test whether the operating system can see the complete lever movement before changing simulator settings. This separates hardware and USB faults from bad control assignments.
- Close the simulator. Connect the throttle directly to the computer rather than through an unpowered USB hub, then restart it. Some simulators only scan controllers during launch.
- Test the raw input. On Windows, open the Game Controllers panel by running
joy.cpl, select the device and inspect its properties. The throttle indicator should move smoothly through its full range; our Windows controller testing procedure applies to other HOTAS units as well as the X52. - Check platform compatibility. A USB throttle that works on PC will not necessarily work on Xbox or PlayStation. Consoles require officially compatible hardware, and detecting a USB device does not guarantee that the simulator can use it.
- Select the correct in-simulator profile. Confirm that you are editing the throttle itself, not the joystick, gamepad or an empty default profile. Updates and reconnecting a device can sometimes cause a different profile to load.
- Move the lever while viewing assignments. If the simulator offers input detection, use it to identify every command receiving that axis. Remove unwanted assignments before adding a new one.
If the axis does not respond in the operating-system test, reinstall only the driver or configuration software required by the manufacturer, try another USB port and retest. A dead, erratic or permanently centred input at this stage is not a simulator binding problem.
Which throttle control should I bind?
A physical lever should be assigned to a continuous throttle axis, not to throttle-increase and throttle-decrease buttons. Digital commands suit a keyboard or gamepad button but cannot follow the position of an analogue lever.
Command names vary, but look for labels such as Throttle Axis, Throttle Axis (0–100%) or an individual engine axis. Start with the combined all-engines axis; use separate engine axes only when the hardware has multiple levers and the aircraft supports them.
| Symptom | Likely cause | What to change |
|---|---|---|
| Lever does nothing | Wrong profile or no axis binding | Bind the detected input to the combined throttle axis |
| Throttle moves only while a button is held | Digital increase/decrease commands | Replace them with a continuous axis assignment |
| Movement is backwards | Reversed axis direction | Enable or disable the axis reversal option |
| Only one engine responds | Lever bound to one engine | Use the all-engines axis or assign every lever deliberately |
| Lever cannot reach idle or full thrust | Bad calibration, dead zone or response curve | Restore a linear curve, reduce excessive dead zones and recalibrate |
Microsoft Flight Simulator users should also check the distinction between analogue and digital commands in our guide to configuring MSFS throttle inputs. For FSX, use these FSX controller and axis checks, since its control interface and controller-enable setting differ from newer simulators.
Why does the throttle move and then snap back?
A throttle that responds briefly and then returns is usually being overridden by another input or by aircraft automation. Duplicate assignments are especially common when a joystick twist, gamepad trigger or second quadrant has inherited a default throttle binding.
- Clear duplicate axes: inspect every connected controller, including gamepads and virtual devices, and remove all unintended throttle assignments.
- Disconnect suspect devices: temporarily unplug everything except the primary stick and throttle. Reconnect devices one at a time after the throttle works.
- Disengage autothrottle: test in a simple aircraft with autothrottle, autothrust and AI piloting assistance switched off.
- Check keyboard commands: a stuck key or repeating throttle command can continually overwrite the lever position.
In Airbus-style aircraft, autothrust normally operates while the physical levers remain in a detent such as CL. That is expected behaviour. The fault is more likely detent calibration if the cockpit reports the wrong detent or repeatedly alternates between two modes.
Why does the throttle work in one aircraft but not another?
Aircraft-specific behaviour points to engine controls, detent calibration or a saved aircraft profile rather than failed hardware. Complex add-on aircraft may require calibration through their own cockpit tablet or configuration panel instead of relying entirely on the simulator’s global response curve.
- Piston aircraft may produce little power with the mixture at idle cut-off or the engine stopped.
- Turboprops can require correctly positioned condition and propeller levers as well as power levers.
- Jets may have fuel cut-off controls, throttle locks or calibrated idle, climb and take-off detents.
- Reverse thrust may use part of the axis, a separate button or a latch. Configure normal forward travel first, then add reverse operation.
- Helicopters distinguish between the engine throttle and collective; assigning one does not replace the other.
What does a reliable throttle setup look like?
A known-good setup has one active throttle-axis assignment, smooth full-range movement in the hardware test, no duplicate inputs and the correct direction of travel. Test it first in a basic single-engine aircraft with automation disabled, then add separate engine levers, detents and reverse thrust one feature at a time.
If the problem is specifically in Microsoft Flight Simulator, follow our MSFS-specific conflict and calibration sequence; it covers the profile, sensitivity and assistance settings particular to that simulator.