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.
Alfalfa, OR
The commercial pilot/owner, an airframe and powerplant mechanic with inspection authorization privileges, performed an annual inspection on the airplane in order to return it to service after it had been in storage for about 2 years. Ground engine run-up checks revealed no discrepancies, and he decided to perform a test flight. After takeoff, the engine sputtered and lost power, and the pilot returned to the airport for a precautionary landing. The airplane overran the runway, struck a tire, and came to rest inverted. A postaccident engine run revealed no mechanical discrepancies that would have precluded normal operation. The reason for the loss of engine power was not determined.
A total loss of engine power after takeoff for reasons that could not be determined, because examination of the engine did not reveal any mechanical anomalies that would have precluded normal operation.
On February 17, 2015, at 1819 Pacific standard time, a Grumman Aircraft Eng. Corp-Schweizer G-164A airplane, N4863, experienced a loss of engine power during takeoff on a local area flight from the Goering Ranches Airport (50OR), Alfalfa, Oregon. The commercial pilot/owner operated the airplane under the provision of 14 Code of Federal Regulations Part 91 as a maintenance test flight. The pilot was not injured, and the airplane sustained substantial damage. Visual meteorological conditions prevailed for the flight that departed 50OR about 1815.According to the pilot, the airplane had been in storage for the past 2 years. He stated that he was also an airframe and power plant mechanic with inspection authorization privileges, and he had recently finished an annual inspection of the airplane. His intent was to perform a maintenance return to service flight. The pilot stated that the airplane had 25 gallons of fuel on board. He performed two 45-minute run-ups with no discrepancies encountered. The pilot stated that he then readied the airplane for the maintenance flight. After takeoff, the engine sputtered and lost power. The pilot returned to land at 50OR, but overran the runway. The airplane struck a tire, and came to rest inverted, which caused structural damage to the tail section. The pilot/owner did not return the National Transportation Safety Board Form 6120.1 titled Pilot Operator Accident/Incident Form. A Federal Aviation Administration (FAA) inspector, inspected the airplane, and performed an engine run-up. The visual inspection revealed that the propeller blades were bent, but there was enough clearance to perform an engine run. Fuel samples were obtained from both wings and the sump; the fuel samples were free of debris, and no water was present. The engine started with no issues, and the engine was run at 700 rpm. They were able to perform a magneto check during the engine run with no discrepancies encountered. They were not able to perform the run up at a higher rpm, due to engine vibration.