Learn why helicopter rotor RPM drops with collective in FSX, how to spot normal droop, and fix governor, throttle and control faults.
Raising the collective increases blade pitch and rotor drag, so a brief rotor RPM droop in FSX and FSX: Steam Edition is normal. A sustained drop means the governor or rotor throttle is not maintaining power, collective demand exceeds available engine torque, or a control assignment is interfering. Lower collective first, then check those systems.
Is rotor RPM droop normal when raising collective?
A brief dip that immediately recovers is normal; rotor RPM that stays low is not. Increasing collective makes every main rotor blade produce more lift, but it also creates more aerodynamic drag. The governor should respond by increasing engine power and restoring the selected rotor speed.
In a turbine helicopter, the tachometer may show separate needles for rotor RPM and power-turbine RPM. Those needles should remain close together during powered flight, although the exact indications depend on the aircraft. Gas-producer speed, often labelled N1, is not the same as rotor RPM.
If the low-RPM warning remains active, the needles separate significantly, or RPM continues falling as collective rises, treat it as a power or control problem rather than ordinary governor lag.
How do I stop rotor RPM falling in FSX?
Recover RPM by reducing collective, then verify the power and rotor-control chain from engine to rotor.
- Lower the collective. Reduce it only as much as needed to recover rotor speed. Pulling more collective while RPM is already low adds drag and makes the condition worse.
- Check the flight throttle and governor. Set the rotor or engine throttle to the aircraft's specified flight position and engage the governor if fitted. Some piston helicopters require manual throttle coordination, while turbine models commonly use a governor to maintain rotor speed.
- Confirm the rotor is connected and free. Release the rotor brake fully and engage the clutch where the aircraft models one. With the engine stopped or disconnected, raising collective will inevitably consume rotor energy and reduce RPM, as it does during an autorotation.
- Inspect control assignments. For many FSX helicopters, the joystick's conventional throttle axis operates the collective. An add-on may also provide separate rotor-throttle or governor controls, so duplicated assignments can close the throttle while the collective is being raised. Our reference for FSX helicopter keyboard and rotor controls identifies the relevant governor, clutch, brake and throttle commands.
- Reduce the power demand. Raise collective gradually while watching torque, manifold pressure or the aircraft's equivalent power gauge. If the engine reaches its limit before rotor RPM recovers, reduce aircraft weight, use less collective or test at a lower, cooler airfield. Large pedal inputs can also increase total power demand.
- Test another helicopter in a fresh flight. If every aircraft behaves the same way, suspect a controller assignment or global simulator setting. If only one model is affected, its startup procedure, gauges or configuration are the more likely cause.
What do the RPM and power gauges reveal?
The relationship between rotor RPM and engine response usually identifies the fault. FSX aircraft vary in how completely they simulate the drivetrain, so use the pattern rather than comparing exact readings between different helicopters.
| Indication | Likely explanation | What to check |
|---|---|---|
| Small RPM dip followed by recovery | Normal governor response | No action if RPM returns to the aircraft's normal range |
| Rotor RPM falls while torque or manifold pressure reaches its limit | Too much collective for the available power | Lower collective, reduce weight and consider density altitude |
| Rotor and engine or power-turbine RPM both fall with little power increase | Governor off, throttle not in the flight position, fuel problem or axis conflict | Check the startup procedure and control mappings |
| Drive RPM remains normal but rotor RPM falls or the tachometer needles split | Clutch, rotor brake, transmission or aircraft-model fault | Check modelled drivetrain controls and reload the aircraft |
| RPM falls after an engine failure or shutdown | Normal loss of rotor energy when collective is raised | Lower collective to preserve RPM during autorotation |
Why does this happen in only one add-on helicopter?
If only one aircraft is affected, its startup logic, governor implementation or installation is the likely cause. Many FSX add-ons use custom gauges or scripts for the governor, throttle and clutch, and they may not respond correctly if the aircraft is loaded with the collective raised or its required gauges are missing.
Follow that helicopter's manual rather than applying the default Bell procedure to every model. For example, the Enstrom package with its FSX-specific operating manual provides aircraft-specific rotor and engine procedures, while a detailed Bell 206B model with animated collective behaviour can provide a useful comparison of normal power response.
If the fault began after editing configuration files, restore the original files before changing individual engine or rotor values. Copying governor or drivetrain entries from another helicopter usually creates mismatched power limits rather than fixing the underlying problem.