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.
Reno, NV
The pilot reported that he was flying as one of a group of seven airplanes in an air race, and, during lap four, the engine lost all power. The pilot increased altitude to 2,000 feet above ground level and entered the landing pattern but had to extend his downwind to avoid traffic still on the race course. The wind took him further away from the runway than he intended so that when he turned toward the runway, he could not complete the turn to the runway heading, and intercepted the runway on a 50-degree angle at an intersection with another runway. The airplane rolled across the intersection, onto a taxiway, and continued onto a dirt ramp before cartwheeling and coming to rest in the dirt about halfway between the taxiway and the runway. Postaccident examination of the engine found that a connecting rod bearing and two connecting rods in the engine fractured and separated, which resulted in the loss of engine power.
Failure of a connecting rod bearing and two connecting rods, which resulted in a loss of engine power while maneuvering at low altitude.
On September 19, 2010, about 1600 Pacific daylight time, an experimental Giboney Thunder Mustang, N151G, collided with terrain during landing at Reno/Stead Airport, Reno, Nevada. The pilot/owner was operating the airplane under the provisions of 14 Code of Federal Regulations (CFR) Part 91. The private pilot sustained minor injuries. The airplane sustained substantial damage to the wings, fuselage, and empennage. The local air race flight departed about 1545. Visual meteorological conditions prevailed, and no flight plan had been filed. The pilot was flying as one of a group of seven airplanes in a race at the Reno National Championship Air Races. He was passing pylon 5 on lap four when the airplane’s engine lost all power. He climbed the airplane to 2,000 feet above ground level (agl). Based on his position and the wind direction, he decided to land on runway 26. He entered the landing pattern, but had to extend his downwind to avoid traffic still on the race course. The wind took him further away from the runway than he intended. When he turned toward the runway, he had insufficient altitude to align with the runway. The pilot stated that the airplane was heading 210° when it touched down on the east side of the intersection of runway 26 and runway 14/32. The airplane rolled across the intersection and onto taxiway A1. The airplane continued across the taxiway onto a dirt ramp, which pitched the airplane up into the air, but below flying speed. He maintained full right rudder and full up elevator; the right wing dropped until it contacted the ground. The airplane cartwheeled twice, and the airplane came to rest in the dirt about halfway between taxiway A1 and runway 26. The pilot reported that a connecting rod bearing and two connecting rods fractured and separated.