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.
Winston-Salem, NC
The pilot stated that before takeoff, he checked the aircraft fuel supply and elected not to refuel. He reported that during examination of the fuel supply, the fuel supply in the left wing tank was two inches below the filler cap, and the right fuel gauge showed 1/4 tank. The pilot thought he had ample fuel for the 269 mile flight to the destination airport. Before reaching his destination, the pilot advised an air traffic controller that he was experiencing engine problems and requested assistance to the nearest airport. Moments later, he reported that the engine was running again, and he wanted to continue the flight to the destination airport. About five miles from the airport, the pilot reported that the engine had quit again. Subsequently, during a forced landing, the airplane collided with a utility pole and lines. Examination of the airplane failed to disclose a mechanical problem or system malfunction. There was no fuel recovered from the aircraft fuel system during field examination of the airframe.
the pilot's improper planning/decision, which resulted in fuel exhaustion, loss of engine power, and a forced landing.
On September 27, 1997, at 1710 eastern daylight time, a Beech 33, N331DP, collided with a utility pole while attempting an emergency landing to a field eight miles southwest of Winston-Salem, North Carolina. The pilot operated the personal flight under the provisions of Title 14 CFR Part 91 with no flight plan filed. Visual weather conditions prevailed at the time of the accident. The airplane sustained substantial damage, and the private pilot and the three passengers were not injured. The flight departed Jasper, Georgia, at 1455. The pilot stated that before departing Jasper he checked the aircraft fuel supply and elected not to refuel. During the examination of the fuel supply, he reported that the fuel supply in the left wing tank was two inches below the filler cap. The right fuel gauge showed 1/4 tank. The pilot thought he had ample fuel for the 269 mile fight back to Winston Salem. At 1640, the pilot advised Greensboro Tower that he was experiencing engine problems and requested assistance to the nearest airport. Moments later, the pilot told the tower controller that the engine was running again, and he wanted to continue the flight to Winston-Salem. At approximately 1647, the pilot reported that the engine had quit again; the airplane collided with the utility pole and lines during the forced landing. Examination of the airplane failed to disclose a mechanical problem or system malfunction. There was no fuel recovered from the aircraft fuel system during the field examination of the airframe. The pilot stated that more fuel should have been put into the right tank before he departed.