LAX04CA288 · Cessna 172S
Cessna 172S · Accident: overrun during takeoff
From Stellar Airpark (KP19) to Chandler Municipal Airport (KCHD)
Event
- NTSB case
- LAX04CA288
- 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
- Unknown
- 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 172S
- 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
- N5327G
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Stellar Airpark (KP19), Chandler, AZTo Chandler Municipal Airport (KCHD), Chandler, AZ
- 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
- Takeoff · roll/run
- 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 › Abort, not performed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane ran off the departure end of the runway on a touch and go landing and went into a chain link fence. The student solo pilot was performing touch and go's and was in right traffic for runway 22R. He flared about a third down the runway, landed the airplane, raised the flaps, and applied full throttle. The airplane veered left towards the left edge of the runway. The pilot applied right rudder and checked his airspeed. He then noticed that he was close to the left side of the runway. He reduced the throttle and increased right rudder input. The airplane returned towards the centerline and he added full throttle. The airplane approached the end of the runway before it had reached flying speed. The airplane went over the runway threshold, continued over dirt then grass, and finally, into the airport boundary chain link fence. After the airplane came to rest the pilot shut down the engine and secured the electrical equipment. The pilot indicated that the airplane had no mechanical failures or malfunctions during the flight.
Probable cause
the student pilot's failure to abort the takeoff. A contributing factor was the pilot's failure to maintain directional control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX04CA288
- Event ID
- 20040901X01342
- Case number
- LAX04CA288
- 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, coordinates. 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: 27d6448cd982a3a02bf99076fc4451a8e2b96d4743ddbf55af599f1bfb4b9711; retrieved 2026-09-22T06:54:43.303Z.