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.
San Jose, CA
According to the pilot, he was flying above hilly terrain southeast of the airport when he heard a loud bang, followed by a violent vibration coming from the engine. The pilot added that the engine did not experience a total loss of power, but performed poorly due to the severe vibration. The pilot reduced the throttle and the vibration subsided, but when he added more throttle the violent vibration returned. The pilot then decided that it was unsafe to continue the flight and began searching for a place to land. He made a forced landing in a pasture, which was uneventful until one of the main landing gear contacted a "deviation" in the ground. The airplane nosed over and came to rest inverted. In a phone interview with the investigator-in-charge, a mechanic, who recovered the wreckage, reported that he examined the engine and discovered that the number 3 cylinder exhaust valve was stuck. The corresponding push rod tube was also bent, and the number 3 connecting rod was still intact.
Partial loss of engine power due to a seized exhaust valve during cruise flight. Rough terrain at the forced landing site was a contributing factor.
On November 20, 2006, at 1238 Pacific standard time, a Stinson 108-1 airplane, N97949, lost engine power and nosed over during a forced landing near San Jose, California. The private pilot, who was the sole occupant, was not injured; the airplane sustained substantial damage. The pilot/owner operated the airplane under the provisions of 14 CFR Part 91 as a personal flight. Visual meteorological conditions prevailed and a flight plan was not filed. The local flight departed Reid-Hill View Airport (RHV), San Jose, California, at 1215. According to the pilot, he was flying above hilly terrain southeast of the airport when he heard a loud bang, followed by a violent vibration coming from the engine. The pilot added that the engine did not experience a total loss of power, but performed poorly due to the severe vibration. The pilot reduced the throttle and the vibration subsided, but when he added more throttle the violent vibration returned. The pilot then decided that it was unsafe to continue the flight and began searching for a place to land. He made a forced landing in a pasture, which was uneventful until one of the main landing gear contacted a "deviation" in the ground. The airplane nosed over and came to rest inverted. In a phone interview with the investigator-in-charge, a mechanic, who recovered the wreckage, reported that he examined the engine and discovered that the number 3 cylinder exhaust valve was stuck. The corresponding push rod tube was also bent, and the number 3 connecting rod was still intact.