FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Flight Alaska Cessna 206 accident

4 Feb 2002 · Bethel, AK, United States

Cessna 206 · Accident: in flight encounter with weather en route

From Bethel Airport (BET) to Chevak Airport (VAK)

Report a problem

Event

NTSB case
ANC02FA014
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 206

Aircraft type
Cessna 206
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
N756HL
Onboard fatalities
Unknown
Route
From Bethel Airport (BET), Bethel, AKTo Chevak Airport (VAK), Chevak, 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 · 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
In flight encounter with weather
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
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

  • Pilot in command › Clearance, not maintained
  • Pilot in command › VFR flight into imc, 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 solo commerical pilot departed on a CFR 135 on-demand cargo/U.S. mail flight en route to a remote coastal village. The flight did not reach the destination. A search and rescue satellite received an ELT signal, and the wreckage was located about 80 miles from the departure airport, along the airplane's intended flight path. A pilot who departed about 25 minutes before the accident airplane, also en route to the same coastal village, characterized the weather conditions along the route as "low visibility with light snow squalls moving through the area." He added that flat light conditions made it very difficult to discern any topographic features. Another pilot who was transiting through the area in the opposite direction, about the time of the accident, characterized the weather conditions as overcast with ceilings ranging between 1,000 and 1,300 feet. As he approached the site where the wreckage was eventually discovered, he encountered momentary visibility restrictions due to fog and light snow. He added that flat light conditions made it very difficult to discern any topographic features among the featureless, snow-covered terrain. The pilot stated that he changed his route in order to avoid worsening weather conditions. The accident airplane was equipped with an avionics package provided by the FAA's Capstone Program. The Capstone Program is a joint industry/FAA demonstration program that includes global positioning system (GPS) avionics, weather and traffic information provided through automatic dependent surveillance-broadcast (ADS-B), and terrain information depicted on a multifunction display (MFD) installed in the cockpit. Terrain depiction information, based on GPS data, is one of several visual display options available to the pilot on the MFD. Damage to the accident airplane's MFD precluded a determination of the visual display option selected at the time of the accident. At the time of the accident, position information from ADS-B equipment in the airplane was being provided to the Air Route Traffic Control Center (ARTCC). The recorded ARTCC data were reviewed to determine the flight track of the accident airplane. The radar-like track depicted the accident airplane's takeoff from the departure airport, on a heading of approximately 300 degrees. While en route, the airplane climbed to an altitude of about 1,800 feet msl. As the track continued in a northwesterly direction and approached the accident site, a gradual descent was noted. The radar-like track stopped approximately 1.8 miles east of the accident site, with a ground speed of approximately 108 knots. Examination of the accident site revealed physical evidence indicating the airplane impacted the ground on a southeasterly heading (directly opposite of the on-course heading for the intended flight) in a slight nose down attitude. No evidence of any pre-impact anomalies with the engine or airplane were noted.

Probable cause

The pilot's continued VFR flight into instrument meteorological conditions, and his failure to maintain adequate ground clearance, which resulted in an in flight collision with terrain. Factors associated with the accident were flat light conditions, and snow-covered terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC02FA014
Event ID
20020228X00285
Case number
ANC02FA014
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: 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: 780db7bd17e1c823d503308e0a1d17638a1c0677d8c93a0a3f8603966c466488; retrieved 2026-09-18T13:07:04.930Z.