Air Methods Messerschmitt-Bolkow-Blohm BK 117 B-2 accident
Messerschmitt-Bolkow-Blohm BK 117 B-2 · Accident: collision during takeoff/landing during initial climb
From Hartford, IL (no airport) to Granite City, IL (no airport)
Event
- NTSB case
- CEN25LA163
- 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
- 0
- 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
- Aircraft type
- Messerschmitt Bolkow Blohm BK-117
- 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
- N880SL
- Operator
- Air Methods
- Onboard fatalities
- Unknown
- Route
- From Hartford, IL (no airport)To Granite City, IL (no airport)
- Aircraft age
- About 37 years (built 1988)
- 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
- Initial climb
- 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
- Collision during takeoff/landing
- 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 oper/perf/capability
- Personnel issues › Action/decision
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The purpose of the public relations flight with the air medical helicopter was to perform landing zone training with a fire department. Prior to the flight, the pilot discussed the confined area landing zone characteristics with another company pilot, and he studied satellite imagery of the confined area landing zone. The flight manifest and the flight risk assessment tool were completed and submitted to the operational control center, which then issued a flight release after approval. Prior to initiating the approach, the pilot performed a high reconnaissance to identify the confined area landing zone and the obstacles which consisted of a tree and power lines. The pilot then performed a low reconnaissance while simultaneously performing a steep approach. The helicopter landed in the vacant lot, consisting of a flat grass field, across the street from the fire department. Several hours later after the training was completed, the pilot performed a ground reconnaissance, noting the tree and the power lines. Ground personnel illuminated the power lines near the confined area landing zone for the night takeoff. The pilot, who was utilizing night vision goggles with the helicopter’s searchlight activated, brought the helicopter to an in ground effect hover, and he balanced the torque indications for the two turboshaft engines. The pilot decided to use the power lines in front of the helicopter as a visual reference for the initial climb. During the initial climb, the helicopter inadvertently drifted rearward, and the tail rotor system impacted the tree. The helicopter rotated to the right, descended, and it came to rest partially upright. Shortly after impacting the ground, a postimpact fire initiated, and partially consumed the helicopter. The front right seat pilot and the rear left seat (aft facing) flight nurse were able to egress on their own from the helicopter. The front left seat flight nurse required assistance from ground personnel to egress from the helicopter. The fire department was able to immediately perform fire suppression efforts on the helicopter. The helicopter sustained substantial damage to the fuselage, the main rotor system, the empennage, and the tail rotor system. The helicopter was not equipped with a crash resistant fuel system, nor was it required by regulation.
Probable cause
The pilot’s failure to maintain directional control during the initial climb at night from a confined area landing zone, that resulted in an impact with a tree, a loss of control, and a subsequent impact with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN25LA163
- Event ID
- 20250425200063
- Case number
- CEN25LA163
- 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, cause areas. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2025-04-25.
- API snapshot SHA-256: 2aa7f2cb1492a62d34a47123caf32550080856d1cd940d1d385031b5d34b13ac; retrieved 2026-09-16T19:50:56.213Z.