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.
Danbury, CT
The student pilot was in the traffic pattern practicing touch and go landings, when the flight instructor reduced the engine power to idle to simulate an engine failure. While the student pilot was maneuvering, the airplane "stalled to the left." The CFI assumed control of the airplane; however, the airplane struck trees about 1/2 mile from the runway. The CFI added that he did not hear the airplane's stall warning horn annunciate at any time during the accident sequence. Examination of the airplane did not reveal any mechanical malfunctions. The airplane's stall warning system functioned normally during post accident testing. The terrain at the accident site sloped upward.
The student pilot's failure to maintain airspeed and the flight instructor's delayed remedial action, which resulted in an inadvertent stall during a simulated forced landing. A factor was the rising terrain.
On August 5, 2002, about 1945 eastern daylight time, a Cessna 152, N89044, was substantially damaged when it impacted trees during a simulated forced landing in Danbury, Connecticut. The certificated flight instructor (CFI) and student pilot sustained minor injuries. Visual meteorological conditions prevailed and no flight plan had been filed for the instructional flight that departed the Danbury Municipal Airport (DXR), Danbury, Connecticut. The flight was conducted under 14 CFR Part 91. During an interview with a Federal Aviation Administration (FAA) inspector, the CFI stated that the airplane was in the traffic pattern for runway 26, at DXR, and the student pilot was practicing touch and go landings. When the airplane was at an altitude of about 1,200 feet, the CFI reduced the engine power to idle, to simulate an engine failure. While the student pilot was maneuvering, the airplane "stalled to the left." The CFI assumed control of the airplane; however, the airplane struck trees about 1/2 mile from the runway. The CFI added that he did not hear the airplane's stall warning horn annunciate at any time during the accident sequence. Examination of the airplane by an FAA inspector did not reveal any mechanical malfunctions. The airplane's stall warning system functioned normally during post accident testing. Additionally, the inspector noted that the terrain at the accident site sloped upward. Winds reported at the airport around the time of the accident were calm.