FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX89FA334 · Cessna 152

30 Sept 1989 · Lancaster, CA, United States

West Coast Air Center Cessna 152 · Accident: in flight collision with terrain/water en route

From General William J Fox Airfield (WJF) to an unrecorded destination

Report a problem

Event

NTSB case
LAX89FA334
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
2 · 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 152

Aircraft type
Cessna 152
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
N6422M
Onboard fatalities
Unknown
Route
From General William J Fox Airfield (WJF)To 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
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 collision with terrain/water
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 › VFR flight into imc, attempted

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

NTSB narrative

THE PILOT AND HIS PASSENGER TOOK OFF FOR A MAINTENANCE TEST FLIGHT TO CONDUCT A VOR RECEIVER CHECK. HIS CHECK POINT WAS OVER THE AIRPORT OF DEPARTURE. THE FLIGHT FAILED TO RETURN AND WAS REPORTED MISSING SIX HOURS AFTER ITS TAKEOFF. THE WRECKAGE WAS FOUND EIGHTEEN HOURS LATER, IMPACTED IN THE SIDE OF A MOUNTAIN APPROXIMATELY 18 MILES NORTHWEST OF THE DEPARTURE AIRPORT. WEATHER REPORTS FOR THE TIME FRAME OF THE ACCIDENT NOTED THAT THE TOPS OF THE MOUNTAINS WERE OBSCURED BY CLOUDS.

Probable cause

THE PILOT'S DECISION TO ENTER INTO IMC WHILE FLYING UNDER VFR. FACTORS CONTRIBUTING TO ACCIDENT WERE: LOW CEILINGS, POOR PLANNING AND DECISIONS, FAILURE TO OBTAIN A PREFLIGHT BRIEFING AND NOT PERFORMING A WEATHER EVALUATION.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX89FA334
Event ID
20001213X29406
Case number
LAX89FA334
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: a986f23152c1464335bc42288fd897175b375cebe47141c29f19da9ef36b51ac; retrieved 2026-09-21T03:07:52.036Z.