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.
Danbury, CT
The pilot planned to conduct a post-maintenance test flight in the vicinity of the departure airport. The pilot initially reported that the takeoff seemed normal at first, but as it progressed it began to feel “sluggish.” When the airplane was about half to three-quarters of the way down the runway, he observed an indicated airspeed of 62 knots, and became concerned the airplane was not performing correctly. He elected to abort the takeoff, retarded the throttle and applied brakes. The airplane continued past the end of the runway, veered into grass, and impacted a perimeter fence, which resulted in substantial damage to the airplane’s left wing. A review of recovered data recorded by the onboard avionics showed that the airplane accelerated to an indicated airspeed of 85 knots before it began decelerating. The pilot, after reviewing the recorded avionics data, acknowledged that the engine developed full rated power throughout the takeoff roll, and that the airplane accelerated normally prior to the abort decision. He also reported that there was no glare that would have impacted his ability to observe the primary flight display’s airspeed indicator. The pilot also stated that there were no preimpact mechanical malfunctions or failures of the airplane that would have precluded normal operation.
The pilot’s decision to abort the takeoff with insufficient runway remaining, which resulted in a runway excursion.
The pilot planned to conduct a post-maintenance test flight in the vicinity of the departure airport. The pilot initially reported that the takeoff seemed normal at first, but as it progressed it began to feel “sluggish.” When the airplane was about half to three-quarters of the way down the runway, he observed an indicated airspeed of 62 knots, and became concerned the airplane was not performing correctly. He elected to abort the takeoff, retarded the throttle and applied brakes. The airplane continued past the end of the runway, veered into grass, and impacted a perimeter fence, which resulted in substantial damage to the airplane’s left wing. A review of recovered data recorded by the onboard avionics showed that the airplane accelerated to an indicated airspeed of 85 knots before it began decelerating. The pilot, after reviewing the recorded avionics data, acknowledged that the engine developed full rated power throughout the takeoff roll, and that the airplane accelerated normally prior to the abort decision. He also reported that there was no glare that would have impacted his ability to observe the primary flight display’s airspeed indicator. The pilot also stated that there were no preimpact mechanical malfunctions or failures of the airplane that would have precluded normal operation.