Accident Bell 407 N457PH, Tuesday 2 May 2017
ASN logo
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 2 May 2017
Type:Silhouette image of generic B407 model; specific model in this crash may look slightly different    
Bell 407
Registration: N457PH
MSN: 53121
Year of manufacture:1997
Total airframe hrs:5839 hours
Engine model:Rolls-Royce 250 C478
Fatalities:Fatalities: 0 / Occupants: 6
Other fatalities:0
Aircraft damage: Substantial
Location:Grand Bay Offshore Installation, GOM -   United States of America
Phase: En route
Departure airport:Boothville, LA (LS08)
Destination airport:Main Pass 311A
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
The commercial pilot was conducting a nonscheduled, cross-country passenger flight. He reported that, while en route, he detected an in-flight vibration and made a precautionary landing on an oil platform. As he was shutting down the engine, the vibration increased, and he initiated an emergency shutdown using the rotor brake.
Postaccident examination revealed that a tip block and weights had separated from one of the tail rotor blades. Cracks were noted on the tail rotor gear box, which was detached from the tailboom support casting. The casting was entirely fractured and exhibited cracking consistent with overstress separations. The left-side attachment studs were fractured and exhibited reversed bending fatigue fractures. The casting also had cracks at the two forward stud hole locations, and stud hole elongation was noted at the two aft stud hole locations.
The separation of the tip block from the tail rotor blade resulted from an incomplete bond area due to a waffle pattern in the adhesive and contamination of the bond line by repair debris. About 50% of the adhesive surface had smooth and glossy surfaces consistent with voids and lack of contact between the adhesive and the tip block, which was likely due to insufficient vacuum pressure being applied while curing the adhesive.
The blade tip exhibited worn separation surfaces and the presence of dark material, consistent with engine exhaust, indicating that a crack had formed along the flat side bond line and then progressed until the degraded bond strength was exceeded by operational loads, and the tip block separated. This resulted in a violent rotor imbalance and induced sufficient loads to crack the gearbox attachment studs and produce rapid fatigue cracking in the left-side attachment studs and to crack and nearly fracture the gearbox support assembly.
The tip block had been repaired about 65 hours before the flight. According to the helicopter manufacturer, after the repairs were made, the blade passed the postbond pull test of 1,320 lbs, which was equal to the load on the tip block at maximum tail rotor rpm, and it was returned to service. Given the postaccident condition of the adhesive, the postrepair test procedures were not adequate to detect the insufficient adhesive bonding, which resulted in the separation of the tip block from the tail rotor blade. After the accident, the helicopter manufacturer revised its approved repair and inspection procedures. The changes included, in part, a revision to the cure cycle process to use only positive pressure (not vacuum pressure) during the cure cycle that cures the adhesive that bonds the block on the blade tip and an expansion of its postrepair inspection procedures.

Probable Cause: An in-flight separation of the tip block from the tail rotor blade due to an inadequate blade repair, which resulted in a rotor imbalance sufficient to crack the gearbox attachment studs and gearbox support assembly, and inadequate postrepair test procedures, which failed to detect the inadequate adhesive bonding.

Accident investigation:
Investigating agency: NTSB
Report number: CEN17LA174
Status: Investigation completed
Download report: Final report




Revision history:

05-May-2017 13:07 Aerossurance Added
10-May-2017 17:30 Anon. Updated [Narrative]
21-Feb-2018 11:35 Aerossurance Updated [Source]
18-Mar-2018 15:37 Aerossurance Updated [Narrative]
09-Nov-2018 13:48 Aerossurance Updated [Narrative]
11-Nov-2018 08:34 ASN Update Bot Updated [Time, Cn, Operator, Total occupants, Departure airport, Destination airport, Source, Narrative, Accident report, ]
05-Apr-2021 12:10 Aerossurance Updated [Operator, Source, Narrative]
20-Mar-2024 16:39 Anon. Updated [Source]

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