9 Nov 2013: EUROCOPTER DEUTSCHLAND GMBH EC135P1 — METRO AVIATION INC

9 Nov 2013: EUROCOPTER DEUTSCHLAND GMBH EC135P1 (N911KB) — METRO AVIATION INC

No fatalities • Shreveport, LA, United States

Probable cause

The mechanic's improper installation of the antitorque pedals, which resulted in an in-flight loss of helicopter control.

— NTSB Determination

Accident narrative

On November 9, 2013, about 1245 central standard time, a Eurocopter Deutschland GMBH EC135P1 helicopter, N911KB, impacted terrain near Shreveport, Louisiana. The commercial pilot and two company mechanics sustained minor injuries and the helicopter was substantially damaged. The helicopter was registered to and operated by Metro Aviation Inc., under the provisions of 14 Code of Federal Regulations Part 91 as a maintenance test flight. Visual meteorological conditions prevailed for the flight, which operated without a flight plan. The local flight was originating from the company's facility in Shreveport, Louisiana.The helicopter had recently undergone maintenance inspections at a company maintenance facility. The day prior to the accident several ground runs were performed on the helicopter in order to track and balance the rotor system and to check the parameters of the number 2 engine. The crew for the maintenance flight consisted of one pilot and two aviation mechanics. The pilot preflighted the helicopter and performed several ground runs. The helicopter was refueled, preflighted again, and the pilot completed a hover test in an adjacent field which was separated by a chain link fence. The hover test was completed without incident and the pilot landed the helicopter back at the maintenance facility. After maintenance personnel made adjustments to the rotor system another hover test needed to be accomplished. The pilot once again preflighted the helicopter and the crew began another hover test. The helicopter was brought to a hover and climbed to about 20 feet above ground level and proceed to overfly a chain link fence towards the adjacent field. When the helicopter was abeam to fence the pilot heard a "pop" and the helicopter began a rapid spin. Directional control of the helicopter was lost and the pilot attempted to regain control by using the anti-torque pedals but he found them ineffective. The pilot was not able to regain control of the helicopter and he reduced the engine throttle for an autorotation. The helicopter descended, landed, rolled, and came to rest on its right side.

A security surveillance camera recorded a portion of the accident sequence. The helicopter was observed to lift into a hover, climb and rotate counterclockwise about 90 degrees before heading towards the chain link fence. As the helicopter exited the camera's field of view the helicopter began a rapid counterclockwise turn.

An examination of the helicopter was conducted by the Federal Aviation Administration with assistance from the airframe manufacturer. Crushing damage was observed on the right, lower, and aft sections of the airframe consistent with a nose high/tail low impact. Cyclic and collective control continuity was established from the controls to the main rotor swashplate. Both anti-torque pedals were found near the wreckage, unattached from their respective attachment levers. None of the attachment hardware was found in the wreckage or in the vicinity of the accident. There was no visible elongation of the pedal bolt holes or the holes on the attachment levers. Tail rotor control continuity was established from the anti-torque pedal levers through to the tail rotor pitch change mechanism. No other preimpact anomalies were detected with the airframe. The engine's Data Collection Unit (DCU) and Engine Electronic Control (EEC) were removed and sent to Pratt & Whitney Canada for data download. Examination of the devices found no fault codes recorded during the accident flight which would indicate an engine malfunction.

A teardown for the right engine found that all the power turbine (PT) blades fractured at the airfoil pocket. The PT shaft showed strong circumferential rubbing. The left engine remained as a training device for hot section inspection until other damage was detected. The left engine was examined and found that all PT blades had fractured in overload. Evidence of significant plastic deformation and secondary cracks, parallel to the fracture, were also visible. Visual examination of the PT shaft showed significant wear consistent with rubbing against an adjacent component. Signatures of frictional heat were also detected. The compressor turbine (CT) disk displayed circumferential rubbing in the inner bore diameter at the same location where the PT shaft had fractured.

The transmission was removed from the helicopter and examined. The examination did not reveal any preimpact anomalies.

A review of the helicopter's log book found an entry dated October 31, 2013, that a mechanic performed the action "disassemble, inspect, and reassemble tail rotor pedals". According to a statement provided by the company's director of maintenance, after the accident a search of the area maintenance area was conducted. Near the area where the helicopter was previously repaired, a small parts bag was found tied to the tail rotor control cable that had been replaced. Inside of the bag were bolts similar to the bolts used to secure the anti-torque pedals.

Contributing factors

  • cause Maintenance personnel
  • cause Incorrect service/maintenance
  • cause Attain/maintain not possible

Conditions

Weather
VMC, wind 160/05kt, 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.