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.
Flushing, MI
Witnesses observed the airplane flying on an easterly heading when it began a turn to the north. As the airplane was turning, it lost altitude and collided with trees, small vegetation, and the ground. The pilot told the State Police he did not think that his altitude was low enough to strike the trees. The on-scene investigation revealed no mechanical anomalies with the airplane or engine that would prevent flight. The pilot did not respond to calls or requests for submission of an accident report from the IIC.
was the pilot not maintaining sufficient altitude to clear obstructions. A factor associated with the accident was the pilot was inattentive to the airplane's altitude.
On May 20, 1997, at 1710 eastern daylight time (edt), a Cessna 172, N8811Z, piloted by a private pilot, was destroyed during a collision with trees, small vegetation, and terrain, while on a landing approach to runway 27 (1,850' X 150' dry sod) at the Flushing-Daltons Airport, Flushing, Michigan. The flight was not operating on a flight plan. Visual meteorological conditions prevailed at the time of the accident. The pilot reported minor injuries. The flight departed Flint, Michigan, at 1645 edt. Witnesses said they saw the airplane flying on an easterly heading when it began a turn to the north. They said the airplane lost altitude during its turn to the north. According to the State of Michigan airplane accident report, the pilot said he "...did not see the tree line and struck the trees... ." The report continues, "[The pilot] did not think his altitude was too low... ." The on-scene investigation revealed no mechanical anomalies with the airplane's engine, airframe, or flight control system that would prevent flight. The pilot reportedly confirmed this according to the Federal Aviation Administration Principal Maintenance Inspector's report. The pilot was sent two NTSB 6120.1/2, Pilot Operator Accident Report Form, and has not returned either one. He has not responded to telephone calls from the NTSB investigator-in-charge to discuss the events surrounding the accident. Information received from the pilot's airplane insurance company showed he had a total time of 774.5 hours on July 31, 1996. The insurance company broker said the pilot had 695 hours in Cessna 172 airplanes.