FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA10MA188 · Eurocopter AS-350-B3

25 Mar 2010 · Brownsville, TN, United States

Memphis Medical Center Air Ambulance Service Eurocopter AS-350-B3 · Accident: windshear or thunderstorm en route

From Jackson-Madison County General Hospital Heliport (TN05) to Haywood County Ems Heliport (99TN)

Report a problem

Event

NTSB case
ERA10MA188
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
3 · 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
Instrument Meteorological Cond

Eurocopter AS-350-B3

Aircraft type
Eurocopter AS-350
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
N855HW
Onboard fatalities
Unknown
Route
From Jackson-Madison County General Hospital Heliport (TN05), Jackson, TNTo Haywood County Ems Heliport (99TN), Brownsville, TN
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
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
Windshear or thunderstorm
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

  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The accident pilot was preparing to return to the helicopter's home base at night after dropping off a patient at a hospital helipad near the end of his 12-hour duty period. The oncoming pilot, who was scheduled for the next duty period, arrived at the helicopter's home base and saw that the helicopter was gone. He was concerned about the weather and called a flight-following center, locating the helicopter on the hospital helipad. The accident pilot then called the oncoming pilot via cellular telephone and asked about the weather. He stated that he was still on the helipad waiting for the flight nurses to return and that he "wanted to get the helicopter out." The oncoming pilot further indicated in postaccident interviews that when he suggested that the accident pilot park the helicopter on the helipad, the accident pilot said that another helicopter already occupied the lower elevation pad, which the oncoming pilot took to mean that the accident pilot did not want to leave the helicopter on the hospital's elevated pad. The two pilots then discussed an approaching weather system. The oncoming pilot reported that the accident pilot told him that he believed he had about 18 minutes to beat the storm and return to home base, so he was going to leave the flight nurses behind and bring the helicopter back.

The oncoming pilot stated that he later called the flight nurses, only to learn that they were on board the helicopter. Rechecking visibility, the oncoming pilot then communicated with one of the nurses on board and told her that she "had the weather beat," and she responded that they were about 30 seconds from arrival. Three witnesses near the accident site stated that they saw lightning and heard thunder at the time of the accident. One witness stated that it was very windy at the time, and another stated that heavy rain bands were passing through the area. After the oncoming pilot heard a loud clap of thunder and saw lightning, he tried to call the crew, but there was no response. The helicopter crashed in an open wheat field about 2.5 miles east of the home base.

Examination of the wreckage revealed no evidence of any preimpact failures or malfunctions of the engine, drive train, main rotor, tail rotor, or structure of the helicopter. Additionally, there was no indication of an in-flight fire.

An examination of meteorological data revealed that the helicopter likely encountered the leading edge of a line of thunderstorms, moving at 61 knots groundspeed. A portion of this line of thunderstorms included localized instrument meteorological conditions, heavy rain, lightning, and wind gusts up to 20 knots. The near-surface region immediately ahead of this advancing line, known as the "gust front," is an area prone to extreme low-level wind shear that often occurs in clear air. Based on these conditions, the helicopter likely encountered severe turbulence from which there was no possibility of recovery, particularly at low level. No evidence existed of a lightning strike at the time of the accident.

Although the pilot encountered an area of deteriorating weather, this did not have to occur as the pilot could have chosen to stay at the hospital helipad. The pilot, however, decided to enter the area of weather, despite the availability of a safer option. Based on the pilot's statement to the oncoming pilot about the need to "beat the storm" and his intention to leave the flight nurses behind and bring the helicopter back (even though the nurses made it back on board), he was aware of the storm and still chose to fly into it. The pilot made a risky decision to attempt to outrun the storm in night conditions, which would enable him to return the helicopter to its home base and end his shift there, rather than choosing a safer alternative of parking the helicopter in a secure area and exploring alternate transportation arrangements or waiting for the storm to pass and returning to base after sunrise when conditions improved. This decision making error played an important causal role in this accident. At the time of the accident, the pilot was nearing the end of his 12-hour duty shift, during which he had flown previous missions and may have had limited opportunities to rest. Further, he had been on duty overnight, and the accident occurred at an early hour that can be associated with degraded alertness. The pilot's length of time awake, his night shift, and the early hour of the accident provide risk factors for fatigue that could have significantly degraded his decision making. However, without complete evidence regarding his sleep and rest activities, the National Transportation Safety Board was unable to determine whether or to what degree fatigue contributed to the pilot's faulty decision to attempt to outrun the storm.

Probable cause

The pilot's decision to attempt the flight into approaching adverse weather, resulting in an encounter with a thunderstorm with localized instrument meteorological conditions, heavy rain, and severe turbulence that led to a loss of control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA10MA188
Event ID
20100325X93604
Case number
ERA10MA188
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. 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: 3bb4b769cb73a7fbc1782a1255fad73bac0a8194aae7b3253a5c4fb193085b9d; retrieved 2026-09-13T20:43:57.440Z.