FATAL Helicopter Crash Explained

This video examines the final moments of the NBC4 NewsChopper crash in Los Angeles and asks a difficult question: did the pilot actually make the correct autorotation inputs, only to run out of usable energy before the helicopter could be recovered? Using the live broadcast audio, ADS-B data, the Airbus AS350 B2 flight manual, rotor RPM warning logic, autorotation performance, and published helicopter human-factors research, we reconstruct the sequence from the first abnormal engine and rotor sounds through the high-RPM warning, low-RPM alert, rapid descent, attempted acceleration, and final flare. The AS350 was nearly stationary when the event began, placing the pilot in one of the most demanding autorotation scenarios possible: a power loss at low airspeed requiring immediate collective reduction, rapid rotor-RPM recovery, aggressive forward cyclic to build approximately 65 knots, and then an accurately timed flare near the ground. We also look closely at the helicopter’s height-velocity envelope and the assumptions behind certification testing, including pilot reaction time. Published research suggests that real pilots confronted with surprise engine failures may take several seconds to recognize and correctly respond to an emergency, while certification testing can rely on much shorter reaction assumptions. The accident helicopter eventually reached a reported descent rate of approximately 4,800 feet per minute while still well below the AS350’s normal autorotation target speed. The final seconds show another low-RPM warning and a pronounced wobble, raising the possibility that the pilot began the flare with insufficient rotor and forward kinetic energy remaining to arrest the descent. This is an early technical analysis based on currently available evidence. The exact mechanical failure has not yet been determined by the NTSB, and several conclusions discussed here remain hypotheses pending the official investigation.