LAX91FA133 · Cessna 320D
Cessna 320D · Accident: in flight encounter with weather en route
From LHU · LAKE HAVASU CTY, AZ to Seattle–Tacoma International Airport (SEA)
Event
- NTSB case
- LAX91FA133
- 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
- Instrument Meteorological Cond
Cessna 320D
- Aircraft type
- Cessna 320
- 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
- N3302Q
- Operator
- John P. Culhane · private individual
- Onboard fatalities
- Unknown
- Route
- From LHU · LAKE HAVASU CTY, AZTo Seattle–Tacoma International Airport (SEA), Seattle, WA
- 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
- In flight encounter with weather
- 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
- Visual flight rules (VFR) flight into instrument meteorological conditions (IMC)
- 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 › VFR flight into imc, continued
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT HAD BEEN IN THE PHOENIX AREA FOR REPAIRS & FOR INSTN OF AVIONICS, AND WAS ON A TRIP TO ANCHORAGE VIA SEATTLE. BFR DEPG LAKE HAVASU CITY, THE PLT RCVD A WX BRIEFING, BUT DID NOT FILE A FLT PLAN. THERE WERE FLT PRCTNS FOR MODERATE TURBC BELOW 16,000', MODERATE ICING IN CLDS & MTN OBSCN. THE PLT REQD & RCVD TFC ADZY FROM EDWARDS APCH CTL WHILE TRANSITING THE PALMDALE ATA. DURING THAT TIME, HE REQD & RCVD THE BAKERSFIELD WX. AT ABOUT 1007 PST, RADAR SERVICE WAS TERMINATED. ABOUT 1 MIN LATER, RADAR CTC WAS LOST AS THE ACFT WAS CRUISING AT 4500' MSL. SUBSEQUENTLY, THE ACFT CRASHED INTO RISING TRRN IN THE TEHACHAPI MTS, ABOUT 15 MI FROM WHERE RADAR CTC WAS LOST. IMPACT OCCURRED ABOUT 75' BELOW THE TOP OF A RIDGE AT AN ELEV OF ABOUT 6000'. AN EXAM OF THE CRASH SITE REVEALED EVIDENCE THE ACFT HAD CRASHED IN A WINGS LEVEL ATTITUDE. NO PREIMPACT PART FAILURE OR MALFUNCTION OF THE ACFT OR ENG WAS FND.
Probable cause
VFR FLIGHT INTO INSTRUMENT METEOROLOGICAL CONDITIONS (IMC) BY THE PILOT, AND HIS FAILURE TO MAINTAIN SUFFICIENT ALTITUDE/CLEARANCE FROM MOUNTAINOUS TERRAIN. FACTORS RELATED TO THE ACCIDENT WERE: THE TERRAIN AND WEATHER CONDITIONS.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX91FA133
- Event ID
- 20001212X16615
- Case number
- LAX91FA133
- 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: d71b222283a266f8dfbec6f0d0cb3f1ae27a3ec8c542767ce678a448099bfd85; retrieved 2026-09-21T01:55:11.035Z.