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.
Spruce Pines, NC
Before attempting to land on the 3,001-ft-long, asphalt runway, the pilot had been advised by personnel at the destination airport that landing toward the upsloping direction of the runway was preferred. The pilot did not check the wind direction prior to landing, and during the landing flare, the airplane did not slow down or descend. The pilot added full flaps, but the airplane continued to float and touched down with about 200 ft of remaining runway. Subsequently, the airplane overran the runway end, proceeded through the airport perimeter fence, traveled down an embankment, and came to rest on a road. The airplane sustained substantial damage to the fuselage. Following the accident, the pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation and stated that he believed that a tailwind was likely present during the landing attempt.
The pilot's failure to familiarize himself with the wind conditions at the destination airport and his failure to attain the proper touchdown point during landing, which resulted in a long, tailwind landing and subsequent runway overrun.
Before attempting to land on the 3,001-ft-long, asphalt runway, the pilot had been advised by personnel at the destination airport that landing toward the upsloping direction of the runway was preferred. The pilot did not check the wind direction prior to landing, and during the landing flare, the airplane did not slow down or descend. The pilot added full flaps, but the airplane continued to float and touched down with about 200 ft of remaining runway. Subsequently, the airplane overran the runway end, proceeded through the airport perimeter fence, traveled down an embankment, and came to rest on a road. The airplane sustained substantial damage to the fuselage. Following the accident, the pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation and stated that he believed that a tailwind was likely present during the landing attempt.