SEA96LA169 · Cessna 172M
Cessna 172M · Accident: in flight collision with object during landing
From Kooskia Municipal Airport (S82) to Pullman-Moscow Regional Airport (PUW)
Event
- NTSB case
- SEA96LA169
- 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
Cessna 172M
- Aircraft type
- Cessna 172
- 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
- N61842
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Kooskia Municipal Airport (S82), Kooskia, IDTo Pullman-Moscow Regional Airport (PUW), Pullman, WA
- 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
- Landing · emergency landing
- 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 object
- 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
- Tree(s)
- 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 › In-flight planning/decision, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
After takeoff, the pilot elected to turn up a valley which would provide the most direct route to his destination. Once committed to that route of flight, he realized that the aircraft could not out-climb the rising terrain. He attempted to land the aircraft at the point where its climb gradient intersected the terrain, but it impacted trees during his attempted emergency landing. Later calculations determined the density altitude to be approximately 5,000 feet.
Probable cause
the pilot's improper in-flight decision to turn up a canyon, which the aircraft was unable to out-climb. Factors relating to the accident were: high ambient temperature, high density altitude, blind/box canyon, and trees in the area where the aircraft's climb profile caused it to come in contact with the raising terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA96LA169
- Event ID
- 20001208X06383
- Case number
- SEA96LA169
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1996-07-26.
- API snapshot SHA-256: c35af932f3c3b38c7c778332fb0c9c6c5c260c11af6759f05b58c5631a7fe3b3; retrieved 2026-09-21T21:38:39.709Z.