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.
Newton, KS
Following a 25 nautical mile cross-country night flight, the private pilot performed a full stop landing. The pilot then departed and stayed in the airport traffic pattern for a second landing. During touchdown, the airplane impacted the runway hard and bounced back into the air before settling back on the runway. One of the two passengers reported hurting her back during the hard landing so the pilot taxied to and shut down the airplane at the airport’s fixed base of operations. After examining the airplane for damage and finding none, the pilot elected to depart with his passengers and successfully flew back to their originating airport. Approximately three months later during the airplane’s annual inspection, the engine firewall was found to be damaged. The pilot later reported that there were no malfunctions or defects with the airplane’s flight controls that contributed to the hard landing.
Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
Following a 25 nautical mile cross-country night flight the private pilot performed a full stop landing. The pilot then departed and stayed in the airport traffic pattern for a second landing. During touchdown the airplane impacted the runway hard and bounced back into the air before settling back on the runway. One of the two passengers reported hurting her back during the hard landing so the pilot taxied to and shut down the airplane at the airport’s fixed base of operations (FBO). After examining the airplane for damage and finding none, the pilot elected to depart with his passengers and successfully flew back to their originating airport. Approximately three months later during the airplane’s annual inspection, the engine firewall was found to be damaged. The pilot later reported that there were no malfunctions or defects with the airplane’s flight controls that contributed to the hard landing.