23 May 2017: AIRBUS AS350 B2 — Coastal Helicopters, Inc.

23 May 2017: AIRBUS AS350 B2 (N207CH) — Coastal Helicopters, Inc.

No fatalities • Juneau, AK, United States

Probable cause

The pilot's decision to depart into an area of degraded visual meteorological and flat light conditions, which resulted in a loss of visual references and subsequent controlled flight into terrain.

— NTSB Determination

Accident narrative

HISTORY OF FLIGHT On May 22, 2017, about 1805 Alaska daylight time, an Airbus AS350 B2 helicopter, N207CH, was substantially damaged when it collided with snow-covered mountainous terrain after departing a remote landing site on the Herbert Glacier, about 21 miles north of Juneau, Alaska. The commercial pilot and three passengers sustained minor injuries; three additional passengers were not injured. The helicopter was registered to and operated by Coastal Helicopters Inc. as a Title 14 Code of Federal Regulations (CFR) Part 135 on-demand air taxi flight. Degraded visual meteorological conditions were reported on the glacier at the time of the accident, and company flight following procedures were in effect for the flight, which originated from Juneau International Airport (JNU), Juneau, Alaska, at 1743. The purpose of the accident flight was to transport five cruise ship passengers who had completed a dogsledding shore excursion and one musher back to the operator's headquarters at JNU. The operator was contracted to provide helicopter transportation to and from the glacier where the dogsledding was conducted (known as "dog camp"). The accident passengers had been transported to the dog camp in the accident helicopter by another pilot. The pilot then returned to JNU, where he picked up another set of passengers to transport back to the glacier. The accident helicopter was one of a flight of two company helicopters that departed for the glacier. While en route, the pilot noted deteriorating weather conditions "moving up the glacier" that consisted of "swirling clouds." The pilot reported the conditions via radio to the operator's headquarters, then the pilots of both helicopters elected to return to JNU. Upon landing, the passengers disembarked, and the two pilots were replaced by other company pilots, who were permitted to fly in lower weather conditions; the two helicopters then departed empty to pick up the passengers on the glacier. The accident pilot stated that en route, the cloud ceilings and visibility were "really good," and she noted a "few clouds moving around" as she neared the glacier. After landing at the dog camp and boarding passengers, the other helicopter departed first, followed by the accident helicopter. The pilot reported that she took off and proceeded down the glacier; about 3/4 mile from the camp, she noted an area of fog along the intended route of flight and chose to return to the dog camp to wait for conditions to improve. She turned the helicopter toward a rocky area in order to maintain visual contact with the ground when, during the turn, the helicopter impacted snow-covered, featureless terrain and came to rest inverted. One passenger reported that he "could not see anything" as the helicopter departed "because of the thick fog." Another passenger described seeing "white everywhere" and stated that "you couldn't tell the sky from the ground." FLIGHT RECORDERS The helicopter did not carry, nor was required to carry, a crashworthy flight data recorder. At the time of the accident, the operator did not have a formal flight data monitoring program in place, nor was it required to have one. SURVIVAL ASPECTS After the helicopter impacted terrain, the passenger seated in the far-right seat of the cabin was unable to activate the buckle of the 3-point restraint system to egress from the inverted helicopter. The pilot noticed that the passenger appeared to be disoriented. The pilot used a personal Leatherman multi-tool to cut through the belt material and release the passenger. The passenger then egressed from the helicopter without further incident.

Contributing factors

  • cause Pilot
  • cause Pilot
  • cause Pilot
  • cause Altitude — Not attained/maintained
  • cause Decision related to condition
  • factor Pilot

Conditions

Weather
VMC, wind 060/03kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.