# Accident 20170604009459A: Cessna 172M, Payson, AZ, June 4, 2017

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 4, 2017, 10:24 local time
- Place: Payson, AZ
- Damage: Destroyed
- Phase of flight: Landing: Approach
- Operating rules: General operating rules (Part 91)
- Location: 34.2669° N, 111.3669° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=34.2669&lon=-111.3669&mi=10
- Aircraft: N50526, a cancelled registration (https://openairdocs.org/deregistered/N50526-2018-04-23) (OpenAirDocs)
- Registry model: Cessna 172M (registry code 2072418, https://openairdocs.org/model/cessna-172m) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172M
- Reported engine: LYCOMING 0-320 SERIES
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 2
- Pilot certificates: Private pilot
- Pilot flight hours: 91 total, 91 in this make and model, 21 in the last 90 days
- NTSB investigation: [NTSB GAA17CA318](https://openairdocs.org/ntsb/GAA17CA318) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20170604009459A

## Narrative

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

WHILE CONDUCTING A PERSONAL FLIGHT FROM FFZ TO PAN WITH ONE PASSENGER, PILOT BEGAN APPROACH TO PAN. PILOT PLANNED ON FULL STOP AT PAN. DA AT TIME WAS APPROXIMATELY 7500?. AS PILOT WAS CROSSING THRESHOLD AT FLAPS 30, 50 KTS,  500?,  AIRCRAFT STARTED DRIFTING RIGHT. PILOT DECIDED TO GO-AROUND AND SELECTED FLAPS 20 AND APPLIED POWER (2500 RPM PLUS). PILOT STATED AIRCRAFT NEVER GAINED SPEED OR ALTITUDE. (THIS WAS CONFIRMED THROUGH STATEMENT BY WITNESS. AFTER EXITING RUNWAY AND AIRFIELD, PILOT ATTEMPTED TO TURN NORTH WHERE AIRCRAFT CONTINUED WITH NO ALTITUDE OR AIRSPEED GAIN. AIRCRAFT FLEW INTO RISING TERRAIN (BRUSH) WITH THAN MINOR INJURIES TO PILOT AND PASSENGER. AIRCRAFT CAUGHT FIRE AND BURNED.

## 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 GAA17CA318](https://openairdocs.org/ntsb/GAA17CA318), Jun 4, 2017: Cessna 172 (N50526), Payson, AZ, destroyed. Probable cause: The pilot’s inadequate preflight planning that did not account for high-density altitude conditions and his subsequent attempted go-around in conditions that prevented the airplane from attaining a…

## Other reports on N50526 (1)

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

- [Incident 19891021062089I](https://openairdocs.org/incident/19891021062089I), Oct 21, 1989: Cessna 172M (N50526), Albany, KY, Minor damage. Partial engine failure after takeoff. Set down on same runway. Veered off side to avert drop at end. Hit a tree.

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.