WPR20LA017

NTSB accident investigation · Cessna 205 · Red Creek, AZ · October 24, 2019

Accident · No injuriesClass 3 · LimitedFinal report
Date
October 24, 2019, 16:00 local (23:00 UTC)
Place
Red Creek, AZ
Injuries
3 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N8326ZCessna 205
Defining event
Landing-aborted after touchdown: Collision during takeoff/land
Weather
Visual (VMC) · Day
Status
Completed
Report
Approved by Office Director
Investigation class
Class 3
NTSB office
Western Pacific Region
Parties
Federal Aviation Administration FSDO
FAA report
20191024022149A
Case key
100510

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 failure to properly configure the flaps for an aborted landing, which resulted in degraded climb performance and impact with vegetation at the end of the runway.

Findings · 3

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.

Action: incorrect action performancePersonnel issues › Action/decision · PilotCessna 210-5A(205A): 1 caseAll aircraft: 1,386 casesProbable cause
Use of equip/info: aircraft controlPersonnel issues › Task performance · PilotCessna 210-5A(205A): 2 casesAll aircraft: 9,295 casesProbable cause
Aircraft capability: climb capabilityAircraft › Aircraft oper/perf/capability · Not attained/maintainedCessna 210-5A(205A): 1 caseAll aircraft: 183 casesProbable cause

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 was landing in crosswind conditions at a 1,200-ft-long remote desert airstrip and performed a go-around after approaching the runway too high. The second approach was stabilized, and, after touching down, he applied the brakes; however, the airplane became airborne again. He applied full engine throttle and continued to fly the airplane in ground effect until reaching the end of the runway. He then pulled back on the control yoke to initiate a climb, but the airplane was unable to climb above the rising terrain and impacted vegetation about 500 ft beyond the runway threshold. The pilot reported that there were no mechanical malfunctions or failures with the airplane that would have precluded normal operation. The wing flaps were found extended to 40° following the accident. The circumstances of the accident are consistent with the pilot’s failure to reduce the flap extension upon initiating the aborted landing, which resulted in degraded climb performance and impact with vegetation at the end of the runway.

Factual narrative

On October 24, 2019, about 1600 mountain standard time, a Cessna 205A, N8326Z, was substantially damaged when it was involved in an accident near Payson, Arizona. The pilot and two passengers were?not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The flight departed from Rocky Mountain Metropolitan Airport (BJC), Denver, Colorado, earlier in the morning. The pilot added 40 gallons of fuel to the airplane at Payson Airport, Payson, Arizona, before departing at 1545. His intention was to fly to Red Creek airstrip and camp there overnight. Red Creek is an unimproved airstrip located within the Tonto National Forest at an elevation of about 2,300 ft. It is composed of a single dirt runway (designation 6/24) that is about 1,200 ft long and 15 ft wide, on a 1.3° slope (15 ft rise) to the west. The airstrip is surrounded by rising terrain, which, according to the Arizona Pilots Association and the Recreational Aviation Foundation, necessitates landing on runway 24 and departing from runway 6. The pilot reported that the flight to Red Creek lasted about 10 minutes, and upon arrival, he overflew the airstrip and observed the windsock, which indicated a direct right crosswind for runway 24, with wind speeds that he estimated to be between 4 and 9 knots. He initiated a landing approach to runway 24 and performed a go-around after judging that the airplane was too high. He reported that the second approach was stabilized, and after touching down, he applied the brakes; however, the airplane became airborne again. He applied full engine throttle and continued to fly the airplane in ground effect until reaching the end of the runway. He then pulled back on the control yoke to initiate a climb, but the airplane was unable to outclimb the rising terrain and impacted vegetation about 500 ft beyond the runway threshold and nosed over. The pilot did not retract the flaps, which remained extended to 40° throughout. The pilot reported no preimpact mechanical malfunctions or failures with the airframe or engine that would have precluded normal operation, and this was the first time he had landed at the airstrip. He stated that the airplane was loaded below its maximum gross weight, but in hindsight, he should have reduced the weight further by both taking on less fuel and reducing baggage. An airstrip bulletin published by Arizona Pilots Association and the Recreational Aviation Foundation stated: Neither the authors of this bulletin, nor the U.S. Forest Service, encourage the use of the Red Creek airstrip!... Know your aircraft’s short field performance and your capabilities!...Winds are unpredictable, but southwest winds are prevalent, causing a potential downdraft at the approach to runway 24....Departure is typically via 6, and you may need to wait out adverse winds! Directional control can be a challenge, and quartering tail winds have contributed to the destruction of several aircraft! The pilot statedthat although he was aware of the airport features, he had not familiarized himself with the number of accidents that had happened there before and that, if he had, he likely would have chosen an alternate airport after encountering the wind conditions during the first landing attempt. The airplane owner’s manual does not provide specific instructions for a balked landing; however, it indicates a flap setting of 40° for short field landings and a flaps setting of 20º for soft-field takeoffs during which the airplane should be flown level in ground effect until a safe climb speed has been established. Additionally, the manual states that if an obstruction ahead requires a steep climb angle, the airplane should be flown at the best angle of climb with flaps up and maximum power.

Aircraft

Registration
N8326Z
Reported as
Cessna 205 (A)
Category
Airplane
Serial number
205-0326
Built
1963
Airframe hours
4,420.78
Engine
Continental IO-550, 300 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Standard, Utility; Standard, Normal
Last inspection
Annual · July 1, 2019 · 20 hours before
Departed
PAN · Payson, AZ
Destination
Red Creek, AZ
Airport
PVT · Red Creek, runway 24, 1,200 × 15 ft, gravel
Equipment
Handheld GPS, Electronic flight bag or handheld device, Auto-pilot, Stall warning system, Satellite tracking device, Onboard weather

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
51
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Instrument ratings
Airplane
Medical
Class 3, With waivers/limitations
Last flight review
April 13, 2018
Seat
Left
Restraint
4-point
Flight hours
472 total · 95 in this make and model · 436 as pilot in command · 25 in the last 90 days · 14 in the last 30 days · 4 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
30° at 11 knots, gusting 18
Visibility
10 statute miles
Lowest ceiling
None
Temperature
57 °F, dew point -4 °F
Altimeter
30.24 inHg
Observed at
KPAN, 20 nm away
METAR
KPAN 242315Z AUTO 03011G18KT 10SM CLR 14/M20 A3024 RMK AO2

Docket · 4

The files NTSB released with the investigation on March 15, 2022, on NTSB’s docket system: statements, records, photos and specialists’ reports. 6.7 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.

Other investigations on N8326Z · 1

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