FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Metro Aviation American Eurocopter LLC AS350B2 accident

19 Sept 2013 · Canton, MS, United States

American Eurocopter LLC AS350B2 · Accident: loss of engine power (total) en route

From Ackerman, MS to Jackson, MS

Report a problem

Event

NTSB case
ERA13LA421
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
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

American Eurocopter LLC AS350B2

Aircraft type
Eurocopter AS350
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
N810LE
Onboard fatalities
Unknown
Route
From Ackerman, MSTo Jackson, MS
Aircraft age
About 3 years (built 2010)
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
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
Loss of engine power (total)
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

  • Aircraft › Aircraft power plant
  • Aircraft › Fluids/miscellaneous hardware
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

As the helicopter departed the helipad, a witness saw dark black smoke coming out of the engine exhaust. (This smoke would not have been visible to the pilot.) The pilot reported that, about 10 minutes after departure, he noticed the illumination of the low engine oil pressure warning light. He noted that the oil pressure gauge was also showing low pressure but that there was no rise in the oil temperature or the exhaust gas temperature. Because the pilot had recently experienced an intermittent oil pressure gauge problem in another helicopter, he assumed the accident helicopter was experiencing a similar problem and continued toward the intended destination while attempting to verify the loss of engine oil pressure. Several minutes later, the pilot noticed a low-torque indication but no rise in the oil temperature or exhaust gas temperature. About 25 minutes after departure, the pilot saw a rise in the exhaust gas temperature and lowered the collective to reduce power. After briefly decreasing, the exhaust gas temperature began rising again, and the pilot located an open field to perform an off-airport landing. The engine experienced a total loss of power before the helicopter reached the open field; the pilot performed an autorotation, and the helicopter landed hard.

Postaccident examination revealed that the engine oil tank was empty and that the engine had sustained heat damage consistent with overtemperature due to oil exhaustion. An obstruction of solidified oil carbon was found in the rear bearing chip detector housing union, which would have restricted the oil scavenge of the rear bearing. According to the engine manufacturer, failure to scavenge the oil in the rear bearing would cause overpressurization of the rear bearing housing area, which would force engine oil out of the rear bearing vent line. In addition, oil overpressurization could overcome the labyrinth seal of the piston shaft, which would allow oil to flow into the gas exhaust path. It is likely that this occurred because oil flowing into the exhaust path would result in black smoke coming from the engine exhaust as was observed by the witness. The continued operation of the engine in this condition likely resulted in the depletion of the oil reservoir, the illumination of the low engine oil pressure warning light, and, subsequently, as the flight continued, a total loss of engine power.

A review of data recovered from a flight recorder installed in the helicopter indicated that, about 2 minutes after departure (about 26 minutes before the accident), the oil pressure dropped from about 4 bars to about 0.2 bar, which would have illuminated the low engine oil pressure warning light. The flight manual and the cockpit emergency checklist both directed that, when the low engine oil pressure warning light was illuminated and the engine oil pressure gauge indicated low oil pressure (as reported by the pilot), the procedure was to land immediately. If the pilot had followed this procedure instead of continuing the flight with the warning light illuminated, it is likely that the accident would have been prevented.

Review of the helicopter's maintenance records indicated that, about 12 flight hours before the accident flight, the engine's 2nd-stage turbine disk (T2) was replaced. During the replacement of the T2, the maintenance technician determined that the rear bearing was "clean"; therefore, he did not clean the rear bearing even though the maintenance procedures required a systematic cleaning when the T2 was replaced regardless of the condition of the bearing. If the cleaning had been performed, as called for in the maintenance procedures, it is likely that the oil carbon deposit in the rear bearing chip detector housing union would have been discovered and removed, thus averting the accident.

Probable cause

The pilot’s improper decision to continue flight with a low engine oil pressure warning light instead of landing immediately in accordance with the flight manual emergency checklist. Contributing to the accident was the maintenance technician’s failure to clean the rear bearing in accordance with the engine manufacturer’s guidance when replacing the 2nd-stage turbine wheel, which resulted in an obstruction of solidified oil carbon in the rear bearing chip detector housing union, subsequent oil exhaustion, and engine failure.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA13LA421
Event ID
20130920X14012
Case number
ERA13LA421
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, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2013-09-20.
  • API snapshot SHA-256: 813e91b7bc5309d1b6206f44e437092f60cf75b7b185abc6a1eda2ba7bd9a690; retrieved 2026-09-15T22:53:28.471Z.