FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX97LA022 · Cessna 152

17 Oct 1996 · Imperial, CA, United States

Anglo American Aviation Cessna 152 · Accident: loss of control on ground/water during landing

From Twentynine Palms Airport (TNP) to Imperial County Airport (IPL)

Report a problem

Event

NTSB case
LAX97LA022
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 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
N48728
Onboard fatalities
Unknown
Route
From Twentynine Palms Airport (TNP), Twentynine Palms, CATo Imperial County Airport (IPL)
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 › Directional control, not maintained
  • Pilot in command › Ground loop/swerve, inadvertent

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

NTSB narrative

When the student pilot first attempted to land, during his third supervised solo cross-country flight, the airplane had excessive altitude and airspeed, so he made a go-around. The pilot successfully touched down on the runway during his next attempt. However, during rollout, the airplane veered left, and the student corrected by applying pressure to the right rudder and/or brake. The airplane then swerved right, went off the side of the runway, entered soft mud on the shoulder, and nosed over.

Probable cause

the student pilot's failure to maintain directional control during landing rollout, which resulted in a ground swerve. Soft terrain on the shoulder of the runway was a related factor.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX97LA022
Event ID
20001208X06931
Case number
LAX97LA022
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: 4be5ef58f8ca5bf228eac23a223458d8d5f4944d02c6799ad343c41c2cd39f8d; retrieved 2026-09-22T20:55:47.566Z.