Mris Eurocopter Deutschland Gmbh MBB BK 117 C-2 incident
Eurocopter Deutschland Gmbh MBB BK 117 C-2 · Incident: powerplant system/component malfunction/failure en route
From Mc Kennan Hospital Heliport (2SD1) to Douglas County Memorial Hospital Heliport (08SD)
Event
- NTSB case
- CEN17IA094
- 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
- Incident
- 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
- 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
Eurocopter Deutschland Gmbh MBB BK 117 C-2
- Aircraft type
- Eurocopter MBB BK 117 C-2
- 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
- N911MK
- Operator
- Mris
- Onboard fatalities
- Unknown
- Route
- From Mc Kennan Hospital Heliport (2SD1), Sioux Falls, SDTo Douglas County Memorial Hospital Heliport (08SD), Armour, SD
- Aircraft age
- About 9 years (built 2008)
- 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
- 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
- Minor
Cause areas
- Aircraft › Aircraft power plant
- Aircraft › Fluids/miscellaneous hardware
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot and two crewmembers were conducting a night helicopter air ambulance flight. While en route, the No. 2 engine twist grip caution light illuminated. The pilot checked the instruments and did not notice anything anomalous. The twist grip light disappeared then reappeared and flickered a few more times. All parameters were in the proper range. Shortly after, he heard a "winding down sound," then " a hissing sound” and detected “the smell of exhaust in the cabin." He responded by turning off the cabin heat then lowered the collective and diverted toward an airport. During the turn, the No. 2 engine FIRE light illuminated, and he noticed an orange glow from the back-right side of the helicopter. He pressed the No. 2 engine emergency off switch, noticed that the FLI needles split, and continued with one engine inoperative. Subsequently the No. 1 fire bottle light illuminated, which, indicated there was a fire in the engine compartment, so he activated the bottle. Then the No. 2 fire bottle light illuminated, which indicated that the fire had not yet been extinguished, so he discharged the second fire bottle. The FIRE light extinguished, and he continued the flight and made a running emergency landing at the diversion airport.
A post-incident examination of the helicopter and inspection of both engines was completed. The No. 2 engine deck area was thermally damaged from an oil fire. The No. 2 engine exhibited significant internal coke buildup with blockages noted in the rear bearing scavenge line and the airframe's vent line 3-way union. The blocked scavenge line allowed the oil to escape the rear bearing chamber, which resulted in oil in the engine's main air path, in the rear bearing vent line, and onto the engine deck. A failure of the rear bearing occurred due to excessive oil lubrication in the rear bearing chamber. The No. 2 engine gas generator rear bearing was found severely damaged and seized; the seizure of the bearing was due to the bearing operating in excess oil.
The No. 1 engine rear bearing assembly also exhibited significant coke buildup in similar locations but continued to operate normally during the incident. The bearing was found covered with coke, but otherwise in good condition. The 3-way union was partially blocked with coke.
The operator would have benefitted in using a high thermal stability oil. The engine maintenance performed by the operator was lacking proper recording and was not completed exactly as prescribed in the engine maintenance manual. If performed properly, the rear bearing strainer maintenance check, the permeability test, and permeability trend analysis could have helped the operator recognize the impending clogging of the rear bearing scavenge line.
Probable cause
The gas generator rear bearing oil scavenge line blocked with coke, which resulted in a failed rear bearing due to an excess of oil lubrication. Contributing to the incident was the operator not completely performing the maintenance items and not utilizing an oil for higher temperatures.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN17IA094
- Event ID
- 20170131X24430
- Case number
- CEN17IA094
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2017-01-27.
- API snapshot SHA-256: 442c279f121807ce189c2f79f0074c71a8bb1679863f00827e9e204642b2e359; retrieved 2026-09-16T04:59:08.626Z.