Broward Sheriff’s EC135 Crashes After Inflight Fire During Emergency Response Mission

The Helicopter Had Less Than Three Minutes

On August 28, 2023, Broward County Sheriff's Office EC135T1 N109BC departed Pompano Beach Airpark on an emergency medical mission.

Accident Facts

About 67 seconds after liftoff, the No. 1 electronic engine control unit recorded a simultaneous double N1 and double N2 failure. The condition should have generated a FADEC FAIL caution and left the fuel-control unit at its existing flow rate.

The pilot did not recall seeing or hearing that warning.

About 90 seconds after liftoff, at roughly 300–400 feet AGL, the pilot heard a loud bang and saw the No. 1 engine's turbine outlet temperature rising. He reduced the engine to idle, declared an emergency and turned back toward the airport.

The helicopter never made it back.

The Throttle Did Not Do What the Pilot Expected

The EECU failure created a particularly difficult cockpit problem. The failure froze the fuel-control unit at a flow rate associated with climb power. The pilot believed he was reducing the engine to idle, but because of the FADEC condition, the normal throttle movement did not actually reduce fuel flow.

The engine therefore continued operating at a high thermal condition.

The No. 1 engine temperature eventually approached 1,000°C, above its 895°C limit. The investigation found evidence of severe thermal damage to the engine and surrounding structure.

The Fire Was Outside the Area the Fire System Protected

This is the most important investigative distinction in the accident.

The No. 1 engine fire warning system was designed to detect a fire within the engine compartment. The fire that destroyed the helicopter developed outside the engine firewall, near the exhaust and air-conditioning condenser area.

The NTSB found that exhaust gases exceeding 1,000°C could have initiated the external airframe fire. The heat damaged nearby fiberglass and composite structure. The tailboom then partially separated.

Once the tailboom and tail-rotor system were compromised, the helicopter lost directional control and entered a right-hand spin.

The Turnback Was Reasonable With the Information Available

The investigation specifically noted that the pilot had no caution and warning indication of an external fire that would have demanded an immediate off-airport landing. He was dealing with an apparent engine problem and rising temperature while close to the airport.

His decision to turn back therefore made sense given what he could see and what the warning system told him.

The tragedy was that the actual hazard was outside the protected engine compartment. By the time the fire's consequences became obvious, the structure was already being compromised.

What the Records Show

The NTSB determined that the probable cause was an inflight fire outside the engine firewalls, likely from overheating of the No. 1 engine for undetermined reasons, which resulted in partial tailboom separation.

Why This Incident Matters

The accident is a reminder that aircraft protection systems have defined boundaries. A fire-suppression system can function exactly as designed and still be irrelevant to a fire outside the compartment it protects.

It also shows how a control-system failure can become a thermal event. The EECU failure, frozen fuel flow, overheating, external fire and tailboom separation were not separate emergencies. They formed one chain.

The exact reason for the EECU failure and overtemperature could not be determined because the post-impact fire severely damaged the evidence. That uncertainty should remain part of the story.

Evidence and Findings

A second bang occurred roughly 90 seconds after the first. The tailboom partially separated, compromising the helicopter's directional-control system. The helicopter then entered a right spin and descended into an apartment building.

That is important because it prevents a common accident-reporting mistake: assuming that a recent maintenance event must have caused the crash simply because it occurred shortly beforehand. The investigation did not establish that.

What Could Have Broken the Chain

The investigation shows that the first barrier was recognition of the EECU failure. The condition should have produced a FADEC FAIL caution, but the pilot did not recall seeing or hearing one.

The next barrier was engine-temperature management. The pilot attempted to reduce power and return to the airport, but the normal control input did not have the expected effect because the fuel-control system had frozen at its existing flow.

The fire-warning system represented another barrier, but it was designed for an engine-compartment fire. The actual fire developed outside the firewall, so the protection system could not address the structural fire.

Finally, the helicopter's tailboom separated before the crew could reach the airport. Once the tail-rotor system was compromised, the aircraft entered an unrecoverable spin.

The accident therefore shows how safety systems can all operate within their design limits while a failure develops outside those limits.

• Understand what an aircraft warning system actually monitors.
• A FADEC or engine-control failure can produce consequences that normal throttle movements do not correct.
• External fires may fall outside the protection envelope of engine fire-suppression systems.
• Return-to-airport decisions must be made using the information available at the time.
• Do not invent an initiating defect when the investigation cannot establish one.

Sources

• Video source (ATC/audio reconstruction)