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.
Mcalpin, FL
The pilot and his passenger were preparing for a cross-country flight. After a routine preflight inspection and engine start, the pilot taxied to runway 27, which was 2,644 ft-long and comprised of turf. The grass was “mid height” and wet from the morning dew. The pilot commonly used a “hump” in the runway as a go/no-go decision point, which was about midfield. During the takeoff roll, he scanned his tablet device for speed and noted 47 knots; 52 knots was stall speed, configured. As the takeoff roll continued, he tried to “pop” the airplane off the ground and into ground effect; this attempt was unsuccessful. He realized that the airplane would not become airborne and it departed the end of the runway, collided with a berm, and spun around to a stop. A postaccident fire ensued and the pilot and passenger egressed the airplane without injuries. Despite attempts to extinguish the fire, it progressed and eventually consumed the fuselage. An inspector with the Federal Aviation Administration reported that the airplane was destroyed. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. He also reported that performing the “no go” decision at the hump in the runway would have prevented the accident.
The pilot’s inadequate preflight planning and failure to abort the takeoff at the predetermined decision point.
The pilot and his passenger were preparing for a cross-country flight. After a routine preflight inspection and engine start, the pilot taxied to runway 27, which was 2,644 ft-long and comprised of turf. The grass was “mid height” and wet from the morning dew. The pilot commonly used a “hump” in the runway as a go/no-go decision point, which was about midfield. During the takeoff roll, he scanned his tablet device for speed and noted 47 knots; 52 knots was stall speed, configured. As the takeoff roll continued, he tried to “pop” the airplane off the ground and into ground effect; this attempt was unsuccessful. He realized that the airplane would not become airborne and it departed the end of the runway, collided with a berm, and spun around to a stop. A postaccident fire ensued and the pilot and passenger egressed the airplane without injuries. Despite attempts to extinguish the fire, it progressed and eventually consumed the fuselage. An inspector with the Federal Aviation Administration reported that the airplane was destroyed. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation. He also reported that performing the “no go” decision at the hump in the runway would have prevented the accident.