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

Amateur-built AUTOGYRO CALIDUS accident near Beaufort, South Carolina, March 5, 2018

On March 5, 2018 at about 2:35 pm local time, a 2015 amateur-built AUTOGYRO CALIDUS (gyroplane), registered N221YT, was substantially damaged in an accident during approach near Beaufort, South Carolina (Beaufort County Airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The gyroplane pilot's failure to maintain rotor speed and aircraft control as he was attempting to return to the runway during a low-altitude simulated engine-out maneuver.

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

What the record shows

Date
March 5, 2018 · about 2:35 pm local time · cases in 2018
Place
Beaufort, South Carolina · Beaufort County Airport · cases near this airport · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Amateur-built AUTOGYRO CALIDUS NO SERIES, built 2015
Registration
N221YT · no longer on the register · serial C00360
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

After performing a normal takeoff, the private pilot of the gyroplane transmitted over the radio that he was going to conduct a simulated engine-out maneuver and return to the opposite runway. Witnesses saw the gyroplane flying toward the runway erratically and at low altitude over a field. The gyroplane's nose pitched up, and the gyroplane rolled inverted before impacting a grass area to the side of the runway. One witness, who was also a pilot, estimated that the gyroplane climbed to 300 to 500 ft above ground level before performing the maneuver and speculated that it may not have been enough altitude to complete the maneuver. Examination of the wreckage did not reveal any preimpact mechanical malfunctions and the two main rotor blades did not exhibit significant rotational damage. It is likely that, as the pilot was maneuvering aggressively at low altitude with the engine power at idle, he allowed the main rotor speed to decay, which resulted in a subsequent loss of control and impact with terrain.

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. Simulated/training event during initial climb
  2. Loss of control in flight during approach defining event
  3. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent

The NTSB's findings

  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Prop/rotor parameters › Not attained/maintained
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Lateral/bank control › Not attained/maintained

Pilot

  • Certificate: private, sport pilot
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 944 hours in all; 91 in this make and model; 9 in the last 90 days; 6 in the last 30 days
  • Last flight review: November 17, 2016
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: frt
  • Injury: fatal

The aircraft

  • Airframe total time: 183.5 hours
  • Last inspection: condition inspection, April 22, 2017
  • Maximum gross weight: 990 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Rotax 912ULS (piston); 184 hours total

The flight

  • Departed from: ARW Beaufort SC at 2:32 pm
  • Destination: ARW Beaufort SC
  • Flight plan: none
  • Runway 7, 3,434 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 310° at 4 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 54°F (12°C), dew point 39°F (4°C)
  • Altimeter: 30.12 inHg
  • Observation at 2:35 pm from ARW

Injuries

FatalSeriousMinorNone
Flight crew1

Photographs from the investigation 5 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

9 documents, released by the NTSB on September 27, 2018. 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 Interview Summaries PDF, 2 pages · our copy View Download
2 Witness Statements PDF, 3 pages · our copy View Download
3 Excerpt from Police Report PDF, 1 page · our copy View Download
4 Pilot Logbook PDF, 30 pages · our copy View Download
5 Aircraft Logbook Excerpts PDF, 3 pages · our copy View Download
6 Weather Report PDF, 2 pages · our copy View Download
7 FAA Inspector Statement PDF, 1 page · our copy View Download
8 Photo Array PDF, 5 pages · our copy View Download
9 Toxicological Report PDF, 1 page · 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/ERA18LA095.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.