FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Grant Aviation Cessna 208B accident

1 May 2017 · Chignik Lake, AK, United States

Cessna 208B · Accident: VFR encounter with IMC en route

From Port Heiden Airport (PTH) to Perryville Airport (PEV)

Report a problem

Event

NTSB case
ANC17FA021
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
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

Cessna 208B

Aircraft type
Cessna 208
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
N803TH
Onboard fatalities
Unknown
Route
From Port Heiden Airport (PTH), PORT HEIDEN, AKTo Perryville Airport (PEV), PERRYVILLE, AK
Aircraft age
About 25 years (built 1992)
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

  • Environmental issues › Conditions/weather/phenomena
  • Environmental issues › Physical environment
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The airline transport pilot was conducting a commercial visual flight rules (VFR) flight. A passenger who was on the first segment stated that the pilot flew the airplane lower than usual for that route, and that the airplane flew through clouds during the flight. The passenger disembarked and the pilot departed on the second segment of the flight with a load of mail. The route included flight across a peninsula of mountainous terrain to a remote coastal airport that lacked official weather reporting or instrument approach procedures. About 28 minutes after departure, an emergency locator transmitter (ELT) signal from the airplane was received and a search and rescue operation was initiated.

The wreckage was located about 24 miles from the destination in deep snow on the side of a steep, featureless mountain at an elevation about 3,000 ft mean sea level. The accident site displayed signatures consistent with impact during a left turn. Examination of the airplane revealed no evidence of mechanical malfunctions or anomalies that would have precluded normal operation. The airplane was not equipped with any recording or flight tracking devices, nor was it required to be; therefore, the airplane's flight track before the accident could not be determined. The airplane was certified for instrument flight and flight in icing conditions and was equipped with a terrain avoidance warning system (TAWS) which was not inhibited during the accident. Although the TAWS should have provided the pilot with alerts as the airplane neared the terrain, it could not be determined if this occurred or if the pilot heeded the alerts.

A review of nearby weather camera images revealed complete mountain obscuration conditions with likely rain shower activity in the vicinity of the accident site. Visible and infrared satellite imagery indicated overcast cloud cover over the accident site at the time of the accident. The graphical forecast products that were available to the pilot before the flight indicated marginal VFR conditions for the entire route. There was no evidence that the pilot obtained an official weather briefing, and what weather information he may have accessed before the flight could not be determined. Additionally, the cloud conditions and snow-covered terrain present in the area likely resulted in flat light conditions, which would have hindered the pilot's ability to perceive terrain features and closure rates. Based on the weather camera, surface, and upper air observations, it is likely that the pilot encountered instrument meteorological conditions inflight, after which he performed a left turn to return to visual meteorological conditions and did not recognize his proximity to the mountain due to the flat light conditions.

The pilot and the dispatch agent signed a company flight risk assessment form before the flight, which showed that the weather conditions for the flight were within the company's acceptable risk parameters. Although the village agents at the departure and destination airports stated that the weather at those coastal locations was good, the weather assessment for the accident flight was based on hours-old observations provided by a village agent who was not trained in weather observation and did not include en route weather information, the area forecast, or the AIRMET for mountain obscuration effective during the dispatch time and at the time of the accident. Since acquiring the accident route from another operator years earlier, the company had not performed a risk assessment of the route and its associated hazards. Multiple company pilots described the accident route of flight as hazardous and considered it an undesirable route due to the terrain, rapidly changing weather, and lack of weather reporting infrastructure; however, the company did not address or attempt to mitigate these known hazards through its risk assessment processes.

The company's controlled-flight-into-terrain (CFIT)-avoidance program stated that each pilot shall have one classroom training session and one CFIT-avoidance training session in an aviation training device (ATD) each year; however, the pilot's training records indicated that his most recent ATD session was 15 months prior. More recent CFIT avoidance training may have resulted in the pilot recognizing and responding to the reduced visibility and flat light conditions sooner.

Probable cause

The pilot's continued visual flight rules flight into an area of mountainous terrain and instrument meteorological conditions, which resulted in controlled flight into terrain (CFIT). Contributing to the accident was the company's failure to provide the pilot with CFIT-avoidance recurrent simulator training as required by their CFIT avoidance program and the company's inadequate flight risk assessment processes, which did not account for the known weather hazards relevant to the accident route of flight.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC17FA021
Event ID
20170502X12758
Case number
ANC17FA021
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: 67ecc9763f13c189e6ead170029f7aa7495d08e65fa2472c441bb16c4cbbcfde; retrieved 2026-09-15T06:01:59.673Z.