19 Jun 2010: LUSCOMBE 11A

19 Jun 2010: LUSCOMBE 11A (N1606B) — Unknown operator

No fatalities • Merced, CA, United States

Probable cause

The pilot’s inability to maintain airplane control during cruise flight due to the failure of the elevator trim tab as a result of missing hardware for the elevator control cable bellcrank to elevator torque tube attachment bracket.

— NTSB Determination

Accident narrative

On June 18, 2010, about 1830 Pacific daylight time, a Luscombe 11A, N1606B, attempted to make an emergency landing on highway 99 near Merced, California, following a flight control issue. During the descent, the left wing was damaged after it struck a heavy advertising sign and fence pole. The pilot/owner operated the airplane under the provisions of Title 14 Code of Federal Regulations Part 91, as a local area flight. The commercial pilot, the sole occupant, was not injured. The airplane sustained substantial damage. Visual meteorological conditions prevailed for the flight that departed from Visalia Municipal Airport (VIS), Visalia, California. No flight plan had been filed for the flight that was destined for the Nut Tree Airport (VCB), Vacaville, California.

In the pilot’s written report (National Transportation Safety Board (NTSB) pilot/operator aircraft accident/incident form 6120.1), he reported that his first leg of the flight originated from Whiteman Airport (WHP), Los Angeles, California. Prior to takeoff, he conducted a thorough preflight and run-up, and reported that everything was normal. The pilot departed WHP and had an uneventful flight and landing at VIS. Prior to departing from VIS, the pilot refueled the airplane, and conducted a walk around of the airplane to check for any discrepancies that may have occurred during his flight from WHP to VIS.

The pilot reported that the departure from VIS to VCB was normal. Several minutes into the flight, the pilot experienced “violent shaking” in the control yoke that shook the entire airplane. Attempting to determine the cause of the shaking, the pilot looked out of the pilot’s side window and observed the trim tab “fluttering” violently up and down. The pilot then looked at the trim wheel in the cockpit and saw that it did not show corresponding movement. The pilot reduced power to slow the airplane; despite the pilot’s full aft elevator pressure, the airplane began to descend. The pilot then realized he did not have elevator control, and started to control the airplane’s pitch angle by manually manipulating the throttle; increasing and decreasing the power setting. The pilot further stated that once he had partial control of the airplane he attempted to contact air traffic control and use his global position system (GPS), but his avionics were flashing on and off, and he began to smell something akin to electrical burning.

The pilot initiated a forced landing onto a road. During the descent, the tire of the left main landing gear bounced off a moving truck, and the airplane floated over an orchard adjacent to a highway. The airplane continued to descend; during landing the left wing struck a heavy advertising sign, followed by a fence post. The airplane turned towards the left, touched down and porpoised twice, striking the propeller on the ground both times. On the second propeller strike, the airplane’s left main landing gear separated from the fuselage, and the airplane slid on its cowling until coming to a rest.

In the pilot’s report he also stated that the trim tab had failed outboard of the trim tab control horn bracket attachment. The upper bolt of the elevator control cable bellcrank to the elevator torque tube attachment bracket was missing.

In the pilot report recommendation section on how the accident could have been prevented, the pilot said to reinvestigate Service Bulletin (AD) 49-40-01, which addressed the Luscombe elevator trim tabs with respect to metal fatigue.

Post-accident examination by an NTSB investigator and a Federal Aviation Administration (FAA) inspector revealed that the inboard tip of the elevator trim tab had separated from the trim tab but remained attached to the operating arm. The bolt hole where the operating arm is attached to the trim tab piece was elongated. Investigators further notated damage to the inboard hinge of the elevator. The elevator torque tube is not a continuous piece; each part fits onto its respective side of the elevator bellcrank. The attachment flange is triangular and both sides are clamped together with three bolts. The forward edge of the right side attachment flange was bent aft. The NTSB investigator did not see a bolt in the upper attachment point or a bolt in the aft attachment point. The upper part of the elevator torque tube rotated aft. The right side of the torque tube had rub marks on the leading edge with corresponding damage on the adjacent airframe skin, with no damage to the rudder skin that is aft of it. The left side torque tube had rub marks on the tailing edge with corresponding damage to the rudder skin behind it, which was buckled. The two bolt holes showed no elongation or other damage.

The FAA inspector further reported that the pilot informed him that he observed arcing marks on the battery leads and on the inside top of the battery case.

According to the airplane’s airframe AD compliance record, it was recorded that on December 1, 1949, the airplane had complied with AD 49-40-01. According to the airframe maintenance logbook, the most recent annual inspection was on January 11, 2010, which stated that the airplane was inspected and determined to be in an airworthy condition at the time of the inspection. The pilot reported that the airplane had flown 7 hours since the annual inspection.

Contributing factors

  • cause Elevator misc structure — Failure
  • cause Attach fittings (flt controls) — Failure

Conditions

Weather
VMC, wind 320/18kt, vis 10sm

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.