Loss of control Accident Hughes 369D N5225C,
ASN logo
ASN Wikibase Occurrence # 169136
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Tuesday 22 July 2014
Time:11:20
Type:Silhouette image of generic H500 model; specific model in this crash may look slightly different    
Hughes 369D
Owner/operator:Olympic Air Inc
Registration: N5225C
MSN: 590497D
Year of manufacture:1979
Total airframe hrs:20790 hours
Engine model:Rolls-Royce 250 C20B
Fatalities:Fatalities: 0 / Occupants: 1
Aircraft damage: Substantial
Category:Accident
Location:near Oso, Washington -   United States of America
Phase: Manoeuvring (airshow, firefighting, ag.ops.)
Nature:External load operation
Departure airport:Oso, WA
Destination airport:Oso, WA
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The commercial pilot was performing external load operations in the helicopter when one main rotor blade separated, which resulted in a loss of control and collision with terrain. The helicopter rolled downhill, and the airframe sustained substantial damage. On-site examination of the wreckage revealed that four of the main rotor blades were fragmented into many pieces. The fifth main rotor blade was found about 900 ft from the main wreckage and exhibited less damage; postaccident examination of this rotor blade revealed that it had separated due to fatigue cracking that had initiated near the root end of the blade at the second-most outboard bolt hole through the spar, skin, and doubler.
Further examination revealed that the fatigue cracks in the separated blade had initiated due to disbondment at the interface between the adhesive film on the blade subassembly and the upper and lower root fittings. Examination of the root fitting assembly revealed paint cracks along the root fitting/blade interfaces, indicative of complete or partial disbondment of the root fittings. When the remaining attachment bolts were removed, the root fittings cleanly separated from the blade subassembly.
The helicopter manufacturer had previously issued a service bulletin indicating that disbondment of the root fitting was caused by a high number of torque events/external lifts per hour that exceeded the helicopter’s “original design fatigue spectrum.” Further, the Federal Aviation Administration had previously issued an airworthiness directive (AD), which instructed the operator to determine and record the number of torque events (TE) accumulated on each main rotor blade. It stated that, on or before accumulating an additional 200 TEs or at the end of each day’s operations, whichever occurred first, the operator was required to record and update the total accumulated TEs. For each blade that had accumulated 13,720 or more TEs and 750 or more hours time in service (TIS), before further flight, unless accomplished previously, the operator was to perform a main rotor blade TE inspection. The AD also required a recurrent main rotor blade TE inspection at intervals not to exceed 200 TEs or 35 hours TIS, whichever occurred first. A review of maintenance records indicated that the blades on the helicopter had accumulated about 1,123 hours TIS and 232,674 TEs since installation. The examination of all of the blades suggested that initial indications of root fitting disbondment, specifically paint cracking around the root fitting/blade interface, occurred sufficiently early to have been detected if the inspections had been performed in accordance with the AD.
The pilot stated that he obtained an airframe and powerplant certificate so that he could perform the TE inspections. He added that he averaged about 200 TEs per hour and that he tried to comply with the AD as best as he could on work sites. On a typical job, he usually did not perform the TE inspections until he got home at night. He read the AD and maintenance manual to determine how to inspect the blades and noted that the inspection procedures stated that the inspector should inspect the root end for cracks. He stated that he looked primarily at the root fitting and metal for cracks, not necessarily the bond line. He added that the intent of inspecting the bond line was not clear to him until the helicopter and blade manufacturers published service notices after the accident, which included color photographs; the photographs showed examples of possible evidence of initial failure of the adhesive bond between the main rotor blade and doubler.
The fracture on the accident blade initially occurred at the second-most outboard bolt hole, which was outside the indicated inspection area for chordwise cracks. Because the crack was outside the indicated inspection area, it was possible that the crack could have been missed or misidentified during an inspection. However, the crack initiated at the disbondment of the root fittings, which was part of the inspection procedure. As a result of the ac
Probable Cause: The pilot/mechanic’s failure to properly perform required inspections of the main rotor blades at the necessary intervals, which resulted in an in-flight separation of a main rotor blade due to disbonding and fatigue cracking. Contributing to the accident was the lack of clear guidance in the helicopter maintenance inspection instructions, which allowed for the possible misinterpretation by maintenance personnel of their intent.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: WPR14LA308
Status: Investigation completed
Duration:
Download report: Final report

Sources:

NTSB

History of this aircraft

Other occurrences involving this aircraft
16 November 1996 N5225C Eagle Air Helicopters,inc 0 Forks, WA sub
7 April 2003 N5225C Olympic Air, Inc. 0 Taholah, Washington sub

Location

Revision history:

Date/timeContributorUpdates
24-Aug-2014 17:20 Aerossurance Added
21-Dec-2016 19:28 ASN Update Bot Updated [Time, Damage, Category, Investigating agency]
30-Nov-2017 18:50 ASN Update Bot Updated [Cn, Other fatalities, Nature, Departure airport, Destination airport, Source, Narrative]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org