WPR12LA413

NTSB accident investigation · Ellefson T-BIRD II · Richfield, UT · September 5, 2012

Accident · Serious injuriesLimited investigationFinal report
Date
September 5, 2012, 10:00 local (16:00 UTC)
Place
Richfield, UT
Injuries
1 serious
Damage
Substantial damage
Phase of flight
Takeoff
Aircraft
N8106CEllefson T-BIRD II
Defining event
Takeoff: Loss of control in flight
Weather
Visual (VMC) · Day
Status
Completed · report December 15, 2014
Report
Approved by Office Director
NTSB office
Western Pacific Region
Parties
Federal Aviation Administration
FAA report
20120905019769A
Case key
84992

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

A loss of control during landing due to a pitch control malfunction. Contributing to the accident was the pilot’s decision to continue flight with a known mechanical problem.

Findings · 2

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.

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

The pilot reported that the new owner of the ultralight had reassembled it and found that it oscillated during level flight and that the owner then contacted him for assistance in diagnosing the issue. He reported that he conducted a preflight inspection and noted no anomalies. Immediately after takeoff, the ultralight began to oscillate up and down with no elevator input. The pilot stayed in the traffic pattern, and the oscillations continued at different altitudes and airspeeds. During landing, the ultralight touched down about 45 knots with upward oscillations. The pilot decided to take off again and experiment with different trim settings. Upon liftoff, the ultralight again began to oscillate with no throttle or elevator inputs. The pilot decided to depart the traffic pattern to further experiment with the trim and power settings; however, different trim and power settings had no effect on the oscillations. The pilot indicated that the oscillations were random, so he could only react to the direction with flight control corrections and could not anticipate which flight control corrections would be needed. The pilot reentered the traffic pattern for landing and, during the landing, when the ultralight was about 5 feet above the ground and at 40 knots, the oscillations began again. The pilot pushed the yoke forward, which stopped the oscillations; however, the rear main landing gear touched down on the runway, which forced the ultralight back into the air. The pilot recalled that the ultralight's nose then pointed downward and that he pushed full left rudder before the ultralight impacted the ground. After the accident, the pilot learned that the owner had reassembled the ultralight without assistance from a mechanic. While inspecting the ultralight after the accident, the pilot noted that, if the pitch control cable was loose, it would randomly move. The ultralight was not made available by the owner for examination; therefore, the reason for the oscillations could not be determined; however, it is likely that the pitch control cable was loose, causing the random oscillations.

Factual narrative

On September 5, 2012, about 1000 mountain daylight time, an experimental amateur built Ellefson T-Bird II ultralight, N8106C, experienced a loss of flight control during landing, and impacted the ground about 1 mile south of the Richfield Municipal Airport (RIF), Richfield, Utah. The commercial pilot operated the ultralight under the provisions of 14 Code of Federal Regulations Part 91 as a test flight. The pilot, the sole occupant, received serious injuries. The ultralight sustained substantial damage. Visual meteorological conditions prevailed for the local area flight, and no flight plan was filed.According to the pilot, he had been contacted by the owner for assistance with his ultralight as it was oscillating in level flight. The owner had told the pilot that he had purchased the ultralight in New Mexico, and that he and the former owner disassembled it for transportation to RIF. The new owner then reassembled the ultralight, and noted that according to the plans, there were saddle washers and spacers missing on the horizontal stabilizer. The pilot told the owner that he had those washers and spacers, and the owner authorized the pilot to "fix whatever was wrong with it." A couple of days before the accident, the pilot met with the owner to get a better understanding of the oscillations, and at that time, the pilot added the washers and spacers that were missing on the horizontal stabilizer. On the day of the accident he performed a preflight, with no mechanical abnormalities noted. On the first flight, immediately after takeoff, the ultralight started to oscillate randomly up and down without any corresponding elevator input from the pilot. He remained in the pattern and performed a low flyby. The oscillations continued at different altitudes and airspeed. The ultralight touched down between 40 and 45 knots, with oscillations in an upward motion, and the yoke was full forward. The pilot decided to take off again to experiment with different trim settings. Upon liftoff, the oscillations began immediately with no throttle or elevator input. He decided to depart the pattern as he wanted to experiment with the trim and power settings; there was no effect on the oscillations. He reentered the pattern for landing. The pilot stated that the oscillations were random and he did not know if the oscillations were going to be up or down. He could only react to the direction and not anticipate the direction, and input flight control authority accordingly. About 5 feet above the ground and 40 knots, the oscillations began again. He pushed the yoke forward, which stopped the oscillation, but the rear main landing gear touched down on the runway and the yoke slammed into his stomach. The ultralight's nose picked up and the ultralight moved to the right. At this point the ultralight's nose was pointed to the ground and the pilot recalled pushing full left rudder before the ultralight impacted the ground. The fuselage, nose, wings, and tail sections weresubstantially damaged. The pilot stated that after the accident, he found out that the owner had reassembled the ultralight without assistance from a mechanic. The pilot also found out that if the pitch control cable was loose, it would move randomly. The owner of the ultralight did not respond to requests to provide additional information about the ultralight, nor was it made available for additional inspection.

Aircraft

Registration
N8106C
Reported as
Ellefson T-BIRD II
Category
Ultralight, amateur-built
Serial number
5168
Airframe hours
224
Engine
Rotax 912UL, 80 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Special, Experimental (Special)
Last inspection
Annual · January 2, 2012
Departed
RIF · Richfield, UT
Destination
RIF · Richfield, UT
Airport
RIF · Richfield Muni Airport

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
65
Injuries
Serious
Certificates
Sport Pilot, Private, Flight instructor
Airplane ratings
Single-engine land
Medical
Class 3, With waivers/limitations
Last flight review
November 20, 2010
Seat
Left
Flight hours
2,300 total · 20 in this make and model

Weather

Conditions
Visual (VMC) · Day
Wind
Calm
Visibility
50 statute miles
Lowest ceiling
None
Temperature
70 °F, dew point 48 °F
Altimeter
30.04 inHg
Observed at
RIF, 1 nm away

Docket · 3

The files NTSB released with the investigation on October 30, 2014, on NTSB’s docket system: statements, records, photos and specialists’ reports. 462 KB 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.