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.
Brevard, NC
While on final approach to land, the pilot noticed a tree that was located near the end of the runway. To avoid the tree, he “stayed high” until he cleared the approach end of the runway and then attempted to “drop quickly” to the field. The airplane touched down on the left main landing gear roughly 2,000 feet beyond the threshold of the 2,900-foot-long runway, and the pilot applied the brakes. The pilot was unable to stop the airplane before it overran the runway. The right main landing gear struck an airport sign, and the airplane came to rest in brambles 100 feet beyond the departure end of the runway. Postaccident examination of the airplane revealed that the airplane’s firewall was substantially damaged. During the examination, no evidence of any preexisting mechanical anomalies that would have precluded normal operation was discovered. During a postaccident interview, the pilot stated that, after the accident, he discovered that the tree he had attempted to avoid was actually located to the right of the runway.
The pilot’s failure to execute a go-around following an approach that was high and fast, which resulted in a runway overrun.
***This report was modified on October 29, 2012. Please see the docket for this accident to view the original report.*** While on approach to a runway, the pilot of the airplane attempted to avoid a tree that was located near the end of the runway. To avoid the tree, he “stayed high” until he cleared the approach end of the runway and then attempted to “drop quickly” to the field. The airplane touched down on the left main landing gear roughly 2,000 feet beyond the threshold of the 2,900-foot long runway, and the pilot applied the brakes. The pilot was unable to stop the airplane before it overran the runway. The right main landing gear struck an airport sign, and the airplane came to rest in brambles 100 feet beyond the departure end of the runway. Postaccident examination of the airplane revealed that the airplane’s firewall was substantially damaged. During the examination, no evidence of any preexisting mechanical anomalies that would have precluded normal operation were discovered. During a postaccident interview, the pilot stated that after the accident, he discovered that the tree he had attempted to avoid was actually located to the right of the runway.