FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

PHI Bell 407 accident

8 Jun 2015 · Pecan Island, LA, United States

Bell 407 · Accident: flight control system malfunction/failure en route

From Vermilion Block, GM to Pecan Island, LA

Report a problem

Event

NTSB case
CEN15LA265
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
0
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
N501PH
Operator
PHI
Onboard fatalities
Unknown
Route
From Vermilion Block, GMTo Pecan Island, LA
Aircraft age
About 16 years (built 1999)
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
Flight control system malfunction/failure
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 oper/perf/capability
  • Aircraft › Aircraft propeller/rotor

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

NTSB narrative

The operator reported that the helicopter air taxi flight was in cruise about 1,000 ft above ground level when the pilot felt an impact and a strong vibration. The pilot completed an instrument and functional control check and could not immediately identify any anomalies. The pilot stated that, as he slowed the helicopter for landing, he noticed a "heavy mechanical sound and strong vibration." The vibration worsened, and the pilot began to have difficulty controlling the helicopter; he subsequently initiated an autorotation and deployed the helicopter's floats. The helicopter touched down in a marshy area, and the pilot and passengers egressed.

During the landing, the main rotor blades contacted the tail boom and one of the tail rotor blades, resulting in separation of the tail rotor gearbox (TRGB) support structure, which was subsequently located in the marsh. A postaccident examination and metallurgical analysis revealed that fatigue fractures on two of the four TRGB attachment studs likely existed before the accident flight. As the fatigue fractures grew larger through the first two attachment studs, their load-carrying capability lessened, and the additional load was transferred to the remaining attachment studs. The progressive failure of the fatigued TRGB attachment studs led to the vibrations felt by the pilot and, ultimately, the uncommanded right yaw and subsequent loss of tail rotor control. The reverse- bending, high-cycle fatigue fracture initiation mode observed on two of the TRGB studs suggests the fatigue fractures were a result of a loss of torque of the attachment stud nuts. The reason for the loss of torque could not be determined based on the available information.

Probable cause

The fatigue fracture of the tail rotor gearbox attachment studs, which resulted in a loss of tail rotor control and a subsequent hard landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN15LA265
Event ID
20150609X15345
Case number
CEN15LA265
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: 5e3e7aba172b12346b42ad4feb22438e809f6fcd783b5b34a3f2dbd5586f9edc; retrieved 2026-09-16T02:24:19.453Z.