On the evening of September 16, 2026, an NBC4 (KNBC) news helicopter crashed in a narrow alleyway between two commercial buildings on Mason Avenue in Chatsworth, in the San Fernando Valley. The on-board reporter and the pilot were killed, along with a bystander on the ground. The helicopter had been hovering over the scene of an earlier fatal bus collision — stationary, with no forward airspeed — when, by the NTSB’s account, something went wrong with the engine

NTSB Investigator in Charge Fabian Salazar has already told reporters that the onboard video captured while the crew was covering the bus crash live is “probably the most important evidence” in the investigation, and that the recording will go to the agency’s lab for sound spectrum analysis. That footage — and, specifically, its audio track — will be Exhibit A in whatever litigation follows.

In that audio track is a warning horn. Most people who have watched the clip assume it’s the low rotor RPM alarm — the horn every helicopter pilot is drilled to react to instantly by lowering the collective to restore rotor RPM, and, if that fails, entering an autorotation to land on the kinetic energy stored in the spinning blades. That is the textbook sequence, and it’s what several observers initially heard.

Listen more closely, though, and the sequence may be more troubling than that. Before the horn most people associate with “low rotor,” there appears to be a moment where the engine sounds like it’s speeding up, not slowing down. Some experienced listeners believe that first tone is the high-rotor-speed alarm — the one that calls for the pilot to raise the collective to slow the rotor down. On this reading, what follows the high rotor alarm is the low-rotor alarm, triggered only after an overspeed event. By the time that second horn sounds, there may be no altitude or energy left to autorotate safely — particularly over terrain that offered no suitable emergency landing area.

One respected voice in the accident-investigation community has offered a specific mechanical theory for why the audio might unfold that way:

“This helicopter had a conversion to a Lycoming LTS101 engine. There has been issues in the past where the fuel control failed (not a FADEC) and engine went high, over speed protection stopped the over speed, but then shut off engine (not suppose to do that), in the accident video you hear engine over speed, high horn (410 rpm), then you hear it fail, low horn (360 rpm), then horn turns off which happens at 250 rotor rpm. This all would be indications that the collective was not lowered after engine failure.”

If that reading holds up, the sequence isn’t a single low-rotor event with a delayed pilot response — it’s an engine overspeed, a fuel-control failure that shut the engine down entirely, and a rotor decay that ran unchecked past the point of recovery. That is a specific and testable mechanical theory, but it is not yet the NTSB’s finding, and it is not the only account already in circulation. ABC News aviation analyst John Nance, reacting to the same audio, described hearing “something winding down in the background” as the aircraft began to shake — consistent with a mechanical failure, but not itself a diagnosis of which component failed or why.

What isn’t in dispute is the flight profile. By multiple accounts, the aircraft was hovering — stationary, with no forward airspeed — over a narrow alley partially blocked by storage containers, with buildings close in on both sides. Every helicopter’s performance charts include what pilots call the “dead man’s curve”: the combination of low altitude and low airspeed at which a safe autorotation following an engine failure is not achievable, regardless of pilot skill. A hovering news helicopter working a story from altitude sits about as deep inside that curve as a flight profile gets. When an emergency does occur under those conditions, there may simply be no good outcome available, whatever the initiating mechanical cause.

The NTSB should issue its preliminary report within 30 days, with a final report and probable-cause determination 18 months or more. That timeline will need to sort out the mechanical, human-factors, and operational threads here. Until then, the audio is a compelling piece of evidence — but it’s evidence that supports more than one narrative. Normally, an examination of the helicopter’s engine and related components would tell the story. But here there was a post-crash fire that may make that evidence all but useless.