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.
Springdale, AR
While practicing simulated engine out procedures, the flight instructor (CFI) 'pulled the mixture off to simulate [an] engine failure.' When the student pilot did not turn towards a field to land the airplane, the CFI took the controls and attempted unsuccessfully to restart the engine. During an approach for a forced landing in an open field, the airplane hit a barbed wire fence, damaging the left horizontal stabilizer, cowling, and fuselage. The airplane touched down 30 to 50 feet beyond the fence and came to a stop without further damage. After landing, the instructor 'restarted the engine to trouble-shoot, but found no trouble as it started immediately.' FAA publication AC 61-21A stated that the throttle should be used to simulate an engine failure.
the flight instructor's improper (unapproved) procedure of using the mixture control to simulate an engine failure. A factor relating to the accident was: the lack of suitable terrain for a forced landing.
On May 11, 1996, at 0905 central daylight time, a Cessna 150M, N704RS, owned and operated by Bassett Flight Center, Inc., sustained substantial damage during a forced landing near Springdale, Arkansas. The certificated flight instructor and his student were not injured. Visual meteorological conditions prevailed for the Title 14 CFR Part 91 instructional flight. The flight originated at Springdale Municipal Airport, Springdale, Arkansas, at 0825. The flight instructor reported that, while practicing simulated engine out procedures, he had "pulled the mixture off to simulate [an] engine failure." When the student pilot did not turn towards a field to land the airplane, he took the controls and attempted unsuccessfully to restart the engine. During the approach to an open field, the airplane hit a barbed wire fence damaging the left horizontal stabilizer, cowling, and fuselage. The airplane touched down 30 to 50 feet beyond the fence and came to a stop without further damage. The flight instructor further reported that, after landing, "I restarted the engine to trouble-shoot, but found no trouble as it started immediately." FAA publication AC 61-21A states in Chapter 9 - Landing Approaches and Landings\Emergency Approaches (simulated) that, "The instructor should give simulated forced landings by retarding the throttle and calling 'Simulated Forced Landing.'"