Autorotation Aerodynamics
In powered flight, the engine drives the rotor through transmission. In an autorotation, the rotor is unpowered — and yet it keeps spinning, often at near-normal RPM, all the way to touchdown. The reason is that during descent, the rotor disc divides into three aerodynamic regions: a stalled inboard region that decelerates the blade, a driving region in the middle that accelerates the blade, and a driven outboard region near the tips that decelerates the blade. Net force depends on the balance of these regions — and that balance is what every collective input changes.
Also called: rotor regions, three-region theory, driven/driving/stall
The starting point: a rotor in descent
When the helicopter is descending without engine power, air is flowing upward through the rotor disc — opposite to the powered-flight case where air flows downward. Each blade still sees a relative wind, but the orientation of that wind has changed. Now the rotor is more like a windmill being driven by the airflow than a fan driving the airflow.
Whether each part of the blade extracts energy from the airflow or absorbs energy from rotation depends on the angle of attack of that blade element relative to the airflow. AOA varies along the blade because each part of the blade moves at a different speed (rotational speed × radius), and the effective angle of attack depends on how fast the air flows up through that point.
The three regions
The rotor disc divides into three concentric regions:
Stall region (inboard ~25%)
Near the rotor hub, the rotational speed is low (small radius × angular velocity). With a strong upward airflow during descent, the relative wind hits these blade sections from below at a steep angle — the angle of attack exceeds the stalling angle. Stalled blade sections produce mostly drag and little lift.
Effect on rotor RPM: stalled sections decelerate the blade. The stall region is acting against you.
Driving region (~25-70% of the radius)
Moving outward, the rotational speed increases and the angle of attack drops below the stall angle. Here's the magic: the aerodynamic force on these blade sections is inclined slightly forward of the axis of rotation. The forward component of that force accelerates the blade.
This is the autorotative region — the engine of an autorotation. Without it, the rotor would spin down within seconds. The driving region pulls energy out of the upward airflow and adds it to rotor rotation.
Driven region (outboard ~30%, near the tips)
At the blade tips, rotational speed is highest. The angle of attack is small. The aerodynamic force is inclined slightly aft of the axis of rotation, which decelerates the blade. The driven region (also called the propeller region) is acting against rotor rotation, like a windmill being slowed by its loaded shaft.
The blade tips contribute the most lift to the rotor disc as a whole — but they're costing you rotor RPM in the process.
The balance — why it works
In a stable autorotation, the energy added by the driving region exactly equals the energy taken away by the stall and driven regions. Net torque on the rotor is zero; rotor RPM stabilizes. The rotor spins indefinitely as long as the descent continues to push air up through the disc.
Disturb the balance and rotor RPM changes:
- Faster descent → more upward airflow → higher AOA across the disc → driving region migrates outward, stall region grows. RPM tends to increase.
- Slower descent → less upward airflow → lower AOA → driving region shrinks, driven region grows. RPM tends to decrease.
- Higher collective (higher pitch on all blades) → AOA increases at every blade station → stall region grows, driving region shrinks. RPM decreases.
Why you don't pull collective during the glide
This is the operationally critical fact, and the reason this aerodynamics matters in practice:
Raising collective during the autorotative glide reduces rotor RPM.
Higher pitch increases AOA on every blade segment. The stall region expands inward; the driving region shrinks; the driven region also contributes less. The rotor's energy balance tips negative — RPM decays. If you pull enough collective for long enough during the glide, you'll lose the rotor RPM you need for the cushion at touchdown.
This is counter-intuitive coming from powered flight, where collective controls altitude. In an autorotation, collective is the rotor RPM control. You manage altitude with airspeed (cyclic), not collective. Collective only comes up at the very end — for the cushion — to convert stored rotor RPM into one final blast of lift before touchdown.
How the flare changes the picture
During the flare, the rotor disc tilts back relative to the airflow. The induced angle of attack across the rotor changes — typically increasing — and the driving region expands. Rotor RPM increases during a properly executed flare.
This is why the flare both slows the helicopter and banks rotor energy: you're spending forward airspeed and slowing descent, but the changing aerodynamic geometry transfers some of that lost energy into faster rotation. By the time you cushion at touchdown, you have more rotor RPM available than you did 50 ft AGL — exactly when you need it.
This is also why a flare that's too aggressive or too long can over-speed the rotor briefly. It's also why flaring late means less RPM increase and less cushion margin at touchdown.
The full picture
An autorotation is an energy-conversion exercise. You start with potential energy (altitude) and end with kinetic energy converted into a soft touchdown. Throughout, the rotor disc is dividing and re-dividing into its three aerodynamic regions, with the balance shifting as you change attitude, airspeed, and collective. The pilot's job is to manage the inputs that shape that balance: airspeed sets the descent rate (and thus the upward airflow); collective sets the AOA (and thus the region balance); cyclic sets the disc tilt (and thus the timing of the flare).
Most pilots learn the procedure first and the aerodynamics second. That works. But understanding the aerodynamics turns "don't pull collective during the glide" from a memorized rule into a clear consequence — which is what you want when something doesn't feel right and you have to make a call.