FlightFollowerDowned pilot ATC, Coast Guard & Navy Battle the Odds to Save 1 soul
The River Became the Flight Path
Cessna 172 N84287 departed Brewton Municipal Airport on August 13, 2019, for a short repositioning flight toward Pensacola. The flight should have been a routine 40-mile movement. Instead, GPS data later reconstructed a prolonged period of extremely low-altitude flight along the Escambia River.
The official record
This occurrence was investigated by the National Transportation Safety Board under accident number ERA19LA246. The Board records the event as occurring on 13 August 2019 at Jay, FL. The aircraft is identified as a Cessna 172, registration N84287. The highest injury level recorded is serious.
The Board’s record additionally lists phase of flight recorded as maneuvering; maneuvering, weather conditions recorded as Visual (VMC), operating under 091.
The investigation is closed. The Board determined the probable cause to be:
The pilot's improper decision to fly over a river at a very low altitude, which resulted in a collision with power lines.
NTSB, accident ERA19LA246
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 ERA19LA246.
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
- Date
- 13 August 2019
- Aircraft
- Cessna 172K, N84287
- Location
- Escambia River near Jay, Florida
- Operation
- Part 91 repositioning flight
- Investigation
- NTSB ERA19LA246
The aircraft descended to roughly 76 feet mean sea level over the river and continued following its course for several miles. At one point it climbed around a bend, then descended again and rejoined the river. Near the final section, the aircraft was only about 105 feet msl and approximately 87 knots when it encountered power lines crossing the river.
The aircraft struck the wires, damaged its wings and propeller and then impacted a sandbar. The commercial pilot survived with serious injuries.
The Numbers Reconstructed the Decision
The NTSB did not have to infer the low-altitude operation from a witness impression. A Garmin GPS recovered from the wreckage contained altitude, heading, airspeed and position information.
The transmission line itself was about 60 feet above ground. The NTSB noted that the line was depicted on the VFR aeronautical chart. The physical marking requirements for that location did not make the line invisible as a navigational hazard, and the chart information provided another reason not to treat the river as an unrestricted low-level corridor.
There Was No Mechanical Explanation Waiting in the Wreckage
Postaccident examination found no anomaly consistent with a pre-impact failure or malfunction that would have prevented normal operation. Engine continuity, control continuity and the relevant aircraft systems did not provide a mechanical explanation for the flight path.
That evidence is important because the pilot later had little memory of the accident sequence. The GPS data therefore became especially valuable in reconstructing what the aircraft actually did.
The investigation did not need a complex chain of mechanical events. The airplane was capable of normal operation, but it was deliberately flown at very low altitude over a river where power lines were present. Once the aircraft descended into that environment, the margin for avoiding an obstacle became extremely small.
The Rescue Became a Second Aviation Problem
The accident did not end when the aircraft hit the sandbar. The pilot was injured and the wreckage was not immediately obvious from the ground. The activated ELT eventually prompted a call to the operator, who began an aerial search.
the original video emphasizes the role of Pensacola-area ATC, a Coast Guard MH-65E helicopter and local emergency personnel. Severe weather affected the rescue environment, and available military or medical aviation resources were constrained by their own operational limitations.
ATC's role was therefore not simply to talk to the accident aircraft. Once the ELT was detected, controllers became part of a search-and-rescue coordination problem, helping locate an aircraft in an area affected by weather while available rescue assets were limited.
What the Records Show
The NTSB determined: “The pilot’s improper decision to fly over a river at a very low altitude, which resulted in a collision with power lines.”
The finding is direct. The accident was not attributed to a hidden mechanical failure or an unforeseeable obstruction. It was the result of the decision to conduct sustained low-level flight over the river.
Why This Incident Matters
Low-level flight can create a powerful visual illusion of control. A river is a clear, continuous feature and can appear to offer an easy route through otherwise unfamiliar terrain. But the same feature that helps a pilot navigate can also encourage the aircraft to remain below normal obstacle-clearance altitudes.
The case also shows how an operational decision can create two separate safety problems: first the collision itself, then the challenge of finding and rescuing an injured survivor in a difficult environment. The fact that the pilot survived does not make the decision benign; it demonstrates how close the flight came to a much worse outcome.
Rescue Became a Race Against Weather
The rescue phase added another layer of aviation risk. After the ELT was detected, the operator began an aerial search, while Pensacola-area ATC worked to locate available aircraft. the reconstruction account describes local medical aviation resources being constrained by thunderstorms and Navy helicopters being limited by fuel. A Coast Guard MH-65E on a training mission was then brought into the response.
The Coast Guard helicopter was not initially operating as a dedicated search-and-rescue mission, yet it was able to respond and locate the wreckage with ATC assistance. The pilot was then reached by emergency personnel and transported for treatment. The sequence is useful because it shows how ATC can remain an active safety resource even after the aircraft has disappeared from the normal flight-management problem and become a rescue target.
- Visual landmarks can become dangerous when they encourage prolonged low-level flight.
- Power lines may be difficult to see even when their presence is charted.
- Very low altitude removes both reaction time and recovery space.
- GPS data can provide decisive evidence when a pilot has limited memory of an accident.
- Search-and-rescue coordination can become a second operational challenge after a survivable crash.