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.
Fullerton, CA
The pilot reported that during landing the airplane porpoised twice down the runway. He decided to continue the landing as he believed there to be sufficient remaining runway to abort the landing. The pilot attempted to stop the airplane using the brakes when the airplane skidded off the end of the runway and struck a chain link fence. The airplane sustained substantial damage to the firewall during the accident sequence. The pilot reported that there were no preexisting mechanical problems with the airplane.
The pilot’s improper flare and inadequate bounced landing recovery, which resulted in a hard landing and porpoise down the runway.
The pilot reported that during landing the airplane porpoised twice down the runway. He decided to continue the landing as there was not enough remaining runway in his opinion to abort the landing. The pilot attempted to stop the airplane using the brakes. The airplane skidded off the end of the runway and struck a chain link fence. The airplane sustained substantial damage to the firewall during the accident sequence. The pilot reported that there were no mechanical problems with the airplane.