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.
Marlboro, MA
According to the pilot, he verified the wind direction and speed by observing the windsock before attempting to land. During the first attempt, he executed a go-around due to excessive altitude. During a second attempt, the pilot initiated a forward slip and landed the airplane two-thirds down the runway. After touchdown, he applied brake pressure, but the airplane continued off the end of the runway and impacted a fence, substantially damaging the fuselage and wings. A postaccident examination of the airframe and engine revealed no mechanical malfunctions or failures that would have precluded normal operation. The pilot reported that it was the first time he had landed at the airport and that it was the shortest runway he had ever attempted to land on. The pilot stated that the accident could have been prevented if he had performed a go-around.
The pilot’s improper touchdown point and failure to perform a go-around in a timely manner, which resulted in a runway excursion.
According to the pilot, he was returning to the rented airplane’s home base when he overflew the accident airport and decided to land. The pilot checked the winds by observing the wind sock before attempting to land on runway 32, a 1,659-foot runway. During the first attempt, the pilot executed a go around due to excessive altitude. During a second attempt, the pilot initiated a forward slip and landed the airplane two-thirds down the runway. The pilot applied brake pressure, but the airplane continued off the end of the runway and impacted a fence, which substantially damaged the fuselage and wings. During a subsequent examination of the wreckage, a Federal Aviation Administration inspector identified no preexisting anomalies with the airplane. The pilot reported that it was the first time he had landed at the airport, and it was the shortest runway he had ever attempted to land on. He also noted that his total flight experience was approximately 90 hours, of which, about 6 hours were in the same make and model as the accident airplane. When asked how he could have prevented the accident, the pilot stated that he should have performed a go-around if he was unsure that he could land and stop on the remaining runway. The operator who rented the airplane to the pilot restricted landings to runways which were at least 3,000 feet long. Winds, recorded at an airport 12 miles to the northeast at the time of the accident, were calm.