Why is my throttle not working in MSFS 2024?

In Microsoft Flight Simulator 2024, a throttle usually stops working because the wrong controller profile is active, the lever is bound as buttons instead of an axis, another device has a conflicting assignment, or the axis is reversed. Select the throttle device, bind the correct axis, remove duplicates, then test a default aircraft.

Fix an MSFS 2024 throttle axis step by step

Most throttle faults can be separated into hardware detection, control binding or aircraft calibration with this sequence.

1. Confirm that the hardware is detected. Open the Controls screen and check that the throttle appears as a device. On PC, run joy.cpl and move the lever; its axis indicator should move smoothly. If it does not appear there, reconnect it directly, check its power and USB connection, and solve the hardware issue before changing MSFS settings. Our controller-detection and USB troubleshooting steps cover this stage in detail. On Xbox Series X|S and PlayStation 5, remember that peripheral support is device- and platform-specific.
2. Select the throttle itself. MSFS stores assignments against individual devices. A mistake we see constantly is editing the yoke, stick or gamepad profile while the separate throttle quadrant is selected elsewhere in the device list.
3. Identify the physical axis. Use the input-search function while moving the lever. Bind that analogue input to a throttle-axis command, not to button commands such as increase throttle, decrease throttle or a fixed percentage.
4. Choose combined or per-engine control. Use the combined throttle axis when one physical lever should move every engine. With a twin-engine quadrant, bind the left and right levers to the numbered engine axes instead. Do not assign combined and numbered throttle axes at the same time.
5. Remove conflicting assignments. Inspect every connected controller, including gamepads, extra quadrants and virtual devices. Clear unwanted throttle axes and any button that continuously commands idle or full power.
6. Check the response graph. Move the lever from idle to full power and confirm that the on-screen indicator travels across the expected range. Enable Reverse Axis only if the direction is wrong. Start with a nearly linear sensitivity curve and a small dead zone rather than trying to repair a bad assignment with an extreme curve.
7. Save and activate the preset. Confirm that the edited preset remains selected for both the device and aircraft. MSFS 2024 may load another saved profile when you change aircraft or controller.
8. Test a simple default aircraft. Use a runway-start flight so the engine is already running. If the throttle works there, the hardware and basic MSFS binding are sound; the original aircraft needs its own detent or throttle calibration.

Which throttle axis should I bind?

The correct binding depends on the number of physical levers and whether the hardware has a usable reverse-thrust range. Command wording can vary slightly by device preset and localisation.

A reverse detent is not universal. Some aircraft use a separate reverse command, while complex Airbus add-ons often require each idle, climb, flex and take-off detent to be calibrated in the aircraft tablet or electronic flight bag.

Why does the throttle move in Controls but not in the cockpit?

If the raw input meter moves but the cockpit lever does not, MSFS 2024 is receiving the hardware signal but not applying the active aircraft binding.

• Check that the assignment was saved on the throttle device rather than another controller.
• Verify that the aircraft has not selected a different control preset.
• Remove simultaneous combined and per-engine assignments.
• Disconnect unused controllers temporarily; gamepad triggers and virtual devices are frequent sources of duplicate throttle input.
• Disengage autothrottle and AI piloting assistance for a diagnostic test. Re-enable the features you normally use once the manual axis works.

If the cockpit lever follows the hardware and then snaps back, look for a second controller command, an engaged autothrottle system or aircraft-specific throttle logic. If it never moves, the active binding or profile remains the likely cause.

Why does the cockpit throttle move but power stay at idle?

A moving cockpit lever with no increase in engine power usually points to aircraft state or calibration rather than a failed controller.

• In a cold-and-dark aircraft, confirm that the engine is running and that fuel shut-off, mixture or condition controls are in the required positions.
• Check that the lever was not accidentally assigned to propeller pitch, mixture or another engine axis.
• On multi-engine aircraft, verify that each numbered throttle controls the intended engine.
• For an Airbus or another detent-based aircraft, calibrate the lever inside that aircraft after establishing the basic MSFS axis binding.

Thrustmaster users can follow our TCA throttle-axis, reverse and detent setup. For separate-engine quadrants, our WinWing combined-versus-per-engine configuration explains how to avoid overlapping assignments. If a default runway-start aircraft works but one add-on does not, stop changing the global sensitivity settings and concentrate on that aircraft's calibration.

Why is the throttle reversed, jumpy or missing part of its travel?

Reversed or incomplete travel is normally caused by inversion, a mismatched axis type, an excessive dead zone or an uncalibrated hardware range.

• Backwards movement: toggle Reverse Axis once. Do not invert the same axis in both hardware software and MSFS unless the device specifically requires it.
• Idle and full power are swapped: confirm the input graph is reversed, rather than changing sensitivity values until the endpoints appear correct.
• The lever jumps between idle and full: make sure it is assigned as an analogue axis rather than two button commands.
• It never reaches an endpoint: check the raw hardware range first, then adjust the MSFS neutral, extremity and dead-zone values only as much as necessary.
• The input spikes: test another direct USB connection and examine the axis in joy.cpl. Spikes outside the simulator indicate a device, connection or calibration problem.

When should I rebuild the throttle profile?

Create a clean profile when several devices control the same throttle, assignments return after being cleared, or an imported preset contains bindings you cannot identify.

Disconnect unused controllers, create a fresh preset for the throttle, bind only one throttle axis and test it in a default aircraft. Add reversers, engine-specific axes and other controls one at a time. If the existing setup is badly tangled, use our procedure to clear duplicate and ghost controller bindings before rebuilding it.