Learn why X-Plane 12 turboprops lag while prop RPM stays high, what is normal, and how to fix power, prop, condition and beta control errors.
In X-Plane 12, a turboprop can respond slowly because its gas generator must spool up before torque rises, while the propeller governor changes blade angle to hold the selected prop RPM. High RPM at low torque can therefore be normal; abnormal lag, RPM hunting or weak power often points to lever positions, bindings or calibration.
Why does propeller RPM stay high when power is low?
A constant-speed propeller is designed to hold its selected RPM across a range of power settings, so prop RPM need not fall when torque falls. The governor changes blade pitch to absorb more or less shaft power while keeping rotational speed near the target set by the propeller lever.
When power rises, the governor generally moves the blades towards a coarser pitch. When power falls, it moves them towards a finer pitch until it reaches an operating limit or pitch stop. The propeller may therefore remain fast and noisy while producing relatively little thrust.
This only applies while the propeller is within its normal governing range. At very low power, or when operating in ground idle, beta or reverse, the normal relationship between the governor, blade angle and power lever changes. Prop RPM may then rise, fall or fluctuate differently according to the aircraft's design.
Power, propeller and condition controls
Most conventionally controlled turboprops divide engine management between three levers:
- Power lever: requests engine power in the flight range and may control blade angle after crossing the flight-idle gate into beta or reverse.
- Propeller lever: selects the governor's target prop RPM and may command feather near the aft end of its travel.
- Condition lever: commonly controls fuel cut-off and the low-idle or high-idle schedule. Its exact function varies by aircraft.
Some turboprops use a single power lever with automatic propeller and engine management. Others require separate controls or aircraft-specific commands. A mistake we see constantly is copying a piston-aircraft control profile without checking what the turboprop actually expects.
Read the right engine gauge
RPM alone is not a reliable indication of turboprop power. The label also matters: Np normally means propeller speed, while Ng or N1 commonly refers to the gas-generator spool.
| Indication | What it shows | How to use it |
|---|---|---|
| Torque | Shaft load delivered to the propeller | Usually the clearest indication of useful power on aircraft that use torque as their primary power gauge |
| Np or prop RPM | Propeller rotational speed | Shows the governor target, not thrust by itself |
| Ng or N1 | Gas-generator speed | Shows the turbine core spooling up or down |
| ITT or TOT | Engine temperature | Used to monitor thermal limits rather than direct thrust |
| Fuel flow | Fuel being scheduled to the engine | Helps confirm that a power-lever input is reaching the engine model |
Use the power indication specified by the aircraft's checklist. Many turboprops use torque, but some use shaft horsepower or another engine-specific measure.
How much turboprop throttle lag is normal?
A short, repeatable delay while Ng and torque build is normal, particularly when advancing from low idle. The turbine has rotational inertia, and its fuel control must schedule fuel without causing a compressor surge, over-temperature or over-torque condition.
The delay is usually most apparent from idle to high power and less obvious when the engine is already running at a higher idle or partial-power setting. There is no universal acceptable time: engine type, condition-lever position, altitude and the aircraft's own systems all affect the response.
- Normal response: the cockpit lever follows the hardware, engine indications change coherently, torque builds without hunting, and the behaviour is repeatable.
- Likely control problem: the cockpit lever jumps, fails to reach full travel or moves without your input.
- Likely systems or aircraft problem: the virtual lever reaches the correct position but Ng, fuel flow and torque do not respond.
- Likely axis jitter: RPM, blade angle or beta indication repeatedly oscillates around one lever position.
Advancing the power lever more aggressively does not remove turbine lag. It may only command a larger change for the engine controller to schedule, and detailed add-ons may limit or delay that command to protect the engine.
How do I tell normal behaviour from a control problem?
The quickest test is to watch the virtual levers and engine instruments while moving one physical control at a time. This separates genuine engine spool-up from an axis that is misassigned, duplicated or crossing an idle detent.
| What you observe | Most likely explanation |
|---|---|
| Np remains high while torque changes smoothly | Normal constant-speed propeller governing |
| The cockpit lever does not follow the hardware | Wrong profile, assignment, calibration or axis direction |
| The cockpit lever moves by itself or fights your input | A second device or duplicate axis is also assigned |
| The lever enters beta or reverse near idle | Detent, response curve or reverse-range assignment problem |
| The lever moves correctly but engine values do not | Incorrect condition setting, fuel cut-off, failure or aircraft-specific logic |
| One engine responds differently in a twin | Per-engine assignment, condition setting or engine failure |
Control audit for X-Plane 12 turboprops
- Start from a known running state. Set the parking brake, stabilise the engines and make sure no active failure or incomplete start is confusing the test.
- Match the hardware to the cockpit. Identify whether the aircraft expects separate power, propeller and condition controls or a single-lever system. Our guide to setting up joystick, yoke and throttle axes in X-Plane 12 explains how to assign and verify the separate controls.
- Check the active control profile. X-Plane can use aircraft-specific profiles, so an assignment that works in one aeroplane may be missing or different in another.
- Remove duplicate assignments. Inspect every connected throttle, joystick, pedal set and spare slider. A forgotten propeller, mixture or throttle axis can continuously override the intended control. Some aircraft use a mixture-style axis for the condition lever; detailed add-ons may use custom commands instead.
- Calibrate the full travel. Confirm that idle and maximum power are reached without flickering. Windows users can also check throttle travel and axis jitter outside the simulator to distinguish hardware faults from X-Plane behaviour.
- Inspect the idle gate. Make sure normal idle does not accidentally enter beta or reverse. Do not stretch a response curve across reverse unless that is how the aircraft and quadrant are intended to work.
- Move one lever at a time. Advance power and watch Ng, fuel flow and torque. At a suitable stable power setting, move the propeller lever and observe Np. Then verify each condition-lever position.
- Compare mouse and hardware input. If moving the cockpit lever with the mouse works but the physical axis does not, the engine model is probably functioning and the assignment is the problem.
- Compare another turboprop. If an aircraft supplied with X-Plane behaves normally using the same hardware, concentrate on the affected add-on's commands, installation and operating procedure.
Response curves can change how physical lever travel maps to the virtual control, but they cannot remove simulated turbine spool-up. Use them to correct travel and detent placement, not to disguise engine behaviour.
What should I check if take-off power is still weak?
Weak take-off acceleration is not normal spool-up if the engine never reaches the checklist power setting. High prop RPM alone does not confirm take-off power; check torque or the aircraft's specified power indication before deciding that full power is available.
- Confirm that the power lever is above flight idle and not trapped in beta or reverse.
- Set the propeller and condition levers to the positions required by the aircraft checklist.
- For a twin, verify that both engines and both sets of levers respond together.
- Release the parking brake and check that noisy or reversed toe-brake axes are not applying partial braking.
- Watch torque and temperature limits rather than simply pushing the lever to its physical stop.
- Check aircraft weight, runway conditions, density altitude and take-off configuration if the expected engine power is present but acceleration remains poor.
If torque reaches the expected value but the aeroplane remains slow, the fault is probably not turbine lag. Brakes, excessive weight, configuration or an unintended ground-range blade angle are more likely. If torque remains low despite correct cockpit lever positions, inspect the condition setting, fuel state, failures and aircraft-specific engine logic.
Aircraft differences in X-Plane 12
Turboprop behaviour can differ substantially between aircraft because X-Plane's built-in engine model may be supplemented or replaced by custom governor, beta, fuel-control and engine-protection logic. A single-lever turboprop should not be expected to respond like a conventionally controlled aircraft with three separate levers.
If the symptoms occur in only one third-party aircraft, follow its supplied operating instructions and confirm that all required components loaded correctly. A clean X-Plane 12 add-on aircraft installation can resolve missing or misplaced files that prevent custom systems from running.
The practical distinction is consistent: stable high Np with changing torque is usually normal governing, while erratic levers, continuous RPM hunting, failure to leave beta or no increase in torque points to configuration, hardware or aircraft-specific trouble.