WPR13CA219
2013-05-06 · Cottonwood, Arizona, United States · Serious · 1 aircraft · Status: Completed
Airport P52
Aircraft involved
Probable cause & findings
The student pilot's decision to attempt a night landing on an unlit runway, which resulted in a misaligned approach and subsequent collision with a fence. Contributing to the accident was the student pilot's improper set-up of the airplane radios, which resulted in his inability to activate the airport runway lights, and his mistaken identification of building lights for runway lights.
Factual narrative
The student pilot reported that he was flying the airplane from Oklahoma to California in pursuit of employment opportunities. During that trip, he was attempting a night landing for a fuel stop at an unattended airport, and was unable to activate the runway lights via radio. He made one approach to runway 32, executed a missed approach, and then initiated an approach to the opposite end, runway 14. He conducted that approach based on "two lights that he thought were the runway" lights. When the airplane was very close to the ground, the pilot realized that the lights were security lights on a building, and initiated a go-around. However, the airplane struck an airport boundary fence to the northeast of the runway, and came to rest on a street outside airport property. The wings and fuselage were substantially damaged by the impact with the fence. Postaccident examination revealed that the number one communications radio in the airplane was set to the proper frequency to activate the runway lights, but that the radio selector switch was set to the number two communications radio, which was set to a different frequency. When power was applied to the airplane and the radio selector switch was set to the number one radio, the runway lights were successfully activated. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. During a cross-country flight, the student pilot was attempting a night landing for a fuel stop at an unattended airport and was unable to activate the runway lights via radio. He made one approach to runway 32, executed a missed approach, and then initiated an approach to runway 14. He conducted that approach based on two lights that he thought were the runway lights. When the airplane was very close to the ground, the pilot realized that the lights were security lights on a building and initiated a go-around. However, the airplane struck an airport boundary fence northeast of the runway and came to rest on a street outside airport property. The wings and fuselage were substantially damaged by the impact with the fence. Postaccident examination revealed that the No. 1 communications radio in the airplane was set to the proper frequency to activate the runway lights but that the radio selector switch was set to the No. 2 communications radio, which was set to a different frequency. When power was applied to the airplane and the radio selector switch was set to the No. 1 radio, the runway lights were successfully activated. The pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Descent/approach/glide path-Not attained/maintained - C
- C Personnel issues-Action/decision-Info processing/decision-Decision making/judgment-Student pilot - C
- F Personnel issues-Task performance-Use of equip/info-Use of equip/system-Student pilot - F
- F Personnel issues-Action/decision-Info processing/decision-Identification/recognition-Student pilot - F
- — Environmental issues-Physical environment-Object/animal/substance-Fence/fence post-Not specified
Verbatim from NTSB's published report. Source file
NTSB_2013_WPR13CA219.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (go-around). All research papers
- NASA NTRS 2025 · Conference Paper A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- Semantic Scholar 2022 · Article (Journal of Safety Research) Go-around accidents and general aviation safety.
INTRODUCTION Changes in General Aviation (GA) accident rates, specifically in the go-around phase, are examined by comparing the number of accidents, the proportion of fatal accidents, and the proport…
- Semantic Scholar 2021 · Article (Aerospace) Classification and Analysis of Go-Arounds in Commercial Aviation Using ADS-B Data
Go-arounds are a necessary aspect of commercial aviation and are conducted after a landing attempt has been aborted. It is necessary to conduct go-arounds in the safest possible manner, as go-arounds …
- NASA NTRS 2021 · Accepted Manuscript (Version with final changes) Go-Around Criteria Refinement for Transport Category Aircraft
Presently, airline pilots are trained to go around if, when lower than 500 ft above the ground, they are outside of a handful of parameters such as airspeed, position, and rate of descent.
- NASA NTRS 2019 · Conference Paper Validation of Proposed Go-Around Criteria Under Various Environmental Conditions
This paper evaluates the effects of environmental conditions on touchdown performance under varying approach states and validates proposed go-around criteria developed using data from a previously con…