PHI Bell 407 accident
Bell 407 · Accident: part(s) separation from aircraft while standing
From 149 · Cameron, LA to 167 · Cameron, LA
Event
- NTSB case
- GAA16CA039
- 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
- N420PH
- Operator
- PHI
- Onboard fatalities
- Unknown
- Route
- From 149 · Cameron, LATo 167 · Cameron, LA
- Aircraft age
- About 8 years (built 2007)
- 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
- Standing · engine(s) start-up
- 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
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The operator reported that the pilot landed and shutdown the helicopter on an offshore platform. He secured the main rotor system by attaching a tiedown to the forward left main rotor blade and he then attached this tiedown to the left front skid cross tube. Several hours later, the pilot entered the right front seat to begin the engine start sequence. The operator reported that the pilot proceeded to start the engine and noted a few seconds after initiating the engine start that the helicopter made an "unusual noise" and began to shake. The pilot then shut down the helicopter without further incident. A postflight inspection revealed substantial damage to the blue main rotor blade.
The operator reported there were no pre-impact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.
Probable cause
The pilot's failure to remove a main rotor blade tiedown, which resulted in substantial damage to a main rotor blade when the engine was started.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA16CA039
- Event ID
- 20151104X84701
- Case number
- GAA16CA039
- 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: b8172c57976b3f8f1890b5f6573614e38e0906b7196d26f790fe91d633730ffe; retrieved 2026-09-16T02:56:53.355Z.