7 May 2013: PIPER PA-28 161

7 May 2013: PIPER PA-28 161 — Unknown operator

No fatalities • Cottonwood, AZ, United States

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.

— NTSB Determination

Accident 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.

Contributing factors

  • cause Descent/approach/glide path — Not attained/maintained
  • cause Student pilot
  • factor Student pilot
  • factor Student pilot
  • Fence/fence post

Conditions

Weather
VMC, wind 170/04kt, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.