SEA97FA027 · Cessna P210N
Cessna P210N · Accident: in flight collision with terrain/water while maneuvering
From Roseburg Regional Airport (RBG) to Portland Troutdale Airport (TTD)
Event
- NTSB case
- SEA97FA027
- 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
- Instrument Meteorological Cond
Cessna P210N
- Aircraft type
- Cessna 210
- 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
- N7823K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Roseburg Regional Airport (RBG), Roseburg, ORTo Portland Troutdale Airport (TTD), Troutdale, 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
- Maneuvering
- 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
- 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
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
- 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 › VFR flight into imc, attempted
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight was initially conducted on an instrument flight rules (IFR) flight plan above an overcast layer of clouds. As the pilot neared the destination airport, he was told by air traffic control (ATC) that there would be a delay in issuing the pilot a clearance for an approach due to other traffic in the area. The pilot elected not to wait. He requested and received vectors to an area of known visual conditions, and then reported that he saw a 'big hole' in the clouds. He canceled his IFR clearance and told ATC that he was going to initiate a circling descent to get underneath the clouds. The airplane dropped below ATC's radar coverage and the pilot was cleared to the destination via his own navigation. About 7 minutes later, the airplane impacted rapidly rising terrain that was shrouded in thick fog.
Probable cause
The pilot's attempt to conduct visual flight into instrument meteorological conditions. A factor contributing to the accident was the presence of thick fog.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA97FA027
- Event ID
- 20001208X07113
- Case number
- SEA97FA027
- 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: 9cbfc7739feb441f8ba7aa08c4f0529879ab703dcbc1222b2afa86c532989007; retrieved 2026-09-20T23:07:29.533Z.