Skip to content

Atlas / NTSB / GAA18CA086

NTSB CAROL · Event

Event GAA18CA086

2017-12-17 North Las Vegas, Nevada, United States Airport · VGT None 1 aircraft Status: Completed

Aircraft involved

Probable cause & findings

The pilot’s failure to stop the main rotor rotation before taxiing the gyroplane in gusting wind conditions, resulting in the main rotor striking the empennage.

Factual narrative

According to the pilot in the experimental amateur-built gyroplane, he landed on a taxiway and taxied to the runway intersection. The intersection was on the right side of runway 30R. The ramp where the pilot wanted to park, was across both runways, on the left side of runway 30L. Unfamiliar with the capabilities of the gyroplane, the tower asked the pilot to air taxi to the ramp. The pilot informed the tower that he could either ground taxi, or takeoff and land on runway 30L, then taxi to the ramp. Tower and the pilot agreed to the latter. He further reported that in anticipation of taxiing to parking, he had allowed the Gyroplane's rotor speed to decrease, and when he turned the gyroplane back onto the taxiway in the gusting wind, the main rotor struck the empennage and the pusher-propeller. The gyroplane sustained substantial damage to the empennage and rotor system. The METAR at the accident airport reported that about the time of the accident, the wind was from 330° at 14kts and gusting to 19kts. Per the National Transportation Safety Board's Pilot Aircraft Accident Report, the pilot identified in the Owner Safety Recommendation section, that this accident could have been prevented if he had waited for the rotor blades to stop completely before repositioning the gyroplane for taxi. The pilot reported that there were no preaccident mechanical malfunctions or failures with the gyroplane that would have precluded normal operation. According to the pilot of the experimental amateur-built gyroplane, he landed on a taxiway and taxied to the runway intersection. The intersection was on the right side of runway 30R. The ramp where the pilot wanted to park, was across both runways, on the left side of runway 30L. Unfamiliar with the capabilities of the gyroplane, the tower controller asked the pilot to air taxi to the ramp. The pilot informed the tower controller that he could either ground taxi or takeoff and land on runway 30L then taxi to the ramp. The controller and the pilot agreed to the latter. The pilot further reported that, in anticipation of taxiing to parking, he had allowed the gyroplane's rotor speed to decrease; when he turned the gyroplane back onto the taxiway in the gusting wind, the main rotor struck the empennage and the pusher-propeller. The gyroplane sustained substantial damage to the empennage and rotor system. The METAR at the accident airport reported that about the time of the accident, the wind was from 330° at 14 kts and gusting to 19 kts. The pilot reported that this accident could have been prevented if he had waited for the rotor blades to stop completely before repositioning the gyroplane for taxi. The pilot reported that there were no preaccident mechanical malfunctions or failures with the gyroplane that would have precluded normal operation. 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 Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
  • C Aircraft-Aircraft propeller/rotor-Rotorcraft flight control-Main rotor control-Incorrect use/operation - C
  • Environmental issues-Conditions/weather/phenomena-Wind-Gusts-Effect on equipment

Verbatim from NTSB's published report. Source file NTSB_2017_GAA18CA086.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

What the literature says.

Academic papers and agency reports matching this event's aircraft type. Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.

Browse the full corpus — academia portal ↗