FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX96LA345 · Cessna 172F

19 Sept 1996 · Ehrenberg, AZ, United States

Cessna 172F · Accident: loss of control in flight on approach

From Casa Grande Municipal Airport (CGZ) to Blythe Airport (BLH)

Report a problem

Event

NTSB case
LAX96LA345
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 172F

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
N5536T
Operator
Unknown
Onboard fatalities
Unknown
Route
From Casa Grande Municipal Airport (CGZ), Casa Grande, AZTo Blythe Airport (BLH), Blythe, 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
Approach · VFR go-around
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 in flight
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
Stall/mush
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 › Airspeed, inadequate
  • Pilot in command › Stall/mush, inadvertent

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

NTSB narrative

The pilot intended to land on a farm road, saw pot holes in the road, and decided to initiate a go-around. He estimated that the aircraft climbed to 50 or 60 feet agl between 50 to 55 mph when he started a right turn to avoid an agricultural aircraft about 1/2 mile ahead. The aircraft stalled in the turn and settled into a cotton field. The pilot said that the wind was calm and there were no mechanical problems with the aircraft.

Probable cause

The pilot's attempt to perform a low altitude evasive maneuver with inadequate airspeed resulting in a stall/mush.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX96LA345
Event ID
20001208X06781
Case number
LAX96LA345
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: f9dcd3817e301c24a35048127ef4555b27afcbc55e64ac93250fd6ee3dc0d54f; retrieved 2026-09-22T21:07:06.952Z.