# Incident 20120222001719I: Piper PA-28R-201, Phoenix, AZ, February 22, 2012

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: February 22, 2012, 12:42 local time
- Place: Phoenix, AZ
- Airport: Phoenix Deer Valley
- Damage: No damage
- Phase of flight: Takeoff: Climb Out
- 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: N320PA, a cancelled registration (https://openairdocs.org/deregistered/N320PA-2015-09-10) (OpenAirDocs)
- Registry model: Piper PA-28R-201 (registry code 7102816, https://openairdocs.org/model/piper-pa-28r-201) (OpenAirDocs)
- Registry engine: Continental IO-360 series (registry code 17025, https://openairdocs.org/engine/continental-io-360-series) (OpenAirDocs)
- Reported make and model: PIPER PA-28R-201
- Reported engine: LYCOMING O-360
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot, flight instructor
- Pilot flight hours: 1,250 total, 35 in this make and model, 143 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20120222001719I

## Narrative

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

AIRCRAFT TOOK OFF FROM PHOENIX DVT RUNWAY 07.  PILOT REPORTED BAD LANDING GEAR INDICATION PRIOR TO LANDING AT DVT RNW 07.  NO DAMAGE TO AIRCRAFT.

## Other reports on N320PA (1)

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

- [Incident 20040715025279I](https://openairdocs.org/incident/20040715025279I), Jul 15, 2004: Piper PA28R201 (N320PA), Phoenix, AZ, Minor damage. (-23) While performing touch & go landings @ dvt, engine lost power during take-off @ approximately 200' AGL. Landed at the end of runway 25 with the landing…

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.
