FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

PHI Bell 407 accident

2 May 2017 · Venice, LA, United States

Bell 407 · Accident: part(s) separation from aircraft en route

From Marmande Airport (LS08) to Main Pass 311A, GM (no airport)

Report a problem

Event

NTSB case
CEN17LA174
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Charter & commuter
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Bell 407

Aircraft type
Bell 407
Category
Helicopter
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N457PH
Operator
PHI
Onboard fatalities
Unknown
Route
From Marmande Airport (LS08), Boothville, LATo Main Pass 311A, GM (no airport)
Aircraft age
About 20 years (built 1997)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 135: Air Taxi & Commuter
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · cruise
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Part(s) separation from aircraft
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft propeller/rotor
  • Organizational issues › Management
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN17LA174
Event ID
20170503X65443
Case number
CEN17LA174
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 22fd85ae48efc133abe0f886dd59c85c9960efe721ff9e211f141bb335c5e1e1; retrieved 2026-09-16T05:13:42.625Z.