# NTSB WPR13CA219: Piper PA-28, N47717, Cottonwood, AZ, May 7, 2013 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Data collection · Final report - Date: May 6, 2013, 23:15 local (May 7, 2013, 06:15 UTC) - Place: Cottonwood, AZ - Coordinates: 34.729999, -112.035003 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=34.7300&lon=-112.0350&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR go-around: Controlled flight into terr/obj (CFIT)](https://openairdocs.org/ntsb-events/120) - Highest injury: Serious injuries - Injuries: 1 serious - Status: Completed, report July 29, 2013 - Report: Approved by Office Director - NTSB office: Western Pacific Region - NTSB case key (mKey): 86824 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR13CA219 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/86824/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=86824 - Page: https://openairdocs.org/ntsb/WPR13CA219 ## Probable cause 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. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Piper PA-28-161, 8 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=7102803), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md) - [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Student/instructed pilot (probable cause); cases with it: [Piper PA-28-161, 19 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=7102803), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md) - [Use of equip/info: use of equip/system](https://openairdocs.org/ntsb-findings/02063015): Personnel issues › Task performance · Student/instructed pilot (probable cause); cases with it: [Piper PA-28-161, 12 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md?model=7102803), [All aircraft, 1,391 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md) - [Info processing/decision: identification/recognition](https://openairdocs.org/ntsb-findings/02041510): Personnel issues › Action/decision · Student/instructed pilot (probable cause); cases with it: [Piper PA-28-161, 6 cases](https://openairdocs.org/ntsb-findings/02041510/cases.md?model=7102803), [All aircraft, 559 cases](https://openairdocs.org/ntsb-findings/02041510/cases.md) - [Object/animal/substance: fence/fence post](https://openairdocs.org/ntsb-findings/03022047): Environmental issues › Physical environment · Not specified; cases with it: [Piper PA-28-161, 1 case](https://openairdocs.org/ntsb-findings/03022047/cases.md?model=7102803), [All aircraft, 313 cases](https://openairdocs.org/ntsb-findings/03022047/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach: Miscellaneous/other](https://openairdocs.org/ntsb-events/900); cases with it: [Piper PA-28-161, 7 cases](https://openairdocs.org/ntsb-events/900/sequence.md?model=7102803), [All aircraft, 1,556 cases](https://openairdocs.org/ntsb-events/900/sequence.md) - [Approach-VFR go-around: Controlled flight into terr/obj (CFIT)](https://openairdocs.org/ntsb-events/120) (defining event); cases with it: [Piper PA-28-161, 6 cases](https://openairdocs.org/ntsb-events/120/sequence.md?model=7102803), [All aircraft, 1,074 cases](https://openairdocs.org/ntsb-events/120/sequence.md) ## Analysis 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. ## 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. ## Aircraft - Registration: [N47717](https://openairdocs.org/deregistered/N47717-2015-05-13), registration cancelled 2015-05-13, S/N 28-7816126, built 1977 (OpenAirDocs) - Reported make and model: PIPER PA-28 (161) - Registry model: [Piper PA-28-161](https://openairdocs.org/model/piper-pa-28-161) (registry code 7102803) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 28-7816126 - Airframe hours: 10162 - Engines: Lycoming O-320 160 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, November 28, 2011, 160 hours before - Departed: Unknown - Destination: P52, Cottonwood, AZ - Airport: P52, Cottonwood Airport, runway 14, 4,252 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot; age 65; injuries: serious; student; medical: class 3, without waivers/limitations; flight hours: 1 total, 1 in this make and model ## Weather - Conditions: Visual (VMC), Night - Wind: 170° at 4 knots - Visibility: 10 statute miles - Lowest ceiling: 7,500 ft broken - Temperature: 61 °F, dew point 41 °F - Altimeter: 30.03 inHg - Observed at: SEZ, 14 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20130506006209A](https://openairdocs.org/incident/20130506006209A), May 6, 2013: Piper PA-28-161, Cottonwood, AZ, Substantial damage. During a telephone conversation with [privacy data omitted] (pilot of N47717) on may 7, 2013 at 14:33, he stated that he had flown N47717 from Oklahoma with an… ## Docket (14 files) The files NTSB released with the investigation on June 14, 2013, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=86824. 4.1 MB in all. - Record of Initial FAA Conversation (item 1, .PDF, 111 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40394183&FileExtension=.PDF&FileName=Record%20of%20Initial%20FAA%20Conversation-Master.PDF - Record of Second FAA Conversation (item 2, .PDF, 56 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40394184&FileExtension=.PDF&FileName=Record%20of%20Second%20FAA%20Conversation-Master.PDF - Record of FAA Communication (item 3, .PDF, 54 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40394185&FileExtension=.PDF&FileName=Record%20of%20FAA%20Communication-Redacted.PDF - Cottonwood Police Dept Report Excerpts (item 4, .PDF, 395 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40395043&FileExtension=.PDF&FileName=Cottonwood%20Police%20Dept%20Report%20Excerpts-Redacted.PDF - FAA Pilot Interview Summary (item 5, .PDF, 574 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40394198&FileExtension=.PDF&FileName=FAA%20Pilot%20Interview%20Summary-Redacted.PDF - Media Report (item 6, .PDF, 111 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40394188&FileExtension=.PDF&FileName=Media%20Report-Master.PDF - Airplane Records Excerpts (item 7, .PDF, 1.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40394189&FileExtension=.PDF&FileName=Airplane%20Records%20Excerpts-Redacted.PDF - Instrument Panel Images (item 8, .PDF, 2 photos, 883 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40394190&FileExtension=.PDF&FileName=Instrument%20Panel%20Images-Master.PDF - METARs (item 9, .PDF, 128 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40394191&FileExtension=.PDF&FileName=METARs-Master.PDF - Site Map (courtesy FAA) (item 10, .PDF, 122 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40394193&FileExtension=.PDF&FileName=Site%20Map%20(courtesy%20FAA)-Master.PDF - Front View of Airplane (Courtesy FAA) (item 11, .PDF, 167 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40394200&FileExtension=.PDF&FileName=Front%20View%20of%20Airplane%20(Courtesy%20FAA)-Master.PDF - Side View of Airplane (Courtesy FAA) (item 12, .PDF, 188 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40394195&FileExtension=.PDF&FileName=Side%20View%20of%20Airplane%20(Courtesy%20FAA)-Master.PDF - Radio Setup (Courtesy FAA) (item 13, .PDF, 159 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40394197&FileExtension=.PDF&FileName=Radio%20Setup%20(Courtesy%20FAA)-Master.PDF - Memo for Record IIC (item 14, .PDF, 92 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40394192&FileExtension=.PDF&FileName=Memo%20for%20Record%20IIC-Redacted.PDF 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. --- 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.