NTSB CAROL · Event
Event GAA18CA179
Registry · N442AG
FAA Aircraft Registry record.
Make / Model
AUTOGYRO GMBH CAVALON
Year of manufacture
2017 · 1 years old at event
Engine
ROTAX 914UL (115 hp)
Seats / Engines
2 seats · 1 engine
Last airworthiness date
20170721
ADS-B equipped
Yes — Mode-S A55212
Registrant of record
COGLEY WILLIAM S
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's failure to maintain directional control during a rejected takeoff. Contributing to the accident was the binding of the control stick, for an undetermined reason, which precipitated the rejected takeoff.
Factual narrative
The pilot of the gyroplane reported that, during the takeoff roll, after the front landing gear became light, he attempted to push the control stick forward, but was unable. He then used both hands in an attempt to push the stick forward. He realized he could not move the control stick forward and therefore could not control the gyroplane. He rejected the takeoff by reducing power, the gyroplane veered to the left, and the rotor struck the runway. Subsequently, the gyroplane rolled onto its left side, skidded down the runway, exited the left side of the runway, and impacted a snowbank. The gyroplane sustained substantial damage to the rotor system and fuselage. The pilot reported that he removed the rotor blade by removing the center pivoting bolt, and in doing so, the rotor head moved forward and freed the stick. The Federal Aviation Administration sent two inspectors to examine the gyroplane. During the visit, the rotor head moved freely in all directions with no evidence of binding or restriction, and no discrepancies were noted with the torque tube or cabling in the keel tube. The brake and trim controls were also moved in various sequences and control positions, but there were no discrepancies found. The FAA inspector added that, with an inadvertent and or unnoticed activation of full aft trim prior to beginning the takeoff roll, there could be enough resistance created to generate the conditions the pilot experienced. The pilot of the gyroplane reported that, during the takeoff roll, after the front landing gear became light, he attempted to push the control stick forward, but was unable. He then used both hands in an attempt to push the stick forward. He realized he could not move the control stick forward and therefore could not control the gyroplane. He rejected the takeoff by reducing power, the gyroplane veered to the left, and the rotor struck the runway. Subsequently, the gyroplane rolled onto its left side, skidded down the runway, exited the left side of the runway, and impacted a snowbank. The gyroplane sustained substantial damage to the rotor system and fuselage. The pilot reported that he removed the rotor blade by removing the center pivoting bolt, and in doing so, the rotor head moved forward and freed the stick. The Federal Aviation Administration sent two inspectors to examine the gyroplane. During the visit, the rotor head moved freely in all directions with no evidence of binding or restriction, and no discrepancies were noted with the torque tube or cabling in the keel tube. The brake and trim controls were also moved in various sequences and control positions, but there were no discrepancies found. The FAA inspector added that, with an inadvertent and or unnoticed activation of full aft trim prior to beginning the takeoff roll, there could be enough resistance created to generate the conditions the pilot experienced. 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-Directional control-Not attained/maintained - C
- C Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot - C
Verbatim from NTSB's published report. Source file
NTSB_2018_GAA18CA179.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.