FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX99FA078 · Cessna 182P

19 Jan 1999 · Danville, CA, United States

Cessna 182P · Accident: in flight collision with terrain/water en route

From Livermore Municipal Airport (LVK) to Sacramento Executive Airport (SAC)

Report a problem

Event

NTSB case
LAX99FA078
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

Cessna 182P

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
N8579M
Operator
Unknown
Onboard fatalities
Unknown
Route
From Livermore Municipal Airport (LVK), Livermore, CATo Sacramento Executive Airport (SAC), Sacramento, 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 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 › Flight into adverse weather, attempted
  • Pilot in command › VFR flight into imc, continued
  • Pilot in command › Weather forecast, disregarded

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

NTSB narrative

The pilot received a preflight weather briefing and filed a VFR flight plan prior to departing Sacramento, California. During the briefing, the pilot was advised of forecast IFR conditions, with ceilings occasionally less than 1,000 feet and 3 miles visibility. Airmets advised mountain obscuration with scattered moderate to heavy rain. The FSS briefer concluded that after 1900-2000, the weather was going to reduce conditions to marginal VFR flight conditions. When the pilot opened his VFR flight plan by radio the briefer again asked him if he had the airmet for mountain obscuration, IFR conditions, and current information for the route. The pilot said yes he did and the briefer concluded by telling the pilot that VFR flight was not recommended. After the pilot arrived at Livermore airport he was asked by the local controller if he had a clearance on file or if he'd like to file one before he departed Livermore, and the pilot declined. The accident site was located between the elevation of 1,900 to 2,000 feet msl on a route consistent with a downwind departure from Livermore. A weather study by the Safety Board found that the airplane most likely experienced light to moderate rain after takeoff, with the airplane encountering heavy to very heavy rain near the accident site. Witnesses who were in the vicinity of the accident location confirmed that it was raining heavily near the accident timeframe.

Probable cause

The pilot's disregard for the preflight weather briefing, and his intentional continuation into adverse weather conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX99FA078
Event ID
20001204X00069
Case number
LAX99FA078
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1999-01-20.
  • API snapshot SHA-256: e9c143addecbb2f1441b1123b39ebd1957b0baef6235e4ffa49898b8df305d33; retrieved 2026-09-20T22:16:03.719Z.