FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

PHI Bell Helicopter Textron Canada 407 incident

1 Dec 2011 · Gulf Of Mexico, United States

Bell Helicopter Textron Canada 407 · Incident: loss of engine power (total) en route

From EC-278C, GM to EC-261, GM

Report a problem

Event

NTSB case
CEN12IA096
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
Incident
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 Helicopter Textron Canada 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
N435PH
Operator
PHI
Onboard fatalities
Unknown
Route
From EC-278C, GMTo EC-261, GM
Aircraft age
Not recorded
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
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
Loss of engine power (total)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Cause areas

  • Aircraft › Aircraft power plant

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

NTSB narrative

While maneuvering for a precautionary landing to an oil rig platform because of a chip light indication, the helicopter's engine lost power. The pilot entered an autorotation, called mayday, inflated the helicopter’s floats, and performed a successful water landing. The pilot and passenger were able to exit the helicopter unassisted into a life raft and were picked up within 10 minutes. Examination and disassembly of the engine revealed the No. 2 bearing had failed. Metallurgical examination of the bearing showed the No. 2 bearing outer ring cracked in fatigue due to false brinnelling, which occurs in cases where the bearing is stationary but is subjected to ambient vibration or shock during transport. A spalling area was severe enough to propagate mechanical stress in the outer ring causing the ring to fracture. The engine compressor section was overhauled 2.7 hours before the failure.

Probable cause

The failure of the compressor section No. 2 bearing due to false brinnelling and fatigue.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN12IA096
Event ID
20111202X64040
Case number
CEN12IA096
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, damage. 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: a327ee45ac0d152d0d2a809df326159734fd1fd81eb56261295852905081516d; retrieved 2026-09-15T16:59:04.543Z.