5 Sep 2012: ELLEFSON T-BIRD II

5 Sep 2012: ELLEFSON T-BIRD II (N8106C) — Unknown operator

No fatalities • Richfield, UT, United States

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.

— NTSB Determination

Accident 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 were substantially 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.

Contributing factors

  • cause Malfunction
  • factor Pilot

Conditions

Weather
VMC, vis 50sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.