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.
Conway, SC
According to the pilot the engine had a "slight miss". The pilot reported that he was at 1,500 feet mean sea level and initiated S-turn maneuvers in an attempt to lose altitude and perform a landing on runway 04. The pilot stated that he was still too high and began to maneuver the airplane for runway 22. He reduced the power, at which time the engine "quit." The pilot stated that he was not in a position to reach runway 22, and maneuvered the airplane to land on a small dirt road. During the forced landing, the airplane struck a pole and several trees, resulting in substantial damage. A Federal Aviation Administration inspector examined the engine. During the examination, it was reported to the inspector that the engine would run for 30 to 45 minutes, start running rough, and then stop. Fuel was traced within the system to the fuel servo. No fuel was found between the fuel servo and engine manifold. An examination of the remaining airplane systems revealed no anomalies.
the loss of engine power due to fuel starvation. The cause of the fuel starvation was not determined. Contributing to the accident was the lack of suitable terrain for a forced landing.
According to the Pilot/Operator Aircraft Accident Report form submitted by the pilot the engine had a "slight miss". The pilot reported he was at 1,500 feet mean sea level and initiated S-turn maneuvers in an attempt to lose altitude and perform a landing on runway 04. He stated that he was still too high and began to maneuver the airplane for runway 22. The pilot reduced power, at which time the engine "quit." The pilot stated that he was not in a position to reach runway 22, and maneuvered the airplane to land on a small dirt road. During the forced landing, the airplane struck a pole and several trees. The fuselage split in half at the gear mount and the right wing separated. A Federal Aviation Administration inspector examined the engine. During the examination, it was reported to the inspector that the engine would run for 30 to 45 minutes, start running rough, and then stop. Fuel was traced within the system to the fuel servo. No fuel was found between the fuel servo and engine manifold. An examination of the remaining airplane systems revealed no anomalies.