FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA19FA034 · Autogyro Cavalon

30 Oct 2018 · Sebring, FL, United States

Cavalon Gyro Autogyro Cavalon · Accident: flight control system malfunction/failure while maneuvering

From Sebring Regional Airport (SEF) to Airport Manatee Airport (48X)

Report a problem

Event

NTSB case
ERA19FA034
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
2 · 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
N198LT
Operator
Cavalon Gyro
Onboard fatalities
Unknown
Route
From Sebring Regional Airport (SEF), Sebring, FLTo Airport Manatee Airport (48X), Palmetto, FL
Aircraft age
About 1 year (built 2017)
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
Maneuvering
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
Flight control system malfunction/failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft propeller/rotor
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

On the morning of the accident, the commercial pilot flew the accident gyroplane for 2 hours and then serviced it with fuel. Later that day, he departed on the accident flight with the passenger. Radar information revealed that the accident gyroplane climbed to an altitude of about 1,000 ft and began a cruise profile on a westerly heading. The gyroplane's radar track traversed the southern border of a nearby lake until it began to descend while flying over the southwestern shore of the lake. The gyroplane's descent followed the shoreline to the northwest before the radar target disappeared. At that point, the gyroplane was at an altitude of 900 ft, a groundspeed of 90 knots, and was located about 0.4 mile southeast of the accident site.

Two mayday calls from the gyroplane were recorded before the sound of impact. During the audible portions of the transmissions, sounds consistent with increasing and decreasing engine power were heard. One witness observed the gyroplane when it was about 300 ft above ground level "with very little airspeed" and before it "entered an autorotation." The witness described multiple heading changes before the gyroplane descended from his view. The gyroplane collided with power lines, a power pole, and a residence. The gyroplane and the residence were consumed by postcrash fire. Examination of the wreckage revealed the pitch control cable between the cyclic control tube and the main rotor head had likely disconnected at the control tube during flight. This connection was secured by a bolt and nut, which were not recovered.

The pilot took possession of the gyroplane on the day before the accident. Upon inspection, the pilot found improper logbook documentation and learned of mechanical discrepancies, including the need for a rotor balance, that rendered the gyroplane unairworthy, but he flew it anyway. During the subsequent flight, the pilot noted that the cyclic pitch control vibration was "excessive." After landing, the pilot attempted to bring the rotor system into balance, but the rotor vibration persisted. The continuing vibration was an indication of a safety-of-flight issue, yet the pilot continued to fly the gyroplane.

Given this information, it is likely that the disconnection of the cyclic pitch control tube from the main rotor system was due to the separation of a bolt and nut that connected them together. Because the nut and bolt were not recovered, they could not be examined to determine whether they had been assembled correctly. While it could not be definitively determined why the nut and bolt separated, it is likely that the unabated vibration reported by the pilot during the previous flights contributed to their eventual separation, and the inflight loss of pitch control. Despite this, the gyroplane likely was still controllable through the use of electric/pneumatic trim and engine power application, per a published emergency procedure. Given the witness statements describing the final moments of the flight, it is likely that the pilot lost control of the gyroplane before impacting powerlines and a residence.

Probable cause

The pilot's improper decision to operate the gyroplane in an unairworthy condition, which resulted in the cyclic pitch control disconnecting in flight. Contributing was the pilot's inability to maintain control of the helicopter utilizing the published emergency procedure.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA19FA034
Event ID
20181030X64550
Case number
ERA19FA034
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. 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: 6f57130252bc5ea50f9bc1b032c8834e4cd47c633c1ed9bc29795bef1e32668f; retrieved 2026-09-15T06:50:09.645Z.