FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX91LA003 · Cessna 210

6 Oct 1990 · Riverside, CA, United States

Cessna 210 · Accident: in flight collision with terrain/water

From Flabob Airport (RIR) to an unrecorded destination

Report a problem

Event

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

Cessna 210

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
N9466T
Operator
Unknown
Onboard fatalities
Unknown
Route
From Flabob Airport (RIR), Riverside, CATo not recorded
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
Unknown
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
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
  • Pilot in command › Impairment(drugs)

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

NTSB narrative

THE PILOT TOOK THE AIRPLANE WITHOUT PERMISSION OF THE OWNER AND FLEW IT FROM AN AIRPORT NEAR HIS RESIDENCE. AFTER ABOUT 25 MINUTES, THE AIRPLANE COLLIDED WITH THE WEST SIDE OF MT RUBIDOUX, WHICH WAS ABOUT ONE MILE EAST-SOUTHEAST OF THE AIRPORT. AN EXAM OF THE CRASH SITE REVEALED EVIDENCE THAT THE AIRPLANE IMPACTED THE RISING TERRAIN WHILE IN A NEAR LEVEL FLIGHT ATTITUDE. ACQUAINTANCES REPORTED THE PILOT WAS FAMILIAR WITH THE AREA, HAVING FLOWN FROM THE AIRPORT FOR OVER 10 YEARS. REPORTEDLY, HE HAD RECENTLY BECOME UNEMPLOYED AND WAS DEPRESSED. TOXOCOLOGY RESULTS INDICATED THE PRESENCE OF COCAINE AND BENZOYLECGONINE IN THE PILOT'S BLOOD AT LEVELS OF 340 AND 1330 NG/ML, RESPECTIVELY.

Probable cause

IMPAIRMENT OF THE PILOT FROM USE OF DRUGS (COCAINE), AND HIS FAILURE TO MAINTAIN CLEARANCE (OR ALTITUDE) FROM THE MOUNTAIN. FACTORS RELATED TO THE ACCIDENT WERE: DARKNESS AND THE PILOT'S PSYCHOLOGICAL CONDTION (DEPRESSION).

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX91LA003
Event ID
20001212X24483
Case number
LAX91LA003
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: e44906e3639431ddb5ce868ea5a59b9d8e1c5abfe4cb9ed618b5f6ef63d29126; retrieved 2026-09-21T02:07:31.361Z.