ERA17CA208
2017-06-16 · Cedar Key, Florida, United States · None · 1 aircraft · Status: Completed
Airport CDK
Aircraft involved
Probable cause & findings
The pilot's failure to stop the airplane within the available runway after conducting the approach and landing with a tailwind.
Factual narrative
The pilot reported that the takeoff, climb, and en route portions of the cross-country flight were uneventful. He checked the wind sock prior to landing and it was "flaccid," indicating calm wind. He slowed the airplane to 80 mph on final approach and landed near the approach end of runway 5, which was 2,355 feet-long. He estimated that the airplane should have rolled to a stop; however, it continued down the runway despite heavy braking. The airplane departed the end of the runway, traveled across a small road, and down an embankment, coming to rest in the water at the edge of the airport boundary.A Federal Aviation Administration inspector examined the wreckage and reported that the airplane sustained substantial damage to the forward fuselage and submersion in salt water. There were tire skid marks on the runway leading to the wreckage. A weather buoy, located about 1 mile east of the airport, recorded wind out of the west about the time of the accident, which would have resulted in a tail wind of up to 8 knots. The pilot reported there were no preimpact mechanical malfunctions or anomalies that would have precluded normal operation of the airplane. The pilot reported that the takeoff, climb, and en route portions of the cross-country flight were uneventful. He checked the wind sock before landing, and it was "flaccid," indicating calm wind. He slowed the airplane to 80 mph on final approach and landed near the approach end of the runway, which was 2,355 ft long. He estimated that the airplane should have rolled to a stop; however, it continued down the runway despite heavy braking. The airplane departed the end of the runway, traveled across a small road and down an embankment, and came to rest in water at the edge of the airport boundary. A Federal Aviation Administration inspector examined the wreckage and reported that the airplane sustained substantial damage to the forward fuselage and submersion in salt water. There were tire skid marks on the runway leading to the wreckage. A weather buoy, located about 1 mile east of the airport, recorded wind from the west about the time of the accident, which would have resulted in a tailwind of up to 8 knots. The pilot reported there were no preimpact mechanical malfunctions or anomalies with the airplane that would have precluded normal operation. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Surface speed/braking-Capability exceeded - C
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
- C Environmental issues-Conditions/weather/phenomena-Wind-Tailwind-Contributed to outcome - C
- C Aircraft-Aircraft oper/perf/capability-Aircraft capability-Landing distance-Capability exceeded - C
- — Environmental issues-Physical environment-Object/animal/substance-Water/moisture-Contributed to outcome
Verbatim from NTSB's published report. Source file
NTSB_2017_ERA17CA208.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗