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.
Falcon, CO
After a night local area personal flight, the pilot was attempting to land at the airport of departure and could not turn on the runway lights by use of the UNICOM. He attempted to land without this aid and the landing was made in a ditch between the runway and taxiway. During landing roll the aircraft struck a culvert. The frequency for the UNICOM had been changed several weeks earlier and this change had been published in NOTAMS, and local air traffic control and flight service had the change published in controller instructions. No evidence was found that the pilot attempted to contact these facilities. Lighting and weather at the time was clear skies and dark night lighting.
Failure by the pilot to select suitable terrain for landing. Factors were inadequate preflight planning and preparation for the flight by the pilot by failing to check NOTAMS and failing to use communication aids available to him.
On September 24, 1996, at 2030 mountain daylight time, a Piper PA28-151, N41369, landed in a ditch between the runway and taxiway at Meadow Lake Airport (00V), Falcon, Colorado. The private pilot and his passenger were not injured and the aircraft sustained substantial damage. Visual meteorological conditions prevailed for this Title 14 CFR Part 91 personal flight and no flight plan was filed. The flight departed Meadow Lake at 1930. The pilot stated that he could not activate the runway lights and was attempting to land without their aid. The touchdown was in a ditch beside the runway and the aircraft struck a culvert during landing roll causing damage to the propeller, engine cowling, left wing, and nose landing gear. At the time of the accident, weather and light conditions were clear skies with dark night lighting. The UNICOM frequency, by which the pilot can activate the lights from his aircraft, had been changed several weeks earlier and this change had been published in NOTAMS (notice to airmen) and was properly listed in controller information at Colorado Springs Municipal Airport Tower (10 miles west of Meadow Lake), Colorado Springs Approach Control and Flight Service. The pilot stated that he was unaware of the frequency change and had not checked NOTAMS prior to departure. In addition, no evidence was found that he attempted to contact any of the above facilities.