FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX05FA023 · Cessna 182Q

31 Oct 2004 · Lebec, CA, United States

Cessna 182Q · Accident: in flight encounter with weather en route

From General William J Fox Airfield (WJF) to 308 · Coalinga, CA

Report a problem

Event

NTSB case
LAX05FA023
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
4 · all aircraft and ground
Ground fatalities
Unknown
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 182Q

Aircraft type
Cessna 182
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
N95902
Operator
Unknown
Onboard fatalities
Unknown
Route
From General William J Fox Airfield (WJF), Lancaster, CATo 308 · Coalinga, 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
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 › In-flight planning/decision, improper
  • Pilot in command › VFR flight into imc, continued

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

While traversing a mountain range between two valleys, the aircraft collided with mountainous terrain after a likely encounter with clouds, moderate turbulence, and up and down drafts in the 500- to 1,000-foot-per-minute range. Examination of the wreckage and the accident site showed that the airplane collided with mountainous terrain while in a wings level cruise flight attitude. The autopilot switch was found in the ON position. The noninstrument rated private pilot departed in VFR conditions with three passengers for a 134-mile trip to celebrate one passenger's birthday at a fly-in restaurant destination. There were no records of the pilot having received weather briefings from any Federal Aviation Administration (FAA) facilities. Recorded radar data showed that instead of flying a direct route the airplane meandered towards a mountain top VOR navigational aid and eventually was about 18 miles off a direct course between the departure and destination airports. About 30 minutes into the flight, the airplane had reversed course and was headed back towards the open desert departure area when radar contact was lost. A moderate north-south surface pressure gradient produced strong, gusty northerly low-level winds over the higher elevations of the mountain range. Observations from satellite imagery indicated that mostly clear skies were present from the departure airport until the accident airplane reached the vicinity of the accident area. A weather satellite visible image showed that cloud cover from the northwest did cover the accident site around the estimated time of the accident though there were clear areas south and west of the VOR. Cloud bases reported around the VOR ranged from on the surface to less than 1,000 feet agl, with tops generally 8,000-10,000 feet mean sea level (msl) in the area. No in-flight advisories (SIGMET or AIRMET) were valid for the accident location when the accident airplane departed. However, AIRMET TANGO was updated at 1335, to include a forecast of occasional moderate turbulence below 12,000 feet over coastal mountain areas. According to pilot reports from very near the accident area around the time of the crash, moderate turbulence and up and down drafts were being experienced from 500 feet to 1,200 feet per minute. There are two small lakes in the vicinity of the VOR. Overflying one lake on the accident flight's last radar observed heading would take the airplane over low terrain on a route back toward the departure airport, whereas overflying the second lake on the last observed heading would take the airplane toward mountainous terrain that rises to 5,430 feet msl within 2 miles, and is the location of the accident site.

Probable cause

the pilot's inadequate in-flight planning/decision by his VFR flight into IMC, and his failure to maintain terrain clearance. Contributing factors were mountainous terrain, low ceilings, and turbulence.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX05FA023
Event ID
20041103X01749
Case number
LAX05FA023
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, coordinates. 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: 98ce67eeb2c2a626ca7dc566439512c9397b399b10e26fff335112d4ee7094d6; retrieved 2026-09-20T18:13:50.333Z.