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.
Westminster, MD
The pilot stated that he entered the traffic pattern behind a Cessna. He stated that there was no radio communication with the Cessna, and after it landed, it maneuvered as if to take the runway again. However, it stopped short with its nose over the right side of the runway. The pilot stated that he came in with 40 degrees of flaps at about 70 mile per hour (MPH). He said that he came in high over the Cessna, pulled power and descended to the runway. His last known airspeed was between 80 and 85 mph. He said he touched down below the numbers, applied the brakes, and the aircraft seemed to slow. He said that at about 10 to 15 feet from the end of the runway, he was too fast, and the aircraft was not slowing down properly. He said he applied power to go around, but the airplane struck the trees off the end of the runway.
the pilot's misjudgement of his speed and distance, his failure to attain the proper touchdown point during the landing, and his delay in executing a go-around (aborted landing), which resulted in an overrun.
HISTORY OF FLIGHT On September 15, 1996, at about 1755 eastern daylight time, N9074W, a Piper PA-28-235, owned and operated by the private pilot, sustained substantial damage after impacting trees off the end of runway 13/31 while landing at the Clearview Airpark, Westminster, Maryland. The pilot was not injured however, the passenger, his son sustained serious injuries. Visual Meteorological conditions existed and no flight plan was filed. The flight was conducted under the provisions of 14 CFR Part 91, and originated from Issex, Maryland at 1525. The pilot stated in the NTSB Form 6120.1/2 pilot/operator report that he entered the pattern behind a Cessna. He stated that there was no radio communication with the Cessna and when it landed it maneuvered as if to take the runway again, however, it stopped short with its nose over the right side of the runway. He stated that he came in with 40 degrees of flaps at about 70 mile per hour (MPH). He said that he came in high over the Cessna pulled power and nosed down for the runway, and that his last known airspeed was between 80 and 85 mph. He said he touched down below the numbers, applied the brakes and the aircraft seemed to slow. He said that at about 10 to 15 feet from the end of the runway he was to fast, and the aircraft was not slowing down properly. He said he applied power to go around but struck the trees off the end of the runway.