CHI08LA052

NTSB accident investigation · Levick RAF-2000-GTX-SE · Salem, IN · December 14, 2007

Accident · Serious injuriesLimited investigationFinal report
Date
December 14, 2007, 14:26 local (19:26 UTC)
Place
Salem, IN
Injuries
1 serious
Damage
Destroyed
Phase of flight
Initial climb
Aircraft
N24DNLevick RAF-2000-GTX-SE
Weather
Visual (VMC) · Day
Status
Completed · report May 28, 2008
Report
Approved by Office Director
Parties
FAA-Indianapolis FSDO
FAA report
20071214828739A
Case key
67415

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 pilot's failure to maintain control of the gyroplane during climbout after takeoff.

Sequence of events

NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.

Loss of control - in flightTakeoff - initial climb
Aircraft control - not maintainedPilot in commandCause
In flight collision with terrain/waterDescent - uncontrolled
Terrain condition - ground

Analysis

A witness reported that after takeoff, when approximately 20 feet above ground level (agl), the gyroplane drifted to the right and the tail turned "abruptly" to the right about 90-degrees. The pilot reduced power and regained control. The gyroplane returned to the runway centerline and the pilot appeared to be setting up for a landing. However, when the gyroplane was about 5 feet above the runway, the pilot increased engine power and started to climb. About 75 to 100 feet agl, the tail of the gyroplane again turned "abruptly" to the right, the nose pitched up "steeply," and the aircraft rolled inverted. It subsequently impacted the ground on the rotor mast. A post accident examination did not reveal any anomalies consistent with a pre-impact failure or malfunction. The pilot did not have any recollection of the accident flight. He reported that he had owned the accident gyroplane for 2-1/2 years, but he was still just learning. He soloed the previous summer and had accumulated about 5 hours of solo flight time. He had about 20 hours total flight time in gyroplanes. The pilot held a private pilot certificate with a single-engine land airplane rating, with about 280 hours flight time in airplanes.

Factual narrative

On December 14, 2007, at 1426 eastern standard time, an amateur-built Levick RAF-2000-GTX-SE gyroplane, N24DN, piloted by a private pilot, was destroyed when it impacted terrain following an in-flight loss of control after takeoff from Salem Municipal Airport (I83), Salem, Indiana. The aircraft had departed from runway 28 (2,500 feet by 50 feet, asphalt) shortly before the accident. The personal flight was being conducted under 14 CFR Part 91 without a flight plan. Visual meteorological conditions prevailed. The pilot sustained serious injuries. The local flight was departing at the time of the accident.

The pilot stated that he did not have any recollection of the flight or of the accident sequence.

A witness to the accident reported that the pilot taxied onto runway 28 and began the takeoff roll. He stated that the gyroplane rotated at about the runway numbers. Approximately 20 feet above ground level (agl), the gyroplane drifted to the right and the tail turned "abruptly" to the right about 90-degrees. The pilot reduced power and regained control. The gyroplane returned to the runway centerline and the pilot appeared to be setting up for a landing. However, when the aircraft was about 5 feet above the runway, the pilot increased engine power and started to climb. About 75 to 100 feet agl, the tail of the aircraft again turned "abruptly" to the right, the nose pitched up "steeply," and the aircraft rolled inverted. It subsequently impacted the ground on the rotor mast.

A post accident examination of the gyroplane was conducted by Federal Aviation Administration inspectors. No anomalies consistent with a pre-impact failure or malfunction were identified. All three composite propeller blades were fragmented. The rotor blades, hub and a portion of the mast had separated from the airframe and were located with the main wreckage. The rudder had also separated from the airframe and was located with the main wreckage. The flight control system was examined. Discontinuities in the flight control system appeared consistent with overload failures sustained during impact.

The pilot reported that he had owned the accident aircraft for 2-1/2 years, but he was still just learning to fly a gyroplane. He soloed the previous summer and had accumulated about 5 hours of solo flight time. He had about 20 hours total flight time in gyroplanes. The pilot held a private pilot certificate with a single-engine land airplane rating. He had acquired about 280 hours flight time in airplanes.

A condition inspection of the gyroplane was completed on May 26, 2007. The aircraft had accumulated 227.5 hours flight time at the time of the inspection.

Aircraft

Registration
N24DN
Reported as
Levick RAF-2000-GTX-SE
Category
Gyroplane, amateur-built
Serial number
H2-98-340
Airframe hours
230
Engine
Subaru, 130 horsepower, reciprocating
Damage
Destroyed
Flight
Personal · Part 91
Airworthiness certificate
Special, Experimental (Special)
Last inspection
Condition · May 1, 2007 · 2.5 hours before
Departed
I83 · Salem, IN
Airport
I83 · Salem Muni, runway 28, 2,500 × 50 ft, asphalt

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
64
Injuries
Serious
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, With waivers/limitations
Last flight review
October 1, 2006
Seat
Left
Flight hours
300 total · 20 in this make and model

Weather

Conditions
Visual (VMC) · Day
Wind
0° at 4 knots
Visibility
10 statute miles
Lowest ceiling
25,000 ft broken
Temperature
43 °F, dew point 27 °F
Altimeter
30.30 inHg
Observed at
SDF, 32 nm away

FAA reports on this event · 1

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

Other investigations on N24DN · 1

Matched to the same aircraft by N-number and date.