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.
Butler, PA
The pilot said the traffic pattern was busy, so he began the pre-rotation process as he taxied the gyroplane onto the runway to depart. At that time, the rotor disk rpm was at 140 rpm, which was 20 rpm above the recommended takeoff speed. The pilot said he slowly applied power because he had a passenger onboard, which may have allowed time for the disk speed to decay and become susceptible to blade flap. During the takeoff roll, the gyroplane’s main rotor blades struck and severed the tail assembly, resulting in substantial damage. The pilot said there were no preimpact mechanical malfunctions or failures that would have precluded normal operation.
The pilot’s failure to monitor rotor disk speed on takeoff, which resulted in blade flapping and the main rotor blades striking the gyroplane’s tail assembly.
The pilot said the traffic pattern was busy, so he began the pre-rotation process as he taxied the gyroplane onto the runway to depart. At that time, the rotor disk rpm was at 140 rpm, which was 20 rpm above the recommended takeoff speed. The pilot said he slowly applied power because he had a passenger onboard, which may have allowed time for the disk speed to decay and become susceptible to blade flap. During the takeoff roll, the gyroplane’s main rotor blades struck and severed the tail assembly, resulting in substantial damage. The pilot said there were no preimpact mechanical malfunctions or failures that would have precluded normal operation.