FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Air Methods Messerschmitt-Bolkow-Blohm BK 117 B-2 accident

13 Nov 2011 · Carbondale, IL, United States

Messerschmitt-Bolkow-Blohm BK 117 B-2 · Accident while standing

From Sparta, IL to Memorial Hosp Of Carbondale Heliport (5IS1)

Report a problem

Event

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

Messerschmitt-Bolkow-Blohm BK 117 B-2

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
N330SL
Operator
Air Methods
Onboard fatalities
Unknown
Route
From Sparta, ILTo Memorial Hosp Of Carbondale Heliport (5IS1), Carbondale, IL
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 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
Standing · engine(s) operating
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
Miscellaneous/other
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 propeller/rotor

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

NTSB narrative

During an engine shutdown procedure following an emergency medical services flight, a main rotor blade sustained substantial damage when it contacted the left vertical stabilizer. The main rotor blade was broken near its root, and the tailboom and tail rotor driveshaft cover were dented. The local recorded wind was 25 knots gusting to 34 knots. The damage was consistent with the main rotor blade flapping with the gusty wind conditions and impacting the stabilizer. The operator reported that there were no preaccident mechanical malfunctions with the helicopter.

Probable cause

The main rotor blade’s contact with the vertical stabilizer during the engine shutdown in strong, gusty wind conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN12CA078
Event ID
20111123X02155
Case number
CEN12CA078
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: 20be1b8756d967d1582c9e6e75e711baee0c2c12b04ef7046e8b844b6bb001d1; retrieved 2026-09-15T16:57:37.242Z.