FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX90LA188 · Cessna 172

22 May 1990 · Lakeport, CA, United States

Modesto Flight Center Cessna 172 · Accident: loss of control on ground/water during landing

From Modesto City Co-Harry Sham Field (MOD) to Lampson Field (1O2)

Report a problem

Event

NTSB case
LAX90LA188
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 172

Aircraft type
Cessna 172
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
N61602
Onboard fatalities
Unknown
Route
From Modesto City Co-Harry Sham Field (MOD), Modesto, CATo Lampson Field (1O2), Lakeport, 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
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
Loss of control on ground/water
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 › Compensation for wind conditions, inadequate
  • Pilot in command › Directional control, not maintained

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

NTSB narrative

THE PILOT CALLED THE AIRPORT UNICOM FOR AN AIRPORT ADVISORY, BUT TO NO AVIAL. HE THEN CIRCLED THE AIRPORT & OBSERVED THE SURFACE WINDS WERE OUT OF THE NORTH BETWEEN 12 - 15 KNOTS. THE AIRPORT WAS SERVED BY ONLY ONE EAST/WEST RUNWAY & THE PILOT ELECTED TO LAND ON RUNWAY 28. HE RPRTD THAT DURING THE LANDING ROLLOUT, A STRONG GUST OF WIND PUSHED THE AIRPLANE TO THE RIGHT INTO THE SOFT, MUDDY SHOULDER, AND THEN IT COLLIDED WITH A DITCH. THE PILOT IMPROPERLY USED THE FLIGHT CONTROLS AND FAILED TO MAINTAIN DIRECTIONAL CONTROL.

Probable cause

THE PILOT'S INADEQUATE COMPENSATION FOR CROSSWIND CONDITIONS. THE CROSSWIND WAS A FACTOR IN THE ACCIDENT.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX90LA188
Event ID
20001212X23187
Case number
LAX90LA188
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: 2fad97c72954453cc604e7a859a55a1cc42febc9a0c253510022b45dc16201e4; retrieved 2026-09-23T06:12:55.217Z.