CEN15FA164 · Airbus Helicopters (Eurocopte EC-130-B4
Air Methods Airbus Helicopters (Eurocopte EC-130-B4 · Accident: settling with power/vortex ring state on approach
From Arch Heliport (MU05) to St Louis University Hospital Heliport (MO55)
Event
- NTSB case
- CEN15FA164
- 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
Airbus Helicopters (Eurocopte EC-130-B4
- Aircraft type
- Airbus Helicopters (eurocopte EC-130
- 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
- N356AM
- Operator
- Air Methods
- Onboard fatalities
- Unknown
- Route
- From Arch Heliport (MU05), St Louis, MOTo St Louis University Hospital Heliport (MO55), St Louis, MO
- Aircraft age
- About 5 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 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
- Approach · VFR pattern final
- 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
- Settling with power/vortex ring state
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
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 service (EMS) helicopter was landing on a privately owned elevated heliport to pick up two medical crewmembers. The medical crewmembers had been dropped off with a patient on a preceding flight. During the preceding flight, the nurse thought about telling the pilot to abort the landing on the heliport because there was a lot of rolling and yawing, and he was having a hard time landing the helicopter. After the landing, the nurse and another medical crewmember stated that the pilot did not want to depart the heliport, but the medical crewmembers told the pilot that there may be potential arrivals of other EMS helicopters. The pilot chose to depart the heliport and obtained fuel at the operator's base of operations. For the return flight to pick up the two medical crewmembers, the wind had increased, and the helicopter approached the heliport in high-wind conditions and with a right, quartering tailwind. Also, the wind along with the surrounding buildings likely created a turbulent airflow/windshear environment in which the helicopter was operating as it approached for landing. The helicopter's operation in a high-power, low-airspeed condition in high-wind conditions, including a right quartering tailwind, likely resulted in a loss of control due to settling with power.
A security video showed the helicopter on a northerly flightpath descending at about a 45-degree angle before impacting the ground and coming to rest on an approximate northerly heading. The pilot sustained fatal injuries due to the subsequent fuel tank fire/explosion, which otherwise would have been a survivable accident.
A postaccident safety evaluation of the heliport showed that the final approach and takeoff area/safety area were obstructed by permanent and semi-permanent objects that pose a serious hazard to helicopter operations. These obstructions limited the available approach paths to the heliport, which precludes, at times, approaches and landings with a headwind. The helipad is privately owned; therefore, it is not subject to Federal Aviation Administration (FAA) certification or regulation.
A review of the helicopter's flight manual revealed that there were no wind speed/azimuth limitations or suggested information available to pilots to base the performance capabilities of the make and model helicopter in their flight planning/decision-making process. Examination of the helicopter revealed no anomalies that would have precluded normal operation and showed engine power at the time of impact.
An accredited representative from the Bureau d'Enquêtes et d'Analyses pour la Sécurité de l'Aviation Civile (BEA) was assigned to this investigation as the state of manufacture of the helicopter. The BEA provided comments on this report, which can be found in the docket.
Probable cause
The pilot's decision to land during unfavorable wind conditions, which resulted in a loss of control due to settling with power. Contributing to the accident were the lack of an adequate approach path due to numerous obstructions and the lack of available guidance regarding the helicopter's performance capabilities in the right quartering tailwind condition.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN15FA164
- Event ID
- 20150308X10201
- Case number
- CEN15FA164
- 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 2015-03-07.
- API snapshot SHA-256: bb6e14391fca493a403ce5c6e5505b903b0f624203a9e72e15c8431e8577f1a4; retrieved 2026-09-14T17:32:48.504Z.