MIA93LA055 · Hughes 369D
Haverfield Hughes 369D · Accident: partial loss of engine power (non-mechanical) en route
From Gulfport Biloxi International Airport (GPT) to an unrecorded destination
Event
- NTSB case
- MIA93LA055
- 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
- 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
- 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
Hughes 369D
- Aircraft type
- Hughes 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
- N6612C
- Operator
- Haverfield
- Onboard fatalities
- Unknown
- Route
- From Gulfport Biloxi International Airport (GPT), Gulfport, MSTo not recorded
- 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 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
- 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
- Partial loss of engine power (non-mechanical)
- 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
- Fuel injection control/system › Contamination
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT STATED HE WAS ABOUT 4 MILES FROM THE AIRPORT AT 300 FEET WHEN THE HELICOPTER YAWED AND THE ENGINE OUT LIGHT AND AUDIO WARNINGS CAME ON. HE THEN NOTICED THE AUTO REIGNITION LIGHT ON. THE ENGINE LOST POWER AND THE HELICOPTER WOULD NOT MAINTAIN ALTITUDE. HE INITIATED AN AUTOROTATION, AND THE HELICOPTER DESCENDED THROUGH TREES AND COLLIDED WITH WATER. THE HELICOPTER THEN ROLLED ON TO THE RIGHT SIDE AND FILLED WITH WATER. THE CREW EXITED THE HELICOPTER. AFTER SPENDING 1 DAY AT THE CRASH SITE AWAITING RESCUE THE CREW WALKED TO SAFETY. POSTCRASH EXAMINATION OF THE ENGINE ASSEMBLY REVEALED NO EVIDENCE TO INDICATE THE REASON FOR POWER LOSS. EXAMINATION OF THE ENGINE FUEL SYSTEM REVEALED THE FUEL CONTROL INLET SCREEN WAS CLOGGED WITH METAL CONTAMINATION AND WAS BYPASSING THE FILTER. NO OTHER EVIDENCE TO INDICATE THE REASON FOR LOSS OF POWER WAS NOTED.
Probable cause
LOSS OF ENGINE POWER DUE TO UNDETECTED FOREIGN MATTER CONTAMINATION OF THE ENGINE FUEL CONTROL. THE LACK OF A SUITABLE LANDING AREA WAS A FACOTR IN THE ACCIDENT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA93LA055
- Event ID
- 20001211X11741
- Case number
- MIA93LA055
- 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: 02c371fc8eb2146131e47e33f73c0b5220a3735a1e098a9b8c2ec2f527885cb8; retrieved 2026-09-21T23:02:44.209Z.