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.
Dunbar, PA
The pilot reported that the purpose of the flight was to test cooling plenum changes that he had recently made to the experimental amateur-built airplane’s automotive conversion engine. After takeoff on the planned flight in the airport traffic pattern, the pilot heard over the radio that another airplane was inbound to the airport for touch-and-go landings, so he flew away from the airport and performed ground reference maneuvers. Shortly after, the pilot returned to the traffic pattern, entering on the upwind leg. Upon turning onto the crosswind leg, his engine began to “sputter”, so he made a 180° turn to land on the opposite direction of the same runway. About that time, he noticed that the other airplane was back taxiing on the runway. He elected to not land on the parallel taxiway due to its condition and out of concern for a possible collision with another aircraft. The pilot overflew the other airplane on the runway, and shortly thereafter his airplane’s engine lost power completely as he neared the end of the runway. About that time the pilot was turning the airplane left, but could feel it slowing, so he leveled the wings and landed straight ahead, perpendicular to the runway. The airplane subsequently traveled over a grass embankment and contacted trees, resulting in substantial damage to the right wing and fuselage structure. The pilot stated that following the accident, an examination of the engine revealed that a bracket for the fuel/air mixture cable had “bent and overextended,” which resulted in the engine’s fuel/air mixture becoming excessively lean. The pilot stated that he had fabricated the bracket during a recent engine replacement and knew that a new bracket would need to be refabricated but had not completed the task it before the accident flight. Based on this information, it is likely that the loss of engine power was the result of the improperly fabricated bracket, which resulted in an excessively lean mixture to the airplane’s engine.
A total loss of engine power as a result of an improperly fabricated fuel-air mixture cable bracket. Contributing was the pilot’s decision to fly the airplane with a known mechanical engine issue, and the presence of another airplane that was back taxiing on the runway while the pilot was attempting to maneuver the airplane for landing.
The pilot reported that the purpose of the flight was to test cooling plenum changes that he had recently made to the experimental amateur-built airplane’s automotive conversion engine. After takeoff on the planned flight in the airport traffic pattern, the pilot heard over the radio that another airplane was inbound to the airport for touch-and-go landings, so he flew away from the airport and performed ground reference maneuvers. Shortly after, the pilot returned to the traffic pattern, entering on the upwind leg. Upon turning onto the crosswind leg, his engine began to “sputter”, so he made a 180° turn to land on the opposite direction of the same runway. About that time, he noticed that the other airplane was back taxiing on the runway. He elected to not land on the parallel taxiway due to its condition and out of concern for a possible collision with another aircraft. The pilot overflew the other airplane on the runway, and shortly thereafter his airplane’s engine lost power completely as he neared the end of the runway. About that time the pilot was turning the airplane left, but could feel it slowing, so he leveled the wings and landed straight ahead, perpendicular to the runway. The airplane subsequently traveled over a grass embankment and contacted trees, resulting in substantial damage to the right wing and fuselage structure. The pilot stated that following the accident, an examination of the engine revealed that a bracket for the fuel/air mixture cable had “bent and overextended,” which resulted in the engine’s fuel/air mixture becoming excessively lean. The pilot stated that he had fabricated the bracket during a recent engine replacement and knew that a new bracket would need to be refabricated but had not completed the task it before the accident flight. Based on this information, it is likely that the loss of engine power was the result of the improperly fabricated bracket, which resulted in an excessively lean mixture to the airplane’s engine.