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.
Bremerton, WA
The pilot stated that he began the cross-country flight with 4 hours of fuel onboard for the estimated 3-hour flight. While over an airport along the route of flight, he found that the headwind was much stronger than forecast. He calculated that he had 1 hour of fuel remaining and that the remaining flight time to his destination was 30 minutes. As he approached his destination, he was receiving vectors from an air traffic controller when the airplane’s engine sputtered and stopped producing power. The pilot successfully restarted the engine. However, it soon stopped producing power again and would not restart. In the dark night, he performed a forced landing to a small opening in the trees. The first rescue personnel on scene reported that they did not detect the smell of aviation fuel and the pilot reported to rescuers that “he believed he had run out of fuel and that the engine just quit on him.” The airplane’s fuselage was bent upwards immediately behind the cabin area, and both wings were bent and wrinkled.
The total loss of engine power as a result of fuel exhaustion due to the pilot's inadequate in-flight planning.
The pilot stated that he began the cross-country flight with 4 hours of fuel onboard with an estimated 3 hours en route. During the flight, while over an airport along the route of flight, he found that the headwinds were much stronger than forecast. He calculated that he had 1 hour of fuel remaining, and that the remaining flight time to his destination was 30 minutes. As he approached his destination, he was receiving vectors from an air traffic controller when the airplane’s engine sputtered and stopped producing power. The pilot successfully restarted the engine. However, soon thereafter, it stopped producing power again, and this time it would not restart. In dark night light conditions, he performed a forced landing to a small opening in the trees. The first rescue personnel on scene reported that they did not “smell an obvious odor of aviation fuel.” Additionally, the pilot reported to rescuers that “he believed he had run out of fuel and that the engine just quit on him.” The airplane’s fuselage was bent upwards immediately behind the cabin area, and both wings were bent and wrinkled.