FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC06GA121 · Eurocopter France AS350 B2

21 Aug 2006 · Nuiqsut, AK, United States

Prism Helicopters Eurocopter France AS350 B2 · Accident: loss of control in flight en route

From Fish Creek, AK to Inigok Airport (4AK1)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's operation. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
ANC06GA121
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
1 · 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 Possible conflict
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 France AS350 B2

Aircraft type
Eurocopter AS350
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
C-FYUN
Onboard fatalities
Unknown
Route
From Fish Creek, AKTo Inigok Airport (4AK1), Inigok, 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 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 · cruise
First occurrenceThe 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

  • External load sling/harness › Entangled
  • Pilot in command › Clearance, not maintained

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 certificated helicopter pilot was dispatched to a remote research site, about 40 miles northeast of the base camp to retrieve an external sling load. The helicopter was being operated under contract to the U.S. government as a public use flight under Title 14, CFR Part 91. The helicopter departed the base camp in the early evening, and did not return. There were no communications with the helicopter pilot, and weather conditions precluded a search until late the next morning. The helicopter's wreckage was located near the shore of a shallow lake, in several feet of water, about 1 mile south of the remote research site. There were no ground scars around the lake's perimeter. The external sling load was at the accident site. The helicopter was equipped for satellite flight following, and the track showed no unusual characteristics from the base camp to the remote research site, nor from the research site to the accident site. Prior to departing the base camp for the research site, the helicopter had recently returned from the research site with a passenger. Both the pilot and passenger told the camp manager that weather conditions at the research site were marginal and deteriorating. The passenger reported that typically from early evening to late morning, fog and low clouds blanketed the area. The pilot was asked to retrieve the load if possible, but not to take any chances. The helicopter was examined at the accident site, and re-examined after recovery. At the accident site, all the helicopter components were accounted for, however, the tail boom had separated from the fuselage, and lay farther out in the lake. The helicopter's cabin had the appearance of having tumbled, but the tail boom did not. The external load was located in the lake, between the tail boom and the fuselage. Examinations of the helicopter and its components established control continuity, and did not reveal any preaccident mechanical anomalies. The helicopter's external load lifting gear revealed damage to the airframe attaching brackets, and supporting cable attachments. The sling load had damage to both the cargo net and the net's cinch ropes. The cargo net was made of white rope containing a black trace, and had several broken ropes, which were not there prior to the accident flight. The net's cinch rope, which was yellow with a blue trace, had been pulled apart at a spliced thimble. During an examination of the tail rotor tracking blade, blue rope fibers consistent with the blue trace fibers of the net's cinch rope, were found trapped under the blade's end cap bolt. Both the tail boom and the tail rotor blades had rope marks in their paint.

Probable cause

The pilot's failure to maintain clearance from the sling load during cruise flight, which resulted in the load becoming entangled in the tail rotor, and an in-flight loss of control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC06GA121
Event ID
20060905X01290
Case number
ANC06GA121
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2006-08-22.
  • API snapshot SHA-256: e95052bff06f19db4b8bac81840be0e9832ad95108b1f4770dc929ce75a8e0e3; retrieved 2026-09-20T17:05:05.845Z.