Overall Trends
Total, fatal, and serious accidents in the selected range.
Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.
Fast key and full-text search with live filters, watches, and precise metadata.
Use quotes for exact phrase matches (for example "fuel selector valve").
Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.
Major cases, deep-report coverage, and investigation media across decades of NTSB history.
Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.
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.
Cottonwood, AZ
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.
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.
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.