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.
Yacolt, WA
The pilot was returning to the airport while conducting a phase 1 test flight in an experimental airplane when he detected a burning odor. He scanned the engine instruments which all showed normal indications. Shortly after, about 4 miles from his home airport, the engine shut down. He reported his position and intentions on the local radio frequency and initiated a forced landing to a down sloping field. During the landing roll the airplane impacted terrain, sustaining substantial damage to the fuselage and wings. The pilot also reported that after he exited the airplane, he didn’t see any oil or water dripping from the cowling or oil spray on the windshield. At the time of the accident the airplane had accrued 16 hours of operation. The FAA conducted a postaccident examination of the experimental airframe and engine, which revealed no preimpact mechanical malfunctions or failures that would have precluded normal operation. The pilot further reported that he found an odor from one of the engine control unit (ECU) connectors, although a review of the electrical system by the FAA did not reveal any evidence of electrical system damage. The ECU was sent to the engine manufacturer and tested normally with a functioning engine. Based on this information, the reason for the loss of engine power could not be determined.
Aircraft-Aircraft power plant-Engine (reciprocating)-(general)-Unknown/Not determined
The pilot was returning to the airport while conducting a phase 1 test flight in an experimental airplane when he detected a burning odor. He scanned the engine instruments which all showed normal indications. Shortly after, about 4 miles from his home airport, the engine shut down. He reported his position and intentions on the local radio frequency and initiated a forced landing to a down sloping field. During the landing roll the airplane impacted terrain, sustaining substantial damage to the fuselage and wings. The pilot also reported that after he exited the airplane, he didn’t see any oil or water dripping from the cowling or oil spray on the windshield. At the time of the accident the airplane had accrued 16 hours of operation. The FAA conducted a postaccident examination of the experimental airframe and engine, which revealed no preimpact mechanical malfunctions or failures that would have precluded normal operation. The pilot further reported that he found an odor from one of the engine control unit (ECU) connectors, although a review of the electrical system by the FAA did not reveal any evidence of electrical system damage. The ECU was sent to the engine manufacturer and tested normally with a functioning engine. Based on this information, the reason for the loss of engine power could not be determined.