Probable cause
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.
NTSB analysis
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.
Text from the NTSB. Open the NTSB docket for GAA18CA086 for the full record.
Event
- Date
- Dec 17, 2017
- Type
- Accident
- Place
- North Las Vegas, Nevada
- Nearest airport
- North Las Vegas (VGT)
- Highest injury
- None
- Weather
- Visual (VMC)
- Light
- Day
APOLLO
- N-number
- N15LU
- Category
- Gyroplane
- Year built
- 2016
- Damage
- Substantial
- Operating rule
- Part 91 (general aviation)
- Purpose of flight
- Personal
From the NTSB aviation accident database: N-registered aircraft, events since 2008, data through Oct 28, 2026. The file is published monthly, so the latest weeks are incomplete and recent records can change. The official source is the NTSB aviation investigation search. CheckAero is independent and not affiliated with the NTSB.