The U.S. aircraft register, updated daily
Accidents · NTSB ERA19FA034 · Final report

Amateur-built Cavalon accident near Sebring, Florida, October 30, 2018

On October 30, 2018 at about 6:48 pm local time, a 2017 amateur-built Cavalon (gyroplane), registered N198LT, was destroyed in an accident during maneuvering near Sebring, Florida (Sebring Rgnl airport). It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 12, 2026. Docket and reports at the NTSB.

What the record shows

Date
October 30, 2018 · about 6:48 pm local time · cases in 2018
Place
Sebring, Florida · Sebring Rgnl · cases near this airport · map
Type
Accident
Injuries
2 people were killed.
Weather
visual conditions (good weather)
Aircraft
Amateur-built Cavalon, built 2017
Registration
N198LT · no longer on the register · serial V00299
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Flight control sys malf/fail during maneuvering defining event
  2. Loss of control in flight during enroute
  3. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
  4. Fire/smoke (post-impact) during post (impact)

The NTSB's findings

  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
  • cause Aircraft › Aircraft propeller/rotor › Rotorcraft flight control › Main rotor control › Not serviced/maintained
  • factor Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
  • factor Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot

Pilot

  • Certificate: flight instructor, commercial pilot, private
  • Ratings: single-engine land; instructor: gyroplane; instrument: airplane; rotorcraft: gyroplane
  • Flight time: 4,010 hours in all; 6 in this make and model; 600 on instruments
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: rgt
  • Injury: fatal

The aircraft

  • Airframe total time: 16.6 hours
  • Last inspection: condition inspection, October 4, 2018; 24 hours since
  • Maximum gross weight: 990 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Rotax 914 UL (piston); 40 hours total
  • Fire on the ground
  • Operator: Cavalon Gyro Llc

The flight

  • Departed from: SEF Sebring FL at 6:40 pm
  • Destination: 48X Palmetto FL
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 030° at 6 knots
  • Sky: clear
  • Temperature: 82°F (28°C), dew point 55°F (13°C)
  • Altimeter: 30.06 inHg
  • Observation at 7:15 pm from KSEF, 8 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Photographs from the investigation 8 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

Documents from the investigation the NTSB's docket: the evidence folder behind the report

31 documents, released by the NTSB on May 5, 2020. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Aircraft Build Timeline - Terri Rose PDF, 3 pages · our copy View Download
2 Memorandum for Record Terri Rose PDF, 1 page · our copy View Download
3 Geoff Painter CLOUD9 Email Statement PDF, 2 pages · our copy View Download
4 Jeffrey Hudson Statement and Email Statement PDF, 4 pages · our copy View Download
5 Witness Statement - Jeffery Hudson 2ND Statement PDF, 2 pages · our copy View Download
6 Memorandum for Record Bob Snyder Initial Interview PDF, 2 pages · our copy View Download
7 Witness Statement - Mike Damboise PDF, 1 page · our copy View Download
8 Witness Statement - Kathy Howitt PDF, 2 pages · our copy View Download
9 Record of Conversation Matthew Hood PDF, 3 pages · our copy View Download
10 Record of Conversation Calvin Cannon PDF, 4 pages · our copy View Download
11 Memorandum for Record Louis Trillo PDF, 2 pages · our copy View Download
12 Memorandum for Record - Denny Velarde - Test Pilot PDF, 1 page · our copy View Download
13 Witness Summary - Kevin Turner PDF, 5 pages · our copy View Download
14 Witness Statement - Curt Ruggles PDF, 2 pages · our copy View Download
15 Memorandum for Record Bob Snyder Flight Controls PDF, 1 page · our copy View Download
16 Maintenance Entries PDF, 1 page · our copy View Download
17 Flight Control Connection Instructions and Inspections PDF, 32 pages · our copy View Download
18 POH Preflight Check PDF, 1 page · our copy View Download
19 Rotax Preflight Excerpt PDF, 1 page · our copy View Download
20 Ground Run Protocol PDF, 1 page · our copy View Download
21 Flight Control Exam PDF, 1 page · our copy View Download
22 Materials Laboratory Report 19-087 PDF, 3 pages · our copy View Download
23 Build Assist Agreement PDF, 1 page · our copy View Download
24 Text Conversation Between Accident Pilot and Autogryro USA PDF, 7 pages · our copy View Download
25 Flight Control Emergency POH Section PDF, 1 page · our copy View Download
26 Memorandum for Record - Rotor Track and Balance PDF, 2 pages · our copy View Download
27 Fuel Purchases PDF, 3 pages · our copy View Download
28 Photo Array PDF, 8 pages · our copy View Download
29 Statement of Party Rep to the NTSB PDF, 2 pages · our copy View Download
30 Toxicology Report PDF, 1 page · our copy View Download
31 Release of Aircraft Wreckage, NTSB Form 6120.15 PDF, 3 pages · our copy View Download

The same docket at the NTSB.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/ERA19FA034.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.