Why doesn't my throttle work in Microsoft Flight Simulator?

Microsoft Flight Simulator throttle failures are usually caused by a lever bound to a button command instead of an axis, the wrong controller profile, or another device sending conflicting input. Select the correct device, assign the proper throttle axis, remove duplicate bindings, calibrate its range and test in a default aircraft.

The control-screen layout differs between Microsoft Flight Simulator 2020 and 2024, but the diagnosis is the same in both.

How do I fix a throttle that is not working in MSFS?

Use this order so that hardware, binding and aircraft problems are tested separately.

1. Confirm that the hardware is detected. On PC, open the Windows game-controller panel by running joy.cpl and move the lever. If its indicator does not move there, reconnect it directly to another USB port and check its manufacturer software; MSFS cannot repair an input that Windows never receives.
2. Select the throttle device and active profile. In the simulator's controls screen, select the throttle quadrant itself rather than the yoke, joystick or gamepad. Check that the intended preset or customised profile is active, clear any search filters and show all available commands.
3. Find and remove incorrect assignments. Search for throttle commands and, where available, search by input to reveal everything assigned to the physical lever. Clear button-style commands such as Throttle Increase from an analogue lever.
4. Bind the lever to an axis. Assign a normal quadrant lever to a throttle command containing Axis. Move only that lever while scanning for an input, because a noisy dial or another moving control can be captured accidentally. Our detailed throttle-axis and reverse-thrust setup explains the binding choices for quadrants and gamepads.
5. Remove duplicate throttle axes. Inspect every connected yoke, joystick, gamepad and quadrant. A mistake we see constantly is leaving the throttle mapped both to a quadrant and to a gamepad stick, causing the inputs to fight and the virtual lever to jump back.
6. Calibrate the full range. Check that idle and maximum thrust are both reached in Windows or the manufacturer's utility, then verify the range in MSFS. Follow our joystick and throttle calibration process if the lever stops short, has a large dead area or produces an uneven range.
7. Test with a default aircraft. Load a simple piston aircraft on a runway with its engine running and no autothrottle. If the throttle works there but not in a complex or third-party aircraft, the remaining problem is aircraft-specific detent calibration, automation or engine configuration.

Which throttle-axis binding should I use?

An ordinary forward-only throttle lever should normally use a 0–100% axis, while a quadrant with a recognised reverse section may use a full-range axis. Command wording can vary slightly by simulator version and device.

Why does a controller throttle return to idle?

A spring-centred stick or trigger returns its axis to zero when released, so a direct throttle-axis assignment can pull the aircraft straight back to idle. Use relative increase and decrease commands on a gamepad unless you deliberately want thrust to follow the control's held position.

What if MSFS cannot detect the throttle at all?

If the device is absent from the controls screen, solve the connection problem before changing bindings. Restart the simulator after reconnecting it, avoid an unreliable USB hub, check that the operating system still recognises it and confirm that the peripheral is supported on the console being used.

When the device appears in Windows but not in the simulator, work through our device-detection, USB and controller-profile checks. Reinstalling the entire simulator is rarely the right first response to a missing peripheral.

Why does the cockpit throttle move but produce no thrust?

If the cockpit lever moves, the binding is reaching the aircraft; the fault is then automation or engine configuration rather than the controller. Disconnect autothrottle or autothrust for the test and disable any piloting assistance that manages aircraft controls.

• In a piston aircraft, check the mixture, fuel selector and engine state.
• In a turboprop, make sure the condition lever is not at fuel cut-off.
• In a jet, confirm that the engines have completed their start sequence and that fuel controls are in the operating position.
• In aircraft with thrust detents, calibrate those detents through the aircraft's own cockpit tablet or configuration system when one is provided.

Airbus-style autothrust is a common source of confusion: the physical lever may need to remain in a defined detent while the system commands thrust. Moving it like a conventional jet throttle can select a different thrust mode rather than directly setting engine power.

Why is the throttle reversed, erratic or controlling one engine?

Reversed, jumping and one-sided throttle behaviour points to axis configuration rather than a completely missing input.

• Idle gives full thrust: enable the axis's reverse option or reverse it in the device software. Do not try to correct a backwards axis with an extreme sensitivity curve.
• The lever jumps or creeps: remove duplicate assignments, then add only enough dead zone to suppress genuine hardware noise.
• Only part of the travel works: recalibrate the endpoints and check that a full-range reverse axis was not selected for a forward-only lever.
• Only one engine responds: inspect the numbered throttle assignments. Bind each physical lever to its matching engine, or use one combined throttle axis when a single lever should control every engine.

Sensitivity changes can improve response around detents, but they cannot fix an undetected device or the wrong command. Use our sensitivity and dead-zone tuning guidance only after the axis reaches both endpoints and behaves in the correct direction.