FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA92LA173 · Piper PA-32R-300

4 Aug 1992 · Farmington, UT, United States

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

From Skypark Airport (BTF) to Sidney Municipal Airport Lloyd W Carr Field (SNY)

Report a problem

Event

NTSB case
SEA92LA173
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
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-32R-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
N7091C
Onboard fatalities
Unknown
Route
From Skypark Airport (BTF), Bountiful, UTTo Sidney Municipal Airport Lloyd W Carr Field (SNY), Sidney, NE
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 · climb to 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

  • Pilot in command › In-flight planning/decision, poor

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

NTSB narrative

THE PILOT OF THE PA-32R-300 ELECTED TO TURN INTO A BOX CANYON DURING HIS EN ROUTE CLIMB TO CRUISE. AT THE TIME HE TURNED INTO THE CANYON, THE PILOT FELT THAT THE RATE OF CLIMB WOULD ASSURE CLEARANCE OF THE RIDGE AT THE END OF THE CANYON. AFTER ENTERING THE CANYON THE AIRCRAFT ENCOUNTERED AN AREA OF DOWNDRAFTS. THE DESCENDING AIR REDUCED THE RATE OF CLIMB TO AN EXTENT THAT WOULD NOT ALLOW THE AIRCRAFT TO OUTCLIMB THE RISING TERRAIN. BY THIS TIME THE PILOT FELT THAT, BECAUSE OF THE NARROWNESS OF THE CANYON, HE COULD NOT SUCCESSFULLY REVERSE COURSE. HE THEREFORE ELECTED TO CONTINUE UP THE CANYON, WHERE HE EVENTUALLY FLEW THE AIRCRAFT THROUGH A CONTROLLED IMPACT WITH THE TERRAIN.

Probable cause

THE PILOT'S POOR INFLIGHT DECISION. FACTORS INCLUDE DOWNDRAFTS AND A BOX CANYON.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA92LA173
Event ID
20001211X15531
Case number
SEA92LA173
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: 026c8487327d44bafd50991e2eb231d34e07512c51683dd29a335a60c051ffed; retrieved 2026-09-21T23:11:10.049Z.