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.
St. Augustine, FL
During a scheduled 100-hour inspection, maintenance personnel discovered structural damage to the airplane’s firewall. According to the flight school’s records, the airplane had been flown 91.4 hours on 77 flights between the time of the previous 100 hour inspection and the time when the damage was discovered. The flight school was never notified of an event that would have possibly caused the firewall damage. Therefore, the actual time and date and the circumstances of the accident could not be determined.
Undetermined due to a lack of information about when the damage to the airplane occurred.
During a scheduled 100 hour inspection, maintenance personnel discovered structural damage to the airplane’s firewall. According to the flight school’s records, there were 77 flights in the accident airplane from the previous 100 hour inspection that took place on May 8, 2012 and July 18, 2012, when the damage was discovered. A total of 91.4 flight hours were accumulated between those inspections. The flight school was never notified of an event that would have possibly caused the firewall damage. The actual time and date of the accident is unknown.