Home / Case Files / Pilot Cessna pilot gets caught in thunderstorms and crashes (Massive rescue effort)

Pilot Cessna pilot gets caught in thunderstorms and crashes (Massive rescue effort)

▪️ERA16FA309📅3 September 2016✈️Cessna 172N N6091E📍Hollywood, Florida
Advertisement

The Warning Came Before the Crash

Cessna 172N N6091E departed Pompano Beach Airpark on September 3, 2016, bound for Ocean Reef Club Airport in Key Largo. The pilot had not obtained a weather briefing before departure.

The official record

This occurrence was investigated by the National Transportation Safety Board under accident number ERA16FA309. The Board records the event as occurring on 3 September 2016 at Hollywood, FL. The aircraft is identified as a CESSNA 172, registration N6091E. The highest injury level recorded is fatal.

The Board’s record additionally lists phase of flight recorded as enroute; uncontrolleddescent; enroute, weather conditions recorded as Visual (VMC), operating under 091.

The investigation is closed. The Board determined the probable cause to be:

The pilot's inadequate preflight and in-flight weather planning, which resulted in continued flight into a thunderstorm and a subsequent loss of airplane control.

NTSB, accident ERA16FA309

A probable cause is the Board’s determination of what brought the occurrence about. It is reached after the investigation closes and supersedes any earlier account, including contemporary reporting and anything inferred from the recording alone.

The full record can be retrieved from the NTSB’s public case system, CAROL, by searching accident number ERA16FA309.

Research and reconstruction

Flight Follower Editorial Team

This reconstruction was researched from official investigation records where they exist, the original air traffic control recording, and contemporary reporting. The aircraft movement, timeline and written account were assembled independently by Flight Follower. Where an investigation is open or no probable cause has been published, the account says so rather than offering one.

About the Flight Follower team · Editorial policy · Corrections

Accident Facts

Accident
ERA16FA309
Date
3 September 2016
Aircraft
Cessna 172N N6091E
Location
Hollywood, Florida
Timeline
09:32 EDT
N6091E departed Pompano Beach Airpark.
1.
Shortly afterward
The pilot requested to fly below 500 feet along the shoreline.
2.
Weather warning
ATC advised of heavy precipitation and recommended turning offshore to avoid the thunderstorm.
3.
About three minutes later
The pilot reported turning back north.
4.
09:50 EDT
The final GPS position showed the aircraft at about 440 feet and 85 knots.
5.
Around 09:51
Radar contact was lost after the aircraft turned east.
6.
Afterward
The wreckage was found submerged in the Atlantic about two miles east of the shoreline.
7.
Outcome
The pilot and pilot-rated passenger were fatally injured.
8.

While flying south along the shoreline, the pilot contacted the Fort Lauderdale/Hollywood tower and requested to remain below 500 feet above ground level. The controller approved the request but warned of heavy precipitation ahead and advised the pilot to turn offshore to avoid the thunderstorm.

The pilot acknowledged the warning. The airplane did not follow the suggested deviation.

The NTSB's final conclusion was: “The pilot's inadequate preflight and in-flight weather planning, which resulted in continued flight into a thunderstorm and a subsequent loss of airplane control.”

The GPS Track Shows the Warning Was Not Followed

The NTSB compared GPS and radar data with weather-radar information. The aircraft maintained a southerly course instead of turning offshore as the controller had advised.

The final GPS-derived position was at about 440 feet, with a groundspeed of 85 knots. Radar contact was then lost as the aircraft was reported turning east at about 200 feet.

The wreckage was located in approximately 15 feet of water. The investigation found no evidence of a pre-impact mechanical malfunction.

The Weather Was the Dominant Hazard

The NTSB classified the defining event as windshear or thunderstorm. The investigation found that the airplane entered an area of extreme precipitation and then descended rapidly.

The report concluded that strong downdrafts and heavy rain associated with the thunderstorm likely caused the loss of control. The pilot had been warned before entering the weather area, which made the decision to continue especially significant.

The Low Altitude Made the Situation Less Forgiving

The pilot had chosen to remain below 500 feet along the shoreline. That left little altitude available if the airplane encountered a severe downdraft or rapidly deteriorating visibility.

Once the aircraft entered the extreme precipitation area, there was little vertical margin for recovery. The final radar and GPS sequence shows the airplane close to the surface when the track ended.

The investigation therefore links weather planning and aircraft control rather than treating the thunderstorm as an unavoidable natural event.

ATC Gave the Pilot a Specific Escape Option

The controller did not merely report that weather was present. The warning identified heavy precipitation four miles ahead at the aircraft's 12-o'clock position and gave a specific avoidance instruction: turn left and fly offshore.

The pilot acknowledged the instruction. Radar and GPS evidence later showed that the aircraft continued south instead.

The Final Minutes Were Below the Altitude Needed for Recovery

The accident therefore shows why low-level weather avoidance is so unforgiving. A pilot who encounters a severe convective cell at several thousand feet may have time to turn, climb or divert. At a few hundred feet, the same encounter can become unrecoverable within seconds.

The Controller's Warning Was an Available Safety Barrier

The NTSB's factual report makes the sequence unusually strong because the controller's warning, radar track and GPS data can be compared. The pilot was told about heavy precipitation ahead and given an avoidance heading. The aircraft did not follow that deviation.

The final loss of control occurred only after the aircraft entered the severe precipitation area. That means the accident was not simply caused by a thunderstorm appearing without warning. The hazard was identified while the pilot still had an opportunity to avoid it.

The NTSB Found No Pre-Impact Mechanical Failure

The wreckage examination did not identify a mechanical malfunction that would have prevented normal operation before the impact. That matters because the weather encounter must be treated as the central physical event rather than an engine or flight-control failure.

The airplane entered extreme precipitation and rapidly descended. The investigation linked that sequence to strong downdrafts and heavy rain. The weather was not merely present in the background; it was the environment in which control was lost.

The Final Flight Path Was Consistent With the Investigation

The last recorded positions place the airplane close to the shoreline and low above the surface. Once the aircraft entered the convective area, the remaining altitude was not enough to absorb a severe downdraft and recover.

That is why the NTSB's conclusion centers on weather planning and continued flight into the thunderstorm rather than on the final turn alone.

Conclusion

N6091E was warned about the thunderstorm before it entered the hazardous area. The pilot continued toward it, then attempted to reverse course after the encounter had already developed.

The NTSB's final finding places the causal weight on inadequate preflight and inflight weather planning and the resulting loss of control. The most important lesson is not that ATC failed to warn the pilot; it is that the warning came before the decision point and the safer option was still available.

“The most important lesson is not that ATC failed to warn the pilot; it is that the warning came before the decision point and the safer option was still available.”

Sources

Audio from the original air traffic control recording, sourced from public recordings and released investigation records. The reconstruction, animation and written account are our own.
Advertisement

The weekly incident