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.
Decatur, TX
The engine started to run rough about a minute after takeoff. The 475-hour student pilot reported a 500 RPM drop. The pilot applied carburetor heat and switched fuel tanks, but neither resulted in an increase in engine power. The pilot leveled-off at approximately 600 feet above the ground. About 3 or 4 minutes into the flight, a severe engine vibration developed and the pilot elected to shut-down the engine and attempted to land in a pasture approximately two miles from the airport. During the landing roll the airplane impacted a fence resulting in structural damage to the wings and additional damage to the propeller. A Federal Aviation Administration inspector that traveled to the accident site noted the airplane's engine chip detector light was illuminated and that the propeller was hard to pull through. The reason for the loss or engine power could not be determined.
The loss of engine power for undetermined reasons. A contributing factor was the lack of suitable terrain for the forced landing.
The engine started to run rough about a minute after takeoff. The 475-hour unrated pilot reported a 500 RPM drop. The pilot applied carburetor heat and switched fuel tanks, but neither resulted in an increase in engine power. The pilot leveled-off at approximately 600 feet above the ground. About 3 or 4 minutes into the flight, a severe engine vibration developed and the pilot elected to shut-down the engine down and attempt to land in a pasture approximately two miles from the airport. During the landing roll the airplane impacted a fence resulting in structural damage to the wings and additional damage to the propeller. A Federal Aviation Administration inspector that traveled to the accident site noted the airplane's engine chip detector light was illuminated and that the propeller was hard to pull through. The reason for the loss or engine power could not be determined.