Jack Harter Helicopters MD Helicopter 369E/500E accident
MD Helicopter 369E/500E · Accident: powerplant system/component malfunction/failure en route
From Lihue Airport (LIH) to Lihue Airport (LIH)
Event
- NTSB case
- ANC24LA017
- 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
- Event fatalities
- Unknown
- 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
MD Helicopter 369E/500E
- Aircraft type
- MD Helicopters 369
- 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
- N633JH
- Operator
- Jack Harter Helicopters
- Onboard fatalities
- Unknown
- Route
- From Lihue Airport (LIH), Lihue, HITo Lihue Airport (LIH), Lihue, HI
- Aircraft age
- About 37 years (built 1987)
- 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
- Powerplant system/component 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 propeller/rotor
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that, while conducting a doors-off helicopter sightseeing flight near the northern shoreline on the island of Kauai, he smelled smoke and immediately began flying toward a beach for a precautionary landing. Very shortly thereafter he heard a loud “pop,” followed by the engine out aural warning tone. The pilot immediately lowered the collective control and entered an autorotation to land at a nearby smaller, remote sand-covered beach. As the helicopter touched down, it rocked forward and nosed down into the sand. The helicopter then rolled to the right and came to rest on its side, resulting in substantial damage to the tail boom, fuselage, and main rotor system. An initial examination revealed that the overrunning clutch and engine-to-transmission driveshaft were fractured. The overrunning clutch was found to have failed at its output (forward) end, with significant thermal damage to the clutch inner race and output bearing. The overrunning clutch assembly, Kaflex driveshaft, and the grease sample from the engine power output pad were collected and sent to the NTSB Materials Laboratory. Further examination of the overrunning clutch found the thermal damage was consistent with frictional heating of the output bearing, leading to the output bearing’s failure, causing the clutch inner race to become very hot and degrade its material strength. The mechanics who maintained and inspected the accident helicopter during its last 100-hour and 300-hour inspections had not removed the output bearing from the overrunning clutch when repacking the bearing with new grease during the inspections. The removal of the output bearing from the overrunning clutch during the regreasing procedure was required by the maintenance manual to allow visual confirmation that the old grease had been pushed out of the bearing during the repacking process. By neglecting to remove the output bearing from the overrunning clutch during the regreasing procedure, the mechanics could not confirm that the old grease had been completely displaced from the output bearing. A significant quantity of old grease likely remained within the output bearing due to the bearing not being removed during the regreasing procedure. Over time, and with continued use, this residual grease likely degraded further, ultimately leading to the failure of the output bearing.
Probable cause
Maintenance personnel’s noncompliance with maintenance manual procedures that required the removal of the overrunning clutch output bearing during the regreasing procedure, which resulted in inadequate regreasing of the bearing and the subsequent failure of the overrunning clutch assembly.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC24LA017
- Event ID
- 20240228193859
- Case number
- ANC24LA017
- 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, cause areas. 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: 0fc71ff46537898227a44e94ae84aabd568dfbeb6c4df9f9a96bd900fe20bdb1; retrieved 2026-09-16T18:33:00.953Z.