- Date
- June 4, 2017, 10:24 local (17:24 UTC)
- Place
- Payson, AZ
- Injuries
- 2 minor
- Damage
- Destroyed
- Phase of flight
- Approach
- Aircraft
- N50526Cessna 172
- Defining event
- Approach-VFR go-around: Aerodynamic stall/spin
- Weather
- Visual (VMC) · Day
- Status
- Completed · report November 14, 2017
- Report
- Approved by Office Director
- NTSB office
- General Aviation Accidents
- Parties
- FAA
- FAA report
- 20170604009459A
- Case key
- 95297
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
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 positive climb rate and resulted in its subsequent descent and impact with rising terrain.
Findings · 5
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
Analysis
The pilot reported that, during an approach to runway 22, the airplane drifted to the right of the runway centerline. He initiated a go-around by turning off the carburetor heat, applying full throttle, decreasing the flaps from 30° to 20°, and pushing forward on the yoke to increase airspeed; the airplane then began to settle into ground effect. The pilot saw that the terrain began to rise, and he recalled that the noise abatement procedure called for a right turn to 270°, so he turned to the right before establishing a climb. The airplane descended into rising terrain, struck trees, and impacted the ground and became engulfed in flames. The postcrash fire destroyed the fuselage. The METAR reported that the wind was variable at 4 knots and that the temperature was 84°F. The field elevation was 5,504 ft, and the altimeter setting was 30.14 inches of mercury. The density altitude was 8,255 ft. Per the National Transportation Safety Board Pilot Aircraft Accident Report, the pilot reported that the accident could have been prevented by reviewing the airplane's performance data and atmospheric conditions, especially density altitude and its effect on performance per the manufacturer's Pilot's Operating Handbook. The pilot stated that he would place greater emphasis on performance planning as an essential activity during flight planning. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Factual narrative
The pilot reported that during an approach to runway 22, the airplane drifted to the right of the runway centerline. He initiated a go-around by turning off the carburetor heat, he applied full throttle, he increased the flaps from 30° to 20°, and he pushed forward on the yoke to increase airspeed. He noticed that the airplane began to settle into ground effect. He saw that the terrain began to rise and he recalled that the noise abatement procedure called for a right turn to 270°, so the pilot turned to the right before establishing a climb. The airplane descended into rising terrain, struck trees and impacted the ground and became engulfed in flames. The post-crash fire destroyed the airplane's fuselage. The METAR reported that the wind was variable at 4 kts. and the temperature was 84° Fahrenheit. The field elevation was 5,504 ft. and the altimeter setting was 30.14. The density altitude was 8,255 ft. Per the National Transportation Safety Board Pilot Aircraft Accident Report, the pilot reported that the accident could have been prevented by reviewing the airplane's performance data and atmospheric conditions, especially density altitude and its effect on performance per the manufacturer pilot operating handbook. In the future, the pilot vowed to place greater emphasis on performance planning as an essential activity during flight planning. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Aircraft
- Registration
- N50526
- Reported as
- Cessna 172 (M)
- Category
- Airplane
- Serial number
- 17264211
- Built
- 1974
- Airframe hours
- 5,320.6
- Engine
- Lycoming O-320, 150 horsepower, reciprocating
- Damage
- Destroyed
- Fire
- On-Ground
- Flight
- Personal · Part 91
- Operator
- Classic Air Aviation LLC
- Registered owner
- Classic Air Aviation LLC
- Airworthiness certificate
- Standard, Normal
- Last inspection
- 100 hour · May 17, 2017
- Departed
- FFZ · Mesa, AZ
- Destination
- PAN · Payson, AZ
- Airport
- PAN · Payson, runway 24, 5,504 × 75 ft, asphalt
- Equipment
- None
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 57
- Injuries
- Minor
- Certificate
- Private
- Airplane ratings
- Single-engine land
- Medical
- Class 3, With waivers/limitations
- Last flight review
- May 12, 2017
- Seat
- Left
- Restraint
- 3-point
- Flight hours
- 92 total · 92 in this make and model · 25 as pilot in command · 21 in the last 90 days · 10 in the last 30 days
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- Variable at 4 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 84 °F, dew point 32 °F
- Altimeter
- 30.13 inHg
- Observed at
- KPAN, 2 nm away
Docket · 3
The files NTSB released with the investigation on October 12, 2017, on NTSB’s docket system: statements, records, photos and specialists’ reports. 6.0 MB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.