MIA01FA006 · Aerospatiale AS-355-F2
Corporate Jets Aerospatiale AS-355-F2 · Accident: airframe, component or system failure en route
From Taylorsville Airport (4NC3) to Duke University North Heliport (NC92)
Event
- NTSB case
- MIA01FA006
- 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
Aerospatiale AS-355-F2
- Aircraft type
- Aerospatiale AS-355
- 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
- N355DU
- Operator
- Corporate Jets
- Onboard fatalities
- Unknown
- Route
- From Taylorsville Airport (4NC3)To Duke University North Heliport (NC92), Durham, NC
- 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
- Airframe, component or system failure
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Company maintenance personnel › Procedures/directives, not followed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
About 5 minutes before landing at a hospital, the main rotor gearbox (MGB) oil pressure warning light illuminated. The pilot continued to the hospital, landed, and performed an immediate engine shutdown. A mechanic disconnected the wiring to the MGB oil pressure switch and the light went out. The mechanic stated he believed the oil pressure switch had failed and he asked the pilot to run the helicopter, hover the helicopter, and if everything was normal, to fly it back to the base hospital. The pilot did the run and hover, and then departed the hospital. The helicopter crashed about 1 minute later. Witnesses stated they heard the helicopter approach the crash site at a low altitude and making a slow thumping noise. Examination of the MGB showed the oil pump idler gear had seized in the oil pump due to undetermined reasons and the oil pump drive shaft had failed due to overstress. The teeth on the engine input gears, intermediate gears, and MGB drive gear in the MGB combining gearbox had failed due to high-temperature overstress, which was the result of oil starvation. The helicopter was not equipped with a MGB oil pressure indicator. The maintenance procedure for trouble shooting an illuminated MGB oil pressure warning light is to first check the electrical circuit, and if this does not correct the problem, to change the oil pressure switch. The mechanic stated he did not have the maintenance manuals with him while working on the helicopter. The MGB had been installed in the helicopter after overhaul, 3 days and 4 flight hours before the accident.
Probable cause
The mechanics failure to comply with manufacturers instructions for correction of a illuminated main rotor gearbox oil pressure warning light resulting in the helicopter being dispatched on a ferry flight with a failed main rotor gearbox oil pump, failure of the main rotor gearbox combining gearbox gears due to oil starvation, loss of main rotor RPM, and the helicopter colliding with trees and the ground during an uncontrolled descent.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA01FA006
- Event ID
- 20001212X22206
- Case number
- MIA01FA006
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2000-10-17.
- API snapshot SHA-256: 4d25f45ef406095c50149f62dee0f7b8a51d1118e67606cb6f295debf5e82f80; retrieved 2026-09-20T20:49:08.220Z.