FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Hageland Aviation Services Cessna 208 accident

19 Dec 2005 · Brevig Mission, AK, United States

Cessna 208 · Accident: loss of control on ground/water while taxiing

From Port Clarence Coast Guard Station (PAPC) to L-3B · Brevig Mission, AK

Report a problem

Event

NTSB case
ANC06CA012
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
0 · 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
Visual Meteorological Cond

Cessna 208

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
N303GV
Onboard fatalities
Unknown
Route
From Port Clarence Coast Guard Station (PAPC), Port Clarence, AKTo L-3B · Brevig Mission, 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
Taxi · from runway
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 on ground/water
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

  • Pilot in command › Compensation for wind conditions, inadequate

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airline transport certificated pilot landed on runway 04, a snow-covered gravel runway, which required a correction for a left crosswind. The operator reported that after landing, as the pilot was turning the airplane to the left in order to back-taxi on runway 04, a gust of wind lifted the right wing, and the left wing and propeller struck the runway. The airplane sustained substantial damage to the left wing. The operator reported that there were no preaccident mechanical anomalies with the airplane.

Probable cause

The pilot's inadequate compensation for crosswind conditions, which resulted in the left wing striking the ground while taxiing. A factor in the accident was a crosswind.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC06CA012
Event ID
20060113X00067
Case number
ANC06CA012
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: 6adf832971b236f7df42ff999d114372b1d97a1072899f4f5087e40e021928e9; retrieved 2026-09-18T14:56:42.926Z.