FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA84FA071 · Piper PA-28RT-201T PA-28RT-20

15 Mar 1984 · HUMPHREY, ID, United States

Piper PA-28RT-201T PA-28RT-20 · Accident: in flight encounter with weather en route

From Hyak Airbase (4U9) to Idaho Falls Regional Airport (IDA)

Report a problem

Event

NTSB case
SEA84FA071
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
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
General aviation
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-28RT-201T PA-28RT-20

Aircraft type
Piper PA-28
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
N29033
Operator
Unknown
Onboard fatalities
Unknown
Route
From Hyak Airbase (4U9), DILL, MTTo Idaho Falls Regional Airport (IDA), Idaho Falls, ID
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 91: General Aviation
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 › In-flight planning/decision, improper
  • Pilot in command › Proper altitude, not maintained
  • Pilot in command › VFR flight into imc, inadvertent

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

NTSB narrative

WHILE ON A X-COUNTRY FLT, THE ACFT ENTERED AN AREA OF RISING TERRAIN & BLOWING SNOW & THE PLT INITIATED A TURN TO REVERSE DIRECTION. DURING THE TURN, HE ENCOUNTERED REDUCED VISIBILITY & THE ACFT COLLIDED WITH THE TOP OF A KNOLL ON SNOW COVERED ROLLING TERRAIN. THE ACFT TRAVELED ABOUT 400 FT AFTER IMPACT, SHEDDING THE ENG & WINGS & CAME TO REST ON ITS RIGHT SIDE.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record SEA84FA071
Event ID
20001214X39173
Case number
SEA84FA071
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. 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: bd68f2bf837d5a9bb4f71f76e53cb94f77f8f45348ffef0f6f2d7232a232c4bb; retrieved 2026-09-21T05:36:45.565Z.