# Accident 20110908025169A: Cessna 172S, Phoenix, AZ, September 8, 2011

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: September 8, 2011, 13:49 local time
- Place: Phoenix, AZ
- Airport: Deer Valley
- Damage: Substantial damage
- Phase of flight: Landing: Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 33.6881° N, 112.0825° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=33.6881&lon=-112.0825&mi=10
- Aircraft: N5275S, registered now (https://openairdocs.org/aircraft/N5275S) (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
- Reported engine: LYCOMING IO-360-L2A
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 115 total, 100 in this make and model, 80 in the last 90 days
- NTSB investigation: [NTSB WPR11CA440](https://openairdocs.org/ntsb/WPR11CA440) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20110908025169A

## Narrative

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

PRIVATE PILOT LOST CONTROL OF AIRCRAFT DURING TOUCHDOWN AND LANDING ROLLOUT. THIS RESULTED IN SUBSTANTIAL DAMAGE TO THE AIRCRAFT. NO MECHANICAL ISSUES WERE FOUND OR BELIEVED TO BE INVOLVED.WINDS WERE LESS THAN 10 KNOTS AT TIME OF ACCIDENT.

## 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 WPR11CA440](https://openairdocs.org/ntsb/WPR11CA440), Sep 8, 2011: Cessna 172 (N5275S), Phoenix, AZ, substantial damage. Probable cause: The pilot's failure to maintain directional control during the landing roll.

## Other reports on N5275S (3)

Matched to the same aircraft by N-number and date.

- [Incident 20170726015289I](https://openairdocs.org/incident/20170726015289I), Jul 26, 2017: Cessna 172S (N5275S), Phoenix, AZ, Minor damage. Bird strike reported while doing pattern work for runway 25L, dvt. Large bird struck left wing 5 inches inboard causing significant dent in between ribs, no…
- [Accident 20160406008689A](https://openairdocs.org/incident/20160406008689A), Apr 6, 2016: Cessna 172S (N5275S), Payson, AZ, Substantial damage. On March 6, 2016 the student pilot was on a solo cross country from deer valley airport (dvt) to pason airport (pan) with a return to dvt. During the landing…
- [Incident 20130615009559I](https://openairdocs.org/incident/20130615009559I), Jun 15, 2013: Cessna 172S (N5275S), Phoenix, AZ, No damage. N5275S landed runway 25L at Phoenix Deer Valley Airport (kdvt). Upon landing, the aircraft veered to the right side of the runway onto the gravel infield. The…

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.