Geisinger Medical Center Eurocopter Deutschland Gmbh MBB-BK 117 C-2 accident
Eurocopter Deutschland Gmbh MBB-BK 117 C-2 · Accident: collision during takeoff/landing
From Muncy Valley Hospital Heliport (7PS5) to Geisinger Rooftop Heliport (79PN)
Event
- NTSB case
- ERA13LA134
- 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
Eurocopter Deutschland Gmbh MBB-BK 117 C-2
- Aircraft type
- Eurocopter MBB-BK 117 C-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
- N481LF
- Operator
- Geisinger Medical Center
- Onboard fatalities
- Unknown
- Route
- From Muncy Valley Hospital Heliport (7PS5), Muncy, PATo Geisinger Rooftop Heliport (79PN), Danville, PA
- Aircraft age
- About 3 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 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
- Landing
- 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
- Personnel issues › Action/decision
- Personnel issues › Psychological
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, as the helicopter approached mountainous terrain near the hospital during a helicopter emergency medical services (HEMS) flight, he turned the helicopter slightly right to pass through a gap in the ridgeline and then continued to fly directly to the heliport. The pilot then radioed that he was "3 minutes out." About this time, the medical crew intubated the patient, and the communications center advised the pilot that two people were on the roof to assist him. He then observed two individuals on the rooftop helipad, which, "while not abnormal," was "not routine." He was "a bit concerned" because he wanted to make sure the personnel were clear of the helipad before landing. The pilot recalled that he was somewhat more attuned to the patient's condition because the medical crew was working hard to keep the patient alive and was moving around the cabin unrestrained. He continued descending the helicopter on a straight-in approach and began the final approach to the rooftop helipad. About 100 yards from touchdown, he noticed something "orange" out of the left window. At almost the same time, the flight paramedic mentioned that he also "saw something orange." The pilot then felt a "slight low frequency vibration," which was also noticed by the flight nurse. About 6 seconds later, he landed the helicopter on the helipad, executed an emergency shutdown, and then cleared the crew to exit.
A contractor who was operating a construction crane near the heliport reported that he was lowering a piece of equipment onto the roof of a building when he observed a helicopter approaching. Another contractor then observed one of the helicopter's blades contact the flag marker, which was mounted on the top of the construction crane boom, and "pieces of wood and flag…flying all over the place." Examination of the helicopter confirmed that the main rotor had contacted the flag marker and that one of its blades was substantially damaged. According to the pilot, neither he, the flight nurse, nor the flight paramedic had seen the construction crane before the helicopter contacted it while approaching the helipad.
Review of photographs taken after the accident revealed that the pilot's straight-in approach to the rooftop helipad passed over the location of the construction crane, which was positioned next to a nearby building. Flight crews had been notified of the construction crane's position 2 days before the accident, and the pilot believed that he had briefed the crew about the presence of the construction crane at the medical center. According to the notification, the crane was to be in position between about 0700 to 1000 local time and was going to have a beacon on top because of the proximity of the helipad. However, no beacon was installed, and the crane was still in use and in position 2 hours 21 minutes after the notification advised that the work was supposed to be completed.
No evidence was found indicating that the continued operation of the construction crane nor its presence was transmitted to the flight crewmembers when the flight was approaching the hospital. The investigation revealed that the communications technician was on the rooftop helipad at the time of the accident, not at her duty station manning the radio. The investigation also revealed that another helipad, which was located at ground level and was not near the construction crane, was available at the time of the accident and could have been used for the landing.
If the pilot had been provided with correct information about the construction crane's operation time and its presence or if he had used the available ground-level helipad, he would have been more likely to have avoided the crane. However, if the pilot had followed the guidance in the company's general operations manual, which required that a high-orbiting reconnaissance be completed before beginning the approach and that all published helicopter procedures for the heliport and helipad be observed (which in the case of the rooftop helipad designated a left traffic pattern), the accident could have been prevented. Instead, the pilot flew a straight-in approach, which placed the helicopter's flightpath near the construction crane, restricted his ability to see due to sun glare, and placed the helicopter in a position that obstructed his view of the construction crane, which would have been behind the instrument panel as the helicopter approached the rooftop helipad.
The National Transportation Safety Board has previously cited time pressure as a risk factor in HEMS flights. Due to the patient's critical condition, the pilot likely felt a sense of urgency to land, which influenced his decision to fly a straight-in approach to the rooftop helipad rather than to conduct a high-orbiting reconnaissance before initiating the approach. Although attempts are generally made to isolate HEMS pilots from the patient's condition while making go/no-go decisions, once onboard, it is difficult for pilots to be unaware of serious medical conditions that may be time critical, which leads to self-induced time pressures.
Probable cause
The pilot’s decision to conduct a straight-in approach to the helipad, which resulted in the main rotor blade impacting a construction crane flag marker. Contributing to the accident was the erroneous information about the construction crane’s operation time and the pilot’s self-induced time pressure, which resulted from his awareness of the patient’s medical situation during the flight.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA13LA134
- Event ID
- 20130215X30422
- Case number
- ERA13LA134
- 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: 57aa5d0808e3c4c24e49e4c74dc39fd8904d5ded93f85cb35f6cf69d165cb0b7; retrieved 2026-09-15T20:56:11.717Z.