FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC17FA004 · Fairchild Heli-Porter PILATUS PC-6 C-H2

28 Oct 2016 · Port Alsworth, AK, United States

Fairchild Heli-Porter PILATUS PC-6 C-H2 · Accident: controlled flight into terrain/object (CFIT) en route

From Lake Hood Seaplane Base (LHD) to Port Alsworth, AK

Report a problem

Event

NTSB case
ANC17FA004
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
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Unknown

Fairchild Heli-Porter PILATUS PC-6 C-H2

Category
Airplane
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
N5308F
Operator
Unknown
Onboard fatalities
Unknown
Route
From Lake Hood Seaplane Base (LHD), Anchorage, AKTo Port Alsworth, AK
Aircraft age
About 41 years (built 1975)
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 · descent
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
Controlled flight into terrain/object (CFIT)
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
  • Environmental issues › Conditions/weather/phenomena

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 pilot was conducting a cross-country flight to a family residence in the turbine-powered, single-engine airplane. The pilot was familiar with the route, which traversed a mountain pass and remote terrain. Before departing on the flight, the pilot communicated with a family member at the residence via text messages and was aware the weather was windy but that the mountain tops were clear. There was no record of the pilot obtaining a preflight weather briefing from an official, access-controlled source, and the pilot indicated to a friend before departure that he had not accessed weather cameras. Weather forecast products that were available to the pilot revealed possible turbulence at low altitudes and icing at altitudes above 12,000 ft along the route of flight, and weather cameras along the planned route and near the destination would have indicated deteriorating visibility in snow showers and mountain obscuration starting about 1.5 hours before departure. The airplane departed and proceeded toward the destination; radar data correlated to the accident flight indicated that the airplane climbed from 4,600 ft to 14,700 ft before turning west over the mountains. Text messages that the pilot sent during the initial climb revealed that the mountain pass he planned to fly through was obscured, and he intended to climb over the mountains and descend through holes in the clouds as he neared the destination. Radar data also indicated that the airplane operated above 12,500 ft mean sea level (msl) for about 30 minutes, and above 14,000 msl for an additional 14 minutes before entering a gradual descent during the last approximate 20 minutes of flight. Review of weather information indicated that cloud layers over the accident area increased during the 30 minutes before the accident, and it is likely that the airplane was operating in icing conditions, although it was not certified for flight in such conditions, which may have resulted in structural or induction icing and an uncontrolled loss of altitude. The airplane wreckage came to rest on the steep face of a snow-covered mountain in a slight nose-down, level attitude. The empennage was intact, the right wing was completely separated, and the forward fuselage and cockpit were partially separated and displaced from the airframe with significant crush damage, indicative of impact with terrain during forward flight.

There was no indication that the airplane was equipped with supplemental oxygen; pilots are required to use oxygen when operating at altitudes above 12,500 ft for more than 30 minutes, and anytime at altitudes above 14,000 ft. It could not be determined if, or to what extent, the pilot may have experienced symptoms of hypoxia that would have affected his decision-making.

The airplane wreckage was not recovered or examined due to hazardous terrain and environmental conditions, and the reason for the impact with terrain could not be determined; however, it is likely that deteriorating enroute weather and icing conditions contributed to the outcome of the accident.

Probable cause

The airplane's collision with mountainous terrain while operating in an area of reduced visibility and icing conditions. Contributing to the accident was the pilot's inadequate preflight planning, which would have identified deteriorating weather conditions along the planned route of flight.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC17FA004
Event ID
20161031X30541
Case number
ANC17FA004
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. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2016-10-29.
  • API snapshot SHA-256: bf448f5c2de1c02b13c3bc8079e8c93d92741e094ff187056b4855dfabf3decd; retrieved 2026-09-14T22:01:54.883Z.