Blue Hawaiian Airbus EC130 T2 accident
Airbus EC130 T2 · Accident: loss of engine power (total) en route
From Lihue Airport (PHLI) to Lihue Airport (PHLI)
Event
- NTSB case
- WPR16FA055
- 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
Airbus EC130 T2
- Aircraft type
- Airbus EC130
- 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
- N11VQ
- Operator
- Blue Hawaiian
- Onboard fatalities
- Unknown
- Route
- From Lihue Airport (PHLI), Lihue, HITo Lihue Airport (PHLI), Lihue, HI
- Aircraft age
- About 1 year (built 2015)
- 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
- 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
- Substantial
Cause areas
- Aircraft › Aircraft systems
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During an air tour flight, the helicopter was about 1/4 mile offshore at 1,450 ft mean sea level (msl) when the pilot heard the low rotor rpm warning horn. He immediately entered an autorotation and turned toward the beach. As he approached the shoreline at 374 ft msl, he made a sharp right turn to avoid large boulders in his intended landing area. The helicopter subsequently landed hard on the beach, bounced, and came to rest.
Examination of the engine revealed that the main fuel injection pipe between the fuel valve assembly and the injection union was cracked and broken at the injection union B-nut connection. Subsequent engine test runs revealed that the starter-generator imparted a vibration into the engine that excited the fuel pipe to vibrate in resonance and ultimately fracture due to reverse bending fatigue at the flared end. The crack or fracture of the fuel pipe allowed pressurized fuel to escape, reducing fuel flow and pressure to the injection manifold below that which was required to sustain combustion, and resulted in the loss of engine power. The vibration imparted into the engine by the starter-generator remained below the global vibration limit for the entire engine, but was sufficient to excite the fuel pipe.
Examination of the starter-generator revealed that the front bearing outer race and support exhibited signatures consistent with fretting and pronounced wear. This observed wear of the front bearing support allowed the armature to oscillate and impart a vibration into the engine frame. Further, the investigation was unable to determine when the vibration began and if the fatigue crack had already started at the time of the last inspection. Without a requirement to look at the front bearing and the shaft play, the operator would have no way to identify the vibration issue.
Onboard video imagery recorded during the accident flight confirmed that the pilot's harness lap belt was positioned properly, low and tight across his hips. Of the six passengers onboard, four passengers' lap belt positioning were visible in recorded cabin imagery, and depicted that the lap belts were not tight across their hips and that the buckle was at or above their waists. Examination of the pilot's seat revealed vertical displacement consistent with a significant amount of vertical energy being absorbed by the seat during the hard landing. Two of the passenger seats displayed some vertical displacement, two displayed minimal vertical displacement, and two seats showed no vertical displacement. The seat displacement was directly related to the amount of vertical energy absorbed by the seat and to the severity of the occupant's injuries. The loose and out-of-position seatbelts most likely allowed the passengers' bodies to shift out of position on the seat before and during the hard landing and did not restrain the occupants in the proper position for the seat to absorb the vertical landing loads for which it was designed.
Probable cause
The fatigue failure of the engine fuel pipe as a result of vibration caused by a worn starter-generator front bearing support, which excited the fuel pipe and caused it to oscillate at a resonant frequency, and a subsequent loss of engine power due to fuel starvation. Contributing to the severity of passenger injuries was the improper positioning of the passengers' seat belts.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR16FA055
- Event ID
- 20160119X14513
- Case number
- WPR16FA055
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2016-01-18.
- API snapshot SHA-256: 44afea8fb2f5a62073d676570f08dda4d86c6a93047d813a2ad4529e02f4fcec; retrieved 2026-09-16T03:05:40.672Z.