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.
Gaithersburg, MD
While on the final approach leg of a simulated forced landing, the airspeed began to decrease to 70 mph, and the pilot added power. About 1/4-mile short of the runway, the airspeed decreased to 60 mph, "presumably because of loss of 10 knot headwind," and the airplane stalled. The airplane descended into a grass field short of the runway, and came to rest upright. The winds recorded at a nearby airport, about the time of the accident, were from 040 degrees at 5 knots.
The pilot’s failure to maintain airspeed, resulting in an inadvertent stall.
On May 15, 2003, at 1215 eastern daylight time, a Piper PA-28R-200, N1514X, was substantially damaged while landing at the Montgomery County Airpark, Gaithersburg, Maryland. The certificated private pilot was not injured. Visual meteorological conditions prevailed and no flight plan was filed for the local personal flight conducted under 14 CFR Part 91. According to the pilot, he was conducting touch and go's to runway 14, a 4,201-foot long, 75-foot wide asphalt runway. On the seventh landing, the pilot elected to perform a simulated power-off, "gliding approach," to the runway. While on the downwind leg, abeam the approach end of the runway, the pilot reduced the throttle to 1,000 rpm's, performed the landing checklist, and added one notch of flaps. He then turned on to the base leg at an airspeed of 80 mph. As the turn on to the final approach leg was made, at an altitude of 350 feet agl, the airspeed began to decrease to 70 mph, and the pilot added power. About 1/4-mile short of the runway, the airspeed decreased to 60 mph, "presumably because of loss of 10 knot headwind," and the airplane stalled. The airplane descended into a grass field short of the runway, and came to rest upright. The winds recorded at a nearby airport, about the time of the accident, were from 040 degrees at 5 knots.