FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Evergreen Helicopters of Alaska Eurocopter Deutschland BK117C1 accident

3 Dec 2007 · Whittier, AK, United States

Eurocopter Deutschland BK117C1 · Accident: VFR encounter with IMC en route

From Cordova Municipal Airport (CKU) to Anchorage, AK

Report a problem

Event

NTSB case
ANC08FA025
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
4 · 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
Instrument Meteorological Cond

Eurocopter Deutschland BK117C1

Aircraft type
Eurocopter BK117
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
N141LG
Onboard fatalities
Unknown
Route
From Cordova Municipal Airport (CKU), Cordova, AKTo Anchorage, AK
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
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
VFR encounter with IMC
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

  • Pilot in command › Altitude/clearance, not maintained
  • Pilot in command › Flight into adverse weather, continued

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The commercial helicopter pilot was on a visual flight rules (VFR) 14 Code of Federal Regulations Part 135 EMS (emergency medical service) patient transfer flight from a remote medical clinic in Alaska to a hospital in Anchorage when it collided with the ocean during instrument meteorological conditions. The flight entailed flying over and near ocean waters and mountainous terrain during dusk and night conditions without lighted ground references (such as buildings and street lights) due to the uninhabited topography. With the pilot and patient were a paramedic and a nurse. While crossing over a portion of ocean approaching rising terrain, the helicopter likely encountered low ceilings and snow squalls. With the pilot unable to discern either the shore or the ocean, it is probable he flew the helicopter under control into the ocean. Pieces of the helicopter and the body of the nurse were recovered several days after the accident. The rest of the helicopter and its occupants are presumed to have sunk in the ocean. There were no distress calls received from the pilot, and no history of any significant mechanical issues with the helicopter.

The accident flight was the pilot's first flight from this clinic, and this was his first winter season flying in Alaska. He had expressed his concern to a mechanic prior to the flight about flying over the accident route and water at night, and also told the nurse to bring his night vision goggles (NVGs) to assist him in seeing terrain. The pilot also had NVGs. It is unknown what weather information the pilot had when he elected to accept the flight. He had access to a company computer, and he and other company pilots routinely did their preflight weather planning using it. There is no record that he received any preflight weather briefing from the FAA, nor contacted them for weather information prior to his departure from the clinic, or sought weather updates while en route. It was night VFR when the pilot departed the clinic, but the weather had deteriorated near the accident site in close proximity to his departure time. The nearest reporting station was about 5 miles from the accident site. About 23 minutes before the accident, it was reporting instrument meteorological conditions with snow and low ceilings.

Aerial search efforts had to be delayed due to the poor weather. Neither the operator nor the hospital provided en route weather updates, or primary dispatch services. The hospital's procedure was to call the assigned EMS pilot to request a flight, and the pilot made the decision to either accept or reject the flight. Company procedures required that the pilot complete a risk assessment form prior to taking a flight. There was no risk assessment form found for the accident flight, and company management could not locate other risk assessment forms for previous EMS flights. An exemplar risk assessment form was completed by the NTSB investigator-in-charge using information that the pilot could reasonably expect to have known prior to accepting the flight. That information equated to a "Moderate" risk level, and required company management's concurrence to authorize the flight. Company management was not notified. The pilot was required to phone the hospital communications center at 10-minute intervals via satellite phone while en route, and when he did not call at the required time, a search was initiated.

The operator's main base was in Anchorage, and the EMS facility was in another Alaska town. The operator had not been assigned a principal operations inspector (POI) to oversee their operations until about 2 months prior to the accident. The POI had not inspected or visited the remote EMS location. Prior to the POI's assignment, the operator did not have a POI assigned for the preceding 22 months, but instead relied on various points of contact (POC) within the local FAA Flight Standards District Office to provide oversight. Investigation disclosed no evidence that any POC had visited the EMS facility. The operator also did not adhere to the proper procedures in training the accident pilot in the use of the NVGs. These discrepancies were not discovered by the FAA until after the accident. NTSB/SIR-06/01 recommended that the FAA require EMS operators to use formalized dispatch and flight-following procedures that include up-to-date weather information and assistance in flight risk assessment decisions. With a formalized dispatch and flight following process, it is probable the helicopter would have been turned around/canceled prior to entering instrument meteorological conditions (IMC), or due to the noncritical nature of the patient, the patient could have waited until an airplane was available that was capable of flying in IMC.

Probable cause

The pilot's decision to continue VFR flight into night instrument meteorological conditions. Contributing to the accident were the operator's failure to adhere to an FAA-approved and mandated safety risk management program, the FAA's failure to provide sufficient oversight of the operator to ensure they were in compliance with the risk management program, the pilot's lack of experience in night winter operations in Alaska, and the operator's lack of an EMS dispatch and flight following system.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC08FA025
Event ID
20071213X01937
Case number
ANC08FA025
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
  • 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, coordinates. 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: 669a07206c76b0bdb2ca504c1af930bd793ed9ed4f0dcf1ed9aecf1651491f9f; retrieved 2026-09-18T12:54:30.956Z.
  • The NTSB's operator name is blank for N141LG; the operator shown is the name the NTSB records it doing business as.