What is helicopter autorotation and how do you simulate it?
Learn how helicopter autorotation works, how an autorotation landing is flown, and how to practise it realistically in a flight simulator.
Helicopter autorotation is a controlled descent in which upward airflow through the rotor disc keeps the blades turning after engine torque is removed. To simulate it, lower collective promptly, hold rotor RPM and the aircraft’s prescribed airspeed, flare near the ground, level the helicopter, then use stored rotor energy to cushion the landing.
For readers of our Aviation & Real-World Flying section, a desktop simulator can teach the sequence, instrument scan, energy management and sight picture. It cannot reproduce motion cues or qualify anyone to perform the manoeuvre in an aircraft. Real autorotation training requires an instructor and the approved procedure for that helicopter.
What is autorotation in a helicopter, and how does it work?
Autorotation keeps the main rotor turning aerodynamically when the engine is no longer supplying useful torque to it. The helicopter descends through the air, creating upward airflow relative to the rotor disc; aerodynamic forces on part of each blade then provide enough driving torque to oppose drag and sustain rotation.
A freewheeling unit normally lets the rotor and transmission overrun a slowing or stopped engine, rather like a bicycle wheel continuing to turn while the pedals stop. The engine does not necessarily have to stop: an autorotation also occurs when it is running but disconnected or producing no useful drive.
The rotor disc is commonly described as having three aerodynamic regions:
- The driving region produces the torque that sustains rotor rotation.
- The driven region consumes some of that torque while producing lift.
- An inner stalled region may exist near the blade roots, where rotational speed is lowest.
The boundaries move with blade pitch, airspeed, descent rate, rotor RPM and manoeuvring. The pilot uses collective and cyclic to keep the balance within the helicopter’s limits.
Autorotation does not mean gliding with a stopped rotor. The spinning rotor stores kinetic energy needed for the flare and touchdown, so preserving rotor RPM is central to the manoeuvre. The standard aviation spelling is autorotation, one word; searches for “auto rotation” usually refer to the same process.
Can a helicopter make an autorotation landing safely?
An autorotation can make a controlled landing possible after total loss of rotor drive, but it does not guarantee a safe outcome. Success depends on height, airspeed, rotor energy, weight, wind, landing surface, helicopter design and the timing of the pilot’s inputs.
During the descent, gravitational potential energy is exchanged for rotor energy, lift and forward movement. Near the ground, the pilot flares to reduce forward speed and descent rate, levels the helicopter to an acceptable touchdown attitude, then raises collective to convert the rotor’s remaining energy into lift.
That final energy reserve is finite. Pulling collective too early can leave insufficient RPM to cushion the actual touchdown; pulling too late cannot arrest the remaining descent. Some helicopters permit a run-on landing, while others require very low forward speed, so wheel and skid procedures are not interchangeable.
How do you practise helicopter autorotation in a flight simulator?
Practise autorotation as a repeatable energy-management exercise, beginning high enough to establish the descent and recover power well before the ground. Always use the simulated helicopter’s manual or included documentation because target airspeeds, rotor limits, flare cues and recovery methods differ substantially between types.
Set up the simulator and controls first
A credible exercise requires correctly assigned controls and a helicopter model that represents freewheeling, rotor inertia and rotor-RPM changes. If collective, throttle and governor behaviour are unclear, review how cyclic, collective, pedals and engine controls interact in a simulator before introducing failures.
- Check the collective axis. Moving the physical collective down must reduce blade pitch. Reversed axes and duplicate assignments are common causes of immediate rotor-RPM loss.
- Separate throttle where appropriate. Do not combine throttle and collective unless the simulated aircraft is specifically designed around that control arrangement.
- Verify the model. When drive is removed, the rotor should continue turning and separate from engine RPM rather than being dragged to a stop. Helicopters with separate engine and rotor tachometer indications should show the needles splitting.
- Review assists. Stability, simplified-helicopter and automatic-RPM aids may hide poor control inputs or prevent a true power-off state. Our guidance on choosing credible helicopter realism settings explains which assistance can interfere.
- Choose forgiving conditions. Start in calm weather over a long runway or broad, level area. Use a consistent cockpit view because changing field of view alters the apparent flare height.
- Create a repeatable starting point. Save or reload the same altitude, speed, weight and wind conditions. This makes changes in technique easier to identify.
Use the simulator’s built-in failure system when available, or a reversible method specified for that aircraft. For early exercises, avoid using a fuel shut-off: it can add restart and system complications that obscure the autorotation itself. Our guide to building repeatable engine-failure scenarios covers safe simulator setup in more detail.
Step-by-step simulated autorotation
The basic sequence is to remove blade drag quickly, stabilise rotor RPM and airspeed, plan the glide, flare, level and spend the stored rotor energy only when landing or recovery is assured.
- Brief the exercise. Record the aircraft’s permitted rotor-RPM range, recommended autorotation airspeed, recovery procedure and any limits on turns or touchdown attitude. Select a landing area before introducing the failure.
- Stabilise the helicopter. Begin in steady forward flight at a safe practice altitude. Starting from a badly trimmed climb, turn or low-RPM condition makes diagnosis difficult.
- Remove engine drive. Trigger the prepared failure or approved throttle condition. Confirm the expected torque reduction and, where modelled, separation between engine and rotor indications.
- Lower collective promptly. Move towards the type’s prescribed low-pitch position to reduce blade drag. Correct the torque-change yaw with pedal and use cyclic to establish the required attitude.
- Control rotor RPM and airspeed. Use cyclic primarily for attitude and airspeed, and small collective changes to keep rotor RPM within limits. Avoid chasing either indication with large, alternating inputs.
- Shape the approach. Keep the landing area within reach and account for wind early. Make smooth turns; abrupt or steep manoeuvres change rotor loading and can move RPM rapidly.
- Flare using the aircraft’s cues. Apply aft cyclic smoothly at the prescribed stage to reduce forward speed and descent rate. An aggressive flare can cause a balloon, while a late flare leaves too little time to level.
- Level and cushion. Use forward cyclic as required to reach the permitted touchdown attitude, hold heading with pedals, then raise collective progressively to convert stored rotor energy into lift. Minimise lateral drift before ground contact.
- Complete the planned recovery. For a power recovery, restore drive as the aircraft procedure requires and anticipate returning torque with pedal. For a simulated full touchdown, accept only the forward speed and attitude allowed for that helicopter and surface.
What does each control do during autorotation?
Collective has the most direct effect on blade pitch and rotor RPM, while cyclic controls attitude, airspeed and the flight path; all the controls remain coupled.
| Control | Primary use | Frequent error |
|---|---|---|
| Collective | Reduce drag after power loss, regulate rotor RPM and cushion touchdown | Holding excessive pitch during entry or raising it before touchdown is assured |
| Cyclic | Set attitude and airspeed, aim the approach and produce the flare | Making an abrupt aft input that balloons the helicopter |
| Anti-torque pedals | Control yaw when engine torque disappears or returns | Holding the powered-flight pedal position through the torque change |
| Throttle or governor controls | Create the simulated loss of drive and perform an approved power recovery | Trying to regulate rotor RPM with engine throttle during a true autorotation |
What airspeed and flare height should you use?
There is no universal autorotation speed or flare height, so use the published figures and visual cues for the helicopter being simulated. Copying a number from another type can produce the wrong descent rate, glide angle or rotor response.
A helicopter may specify one condition for minimum rate of descent and another for maximum glide distance. Minimum descent is useful when time aloft matters; maximum glide is used when reaching a more distant landing area matters. Wind affects the reachable ground area, but indicated airspeed—not groundspeed—remains the primary speed reference unless the aircraft procedure says otherwise.
Flare timing depends on forward speed, descent rate, rotor inertia, weight and the helicopter’s approved technique. Flaring too high spends speed and rotor energy while substantial height remains. Flaring too low leaves insufficient room to reduce descent and establish the correct touchdown attitude.
Power recovery or full-touchdown autorotation?
Choose a power recovery while learning the entry, descent and flare; choose a simulated full touchdown only after those elements are repeatable and the model has credible rotor and ground-contact physics.
Begin with recoveries at altitude, then reduce the recovery height in controlled stages. Restoring maximum power at the last moment is not a substitute for the aircraft’s procedure: torque, yaw, engine acceleration and rotor-governor behaviour differ between helicopters.
A full-touchdown autorotation adds the hardest energy decision—when to level and raise collective with no power available to correct a mistake. Real aircraft practice must be instructor-led; our overview of how helicopter training is structured and supervised explains why desktop rehearsal is not a replacement.
Why does a simulated autorotation go wrong?
Most unsuccessful simulated autorotations result from delayed collective reduction, incorrect axis assignments, unstable airspeed or spending rotor energy too early.
| Symptom | Likely cause | What to change |
|---|---|---|
| Rotor RPM falls immediately | Collective lowered too slowly, reversed axis, duplicate binding or unrealistic drivetrain modelling | Restart higher, lower collective promptly and verify the complete control range |
| Rotor RPM exceeds its limit | Collective held fully down after RPM has risen, abrupt loading changes or poor model behaviour | Use small collective corrections permitted by the procedure and smooth the manoeuvre |
| Engine and rotor RPM never separate | Idle power is still driving the rotor, the wrong failure was selected or freewheeling is not modelled | Check the failure state and test the aircraft model before judging technique |
| The landing area becomes unreachable | Wrong glide condition, late site selection, excessive turning or poor wind allowance | Select the site earlier and use the published maximum-glide technique when distance is required |
| The helicopter balloons in the flare | Excessive entry speed or an abrupt aft-cyclic input | Repeat from a stable approach and apply the flare progressively |
| The flare works but touchdown is hard | Collective raised too early, rotor RPM was already low or the helicopter was not levelled in time | Preserve RPM during the descent and delay the progressive cushion until landing is assured |
| The helicopter yaws during recovery | Engine torque returned without matching pedal input | Restore power as prescribed and anticipate the helicopter’s torque direction |
How can you tell whether the simulator models autorotation properly?
A useful helicopter model should reproduce the main energy relationships rather than merely allowing the aircraft to descend with the engine at idle.
- Rotor RPM should remain independent of a failed or disconnected engine.
- Lowering collective should reduce blade drag and help preserve or recover RPM; raising it should consume rotor energy.
- Airspeed, bank angle, loading and flare inputs should produce believable changes in RPM and descent rate.
- The flare should trade forward speed for reduced descent and may produce a temporary RPM increase.
- The final collective pull should provide a finite cushion, not unlimited lift at low RPM.
- Weight, wind and density conditions should alter the approach without making the basic physics disappear.
If these behaviours are absent, the simulator can still help with failure recognition and control sequencing, but it should not be used to judge flare height, touchdown performance or the capabilities of the real helicopter.
Can a helicopter autorotate from a hover?
A hover engine failure is possible to manage only within the helicopter’s height, speed and rotor-energy limitations, and it is not the same exercise as a stabilised forward-flight autorotation.
Near the ground, some helicopters can use stored rotor inertia to cushion a prompt landing. At greater height but with little forward speed, there may be insufficient room to establish a normal autorotation before impact. This is why helicopter manuals contain height–velocity guidance and separate procedures for engine failure in the hover; do not force the cruise autorotation sequence into a low-height scenario.