Event GAA20CA044

Factual narrative

The gyroplane pilot reported that, during the takeoff roll, the rotor "flapped" and struck the rudder. He aborted the takeoff and taxied to the ramp without further incident. The gyroplane sustained substantial damage to the rudder. The pilot reported that there were no preaccident mechanical failures or malfunctions with the gyroplane that would have precluded normal operation. The pilot added that he did not configure the rotor speed according to the manufacturer's recommended value prior to takeoff and should have followed the checklist. The pilot reported that, during the takeoff roll, the gyroplane's rotor "flapped" and struck the rudder. He aborted the takeoff and taxied to the ramp without further incident. The gyroplane sustained substantial damage to the rudder. The pilot reported that there were no preaccident mechanical failures or malfunctions with the gyroplane that would have precluded normal operation. The pilot stated that if he had aborted the takeoff at the first indication of a problem the accident could have been avoided. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12

NTSB Findings

Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).

• C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Prop/rotor parameters-Not attained/maintained - C
• C Personnel issues-Task performance-Use of equip/info-Use of equip/system-Pilot - C
• F Personnel issues-Action/decision-Action-Delayed action-Pilot - F