18 Jan 2010: EUROCOPTER AS 350 B2 — Liberty Helicopters, Inc.

18 Jan 2010: EUROCOPTER AS 350 B2 (N696BH) — Liberty Helicopters, Inc.

No fatalities • New York, NY, United States

Probable cause

The failure of maintenance personnel to properly secure one tail rotor pitch change link to its respective tail rotor blade resulting in an in-flight separation of the link from the blade. Contributing to the accident was the lack of an adequate post-maintenance inspection procedure.

— NTSB Determination

Accident narrative

On January 18, 2010, about 1733 eastern standard time, a Eurocopter AS 350 B2, N696BH, registered to Broadcast Helicopter Corporation and operated by Liberty Helicopters, Inc., experienced an in-flight vibration about 4 minutes after takeoff and landed at the West 30th Street Heliport (JRA), New York, New York. Visual meteorological conditions prevailed and company VFR flight following was in effect for the positioning flight operating under the provisions of 14 Code of Federal Regulations (CFR) Part 91. The helicopter was substantially damaged and the commercial pilot, who was the sole occupant, was not injured. The flight originated from the Downtown Manhattan/Wall Street Heliport (JRB), New York, New York, at 1729, and was enroute to JRA.

The pilot stated that during cruise flight while flying at 600 feet, he announced his intent to land at JRA, and was cleared to land on spot 3 of the heliport behind another aircraft that was approaching from the north. At that time he felt a vibration which he could feel through the airframe including the anti-torque pedals and cyclic. The pilot further stated that he had positive control of the helicopter and felt the safest thing to do was continue with the landing. The vibration remained constant and during the approach he maintained control of the helicopter. After touchdown on spot 3 he immediately began to shutdown the helicopter and applied the rotor brake. The vibration increased dramatically as the rotor speed decreased. After the main and tail rotors stopped, the pilot exited the helicopter and noticed damage to the tail rotor and the surrounding area. One pitch change link of one tail rotor blade was separated fromits attach point at the blade and the blade was out of its normally installed position.

During postaccident inspection of the helicopter by representatives of the Federal Aviation Administration (FAA) and Liberty Helicopters, Inc., a hole was found in the right side of the tailboom near station 3700, and the tailcone was damaged near station 4880.6. The pitch change link of one tail rotor blade was found not connected to the blade control horn, and the securing hardware link, consisting of the bolt, castellated nut, and cotter pin were not found. The opposite end of the link remained attached to the pitch change spider assembly, and was secured by a cotter pin. The tail rotor blade with the separated pitch change link exhibited paint transfer marks on the leading edge of the blade near the blade tip consistent with the color of the tailboom. The same area of the blade tip showed abrasion on it’s leading edge. No dents in the area of the paint transfer marks were observed. The other tail rotor blade pitch change link was found properly connected at both ends, with both ends secured by cotter pins. The tail rotor was retained for further examination.

Review of the maintenance records showed an annotation that on January 11, 2010, the tail rotor pitch change spider bearing was removed and replaced because it was a service life limited item. The bearing installation procedure required the removal of the tail rotor assembly which required removal of the pitch change links. After the maintenance was performed, the helicopter was test flown and approved for return to service on January 16, 2010. The helicopter was not operated in revenue service on January 17, 2010, but on the accident date, including the accident flight, was operated a total of 4 flights lasting a total of 39 minutes.

One mechanic stated that on January 11th, he elected to work on the tail rotor section and noticed unusual play on one of the tail rotor pitch change links. When his inspection of it was completed, the company director of maintenance informed him that the bearing of the tail rotor pitch change spider needed to be replaced because it was a life limited item. The mechanic secured the pitch link he had previously removed from the tail rotor blade and tightened the hardware in an effort to avoid losing any parts. He then removed the tail rotor assembly and provided a turn over briefing advising maintenance personnel of what he had done. The following day, the tail rotor assembly was installed and one mechanic reported inspecting the pitch change links at the tail rotor pitch change spider and confirmed both were secure with cotter pins. He also inspected the tail rotor through bolt for proper security but did not mention checking the security of the pitch links at either tail rotor blade.

Detailed examinations of the tail rotor assembly by the Safety Board’s Materials Laboratory did not disclose mechanical evidence that the missing bolt that would have secured the pitch change link was properly installed and secured with a cotter pin. A factual report (Materials Laboratory Factual Report No. 10-048) describing the detailed examination of the tail rotor assembly components is available in the public docket of supporting documentation for this accident investigation.

The helicopter was maintained in accordance with a FAA Approved Aircraft Inspection Program. The inspection program at that time did not include, nor was it required to include required inspection items for a quality control inspection following maintenance or repair of critical safety of flight items.

Contributing factors

  • cause Incorrect service/maintenance
  • factor Operator

Conditions

Weather
VMC, 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.