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.
Phoenix, AZ
The aircraft was on its initial test flight following construction and certification. Following takeoff, the pilot flew for nearly an hour while exploring the handling qualities of the aircraft. After returning to the airport, the pilot made a pass over the airstrip to check controllability in the landing configuration. In his statement he reported that in initiating the missed approach he 'applied full power and pulled to 55 IAS and 2.5G's at 300 feet agl . . .(then) I pushed over and reduced to 5000 rpm.' At this point, the pilot noticed a loss of rpm, followed 5 seconds later by a complete loss of engine power. He turned toward a landing site, and at 10 feet agl started to flare for touchdown. The pilot stated that the airplane was not flying and he had no control of the aircraft. The aircraft touched down hard on a dirt road. The pilot reported that the engine was free to rotate, with no evidence of internal failure. He believes the loss of power was due to a fuel system vent blockage.
The pilot's failure to maintain an adequate airspeed margin during the forced landing, which resulted in an inadvertent stall/mush.
On November 22, 1997, at 1102 hours mountain standard time, a Rans S91 experimental airplane, N9291T, collided with a dirt road following a loss of engine power at Phoenix, Arizona. The aircraft was owned and operated by the pilot/builder and was on its initial test flight following construction and certification. The aircraft sustained substantial damage and the pilot received minor injuries. The airplane departed Pinnacle Peak landing strip at 1002 for a local flight. Visual meteorological conditions prevailed. Following takeoff, the pilot flew for nearly an hour while exploring the handling qualities of the aircraft. After returning to the airport, the pilot made a pass over the airstrip to check controllability in the landing configuration. In his statement he reported that in initiating the missed approach he "applied full power and pulled to 55 IAS and 2.5G's at 300 feet agl . . .(then) I pushed over and reduced to 5000 rpm." At this point, the pilot noticed a loss of rpm, followed 5 seconds later by a complete loss of engine power. He turned toward a landing site, and at 10 feet agl started to flare for touchdown. The pilot stated that the airplane was not flying and he had no control of the aircraft. The aircraft touched down hard on the road. The pilot reported that the engine was free to rotate, with no evidence of internal failure. He believes the loss of power was due to a fuel system vent blockage.