ERA18LA095

NTSB accident investigation · Robert Snyder Autogyro Calidus · Beaufort, SC · March 5, 2018

Accident · FatalLimited investigationFinal report
Date
March 5, 2018, 09:35 local (14:35 UTC)
Place
Beaufort, SC
Injuries
1 fatal
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N221YTRobert Snyder Autogyro Calidus
Defining event
Approach: Loss of control in flight
Weather
Visual (VMC) · Day
Status
Completed · report October 10, 2018
Report
Approved by Office Director
NTSB office
Eastern Region Aviation
Parties
FAA/FSDO
FAA report
20180305001459A
Case key
96822

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

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.

Findings · 3

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Performance/control parameters: prop/rotor parametersAircraft › Aircraft oper/perf/capability · Not attained/maintainedRobert Snyder AUTOGYRO CALIDUS: 1 caseAll aircraft: 182 casesProbable cause
Performance/control parameters: lateral/bank controlAircraft › Aircraft oper/perf/capability · Not attained/maintainedRobert Snyder AUTOGYRO CALIDUS: 1 caseAll aircraft: 390 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

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.

Factual narrative

On March 5, 2018, about 0935 eastern standard time, an experimental, amateur-built Autogyro Calidus gyroplane, N221YT, was substantially damaged when it impacted terrain during approach to Beaufort County Airport (ARW), Beaufort, South Carolina. The private pilot was fatally injured. The gyroplane was owned and operated by the pilot under the provisions of Title 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed for the local personal flight, which departed ARW about 0932.According to a witness who worked at the airport, the pilot of the gyroplane made a transmission on the airport's common traffic advisory frequency (CTAF) that he was taking off on runway 25. The witness observed the gyroplane take off and climb to about 75 ft above ground level about halfway down the 3,434-ft-long runway. The gyroplane was climbing slowly, and everything appeared normal. The witness did not continue to watch the gyroplane but heard the pilot make another routine radio transmission at 0933. At 0937, the witness received a telephone call that the gyroplane had crashed near the departure end of runway 25 at 0935. The caller reported to the witness that the gyroplane was low over a field when it rolled inverted and impacted a marsh. Another witness reported that he was taxiing his airplane for takeoff on runway 7 at ARW. The gyroplane had just taken off and the accident pilot announced on the CTAF that he was departing on runway 25 and returning to runway 7 with a simulated engine out. The witness estimated that the gyroplane climbed to 300 to 500 ft above ground level before performing the maneuver. By the time the witness's airplane reached the runway 7 threshold, the gyroplane had crashed. The witness further stated that it was possible that the accident pilot did not obtain enough altitude to perform the maneuver. A third witness was driving his car near the departure end of runway 25. He stated that the gyroplane climbed from the runway and flew over a road at the departure end. At that time, it appeared to be flying straight. About 10 seconds later, the gyroplane reversed direction and seemed to be flying back toward the departure end of the runway. The gyroplane was flying erratically and looked like it was "performing tricks;" specifically, the nose was pitching up, down, left, and right. As the gyroplane neared the runway, the nose pitched up and the gyroplane rolled inverted and impacted the ground. A fourth witness reported that he was sitting on the tailgate of his pickup truck in the parking lot of a department store adjacent to the airport. The witness watched the accident gyroplane perform touch-and-go landings. The witness estimated that the gyroplane performed four touch-and-go landings over a period of 15 to 20 minutes before the accident occurred. The pilot held a private pilot certificate with ratings for airplane single-engine land and instrument airplane. He also held a sport pilot certificate. The pilot's mostrecent Federal Aviation Administration (FAA) third-class medical certificate was issued on September 13, 2017. At that time, he reported 921 total hours of flight experience. Review of the pilot's logbook revealed that he had accrued about 944 total hours of flight experience at the time of the accident, of which about 91 hours were in the accident gyroplane. The pilot had flown about 6 hours during the 30 days preceding the accident, all of which were in the accident gyroplane. He flew 9 hours during the 90 days preceding the accident and all but 1 of those hours were in the accident gyroplane. The two-seat tandem, fixed tricycle gear, composite gyroplane was assembled from a kit and issued an FAA experimental airworthiness certificate in 2015. It was powered by a Rotax 912ULS, 100-horsepower engine, equipped with an HTC three-blade, ground adjustable, composite pusher propeller and a two-blade aluminum rotor. Review of the maintenance records revealed that the gyroplane's most recent condition inspection was completed on April 22, 2017. At that time, the airframe and engine had accumulated 183.5 total hours of operation. The 0935 recorded weather at ARW included wind from 310° at 4 knots, 10 statute miles visibility, clear sky, temperature 12°C, dew point 4°C, and altimeter setting of 30.13 inches of mercury. Examination of the wreckage by an FAA inspector revealed that it came to rest on its right side north of the departure end of runway 25. There was no debris path noted and the fiberglass cockpit and engine enclosures were destroyed. The nose section, with the nose landing gear attached, had separated from the fuselage, but all associated cables remained attached. The main landing gear was partially collapsed. The tailboom was twisted and canted to the left of the fuselage, with its horizontal stabilizer bent upward. All three propeller blades were fractured. One main rotor blade separated from the hub and exhibited an approximate 90° upward bend near the blade root. The other main rotor blade remained attached to the hub and did not exhibit damage with the exception of separation near the blade tip. One fuel tank was breached during impact. The other fuel tank remained intact and contained about 5 gallons of automotive fuel. No water or other contamination appeared in the fuel. The engine remained intact and attached to its mounts. Two FAA inspectors examined the wreckage after it was recovered to a hangar. Due to the disposition of the wreckage, they were only able to rotate the propeller about 90°, but they noted no binding and observed continuity through the engine. The gyroplane's flight controls consisted of push-pull tubes that sustained impact damage; however, there was no evidence of a preaccident flight control discontinuity. The Medical University of South Carolina, Charleston, South Carolina, performed an autopsy on the pilot. The autopsy report noted the cause of death as blunt trauma to head and chest. The FAA BioaeronauticalSciences Research Laboratory, Oklahoma City, Oklahoma, performed toxicological testing on specimens of the pilot. The results were negative for drugs and alcohol.

Aircraft

Registration
N221YT
Reported as
Robert Snyder Autogyro Calidus (NO SERIES)
Category
Gyroplane, amateur-built
Serial number
C00360
Built
2015
Airframe hours
183.5
Engine
Rotax 912ULS, 100 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Special, Experimental (Special)
Last inspection
Condition · April 22, 2017
Departed
ARW · Beaufort, SC
Destination
ARW · Beaufort, SC
Airport
ARW · Beaufort County Airport, runway 7, 3,434 × 75 ft, asphalt
Equipment
Unknown

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
69
Injuries
Fatal
Certificates
Private, Sport Pilot
Airplane ratings
Single-engine land
Instrument ratings
Airplane
Medical
Class 3, With waivers/limitations
Last flight review
November 17, 2016
Seat
Front
Restraint
4-point
Toxicology
Performed
Flight hours
944 total · 91 in this make and model · 9 in the last 90 days · 6 in the last 30 days

Weather

Conditions
Visual (VMC) · Day
Wind
310° at 4 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
54 °F, dew point 39 °F
Altimeter
30.12 inHg
Observed at
ARW

Docket · 9

The files NTSB released with the investigation on September 27, 2018, on NTSB’s docket system: statements, records, photos and specialists’ reports. 10.0 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.