NTSB CAROL · Event
Event GAA18CA086
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 ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
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.
- NASA NTRS 2019 · Technical Memorandum (TM)
Water/glycol temperature control circuit failed in the automatic mode: Apollo 16
An anomaly report concerning failure of the water/glycol temperature control circuit during the Apollo 16 flight is presented. The anomaly is described and diagrams of the system are presented.
- NASA NTRS 2019 · Technical Memorandum (TM)
Apollo 15 mission main parachute failure
The failure of one of the three main parachutes of the Apollo 15 spacecraft was investigated by studying malfunctions in the forward heat shield, broken riser, and firing the fuel expelled from the co…
- NASA NTRS 2019 · Reprint (Version printed in journal)
Integrated operating mode of the Apollo mission simulator.
Integrated operating mode of Apollo mission simulator with mission control center for combined training of Apollo flight and ground crews
- NASA NTRS 2019 · Conference Paper
Integrated operating mode of the apollo mission simulator.
Integrated operating mode of Apollo mission simulator with mission control center for combined training of Apollo flight and ground crews
- Embry-Riddle Scholarly Commons 2016 · Conference paper
Mid Day Concurrent Session: Apollo EECOM: Journey of a Lifetime - Sy Liebergot
Sy Liebergot's account of his role in helping to save the Apollo XIII NASA mission.
- NASA NTRS 1995 · Other - N68-27995
Development and Verification of the Vibration Test Requirements for the Apollo Command and Service Modules
Development and verification of vibration test requirements for Apollo command and service modules
Browse the full corpus — academia portal ↗