FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA99FA152 · Cessna T210M

29 Aug 1999 · MARCOLA, OR, United States

Cessna T210M · Accident: in flight collision with object en route

From Mesa Del Rey Airport (KIC) to 3S2 · AURORA STATE, OR

Report a problem

Event

NTSB case
SEA99FA152
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
3 · 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
Unknown

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
N747CC
Operator
William R. Crinklaw · private individual
Onboard fatalities
Unknown
Route
From Mesa Del Rey Airport (KIC), King City, CATo 3S2 · AURORA STATE, 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
En route · descent
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
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 › Clearance, not maintained

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

NTSB narrative

The student pilot, whom records show did not make use of FAA or DUATS weather briefing services prior to departure, encountered deteriorating weather while en route from King City, California, to Aurora, Oregon. Upon encountering the weather, the pilot initiated a descent through 'multiple cloud layers' in order to attempt to continue on to his planned destination. Near the last part of the descent, while entering an area of mountainous/hilly terrain, the aircraft collided with trees on a densely forested hillside. Witness reported clouds, low ceilings, and rain showers in the area at the time of the accident.

Probable cause

The pilot's failure to maintain clearance from the terrain while descending in an area of deteriorating weather. Factors include mountainous terrain, clouds, low ceilings, the pilot's inadequate preflight weather analysis, and his improper decision to attempt to continue on to his planned destination after encountering deteriorating weather.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA99FA152
Event ID
20001212X19644
Case number
SEA99FA152
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: 22f4e79f800637807ecfe55809fd62a7be8561f675d2a3a293e694e3c7baeb08; retrieved 2026-09-20T21:50:56.634Z.