Why does my turboprop throttle jump to idle or feather in MSFS 2024?
Fix an MSFS 2024 turboprop throttle that jumps to idle or feather by correcting axis bindings, detents, calibration and control conflicts.
In Microsoft Flight Simulator 2024, a turboprop power lever usually jumps to idle because two controls are fighting, the axis is reversed, or a reverse detent is miscalibrated. If the propeller actually feathers, a propeller/RPM binding is wrong or the engine has shut down and triggered feathering logic.
Which turboprop control is actually moving?
On a conventional turboprop, the throttle and feather controls are separate. The power lever controls engine power and the beta or reverse range, while the propeller lever governs RPM and moves the blades towards feather.
| Observed symptom | Most likely cause |
|---|---|
| Power lever snaps to idle | Duplicate throttle command, reversed axis, incorrect endpoint or an active throttle-cut button |
| Propeller/RPM lever moves to feather | Hardware lever wrongly assigned to a propeller axis or feather command |
| Condition lever moves to cut-off | Mixture or condition axis conflict, which shuts down the engine |
| Power lever enters beta or reverse at the idle gate | Full-range throttle and physical detent do not agree |
| Lever stays still but the propeller feathers | Engine shutdown, fuel starvation, failure or automatic feathering logic |
Some turboprops use a single power lever and manage propeller RPM automatically. Do not add a propeller-axis assignment unless that aircraft exposes a manual propeller control. Our guide to turboprop feathering and the three lever types explains the distinction in more detail.
How do I stop the throttle jumping to idle?
Remove every conflicting assignment, bind the correct throttle range and then calibrate the idle and reverse positions.
- Park the aircraft and identify the moving control. Watch the virtual power, propeller and condition levers while moving one hardware lever slowly. This tells you whether MSFS is receiving a throttle input or a different command entirely.
- Check every connected device. A joystick, throttle quadrant, controller and keyboard can all have active bindings at the same time. Temporarily clear throttle, propeller and mixture assignments from everything except the device being tested.
- Bind one appropriate throttle axis. Use the 0–100% throttle axis for a forward-only lever. Use a full-range axis only when the hardware has a usable range below idle and the aircraft supports beta or reverse calibration. Twin-engine quadrants should use the corresponding engine-specific axes.
- Remove cross-bindings. Search the profile for
propeller,RPM,mixture,condition,featherandreverse. A spare axis accidentally assigned to mixture or condition can cut the fuel when it reaches its minimum. - Clear unwanted digital commands. Look for throttle cut, throttle decrease, reverse toggle and feather commands assigned to buttons, switches or keys. The F1–F4 throttle inputs are another common source of sudden changes; our keyboard control reference identifies the default power commands.
- Calibrate direction and endpoints. The input indicator should move smoothly across its range without flickering or reversing. Use the reverse-axis option when direction is wrong rather than trying to compensate with sensitivity. Our throttle calibration procedure covers endpoint errors, jitter and duplicate axes.
- Set aircraft-specific detents. If the aircraft's EFB or cockpit tablet provides throttle calibration, define idle, flight idle and reverse there. The simulator profile and aircraft calibration must agree.
- Retest without automated assistance. Disable AI piloting or assisted engine control while diagnosing the problem, then move the lever slowly through idle. Also check the fuel selectors, condition lever and enabled failures if the propeller feathers without a cockpit lever moving.
Which throttle axis should I choose?
The correct axis depends on whether the physical lever includes a reverse region.
| Control type | Choose it when | Common mistake |
|---|---|---|
| Throttle Axis 0–100% | The hardware lever covers forward power only | Expecting the bottom of the axis to provide reverse automatically |
| Full-range Throttle Axis | The lever has a calibrated section below idle for beta or reverse | Using it without matching the aircraft's idle and reverse detents |
| Engine-specific throttle axes | A multi-engine quadrant has a separate lever for each engine | Leaving a general throttle axis active alongside them |
| Increase, decrease or cut commands | A keyboard or button is being used instead of an analogue lever | Binding these commands to switches that remain held |
Control labels can vary slightly between device profiles and aircraft. Our comparison of MSFS throttle axis types covers forward-only, full-range and digital throttle setups.
Why does it happen only near idle or after loading?
A jump at the idle detent usually means the beta or reverse boundary is incorrectly defined. It can also happen when a physical detent activates a reverse button while the analogue axis is already entering the reverse range, effectively sending two commands.
Use either a calibrated full-range axis or a forward-only axis with a separate reverse command; avoid combining both methods. If the input trace flickers at idle, make the smallest dead-zone or endpoint adjustment that stabilises it rather than flattening the whole response curve.
After loading a flight, the virtual cockpit may retain its starting position until the first hardware input arrives. If the physical quadrant is at idle while the aircraft starts with take-off power, touching the lever will make the cockpit control jump immediately to the hardware position. Set the quadrant to the expected position before releasing the parking brake.
What if the control bindings are correct?
If the cockpit power lever remains stationary while the propeller feathers, the simulator is reacting to the aircraft rather than moving the throttle. Check that the condition lever is not at fuel cut-off, the selected tank contains fuel and no engine failure has been enabled.
On an aircraft equipped with automatic feathering, loss of engine torque can feather the propeller as designed. A problem affecting only one engine points towards an engine-specific axis, fuel setting or failure; a problem affecting only one aircraft points towards that aircraft's EFB calibration or engine logic. Testing the same hardware profile in another default turboprop separates a device-level conflict from an aircraft-specific one.