FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN18FA149 · Eurocopter AS 350 B2

26 Apr 2018 · Hazelhurst, WI, United States

Air Methods Eurocopter AS 350 B2 · Accident: loss of control in flight en route

From Dane County Regional Truax Field (MSN) to Howard Young Medical Center Heliport (60WI)

Report a problem

Event

NTSB case
CEN18FA149
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
Visual Meteorological Cond

Eurocopter AS 350 B2

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
N127LN
Operator
Air Methods
Onboard fatalities
Unknown
Route
From Dane County Regional Truax Field (MSN), Madison, WITo Howard Young Medical Center Heliport (60WI), Woodruff, WI
Aircraft age
About 12 years (built 2006)
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
Loss of control in flight
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
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Physical
  • Personnel issues › Task performance

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

NTSB narrative

The helicopter pilot and two emergency medical service crewmembers were on a repositioning flight in night visual meteorological conditions after two helicopter air ambulance flights and a refueling stop. The total flight time for the first three flights was 94 minutes and occurred over a period of about 2 ½ hours.

The helicopter departed on the accident flight about 2107. About 1 minute later, the pilot asked the crewmembers whether they were "alright." One crewmember responded "yup" and then asked the pilot, "question is are you alright up there?" The pilot responded, "uhhh think so. Good enough to get us home at least." There was no further discussion related to fatigue. During the flight, the pilot adjusted his seat position and flexed his legs, which were actions consistent with signs of fatigue. Also, although the pilot participated in the medical crewmembers' conversations in the middle of the flight, he did not participate in their conversations near the end of the flight. During the last portion of flight, the helicopter entered a progressively steepening right bank, and the pilot did not respond as the medical crewmembers shouted his name. The helicopter descended and became inverted, and the pilot continued not to respond as the crewmembers' shouted his name.

After the helicopter began to roll to the right, the pilot slumped to the left, appearing incapacitated. There was no evidence indicating that the pilot was suffering from a medical condition that could have caused his incapacitation. There was also no evidence of poor quality or quantity of sleep; the pilot's wife reported no issues with the pilot falling asleep or staying asleep, and cellular telephone records and his wife's interview indicated adequate sleep opportunity in the days preceding the accident. On the day of the accident, cellular telephone activity revealed two possible opportunities for the pilot to sleep before going on duty but it is not known if the pilot rested during those times. Thus, the pilot could have been awake for about 15.5 hours at the time of the accident (based on telephone records showing activity at 0725 the morning of the accident) if he did not take advantage of the sleep opportunities. Although this time since awakening would not be considered excessive, this accident shift was the pilot's first after returning from a week-long vacation during which his circadian rhythm would have had him sleeping. Further, the environment created by the helicopter vibration, darkness of night, and few operational demands during the cruise phase of flight would have increased the pilot's fatigue and the body's biological desire to sleep. These factors, along with the pilot's movements observed on the image recorder, indicated that the pilot became fatigued during the flight. Thus, he pilot likely fell asleep during the flight as a result of the time of day, his time since awakening, and the fatigue-inducing effect of the 1 ½ hour flight.

No light or audio warnings that would indicate a mechanical malfunction were observed during the accident flight. Postaccident examination and testing revealed no preimpact anomalies that would have precluded normal operation of the helicopter.

Probable cause

The pilot's loss of helicopter control as a result of fatigue during cruise flight at night.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN18FA149
Event ID
20180427X55413
Case number
CEN18FA149
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 2018-04-27.
  • API snapshot SHA-256: 0a206418462291ecb14f16642dc44a8c778d05769b58bc64fee57cd44ef7ae10; retrieved 2026-09-15T06:39:45.522Z.