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.
New Castle, VA
According to the pilot, the airplane was accelerating normally during the takeoff roll into a 6- to 8-knot headwind. About halfway down the turf runway, the airplane became airborne and then settled back onto the runway. The pilot decided to abort the takeoff and reduced power while applying the brakes. He realized that the airplane would not be able to stop prior to impacting a berm located at the end of the runway and added full power. The airplane cleared the berm, crossed a dirt road, and impacted a tree and several boulders before coming to rest in a pond. The pilot stated that it had rained earlier in the day and that the runway might have still been damp. The pilot reported no mechanical malfunctions or failures with the airframe or engine that would have precluded normal operation.
Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Airspeed-Not attained/maintained
According to the pilot, all indications were in the "normal range," and the airplane was accelerating normally during the takeoff roll into a 6- to 8-knot headwind. About halfway down the 2,400-foot turf runway, the airplane attained "2/3 flying speed," and between that point and the end of the runway, it became airborne, then settled back onto the runway. The pilot decided to abort the takeoff, and reduced power and applied braking, but then realized that the airplane would not be able to stop prior to impacting a berm located at the end of the runway. He added full power, and the airplane cleared the berm, crossed a dirt road, impacted a tree and some boulders, and came to rest in a pond. The pilot stated that it had rained earlier in the day and the runway might have still been damp. The pilot also stated that he "did not detect any mechanical malfunctions."