# NTSB LAX04CA288: Cessna 172S, N5327G, Chandler, AZ, August 8, 2004

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: August 8, 2004, 10:42 local (17:42 UTC)
- Place: Chandler, AZ
- Coordinates: 33.29861, -111.915832
- Nearby events: https://openairdocs.org/map.md?lat=33.2986&lon=-111.9158&mi=10
- Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report October 28, 2004
- Report: Approved by Office Director
- Parties: Federal Aviation Administration
- NTSB case key (mKey): 59871
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX04CA288
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/59871/pdf
- Page: https://openairdocs.org/ntsb/LAX04CA288

## Probable cause

the student pilot's failure to abort the takeoff.  A contributing factor was the pilot's failure to maintain directional control.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- Overrun, takeoff - roll/run
  - touch-and-go - attempted, pilot in command
  - directional control - not maintained, pilot in command (contributing factor)
  - abort - not performed, pilot in command (cause)
- On ground/water collision with object, takeoff - roll/run
  - object - fence

## Analysis

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.

## Factual narrative

On August 8, 2004, at 1042 Pacific daylight time, a Cessna 172S, N5327G, ran off the departure end of the runway during a touch-and-go, and collided with terrain and a fence at Chandler Municipal Airport, Chandler, Arizona.  Angel Air Flight School owned the airplane, and was operating it under the provisions of 14 CFR Part 91.  The student pilot was not injured, and the airplane was substantially damaged.  Visual meteorological conditions prevailed, and a visual flight plan had not been filed.  The instructional flight originated at Stellar Airpark, Chandler, at 1030.

The student solo pilot stated in the Pilot/Operator Aircraft Accident Report (NTSB Form 6120.1/2) that he was performing touch-and-go's at Chandler Municipal Airport, and was in right traffic for runway 22R.  He flared about a 1/3 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.

## Aircraft

- Registration: [N5327G](https://openairdocs.org/aircraft/N5327G), registered now, S/N 172S9357 (OpenAirDocs)
- Reported make and model: Cessna 172S
- Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs)
- Category: Airplane
- Serial number: 172S9357
- Engines: Lycoming IO-360-L2A reciprocating
- Damage: Substantial damage
- Flight: Instructional, Part 91
- Registered owner: Angel Air Flight School
- Airworthiness certificate: Standard, Normal
- Departed: KP19, Chandler, AZ
- Destination: KCHD, Chandler, AZ
- Airport: KCHD, Chandler Municipal Airport, runway 22R

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Student pilot; age 37; student; medical: class 1; flight hours: 53 total, 52 in this make and model, 53 in the last 90 days, 33 in the last 30 days

## Weather

- Conditions: Visual (VMC), Day

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20040808019419A](https://openairdocs.org/incident/20040808019419A), Aug 8, 2004: Cessna 172S, Chandler, AZ, Substantial damage. (-23) During solo touch and go practice student lost directional control on takeoff roll. Student stated that after touching down approximately 1/3 down the…

## Other investigations on N5327G (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB LAX03LA231](https://openairdocs.org/ntsb/LAX03LA231), Jul 12, 2003: Cessna 172S (N5327G), Chandler, AZ, substantial damage. Probable cause: The pilot's misjudged landing flare, improper recovery from a bounced landing and failure to maintain directional control, resulting in a runway sign collision.

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
