FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA84FA030 · Piper PA-34-220T

30 Dec 1983 · Pocatello, ID, United States

Piper PA-34-220T · Accident: loss of control in flight on approach

From Salt Lake City International Airport (SLC) to an unrecorded destination

Report a problem

Event

NTSB case
SEA84FA030
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
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-34-220T

Aircraft type
Piper PA-34
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
N8362L
Operator
Unknown
Onboard fatalities
Unknown
Route
From Salt Lake City International Airport (SLC), Salt Lake City, UTTo not recorded
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
Approach · IFR missed approach
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 in flight
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 › Aircraft handling, not maintained
  • Pilot in command › Spatial disorientation

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

NTSB narrative

DURING ARRIVAL, THE PLT INITIATED AN ILS APCH TO RWY 2L. AT THAT TIME, THE WX IN PART WAS 700 FT SCATTERED TO BROKEN, 1300 TO 1500 FT OVERCAST,VISIBILITY 1 TO 1 1/2 MI WITH LIGHT SNOW & FOG. ABOUT 3 MIN AFTER CALLING INBOUND ON THE APCH, THE PLT INITIATED A MISSED APCH. HE WAS CLEARED BACK TO THE OUTER MARKER & WAS INSTRUCTED TO MAINTAIN 7000 FT & CONTACT DEPARTURE CONTROL. AFTER CHANGING RADIO FREQUENCIES THE PLT WAS CLEARED FOR ANOTHER ILS APCH, WHICH HE ACKNOWLEDGED. SHORTLY AFTER THAT, THE ACFT CRASHED APRX 1 1/2 MI NORTHWEST OF RWY 21. THERE WERE NO KNOWN WITNESSES. TOWER PERSONNEL STATED THAT THEY SAW THE ACFT BRIEFLY DURING THE MISSED APCH, AND AT THAT TIME, NOTHING UNUSUAL WAS NOTED CONCERNING THE ACFT'S FTL ATTITUDE OR LOCATION. AN EXAM OF THE CRASH SITE REVEALED THAT THE ACFT HAD CRASHED INTO SNOW COVERED TERAIN WHILE ON A NORTHWESTERLY HEADING, IN A NEAR WINGS LEVEL, STEEP DESCENT. NO EVIDENCE OF A PREIMPACT/MECHANICAL MALFUNTION OR FAILURE WAS FOUND.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record SEA84FA030
Event ID
20001214X45411
Case number
SEA84FA030
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: c827d5c56b83677f75d3edeab95fcba67ac60c879fc1f70bdcc31f70518e9d13; retrieved 2026-09-18T14:29:14.331Z.