Overall Trends
Total, fatal, and serious accidents in the selected range.
Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.
Fast key and full-text search with live filters, watches, and precise metadata.
Use quotes for exact phrase matches (for example "fuel selector valve").
Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.
Major cases, deep-report coverage, and investigation media across decades of NTSB history.
Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.
NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.
The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.
The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.
Crystal River, FL
The pilot stated that the approach to the runway was normal, but the airplane touched down further down the runway than he expected. He added power to take off but did not have enough airspeed and runway remaining; he subsequently reduced the engine power and applied the brakes. The airplane exited the end of the runway and impacted a fence, resulting in substantial damage to the engine firewall and both left and right wings. The pilot reported there were no mechanical malfunctions or anomalies with the airplane. He stated that after the accident he looked at the windsock and there was a strong tailwind.
The pilot's failure to attain the proper touchdown point, and his improper decision to perform a go-around with a tailwind and insufficient runway remaining.
The pilot was conducting a cross-country flight to an unfamiliar airport. He stated that as he neared the airport, he obtained information from the airport's automated weather observation system, which reported calm wind. The pilot selected runway 09, and conducted an approach to the runway in order to perform a touch and go landing. However, the pilot stated the airplane was not in a position to land, and subsequently performed a go-around. The pilot stated that the second approach was normal, but the airplane touched down on the runway further from the intended point of landing than he expected. He added power to take off, but could not become airborne within the remaining runway. The pilot reduced engine power and applied brakes, but the airplane traveled off the end of the runway and impacted a fence, resulting in substantial damage to the engine firewall and both left and right wings. The pilot reported there were no mechanical malfunctions or anomalies with the airplane and that, after the accident, the airport windsock indicated a tailwind condition. Recorded weather at the airport about the time of the accident included wind from 310 degrees at 7 knots.