FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA84FA223 · Cessna T210M

7 Sept 1984 · SKAMANIA, WA, United States

Cessna T210M · Accident: in flight encounter with weather en route

From Eastern Oregon Regional Airport at Pendleton (PDT) to 60S · Vancouver, WA

Report a problem

Event

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

Cessna T210M

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
N191WB
Operator
Unknown
Onboard fatalities
Unknown
Route
From Eastern Oregon Regional Airport at Pendleton (PDT), Pendleton, ORTo 60S · Vancouver, 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
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 encounter with weather
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 › Aircraft handling, not maintained
  • Pilot in command › Design stress limits of aircraft, exceeded
  • Pilot in command › Spatial disorientation
  • Pilot in command › VFR flight into imc, attempted

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

NTSB narrative

A WITNESS, LOCATED 3 MI SE OF THE ACCIDENT SITE, REPORTED HEARING THE ACFT 'REV UP TO A SCREAM FOLLOWED BY A CRASH THAT SOUNDED LIKE A MINIATURE SONIC BOOM.' THE ACFT CONTACTED THE TERRAIN IN AN UNCONTROLLEDD DESCENT AT AN ELEV OF 2100 FT MSL. INSPECTION OF THE WRECKAGE REVEALED THE HORIZONTAL STABILIZER AND LEFT WING HAD SEPARATED FROM THE ACFT. THE SEPARATED OUTBOARD SECTION OF THE LEFT WING WAS NOT LOCATED. METALLURGICAL EXAM OF THE REMAINING PORTION OF THE LEFT WING SPAR DISCLOSED A FAILURE 'TYPICAL OF OVERSTRESS.' THE NEAREST WX REPORTING STATION, TROUTDALE, OR, LOCATED 13 NM SW OF THE ACCIDENT LOCATION AT AN ELEV OF 30 FT MSL HAD A 1845 PDT OBSERVATION OF: 2500 FT SCATTERED, E4000 FT OVERCAST WITH 20 SM VIVIBILITY.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record SEA84FA223
Event ID
20001214X41226
Case number
SEA84FA223
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 1984-09-08.
  • API snapshot SHA-256: 3499216b482acac2a5652c053135b9f76c8694283fd38ca184c69b8ac1b65196; retrieved 2026-09-21T05:21:11.985Z.