LAX96FA067 · Cessna 340A
Cessna 340A · Accident: in flight collision with object on approach
From Big Bear City Airport (L35) to Brackett Field (POC)
Event
- NTSB case
- LAX96FA067
- 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
- Instrument Meteorological Cond
Cessna 340A
- Aircraft type
- Cessna 340
- 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
- N37324
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Big Bear City Airport (L35), Big Bear Lake, CATo Brackett Field (POC), La Verne, 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
- Approach · IFR missed approach
- 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
- 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
- Tree(s)
- 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 › IFR procedure, not followed
- Pilot in command › Impairment(drugs)
- Pilot in command › Planning/decision, improper
- Pilot in command › Proper altitude, not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot departed his home base in VFR conditions without filing a flight plan and did not request or receive a preflight or en route weather briefing from the FAA. While en route, he contacted Southern California TRACON (SOCAL) and requested an ILS runway 26 approach to the destination airport. SOCAL cleared the pilot for the approach and to change to an advisory frequency. There was no current weather report available at the airport because the tower was closed, but another pilot who was on the same frequency stated that the airport weather was 'zero zero.' (An automated weather observation system at the airport recorded 'zero zero' conditions near the time of the accident.) Ground witnesses heard the airplane as the pilot began a missed approach. However, the airplane collided with trees and a snack bar building about 1/4 mile northwest of the departure end of the runway. Impact occurred as the airplane was in a right turn through a heading of 345 degrees, which was the opposite direction of turn for the missed approach procedure. Toxicology test of the pilot's blood showed 1.518 mcg/ml Fenfluramine and 0.678 mcg/ml Phentermine; these are appetite suppressant drugs that are chemically related to amphetamines and have a high incidence of abuse. Neither of these drugs was approved by the FAA for use while flying aircraft. The amount of Fenfluramine in the pilot's blood was above a normal level for control of appetite.
Probable cause
the pilot's impairment of judgment and performance due to drugs, his resultant improper planning/decision, his failure to follow proper IFR procedures, and his failure to maintain proper altitude during a missed approach. Factors relating to the accident were: the pilot's inadequate weather evaluation, and the adverse weather condition (below landing minimums).
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX96FA067
- Event ID
- 20001207X05016
- Case number
- LAX96FA067
- 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: 34a59ad25ebbd61458f0aec2640bec4bdb6c91d68909ad76637bee988b4035e7; retrieved 2026-09-20T23:30:08.650Z.