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.
Williamson, GA
The pilot reported that he approached the turf runway at his home airport with a tailwind, which he estimated to be about 20 knots and gusting. The airplane “just floated” at the intended touchdown point, and then touched down about 1/3 of the way down the 2,500-ft-long runway. After touchdown, the airplane bounced, and he added some engine power “so that the impact of the second touchdown would be mitigated.” After the second touchdown, he applied “maximum braking effort.” He reported that the braking action was “nil” due to the freshly mowed turf, and he was unable to stop the airplane on the runway. The airplane crossed over a road at the end of the runway, nosed over, came to rest inverted, and sustained substantial damage to the vertical stabilizer and rudder. The pilot stated that the opposite runway was not used for landing at this airport, due to tall trees at the approach end, which would have required a touchdown “well past” the midpoint of the runway. Further, the opposite runway had a “radical” downward slope (its elevation decreased about 80 ft over the 2,500-ft length). The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
Environmental issues-Conditions/weather/phenomena-Wind-Tailwind-Decision related to condition
The pilot reported that he approached the turf runway at his home airport with a tailwind, which he estimated to be about 20 knots and gusting. The airplane “just floated” at the intended touchdown point, and then touched down about 1/3 of the way down the 2,500-ft-long runway. After touchdown, the airplane bounced, and he added some engine power “so that the impact of the second touchdown would be mitigated.” After the second touchdown, he applied “maximum braking effort.” He reported that the braking action was “nil” due to the freshly mowed turf, and he was unable to stop the airplane on the runway. The airplane crossed over a road at the end of the runway, nosed over, came to rest inverted, and sustained substantial damage to the vertical stabilizer and rudder. The pilot stated that the opposite runway was not used for landing at this airport, due to tall trees at the approach end, which would have required a touchdown “well past” the midpoint of the runway. Further, the opposite runway had a “radical” downward slope (its elevation decreased about 80 ft over the 2,500-ft length). The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.