FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Hageland Aviation Services Flight 502

10 Apr 1997 · Wainwright, AK, United States

Cessna 208B · Accident: in flight collision with terrain/water while maneuvering

From Wiley Post Will Rogers Memorial Airport (BRW) to Wainwright Airport (AWI)

Report a problem

Event

NTSB case
ANC97MA161
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
5 · all aircraft and ground
Ground fatalities
0
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
Unknown

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
N408GV
Onboard fatalities
Unknown
Route
From Wiley Post Will Rogers Memorial Airport (BRW), BARROW, AKTo Wainwright Airport (AWI), 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
Maneuvering
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 collision with terrain/water
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 › Altitude/clearance, not maintained
  • Pilot in command › VFR flight into imc, intentional

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

NTSB narrative

The pilot had contacted the FSS 11 times on the day of the accident to obtain weather briefings. The conditions were below VFR minimums, which were required to conduct the passenger-carrying commercial flight in a single-engine airplane. The conditions later improved and the pilot departed under a special VFR clearance. The pilot performed two approaches at the destination airport in IMC that were consistent with the two GPS approaches that were available there. Weather data and witnesses indicate that daylight conditions, low clouds and poor visibility prevailed, with cloud tops at 1,000 feet. After the second approach, the pilot radioed that he was heading back to the departure airport because he could not see the airport. No distress calls or unusual engine noises were heard. The airplane subsequently flew north of the airport and away from the departure airport at an altitude beneath the minimum radar coverage of 2,200 feet. It impacted the frozen Arctic Ocean in a right bank and at a 60-degree nose-down attitude about three miles away from the location of the pilot's last radio transmission. An examination of the airplane (before it sank through cracking ice) revealed no pre-impact mechanical malfunctions. An examination of the propeller revealed that it was under a power setting consistent with a maneuvering airspeed at the time of impact. An examination of the autopilot annunciator filament revealed that the autopilot was not engaged at impact. The airplane was nearly full of fuel and over its published maximum gross weight at impact. Small pieces of clear ice, about 1/4-inch thick, were found on portions of the tail surfaces. Interviews with operator employees and the pilot's wife revealed that the pilot may have felt pressure from himself and passengers to complete the flight.

Probable cause

The pilot's intentional VFR flight into instrument meteorological conditions and his failure to maintain altitude/clearance from terrain. Factors contributing to the accident were the weather conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC97MA161
Event ID
20001208X07657
Case number
ANC97MA161
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1997-04-11.
  • API snapshot SHA-256: 9c13f6b080a2a1b22dfee2884095935acca4fa719f712607bfeaf5f3274852aa; retrieved 2026-09-18T13:29:49.713Z.