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.
Salem, OR
The pilot reported that 'while practicing [a] short field approach, I landed a little shorter than planned.' The aircraft impacted the up-sloping terrain short of the threshold to the pilot's 900 foot long, turf landing strip and nosed over, coming to rest approximately 18 feet beyond the gear contact with the up-sloping edge. The left main landing gear folded aft upon ground impact.
The pilot-in-command's misjudgment of distance/altitude on final approach, and overload of the left main landing gear. A factor was the embankment at the end of the landing strip.
On March 5, 1999, approximately 1630 Pacific standard time, a Piper PA-12, N4328X, registered to and being flown by a private pilot, was substantially damaged when the aircraft impacted sharply up-sloping terrain just short of the landing threshold at the pilot's personal, non-airspaced landing strip near Salem, Oregon. The aircraft was on a short final approach, landing to the south, when the main gear impacted the terrain and collapsed. The aircraft then nosed over. The pilot sustained minor injuries. Visual meteorological conditions prevailed, and no flight plan had been filed. The flight, which was personal, was to have been operated under 14CFR91, and originated from Salem approximately 1610. The pilot reported that "while practicing [a] short field approach, I landed a little shorter than I planned. The landing wheels contacted the very end of the runway, which caused the nose to make contact on the grass strip, and [the plane] flipped over on its back. " The pilot stated that there was no mechanical malfunction with the aircraft at the time. An inspector with the Federal Aviation Administration's Hillsboro Flight Standards District Office examined the aircraft and accident site/landing strip. He reported that the landing strip was approximately 900 feet in length, 45 feet in width, and oriented along a north/south magnetic bearing (refer to DIAGRAM I). The landing surface was grass and the north end of the strip descended sharply approximately 20 feet (vertical height) to lower terrain (refer to photograph 1). Marks in the soil at the crest of the up-sloping edge of the runway's north threshold matched the distance between the main landing gear, and were consistent with a gear impact (refer to photograph 2). The aircraft was observed to be inverted at a point approximately 18 feet beyond the main gear impact at the up-sloping north end, and displayed extensive aftward left main landing gear deformation(refer to photograph 3).