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.
Simsbury, CT
The student pilot reported that he was preparing for his private pilot check ride, and after about 90 minutes of flying, he approached the airport and entered the traffic pattern for runway 21, a 2,205-ft-long runway. The student pilot added that, while established on "short final," he chose to perform a go-around because he was not "comfortable" with the approach. On the second landing attempt, the airplane floated past the intended touchdown point before landing on the runway, and the student pilot was unable to stop the airplane before it went off the departure end. Subsequently, the airplane struck a perimeter fence and an embankment, which resulted in the nose landing gear collapsing and substantial damage to the fuselage and left wing. The student pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. The winds reported at an airport 4 miles east of the accident location were from 320° at 7 knots.
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Not attained/maintained - C
The student pilot reported that he was preparing for his private pilot check ride and after about 90 minutes of flying, he approached the airport and entered the traffic pattern for runway 21, a 2,205 ft-long runway. While established on "short final," he elected to perform a go-around because he was not "comfortable" with the approach. On the second landing attempt, the airplane floated past the intended touchdown point, before landing on the runway, and the student pilot was unable to stop the airplane before it went off the departure end. Subsequently, the airplane struck a perimeter fence and an embankment, which resulted in the nose landing gear collapsing and substantial damage to the fuselage and left wing. The student pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. The winds reported at an airport 4 miles east of the accident location were from 320 degrees true at 7 knots.