FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN11FA118 · Eurocopter AS350-B2

19 Dec 2010 · La Monte, MO, United States

Air Methods Eurocopter AS350-B2 · Accident: loss of engine power (total) during takeoff

From La Monte, MO to Fristo, MO

Report a problem

Event

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

Eurocopter AS350-B2

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
N549AM
Operator
Air Methods
Onboard fatalities
Unknown
Route
From La Monte, MOTo Fristo, MO
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
Takeoff
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 systems
  • Not determined › Not determined

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

NTSB narrative

The emergency medical services flight crew was departing from their home base helipad on the fourth flight of the day. The pilot reported that he began to lift straight up in a slow climb to about a 100- to 125-foot-high hover. As he completed a left pedal turn to depart into the wind, he confirmed that he was clear vertically of a tree that was directly east of the helipad. As he began a slow transition to forward flight, he heard a loud "bang." The pilot immediately reacted to the sound by slightly lowering the collective and turning to the right to get back to the helipad. He lowered the nose briefly and then began to flare the helicopter as he pulled up on the collective. The helicopter hit hard on the helipad, which spread the helicopter's landing skids so that the helicopter was lying on its belly, and the fuel tank ruptured during the impact. There was no postimpact fire. The pilot turned off the main electrical push button and began to yell "get out" to the flight crew. The pilot exited the helicopter unassisted and crawled about 15 to 20 feet away; medical crewmembers on board were assisted out of the helicopter by first responders.

Postaccident examination revealed that damage to the helicopter was consistent with a high vertical velocity impact. Examination of the main rotor and tail rotor drive systems revealed evidence of low rpm on impact. Recorded nonvolatile data indicated that the engine experienced a flameout before ground impact. During the on-site examination, all fuel, oil, and air lines and connections were found to be tight. Additionally, the fuel flow lever was found in the flight detent, and the fuel shutoff lever was found lock-wired in the open position. There was no indication that the fuel filter annunciator light had illuminated during the accident flight, which would indicate that the fuel filter was clogged or that the filter bypass had opened. The on-site examination revealed that the fuel filter cartridge exhibited no anomalies, and the bypass open indicator was not extended. The bypass open indicator operated normally during subsequent tests.

The engine was run on a test cell and operated within the original equipment manufacturer's specifications for all tests performed. Tests performed on the fuel control unit, starting drain valve, overspeed drain valve, pressurizing valve, bleed valve, start electrovalve, and the fuel injection manifold, as well as a three-dimensional check of the axial compressor, revealed no malfunctions or failures that would have precluded normal operation.

The fuel was examined and no contamination was present. There was no evidence of ingestion of water, snow, or ice that would lead to an engine flameout. During the accident flight, the weather conditions required for ice buildup in the air intake filter were not present, and the temperatures in the intake plenum and air filter before engine start were not conducive to ice formation.

Although examination of the helicopter's fuel circuit revealed that it operated correctly, during testing air was drawn into the fuel circuit between the fuel filter assembly and the fuel pumps when the fuel filter assembly drain valve was depressed. Numerous tests were conducted to determine if the air in the fuel lines and the fuel filter assembly could be purged during the engine start sequence and/or by normal engine operation. The tests revealed that some air would still remain trapped in the upper cavity of the fuel filter assembly (the volume of the cavity measured 33 milliliters). The additional tests, which simulated the fuel flow rates at flight idle, maximum takeoff power, and maximum engine generator speed, revealed that the volume of trapped air was about 1 to 2 cubic centimeters. An exemplar engine was subjected to 16 tests on a test cell to determine the effects on the engine if the trapped air was released through the fuel bypass valve located on top of the fuel filter assembly. The engine did not flame out during any of the tests, although one of the tests using a pre-clogged cartridge resulted in a fuel flow interruption lasting 5 milliseconds, a transient disturbance of the engine parameters, and a transient slower rate of power increase for about 5 seconds. The tests did not account for variables such as a "cold soaked" aircraft, cold fuel, air flow disturbances due to rotor wash, the effects of air filters certified under supplemental type certificates and the possible degraded condition of those air filters, no use of compressor outlet pressure bleed air, and no electrical load on the engine.

Analysis of the faults that resulted in the uncommanded in-flight shutdown of the engine indicated that the most likely reason for the flameout was an interruption of fuel flow to the engine. Although the investigation found that air could be introduced into the fuel system through the fuel filter assembly, the mechanism that would allow air to disrupt the fuel flow to the engine and result in an engine flameout could not be determined.

Probable cause

An interruption of fuel to the engine due to air in the fuel lines, which resulted in an engine flameout and the total loss of engine power. The reason for air in the fuel line resulting in an engine flameout could not be determined because postaccident testing did not reveal the mechanism that would lead to such a result.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN11FA118
Event ID
20101220X81957
Case number
CEN11FA118
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: investigation status, coordinates. 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: bb60f7db6b58bed264400440cd133be34ce12f00502beadbfced569c4aa0289d; retrieved 2026-09-15T15:38:10.224Z.