# Incident 20120411004819I: Cessna 172S, Phoenix, AZ, April 11, 2012

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: April 11, 2012, 15:15 local time
- Place: Phoenix, AZ
- Airport: Phoenix-Deer Valley
- Damage: Minor damage
- Phase of flight: Landing: Rollout
- Operating rules: General operating rules (Part 91)
- Location: 33.6883° N, 112.0826° W: Placed by OpenAirDocs at PHOENIX DEER VALLEY (DVT), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=33.6883&lon=-112.0826&mi=10
- Aircraft: N2166K, a cancelled registration (https://openairdocs.org/deregistered/N2166K-2013-09-25) (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: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Student
- Pilot flight hours: 45 total, 8 in this make and model, 37 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20120411004819I

## Narrative

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

STUDENT LANDED ON RUNWAY 25R AT DVT AND TRIED TO EXIT B9 TAXIWAY AT TOO HIGH OF SPEED. THE AIRCRAFT TILTED UP ONTO THE LEFT MAIN AND NOSE AND THE PROP STRUCK THE RUNWAY. THE STUDENT CORRECTED THE AIRCRAFT AND CONTINUED DOWN RUNWAY 25R TO TAXIWAY B5 AND TAXIED TO THE RAMP.

## Other reports on N2166K (1)

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

- [Accident 20130404004739A](https://openairdocs.org/incident/20130404004739A), Apr 4, 2013: Cessna 172S (N2166K), Phx, AZ, Substantial damage. During a part 61 training flight the student lost control of the aircraft during takeoff. The instructor took control of the aircraft and was unable to gain…

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.