FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX96LA079 · Cessna 182Q

26 Dec 1995 · Fallbrook, CA, United States

Cessna 182Q · Accident: overrun during landing

From Long Beach International Airport (LGB) to Fallbrook Community Airpark (L18)

Report a problem

Event

NTSB case
LAX96LA079
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
0 · 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 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
N97196
Operator
Unknown
Onboard fatalities
Unknown
Route
From Long Beach International Airport (LGB), Long Beach, CATo Fallbrook Community Airpark (L18)
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
Landing · landing roll
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
Overrun
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Pilot in command › Go-around, not performed
  • Pilot in command › Preflight planning/preparation, inadequate
  • Pilot in command › Proper touchdown point, not attained
  • Pilot in command › Wrong runway, selected

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

NTSB narrative

After arriving over the airport, the pilot was unsuccessful in obtaining an airport advisory by using the common traffic advisory frequency (CTAF) from a flight information publication that was in his possession. (After the accident, he noticed the publication was out-of-date and did not have the correct CTAF published.) The pilot said he could find no means for determining the wind direction, and he elected to land on runway 18. During the landing roll, he was unable to stop the aircraft on the remaining runway, and it overran the departure end, encountered a rough surface, and nosed over. The pilot said that after the accident, he realized he had unknowingly landed downwind with a 15-knot tail wind. Ground witnesses reported that the aircraft was very fast and had touched down about 1,000 feet down the 2,160-foot-long runway. The witnesses also stated that the winds had been steady from the north at 10 to 15 knots all morning.

Probable cause

the pilot's inadequate preflight planning/preparation (failure to ensuring the flight information publication was current); his selection of the wrong runway for landing; his failure to achieve the proper touchdown point during the landing; and his failure to go around, while there was still sufficient airspeed and runway available. The tailwind was a related factor.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX96LA079
Event ID
20001207X05034
Case number
LAX96LA079
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: a788ff49ab7b0d59044114db67878c84d57c83b98fbdb94af8b00557756a3398; retrieved 2026-09-22T22:56:27.253Z.