A fixed-wing aircraft that loses power can glide. The physics are forgiving: wings produce lift as long as air moves over them, and a skilled pilot — or a well-tuned autopilot — has minutes to find a runway or a field. A helicopter with a failed engine has no such grace period. Without powered rotation, the main rotor decelerates in seconds. If nothing is done, rotor RPM falls below the minimum needed to generate lift, the blades stall, and the aircraft falls ballistically. What saves a helicopter in this scenario is autorotation — and automating it is one of the hardest real-time control problems in aviation.

Autorotation is not a powered procedure. It is a controlled energy exchange. When the engine fails, the pilot immediately lowers collective pitch, reducing blade angle of attack to near zero. This removes the aerodynamic load that was slowing the rotor, and the relative wind from the descending aircraft now drives the blades from below — the same physics as a falling sycamore seed. The rotor spins up on its own, storing kinetic energy that will be used in the final flare. The aircraft descends at a steep angle, typically between 1,500 and 2,000 feet per minute in a conventional single-engine design, while the pilot manoeuvres laterally to reach a suitable landing site. Then, just above the ground — usually within the last 40 to 100 feet — the pilot pulls collective sharply. This converts rotor inertia into lift, slowing the descent dramatically. The manoeuvre must be timed almost exactly right. Too early and the rotor bleeds energy before touchdown; too late and the deceleration is insufficient. The margin for error is measured in tenths of a second.

Manned helicopter pilots train this procedure repeatedly, and it remains demanding even for experienced crews. For an unmanned rotorcraft, the challenge is not manual dexterity — it is the architecture of sensing, prediction, and actuation that must replicate what a trained human does through feel and reflex in under two minutes of total elapsed time.

The autonomous control problem breaks into three phases, each with its own failure modes. In the entry phase — the first two to four seconds after engine loss — the flight computer must detect that power has been lost, lower collective immediately to prevent rotor stall, and simultaneously arrest any lateral drift before the aircraft enters an unrecoverable attitude. Engine-out detection sounds straightforward but is not: transient power dips, sensor noise, and clutch disengagement events can look similar in telemetry. A system that waits for confirmation wastes the rotor inertia it needs. A system that reacts to false positives may initiate an unnecessary autorotation in normal flight. The detection logic has to be tuned to the specific drivetrain of each airframe, not borrowed from a generic algorithm.

In the descent phase, the system must manage rotor RPM within a narrow band — high enough to store energy for the flare, low enough not to overspeed the rotor and shed blades. This is an energy management problem that couples airspeed, sink rate, rotor RPM, and remaining altitude into a single state vector. The aircraft must simultaneously navigate toward a landing zone while holding that state vector in bounds. On a coaxial design — where two counter-rotating rotor discs occupy the same mast — the control laws are more complex still, because pitch, roll, and yaw inputs interact differently across the two discs. The heavy-lift UAV platforms that operate in demanding logistics and public-safety roles must account for this interaction under time pressure.

The flare is where the manoeuvre succeeds or fails. The flight computer must judge — from altitude, sink rate, and rotor RPM — the precise moment to initiate collective pull. On a conventional manned helicopter, this judgment is partly tactile: a pilot feels the aircraft begin to settle and responds. An autonomous system has no haptic channel. It works from barometric altimeter data, radar altimetry if equipped, and inertial measurement, each carrying its own latency and noise floor. The flare also changes the aircraft's pitch attitude sharply, which can introduce ground effect interactions and aerodynamic interference with any payload below the fuselage. The terminal phase of an autonomous autorotation therefore involves a sequence of tightly coupled events — flare initiation, pitch attitude management, RPM drain control, and skid or wheel contact — that must execute in the right order and at the right time without any human in the loop.

Why does this matter for unmanned systems specifically? Because the consequence calculus is different. A manned helicopter carries its most important asset — the crew — in the aircraft. The entire regulatory and engineering tradition of manned rotorcraft safety is built around protecting those people, and autorotation is the last resort when everything else has failed. An unmanned system operating in urban or populated areas carries no crew, but it operates over people, infrastructure, and property on the ground. The failure mode that matters is not crew injury but uncontrolled ballistic descent into a populated area. Autonomous autorotation is therefore not just a capability that mirrors what manned aircraft do; it is a prerequisite for operating class of unmanned rotorcraft over populated areas at all. Without it, the residual risk of a power failure is a falling object with no trajectory control — an unacceptable outcome in any serious operational context.

The research and engineering direction is clear, even if the production implementations are not yet widespread. Model-predictive control schemes that propagate the rotor energy state forward over the remaining altitude are showing promise in simulation and limited flight test. Machine-learning approaches trained on high-fidelity physics models can generate flare timing policies that outperform classical control in non-nominal conditions — partial rotor failures, asymmetric loading, crosswind at touchdown. The sensing layer is also evolving: radar altimeters accurate to centimetres at low altitude, combined with high-rate IMUs and real-time airspeed estimation, give the control system the state information it needs to close the loop at the speed the flare demands.

For any serious heavy-lift unmanned helicopter programme, autonomous emergency recovery is not a future feature — it is a foundational safety requirement that shapes airframe design, sensor architecture, and certification strategy from the start. The goal is a system that, given an engine failure at any point in its operational envelope, can bring the aircraft to a controlled landing without ground casualties and without human intervention. That goal is achievable. The path to it runs through control theory, flight dynamics, and the kind of rigorous physical AI development that treats safety not as a compliance checkbox but as the design constraint that defines everything else.

固定翼飞机失去动力后可以滑翔。直升机没有这种宽裕——发动机一旦停车，主旋翼在数秒内减速。唯一的出路是自转着陆：飞行员立即压低总距，使旋翼在下降气流驱动下自旋储能，最后在接地前拉杆，将动能转化为升力减速落地。整个过程的容错窗口以十分之一秒计。

对于无人直升机，自主自转的控制问题分为三个阶段：入口阶段（发动机停车检测与旋翼保护）、下降阶段（转速与能量管理）、拉平阶段（精确的拉杆时机）。同轴反转旋翼布局进一步提升了控制律的复杂度，因为两层旋翼盘的俯仰、横滚、偏航耦合方式不同于常规构型。对于在城市或人口密集区运行的重型无人直升机平台，发动机失效若无轨迹控制，结果是无控弹道坠落——这在任何正式运营场景下都不可接受。自主应急恢复因此是运营合规的基础性安全要求，而非未来的可选功能。

当前的工程方向包括：基于模型预测控制的旋翼能量前向传播、经高保真物理模型训练的机器学习拉杆策略，以及厘米级精度的低空雷达高度计与高速惯导的融合感知层。对于认真对待物理AI开发的重型无人直升机项目，自转着陆能力不是设计末期的补充，而是从气动布局、传感器架构到适航取证策略的核心约束。

固定翼飛機失去動力後可以滑翔。直升機沒有這種寬裕——發動機一旦停車，主旋翼在數秒內減速。唯一的出路是自轉著陸：飛行員立即壓低總距，使旋翼在下降氣流驅動下自旋儲能，最後在接地前拉桿，將動能轉化為升力減速落地。整個過程的容錯視窗以十分之一秒計。

對於無人直升機，自主自轉的控制問題分為三個階段：入口階段（發動機停車偵測與旋翼保護）、下降階段（轉速與能量管理）、拉平階段（精確的拉桿時機）。同軸反轉旋翼佈局進一步提升了控制律的複雜度，因為兩層旋翼盤的俯仰、橫滾、偏航耦合方式不同於常規構型。對於在城市或人口稠密區運行的重型無人直升機平台，發動機失效若無軌跡控制，結果是無控彈道墜落——這在任何正式運營場景下都不可接受。自主緊急恢復因此是運營合規的基礎性安全要求，而非未來的可選功能。

當前的工程方向包括：基於模型預測控制的旋翼能量前向傳播、經高保真物理模型訓練的機器學習拉桿策略，以及厘米級精度的低空雷達高度計與高速慣導的融合感知層。對於認真對待物理AI開發的重型無人直升機項目，自轉著陸能力不是設計末期的補充，而是從氣動佈局、感測器架構到適航取證策略的核心約束。