# Accident 20041105034869A: Cessna 172S, Chandler, AZ, November 5, 2004

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 5, 2004, 08:30 local time
- Place: Chandler, AZ
- Airport: Stellar Airpark Airport
- Damage: Substantial damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 33.2986° N, 111.9158° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=33.2986&lon=-111.9158&mi=10
- Aircraft: N20519, registered now (https://openairdocs.org/aircraft/N20519) (OpenAirDocs)
- Registry model: Cessna 172S (registry code 2072439, https://openairdocs.org/model/cessna-172s) (OpenAirDocs)
- Registry engine: Lycoming IO-360-L2A (registry code 41597, https://openairdocs.org/engine/lycoming-io-360-l2a) (OpenAirDocs)
- Reported make and model: CESSNA 172S
- People aboard: 1
- Fatal injuries: 0
- Pilot certificates: Student
- Pilot flight hours: 48 total, 14 in this make and model, 6 in the last 90 days
- NTSB investigation: [NTSB LAX05CA028](https://openairdocs.org/ntsb/LAX05CA028) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20041105034869A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) PILOT DID NOT EXECUTE PROPER RECOVERY ON BOUNCED LANDING RESULTING IN PIO. AIRCRAFT RECEIVED PROP STRIKE AND BENT FIRE WALL.

## The NTSB's investigation of this event (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 LAX05CA028](https://openairdocs.org/ntsb/LAX05CA028), Nov 5, 2004: Cessna 172S (N20519), Chandler, AZ, substantial damage. Probable cause: the pilot's improper flare, which resulted in a hard landing. Contributing factors were his improper recovery from the subsequent bounced landing and pilot-induced oscillations.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
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.