WPR16FA072 · Bell 206B B
Genesis Helicopters Bell 206B B · Accident: system/component malfunction/failure (non-power) en route
From HLN · Honolulu, HI to HLN · Honolulu, HI
Event
- NTSB case
- WPR16FA072
- 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
- 1 · 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
- General aviation
- 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 206B B
- Aircraft type
- Bell 206
- 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
- N80918
- Operator
- Genesis Helicopters
- Onboard fatalities
- Unknown
- Route
- From HLN · Honolulu, HITo HLN · Honolulu, HI
- Aircraft age
- About 37 years (built 1979)
- 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 91: General Aviation
- 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
- System/component malfunction/failure (non-power)
- 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
- Environmental issues › Physical environment
- Organizational issues › Support/oversight/monitoring
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
The commercial pilot of the helicopter was performing a local air tour around the island with four passengers onboard. During the flight, he noticed a vibration throughout the cabin. The pilot diverted toward the destination airport; however, when the vibration stopped shortly thereafter, he decided to initiate a turn so the passengers could see a nearby landmark. The vibration returned shortly thereafter, and the pilot began to maneuver toward the destination airport a second time. The pilot stated that the vibration developed into a grinding sensation, which was followed by illumination of the main rotor low rpm warning light and an increase in engine rpm to the point where the engine and rotor RPM needles were no longer matched on the power turbine gauge. The pilot initiated an approach to a grassy area near the shoreline; however, due to the presence of people nearby, he turned the helicopter slightly left to land in the water as close to shore as possible. The pilot said that, about 20 ft above the water, it felt like the main rotor stalled, the helicopter lost lift, and it "fell out of the sky." The helicopter descended rapidly into the water and sank about 20 ft from the shoreline.
Three of the passengers were able to egress the helicopter following impact; however, the middle aft seat passenger was trapped inside. A first responder stated that he and another person repeatedly dove underwater to cut the passenger's seatbelt straps and extract him. The first responder reported that the passenger's life preserver appeared to be entangled with the seatbelts. Postaccident examination of the life preserver revealed signatures of inflation and cut waist straps, with no other damage noted. It could not be determined when or how the life preserver was inflated; the first responder could not recall whether it was inflated and the nurse providing CPR said it was not inflated. Review of treatment records for the passenger revealed evidence consistent with drowning, and no traumatic injuries to the head or neck. It could not be determined whether the passenger was unable to extricate himself from the restraint, or if he had a period of unconsciousness resulting from the impact that contributed to his drowning. The helicopter's doors were not installed at the time of the accident and all five seat restraints were found to be in working order and undamaged.
Postaccident examination of the helicopter revealed that the engine-to-transmission drive shaft was separated at the transmission side. Metallurgical examination of the engine-to-transmission drive shaft components revealed that the forward coupling did not appear to be lubricated and that there were multiple indications of exposure to elevated temperature, such as heat tinting and loss of the temperature plates on the forward outer coupling, high-temperature cadmium-induced brittle fracture of two forward attachment bolt heads, and a loss of hardness of the bolt head material due to high-temperature tempering. The external spline teeth on the forward spherical coupling were worn down to the bottom landings, while comparatively minor wear marks were observed on the mating internal spline teeth of the forward outer coupling. The asymmetry in the wear pattern between the spherical coupling and the outer coupling combined with the observations consistent with elevated temperatures indicate that the assembly likely failed by overheating due to lack of lubrication. This resulted in softening and subsequent failure of the spring that limits and centers the spherical coupling. When the spring failed, the coupling shifted forward, damaging the forward end of the outer coupling, fracturing the forward cover plate, and wearing the external spline teeth down to the bottom landings. Following the failure of the drive shaft, the engine would have continued to operate, but would not have been able to drive the main rotor.
Interviews with the pilot, the owner of the company, and a non-mechanic rated maintenance assistant indicated that maintenance had recently been conducted on the engine-to-transmission drive shaft, even though this was not recorded in the helicopter's maintenance records. In addition, the owner, who was a rated mechanic, was not present the entire time throughout the removal, inspection, and subsequent reinstallation of the engine-to-transmission drive shaft.
It is likely that, when this maintenance was conducted, grease was not applied to the forward coupling as specified in the manufacturer's maintenance manual. Further review of maintenance records revealed no entries pertaining to a current annual inspection or 100-hour inspection. Additionally, a component inspection sheet provided by the operator revealed that several required component inspections were overdue and had not been completed at the time of the accident.
Although the FAA was conducting oversight in accordance with their guidance, increased inspections may have uncovered the inadequate maintenance and documentation, which in turn, may have prevented the accident.
Probable cause
The in-flight failure of the engine-to-transmission drive shaft due to improper maintenance, which resulted in low main rotor rpm and a subsequent hard landing to water.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR16FA072
- Event ID
- 20160218X71040
- Case number
- WPR16FA072
- 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, coordinates. 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: 5383231fe730daecc8620c6b3b9a851511ee4b2508cf4310f53a02a3f634aa23; retrieved 2026-09-14T21:42:24.838Z.