Medevec Helicopter CRASHES with Patient

The Warning Started With a Twist-Grip Indication

A medical helicopter was flying at night toward a hospital helipad with two crewmembers and a patient when the pilot saw a twist-grip caution indication associated with the No. 1 engine.

Accident Facts

The pilot also saw another caution but could not later recall its exact message. He checked the engine throttles by feel and did not initially detect an abnormal position. The crew then decided to divert toward a nearby airport.

During the turn, the indications for the two engines no longer matched. The No. 2 indication appeared lower and oscillating. About a minute later, the low-rotor-RPM horn sounded.

The Investigation Pointed to an Engine Control Setting

The postaccident examination did not find a pre-impact mechanical malfunction in the throttles, linkages, engines, control systems, cockpit display system or electronic engine control units that would have prevented normal operation.

Data recovered from the helicopter provided the more important clue. About four minutes after takeoff, the No. 1 engine was placed in manual mode and removed from EEC control. The sequence was consistent with the pilot inadvertently moving the No. 1 engine throttle out of its neutral detent.

The engine then remained in manual mode for several minutes. The resulting mismatch between engine indications and the later low-rotor-RPM warning created the emergency that forced the crew into an autorotation.

The Patient Was Still on Board

This was not an empty training flight. The helicopter was carrying a patient and operating under a medical mission profile when the emergency developed.

That context increases the operational pressure but does not change the immediate priorities. Once rotor RPM began falling, the pilot had to preserve the rotor's energy and find a survivable landing area.

The pilot selected what appeared to be the best available dark area and committed to an autorotation. The helicopter was low enough that there was little room to recover from a poor landing decision.

Why the Autorotation Still Ended in a Survivable Impact

The helicopter did not simply descend vertically. The pilot managed rotor RPM and airspeed, adjusted the flight path toward the selected landing area and reached the ground with the aircraft remaining largely upright.

The impact caused substantial damage, but the sequence demonstrates the value of immediately responding to low rotor RPM. The collective was lowered to protect rotor speed rather than raised in an attempt to arrest the descent prematurely.

That is the critical aerodynamic lesson: rotor energy is the resource that must be preserved during an autorotation.

Evidence and Findings

That control-state change explains why the cockpit indications became inconsistent and why the low-rotor-RPM warning appeared. Once rotor RPM began to decay, the pilot had to lower the collective and transition into an autorotation while simultaneously selecting a landing areat night.

The helicopter eventually struck terrain and rotated before coming to rest upright. The fact that the aircraft remained upright is significant because it indicates that the pilot retained enough control authority to manage the autorotation through the final phase.

The case therefore illustrates the difference between a mechanical failure and a control-state problem. The engines and control system were not found to have failed in a way that made normal operation impossible; the investigation instead focused on the inadvertent change in engine-control mode and the resulting loss of rotor performance.

What Could Have Broken the Chain

The first interruption point was recognition of the engine-control state. The pilot did not initially realize that the No. 1 engine had moved out of EEC control. Once the indications diverged, however, the crew did recognize that the propulsion situation was abnormal and began diverting.

The next barrier was the low-rotor-RPM response. Lowering the collective protected the rotor system and gave the pilot the energy needed for autorotation.

The final barrier was landing-site selection. The pilot chose a dark area that appeared to offer the best chance of a survivable landing. That decision was not perfect—the helicopter still struck terrain—but it preserved the occupants' survival.

The case therefore shows how recovery can still succeed after an unusual control-system problem if the pilot protects rotor energy and commits early to a landing area.

The Final Safety Margin

The case also demonstrates why electronic engine-control data can be more reliable than a pilot's memory of a rapidly developing emergency. The pilot remembered the indications and the low-RPM warning, but the recovered data showed exactly when the No. 1 engine entered manual mode. That allowed investigators to reconstruct a control-state change that was not obvious in the cockpit at the time.

• Treat unusual engine-control indications as a genuine emergency.
• Protect rotor RPM immediately when low-RPM warnings appear.
• In an autorotation, select a survivable landing area early.
• Medical missions do not change the basic priority of aircraft control.
• Postaccident data can reveal a control-state change that was not obvious to the pilot during the emergency.

Sources

• Video source (ATC/audio reconstruction)