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.
Warrenton, VA
The pilot reported that this was his third skydiving flight of the day and he performed a back taxi on the runway for takeoff. He further reported that as he rotated the airplane for takeoff, he heard a "steady" stall warning horn, the flight controls felt mushy, and the airplane would not climb. The pilot reported that he aborted the takeoff and applied max braking and reverse thrust, but the airplane overran the runway remaining. Subsequently, the landing gear collapsed and the airplane collided with a fence. The left and right wing sustained substantial damage. After the accident, the pilot reported that he observed the wing flaps in the fully retracted position. He reported that the flaps should have been set to 20 degrees for takeoff. The pilot reported that he forgot to set the flaps during the back taxi for takeoff because he was communicating with other airplanes near the airport. The pilot reported that he did not use a physical checklist, but he did run through a checklist mentally. The pilot reported no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
The pilot's failure to set the wing flaps for takeoff, which resulted in an aerodynamic stall, an aborted takeoff, and a runway overrun.
The pilot reported that this was his third skydiving flight of the day and he performed a back taxi on the runway for takeoff. He further reported that as he rotated the airplane for takeoff, he heard a "steady" stall warning horn, the flight controls felt mushy, and the airplane would not climb. The pilot reported that he aborted the takeoff and applied max braking and reverse thrust, but the airplane overran the runway remaining. Subsequently, the landing gear collapsed and the airplane collided with a fence. The left and right wing sustained substantial damage. After the accident, the pilot reported that he observed the wing flaps in the fully retracted position. He reported that the flaps should have been set to 20 degrees for takeoff. The pilot reported that he forgot to set the flaps during the back taxi for takeoff because he was communicating with other airplanes near the airport. The pilot reported that he did not use a physical checklist, but he did run through a checklist mentally. The pilot reported no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.