International Helicopter Aerospatiale 350D accident
Aerospatiale 350D · Accident: total loss of engine power (mechanical failure) en route
From FISHER ISLAND, FL to Cat Cay Airport (MYCC)
Event
- NTSB case
- MIA90FA081
- 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
- 2 · all aircraft and ground
- Ground fatalities
- 0
- 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
Aerospatiale 350D
- Aircraft type
- Aerospatiale 350
- 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
- N5778W
- Operator
- International Helicopter
- Onboard fatalities
- Unknown
- Route
- From FISHER ISLAND, FLTo Cat Cay Airport (MYCC), CAT CAY,BAHAMAS
- 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
- Turbine assembly, turbine blade › Fatigue
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE HELICOPTER WAS IN CRUISE FLT OVR THE OCEAN, WHEN THE PLT HEARD A LOUD NOISE & NOTED A LOSS OF ENG POWER. HE ENTERED AN AUTOROTATION & TOLD THE PSGRS TO PUT ON THEIR LIFE JACKETS. AT ABT 100' ABV THE WATER, HE DEPLOYED THE EMERG FLOATS, THEN SUCCESSFULLY LANDED IN THE OCEAN ABOUT 3 MI FROM SHORE. AFTER LNDG, A WAVE HIT THE HELICOPTER & IT ROLLED OVR. THE PLT & PSGRS GOT ONTO THE BELLY OF THE HELICOPTER, THEN THE PLT DOVE UNDER THE WATER & RETRIEVED THE ELT. HOWEVER, AFTER HE ACTIVATED THE ELT, ANOTHER WAVE HIT & THE PLT DROPPED IT AS HE REACHED TO HELP A PSGR. ONE PSGR EXPIRED ABT 8 HRS LATER & THE OTR PSGR EXPIRED ABT 15 HRS AFTER THE ACDNT. BOTH DIED FM DROWNING. THE ACDNT OCCURRED AT ABT 1115 EST; THE COAST GUARD WAS NOTIFIED OF THE SITUATION AT 1530 EST. THE PLT WAS RESCUED AT 0430 EST THE NEXT DAY. A SUBSEQUENT EXAM OF THE ENG REVEALED THAT A POWER TURBINE BLADE HAD FAILED FROM FATIGUE, WHICH RESULTED IN THE LOSS OF ENG POWER.
Probable cause
FATIGUE FAILURE OF AN ENGINE TURBINE BLADE, WHICH RESULTED IN A LOSS OF POWER. ROUGH OCEAN WATER IN THE EMERGENCY LANDING AREA WAS A RELATED FACTOR.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA90FA081
- Event ID
- 20001212X22756
- Case number
- MIA90FA081
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: c8e3a479420b3e5af8cb07347571ebe54b931a0e126c6949b869c283e17bdd9d; retrieved 2026-09-18T14:06:42.870Z.