FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Grant Aviation Flight 3321

2 Mar 1996 · Nome, AK, United States

Piper PA-32-301 · Accident: in flight encounter with weather en route

From Stro's Airport (AK54) to Nome Airport (OME)

Report a problem

Event

NTSB case
ANC96LA027
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
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
Instrument Meteorological Cond

Piper PA-32-301

Aircraft type
Piper PA-32
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
N8374T
Onboard fatalities
Unknown
Route
From Stro's Airport (AK54), TELLER, AKTo Nome Airport (OME), 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
Substantial

Cause areas

  • Pilot in command › Altitude/clearance, not maintained
  • Pilot in command › VFR flight into imc, continued

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

NTSB narrative

The pilot and passenger departed a remote airstrip on a commuter flight in marginal VFR conditions. The pilot reported that he was crossing low hills about 1,000 feet AGL and encountered turbulence and a possible loss of engine power. The engine did not run rough but the airplane continued to descend until impact. The airplane struck a snow covered hill about 15 miles west of the destination airport. The passenger reported that the majority of the flight was conducted with limited downward visibility. Just prior to impact, the passenger reported white-out conditions, and no terrain was visible. The airplane received damage to the landing gear, fuselage, and wings. The pilot and passenger were rescued about 4 hours after the accident. The destination airport reported weather conditions that included a 1,300 feet overcast sky and a visibility of 10 miles in light snow. The operator reported no engine malfunction.

Probable cause

the pilot's continued VFR flight into instrument meteorological conditions and his failure to maintain adequate altitude/clearance from terrain. Low ceilings and snow covered terrain were factors in the accident.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC96LA027
Event ID
20001208X05337
Case number
ANC96LA027
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
  • 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: cfddcfa323ae7d6aaef8992cabfab28f50993f56cb88c966368d70fcfafc515c; retrieved 2026-09-18T17:53:01.300Z.
  • The NTSB's operator name is blank for N8374T; the operator shown is the name the NTSB's other records give its FAA operator code, ENHA.