FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA85FA203 · Piper PA-32-300

27 Aug 1985 · BRIDGE, ID, United States

Piper PA-32-300 · Accident: in flight collision with terrain/water en route

From Friedman Memorial Airport (SUN) to Salt Lake City International Airport (SLC)

Report a problem

Event

NTSB case
SEA85FA203
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
Visual Meteorological Cond

Piper PA-32-300

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
N2282M
Operator
Unknown
Onboard fatalities
Unknown
Route
From Friedman Memorial Airport (SUN), Sun Valley, IDTo Salt Lake City International Airport (SLC), Salt Lake City, UT
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 collision with terrain/water
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

  • Reason for occurrence undetermined

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

NTSB narrative

AT 1445 MDT, THE 60 YR OLD PLT DEPARTED ON A ROUTINE, VFR, REPOSITIONING FLT WHICH HE HAD FREQUENTLY FLOWN BEFORE. AFTER TAKEOFF, HE LEVELED THE ACFT AT 9500 FT ON A DIRECT COURSE TOWARD THE DESTINATION. WHILE EN ROUTE AT ABOUT 1515, THE ACFT BEGAN A SHALLOW OSCILLATORY DESCENT WHEN IT WAS ABOUT 28 MI FROM THE BLACK MTN RANGE. SUBSEQUENTLY, THE ACFT COLLIDED WITH A RIDGE ABOUT 1 MI FROM BLACK MTN PEAK WHILE IN A WINGS LEVEL ATTITUDE AT AN ELEVATION OF ABOUT 8500 FT. THE WX AT THAT TIME WAS VFR WITH ONLY SCATTERED CLOUDS & 15 MI VISIBILITY. AN EXAM OF THE WRECKAGE REVEALED NO EVIDENCE OF A PREIMPACT PART FAILURE OR MALFUNCTION. THE ACFT WAS EQUIPPED WITH AN ARNAV-20 LORAN UNIT & A CENTURY IIB AUTOPILOT.THE AUTOPILOT HAD NO ALT HOLD FUNCTION, BUT ITS MODE SELECTOR WAS FOUND POSITIONED TO THE 'HDG' POSITION. ALSO, THE ELEVATOR TRIM WAS FOUND NEAR THE NEUTRAL POSITION. PATHOLOGICAL & TOXICOLOGICAL EXAMS REVEALED NO INDICATION OF A PHYSIOLOGICAL PROBLEM. THE POSSIBILITY OF THE PLT FALLING ASLEEP OR BECOMING INCAPACITATED COULD NOT BE DETERMINED.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record SEA85FA203
Event ID
20001214X37643
Case number
SEA85FA203
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: 3d5e55d5d52d2e53fc6e7639ab74caf211cbb89991189e7eca766b8c2d12d3b3; retrieved 2026-09-21T04:52:10.790Z.