CEN22FA016 · AutoGyro Cavalon
AutoGyro Cavalon · Accident: runway excursion during takeoff
Event
- NTSB case
- CEN22FA016
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 1 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
AutoGyro Cavalon
- Aircraft type
- Autogyro CAVALON
- Category
- Gyroplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N419LB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 3 years (built 2018)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Takeoff
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Runway excursion
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
A witness reported that the pilot purchased the gyroplane in January 2020 and has been undergoing flight lessons. Two days before the accident was the pilot’s first solo flight. On the day of the accident, the witness observed the gyroplane positioned heading to the north on a 300-yard, private, field. The wind was gusting from the south, which was a tailwind. The pilot added full engine power and the gyroplane started its takeoff roll toward the north. The gyroplane never lifted off the ground and impacted a barbed wire fence at the end of the field. The witness proceeded toward the accident site, and he observed that the pilot was ejected from the gyroplane. The gyroplane came to rest upright with the engine still running. After calling for help, he turned the engine off via cockpit controls.
The pilot’s flight instructor reported that the pilot had about 20 total hours of flight training over the course of about a year. He would fly a few hours at a time with large gaps in-between. The pilot traveled a long distance to obtain the instruction and about 3 months prior to the accident, he elected to move the gyroplane closer to his home despite the instructor informing him he was not ready for solo flight. It is unknown if the pilot obtained additional flight instruction as advised.
On scene examination of the airframe did not reveal any anomalies that would have precluded normal operations. A large hole was noted in the forward windscreen; the seatbelts remained secured to the airframe, and they were not clasped. Since the pilot was ejected, it is likely he was not wearing a seatbelt.
The nearest weather reporting station was about 7 nautical miles northwest of the accident site. At the time of the accident, wind was from 160° at 8 knots, gusting to 17 knots, which would have been a tailwind. The AutoGyro Cavalon Pilot Operating Handbook states under Environmental Limitations “Maximum tailwind component for take-off and landing…5 knots.”
The pilot’s toxicology results showed that he had used methamphetamine. His high methamphetamine blood level was consistent with methamphetamine abuse although the level does not indicate if he was experiencing early drug effects (possibly feeling alert, euphoric, and invulnerable, with a tendency to make high-risk decisions) or later effects (possibly feeling restless, disorganized, uncoordinated, and craving more drug). Toxicology results also showed that the pilot had used THC, although it is impossible to infer specific impairing effects from the measured levels of THC and its metabolites, or to predict how THC and methamphetamine effects may have interacted.
Given the pilot’s overall lack of experience, along with his decision to take off with a tailwind, it is likely he did not possess the necessary skill or experience to safely conduct solo flight. Therefore, it was impossible to determine whether impairment of his handling of the aircraft from drug effects contributed to the accident.
Probable cause
The pilot’s lack of experience in the gyroplane and his decision to takeoff with a tailwind. As a result, the gyroplane did not generate enough lift to takeoff before it struck a barbed wire fence. Contributing to the accident was the pilot’s failure to wear a seatbelt, which would have reduced his level of injury.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN22FA016
- Event ID
- 20211019104119
- Case number
- CEN22FA016
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 8fd00750bacd4334caeeb026db51ab2bb296a87f2c8de5658907aa68ddab2f3e; retrieved 2026-09-15T07:35:43.379Z.