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.
Denver, CO
The pilot stated that it was a very windy day with winds above 20 mph and gusts to 30 mph when he attempted a takeoff in his gyroplane. He stated that during the takeoff roll with the pre-rotor engaged to 130 to 140 RPM, he gently eased back on the cyclic and a gust of wind caught the rotors. He felt the rotor flap and then a bump. He immediately arrested the rotor flap and then continued the takeoff roll. When the gyroplane became airborne, he realized there was less rudder authority and returned to land at the departure airport without further incident. After landing, the pilot noticed that rudder had been damaged due to a rotor strike, which likely occurred when the rotor flapped during takeoff, resulting in substantial damage to the rudder. The pilot stated that he should have had the rotors pre-rotated to 160 RPM or greater prior to pulling back on the cyclic, and there were no preaccident mechanical malfunctions or failures of the gyroplane that would have precluded normal operation.
The pilot’s failure to attain rotor RPM and maintain proper rotor disc angle during takeoff which resulted in a rotor strike with the rudder.
The pilot stated that it was a very windy day with winds above 20 mph and gusts to 30 mph when he attempted a takeoff in his gyroplane. He stated that during the takeoff roll with the pre-rotor engaged to 130 to140 RPM, he gently eased back on the cyclic and a gust of wind caught the rotors. He felt the rotor flap and then a bump. He immediately arrested the rotor flap and then continued the takeoff roll. When the gyroplane became airborne, he realized there was less rudder authority and returned to land at the departure airport without further incident. After landing, the pilot noticed that rudder had been damaged due to a rotor strike, which likely occurred when the rotor flapped during takeoff, resulting in substantial damage to the rudder. The pilot stated that he should have had the rotors pre-rotated to 160 RPM or greater prior to pulling back on the cyclic, and there were no preaccident mechanical malfunctions or failures of the gyroplane that would have precluded normal operation.