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.
Milledgeville, GA
According to the student pilot, while flying the final leg of the traffic pattern, during his solo flight, he noticed that the airplane was "too high," and pulled the power to idle. Then he noted that the airplane was "too fast" and applied back pressure to the control yoke. The airplane then ballooned and subsequently the student pilot added power to go around; however, the airplane impacted the runway in a nose down attitude, became airborne, impacted the runway again, the nose gear assembly collapsed, and the airplane came to rest in the dirt on the left side of the runway. The accident sequence resulted in substantial damage to the fuselage. There were no reported preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Landing flare-Not attained/maintained - C
According to the student pilot, while flying the final leg of the traffic pattern, during his solo flight, he noticed that the airplane was "too high," and pulled the power to idle. Then he noted that the airplane was "too fast" and applied back pressure to the control yoke. The airplane then ballooned and subsequently the student pilot added power to go around; however, the airplane impacted the runway in a nose down attitude, became airborne, impacted the runway again, the nose gear assembly collapsed, and the airplane came to rest in the dirt on the left side of the runway. The accident sequence resulted in substantial damage to the fuselage. There were no reported preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.