Tropical Helicopters McDonnell Douglas 369D accident
McDonnell Douglas 369D · Accident: total loss of engine power (mechanical failure) en route
From Hilo International Airport (ITO) to Hilo International Airport (ITO)
Event
- NTSB case
- LAX03FA200
- 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
- 4 · 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
McDonnell Douglas 369D
- Aircraft type
- McDonnell Douglas 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
- N4493M
- Operator
- Tropical Helicopters
- Onboard fatalities
- Unknown
- Route
- From Hilo International Airport (ITO), Hilo, HITo Hilo International Airport (ITO)
- 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 · cruise
- First occurrenceThe 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
- Total loss of engine power (mechanical failure)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Compressor assembly › Fatigue
- Manufacturer › Acft/equip, inadequate design
- Other maintenance personnel › Maintenance, installation, inadequate
- Turbine assembly › Separation
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The helicopter crashed onto a rugged hardened lava flow following a loss of engine power during cruise. The pilots of other helicopters heard the pilot make a mayday call with the clear "engine out" audio warning in the background. A post crash fire consumed the majority of the wreckage. An airframe examination revealed no evidence of a preimpact malfunction in what remained of the airframe. An engine inspection and a metallurgical examination revealed that the compressor-coupling adapter, a Parts Manufacturer Approval (PMA) part made by a company other than Rolls-Royce, had failed above the shear point due to fatigue cracking initiated by fretting on the pilot diameter, which had disconnected the compressor from the turbine section. The metallurgist noted that the damage was consistent with the rotation of the aft piece of the fractured compressor-coupling adapter within the stub shaft after it had separated. Fretting damage to the impeller corresponded to the fretting damage on the compressor-coupling adapter, and indicated relative movement between the parts. Rolls-Royce had records of 12 other compressor-coupling adapters that had fractured and failed, with all instances of the failure/fracture occurring in this specific new coupling design, which was significantly different than the previous design. The nature of the fretting and fractures indicated that the newly designed couplings have a small amount of longitudinal movement that is occurring between the outer diameter of the compressor-coupling adapter and the inner diameter of the impeller, which was not a factor in the previous design. If the spur adapter gear, compressor-coupling adapter, and compressor impeller (all coaxial spline joints) were in alignment, there would be no significant longitudinal movement of the pilot diameter. However, any axial misalignment of these components during engine buildup, for example, could induce a misalignment that would result in relative motion between the components with each engine rotation. The misalignment would also induce bending stresses into the compressor-coupling adapter in addition to torsion stresses that could result in fatigue. The combination of fretting damage and cyclic bending stresses are most likely the main factor in the failures of these couplings. One month prior to the accident, company maintenance personnel had changed out the engine gearbox due to finding a loose stud on the gearbox to turbine section mounting. Changing the gearbox would involve disturbing the coaxial spline joints between the spur adapter gear, compressor-coupling adapter, and compressor impeller.
Probable cause
a loss of engine power due to the fatigue fracture and separation of the compressor coupling adapter. The fatigue fracture was initiated by fretting on the pilot diameter due to both the inadequate design of the coupling and the coaxial misalignment of the spur adapter gear, compressor-coupling adapter, and compressor impeller during recent engine maintenance where the gearbox was removed and replaced. A factor in the accident was the unsuitable nature of the terrain to make an emergency landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX03FA200
- Event ID
- 20030630X00970
- Case number
- LAX03FA200
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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: e4714d6709e8eedacadfbebdf1bd5620a505ce86326e7c493e7aabd7779a695c; retrieved 2026-09-18T13:02:37.046Z.
- The NTSB's operator name is blank for N4493M; the operator shown is the name the NTSB records it doing business as.