LAX90FA211 · Beech 35-33
Alameda Flying Club Beech 35-33 · Accident: in flight collision with terrain/water
From Oakland San Francisco Bay Airport (OAK) to Camarillo International Airport (CMA)
Event
- NTSB case
- LAX90FA211
- 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
Beech 35-33
- Aircraft type
- Beechcraft 35
- 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
- N996T
- Operator
- Alameda Flying Club
- Onboard fatalities
- Unknown
- Route
- From Oakland San Francisco Bay Airport (OAK), Oakland, CATo 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
- 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
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT RECEIVED A PRELFIGHT WEATHER BRIEFING WHICH INCLUDED A FORECAST FOR VISUAL METEOROLOGICAL CONDITIONS ALONG THE PROPOSED ROUTE OF FLIGHT. HE TOOK OFF ON A CROSS-COUNTRY FLIGHT UNDER VISUAL FLIGHT RULES WITHOUT FILING A FLIGHT PLAN. ABOUT 1-1/2 HRS AFTER THE PLANE TOOK OFF, A RANCHER FOUND ITS WRECKAGE BURNING IN AN OUTLYING/LEVEL PASTURE, AFTER A NEIGHBOR ADVISED HIM OF SMOKE EMANATING FROM THE PASTURE. THE AIRCRAFT IMPACTED THE GROUND IN AN UPRIGHT ATTITUDE WITH THE FLAPS AND LANDING GEAR RETRACTED. THE WRECKAGE BOUNCED, SLID AND TUMBLED ABOUT 447 FEET BEFORE COMING TO REST. IMPACT OCCURRED IN A DIRECTION THAT WAS PERPENDICULAR TO THE ROUTE OF FLIGHT. NO PREIMPACT PART FAILURE OR MALFUNCTION OF THE AIRCRAFT WAS FOUND. THE OWNER SAID THE PILOT HAD OVERSTRESSED THE AIRCRAFT ON A PREVIOUS FLIGHT, BUT NO RELATIONSHIP WAS VERIFIED BETWEEN THAT EVENT AND THE ACCIDENT.
Probable cause
UNDETERMINED.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX90FA211
- Event ID
- 20001212X23442
- Case number
- LAX90FA211
- 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: ff307663d7ebeca160dca2c4a6ee98df2fae2dc4243afa08c56d5fb6a1cbac4e; retrieved 2026-09-21T02:36:34.626Z.