FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX93FA377 · Beech F33A

25 Jul 1993 · Baker, CA, United States

American Aeronautical Foundati Beech F33A · Accident: loss of control in flight en route

From Roosevelt Municipal Airport (74V) to Camarillo International Airport (CMA)

Report a problem

Event

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

Beech F33A

Aircraft type
Beechcraft 33
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
N3022W
Onboard fatalities
Unknown
Route
From Roosevelt Municipal Airport (74V), Roosevelt, UTTo Camarillo International Airport (CMA), Camarillo, CA
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
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

  • Reason for occurrence undetermined

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

NTSB narrative

THE PILOT AND PAX HAD ATTENDED A WEEKEND-LONG GATHERING, AND SOME PEOPLE PRESENT REPORTED EXPERIENCING VOMITING AND DIARRHEA - POSSIBLY DUE TO FOOD POISONING. THERE WERE NO REPORTS THAT THE PILOT OR HIS PAX DISPLAYED ANY SYMPTOMS PRIOR TO DEPARTURE. DURING THE FLIGHT, RADAR TRACKED AN UNIDENTIFIED VFR TRANSPONDER TARGET AT 8,500 FT MSL UNTIL IT DISAPPEARED NEAR THE CRASH SITE. THE WRECKAGE WAS FOUND 4/30/94 ABOUT 20 MI NE OF BAKER. EXAM OF THE WRECKAGE REVEALED THAT THE AIRPLANE HAD IMPACTED IN A HIGH-SPEED 75-DEG DESCENT. THE AIRPLANE HAD A THROW-OVER YOKE; NEITHER OF THE PASSENGERS WERE RATED PILOTS. NO ATC FACILITY REPORTED ANY CONTACT WITH THE PILOT AFTER HIS DEPARTURE. THE PILOT'S FAMILY REPORTED A FAMILY HISTORY OF EARLY HEART DISEASE. THE FAMILY ALSO REPORTED THAT THE PILOT HAD AN ELEVATED LEVEL OF CHOLESTEROL. THERE WAS NO EVIDENCE FOUND TO INDICATE A MECHANICAL MALFUNCTION OF THE AIRCRAFT OR ITS COMPONENTS. AN AIRMET WAS IN EFFECT AT THE TIME OF THE ACCIDENT ADVISING OCCASIONAL MODERATE TURBULENCE COULD BE EXPECTED BELOW 20,000 FT.

Probable cause

A LOSS OF CONTROL FOR UNDETERMINED REASON(S).

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX93FA377
Event ID
20001211X12938
Case number
LAX93FA377
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 1993-07-26.
  • API snapshot SHA-256: a0425a97b42e164b6b9daa72403e64cf290f1a74e1d68b9e99f82a9217d465ec; retrieved 2026-09-21T00:27:02.875Z.