Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

May 7, 2013 · Piper PA-28 161 · N47717

Cottonwood, AZ

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
May 7, 2013
Injury Outcomes
1 injury (1 serious injury)
Location
Cottonwood, AZ
Aircraft
Piper PA-28 161
Tail Number
N47717
Injuries
Serious
Aircraft Damage
Substantial
NTSB Number
WPR13CA219

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.

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

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

Flight

Event TypeAccident
Event Time23:15 MST
Nearest AirportCottonwood Airport (1nm)
Runway14
Runway Length4252 ft
Runway Width75 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-28 161
Tail NumberN47717
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320 · Reciprocating · 160
Seats4

People & Injuries

Injury Summary1 injury (1 serious injury)
Fatal0
Serious1
Minor0
Uninjured0
Total1
Crew 1Age 65 · Third Class · Serious

Conditions

ConditionsVMC
LightNight
Wind170° @ 4 kt
Visibility10 sm
CeilingBroken clouds 7500 ft
Temperature / Dew Point61 F / 41 C
Altimeter30.03 inHg
Observation Time05:55
Weather SourceWFAC

Appendix: Source Data