FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX97LA256 · Cessna 150F

28 Jun 1997 · Casa Grande, AZ, United States

Cessna 150F · Accident: loss of control on ground/water during landing

From Yuma International Airport / Marine Corps Air Station Yuma (YUM) to Casa Grande Municipal Airport (CGZ)

Report a problem

Event

NTSB case
LAX97LA256
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 150F

Aircraft type
Cessna 150
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
N6634F
Operator
Unknown
Onboard fatalities
Unknown
Route
From Yuma International Airport / Marine Corps Air Station Yuma (YUM), Yuma, AZTo Casa Grande Municipal Airport (CGZ)
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 · Estimated position: the centre of Casa Grande, AZ, the place the record names. Not the accident site.

NTSB narrative

The pilot reported that she made a normal landing on the runway and that the winds were calm. She said that during the landing the airplane swerved to the right. She attempted to correct the swerve, but with no success. The airplane exited the runway and struck a drainage ditch on the side of the runway. Rudder control continuity was established at the accident site. Detailed examination of the aircraft disclosed no preimpact damage or malfunctions on the landing gear, brakes, or nose gear. The student pilot had logged over 49 hours of dual instruction with 6 hours of flight time with the instructor who had approved her solo flights.

Probable cause

Failure of the student pilot to maintain directional control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX97LA256
Event ID
20001208X08184
Case number
LAX97LA256
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: fead277ce7672161f4cac9e3c5d2592430d0a2c3acc321a5c0b07e03bf96a95d; retrieved 2026-09-22T19:20:59.000Z.