SEA87FA185 · Cessna TR182
Cessna TR182 · Accident: loss of control in flight on approach
From 1S4 · Scappoose, OR to S47 · Tillamook, OR
Event
- NTSB case
- SEA87FA185
- 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
- 2 · 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
Cessna TR182
- Aircraft type
- Cessna 182
- 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
- N9484R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 1S4 · Scappoose, ORTo S47 · Tillamook, OR
- 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
- Approach · IFR initial 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 control, not maintained
- Pilot in command › Spatial disorientation
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DRG ARRIVAL, THE PLT WAS CLEARED FOR AN NDB-A APCH & RECEIVED APPROVAL TO CHANGE TO THE LOCAL ADZY FREQ. AFTER THAT, THERE WAS NO FURTHER RADIO COMM WITH THE ACFT. RADAR DATA SHOWED THE ACFT CROSSED OVER THE INITIAL APCH FIX (IAF) & BEGAN A RGT OUTBOUND TURN TOWARD THE PROCEDURE TURN AREA. RADAR CONTACT WAS LOST ABT 3 MI WEST OF THE IAF. WHEN THE ACFT DID NOT ARRIVE, A SEARCH WAS INITIATED. IT WAS FND THE NEXT DAY WHERE IT HAD CRASHED IN MOUNTAINOUS TERRAIN AT AN ELEV OF ABT 1100'. IMPACT OCCURRED IN A STEEP NOSE DOWN, LEFT WING DOWN ATTITUDE. NO PREIMPACT PART FAILURE/MAL- FUNCTION OF THE ACFT OR ENG WAS FND. PERSONNEL AT THE ARPT (ELEV 35') ESTD THE WX WAS ABOUT 1000' OVERCAST, 5 MI VIS WITH LIGHT RAIN & FOG. A HELICOPTER PLT, WHO WAS SEARCHING FOR THE DOWNED ACFT, RPRTD THE MTNS & HILLS IN THE AREA WERE OBSCURED BY CLOUDS. HE WAS UNABLE TO REACH THE AREA OF THE CRASH SITE ON THE DAY OF THE ACDNT DUE TO RAIN & FOG.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record SEA87FA185
- Event ID
- 20001213X32207
- Case number
- SEA87FA185
- 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: dd1fa6adfa7ddc516dfeefa012cd4a47026774afedf5b921f0ccf1eb4d63fa02; retrieved 2026-09-21T03:59:16.904Z.