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.
Roseburg, OR
The experimental aircraft had not been flown in a year, and the fuel system, including the electrical and engine driven fuel pumps, had been modified and adjusted over the previous year, as had the carburetor. Shortly after takeoff, the engine stopped operating and the pilot maneuvered the aircraft in a left 180-degree descending turn to land downwind on runway 16. The aircraft landed long, rolled off the upwind end of the runway and collided with a fence. The winds at the airport were from 340 degrees magnetic at 8 knots. An FAA inspector examined the aircraft's engine and found no evidence of a mechanical malfunction.
A total loss of power for undetermined reasons and the pilot's misjudgment of distance and speed while maneuvering to a forced landing at a nearby airport. Contributing factors were the 8 knot tailwind and the fence which the aircraft impacted when it over ran the upwind end of the runway.
On July 24, 2001, approximately 2020 Pacific daylight time, a Hutton KR-2 homebuilt aircraft, N4GJ, registered to and being flown by a private pilot, was substantially damaged when it impacted a chain link fence during the landing roll following a total loss of power while maneuvering. The aircraft was executing an emergency landing at the Roseburg Regional Airport, Roseburg, Oregon. The pilot was uninjured. Visual meteorological conditions existed and no flight plan had been filed. The flight, which was personal, was operated under 14 CFR 91, and originated from Roseburg approximately 5 minutes earlier. The pilot reported that the aircraft had not been flown in about a year. He had taken off with the intention of remaining in the vicinity of the Roseburg airport and reported having six gallons of gas in each wing tank. While established on a northerly heading slightly east of the airport, the engine began to sputter and lost all power within about five seconds. The pilot executed a left 180-degree descending turn to land downwind on runway 16 at Roseburg. The aircraft landed long, rolled off the upwind end of the runway and collided with a fence. Winds at Roseburg at 1953 local were from 340 degrees magnetic at 8 knots. An inspector from the FAA's Hillsboro, Oregon, Flight Standards District Office examined the aircraft and it's records following the accident. He reported finding no mechanical malfunction with the aircraft's engine. The pilot/owner reported to the inspector that the fuel system, including the electrical and engine driven fuel pumps, had been modified and adjusted over the previous year, as had the carburetor. Additionally, the inspector noted that there was no record of a condition inspection within the aircraft's logbook.