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.
Friendly, MD
While on the last leg of a solo cross-country flight, the student pilot became disoriented and contacted air traffic control for assistance. The air traffic controller at vectored the airplane over the destination airport two times, but the student pilot could not visually identify the airport due to increasing darkness. After about 20 minutes of searching for the airport, the fuel supply was exhausted, and the engine quit. The student pilot conducted a forced landing to a road, where it struck a tree before coming to rest upright. Visual inspection of the airplane after the accident revealed no evidence of fuel in the airplanes wing tanks or at the accident site.
The pilot's inability to locate the airport, which resulted in fuel exhaustion. A factor related to the accident was the night light conditions.
On August 21, 2000, about 2105 Eastern Daylight Time, a Cessna 150F, N8709G, was substantially damaged during a forced landing near Friendly, Maryland. The student pilot was not injured. Night visual meteorological conditions prevailed and no flight plan was filed for the solo instructional flight conducted under 14 CFR Part 91. According to the student pilot's flight instructor, the student pilot was signed off by his flight instructor to conduct a solo cross-country flight. At 1602, the student pilot departed the Potomac Airfield (VKX), Friendly, Maryland, and proceeded to Salisbury, Maryland. The student pilot landed and then proceeded back to VKX. While proceeding to VKX, the student pilot became disoriented and contacted Andrews Air Force Base (ADW) for assistance. The air traffic controller at ADW vectored the airplane over VKX two times, but the student pilot could not visually identify the airport due to increasing darkness. After about 20 minutes of searching for the airport, the fuel supply was exhausted, and the engine stopped. The student pilot conducted a forced landing to a road, where the airplane struck a tree before coming to rest upright. Visual inspection of the airplane by a Federal Aviation Administration inspector revealed no evidence of fuel in the airplanes wing tanks or at the accident site.