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.
Woodstock, AL
About 30 minutes after refueling, and at a cruise altitude of about 2,000 feet, the engine failed. The pilot attempted to restart the engine during the forced landing. The engine failed to restart; the airplane glided short of intended off-airport landing area, and struck the top of a tree. After striking the tree the airplane went nose first into a marshy area. The engine was equipped with a dual electronic ignition, controlled by a computer in conjunction with a computer driven fuel compensation unit. The electronic equipment was damaged beyond testing capability. The factory representative for the engine company stated, '...that he believed the malfunction was the result of one or more computers.' Due to impact damage to the electronic components, the cause of the engine failure was not determined.
a total engine failure for undetermined reason, resulting in a forced landing and subsequent impact with a tree.
On April 13, 2000, about 1610 central standard time, a homebuilt Hartline Glastar, N897G, owned by a private individual impacted with trees during a forced landing near Woodstock, Alabama. Visual meteorological conditions prevailed at the time, and no flight plan was filed for the 14 CFR Part 91 personal flight. The airplane was substantially damaged. The two private-rated pilots reported serious injuries. The flight had departed Sylacauga, Alabama, at 1630, en route to Paducah, Kentucky. According to the FAA inspector's statement, "...the pilot was flying at cruise flight for about 30 minutes after refueling...at approximately 2,000 feet, the engine failed. The pilot attempted to restart during a glide to [a] suitable landing area. The engine failed to restart, aircraft glided short of intended off-airport landing area, struck the top of a tree...." After striking the tree the airplane went nose first into a marshy area. In addition, the inspector stated, "...this engine has a dual electronic ignition controlled by a computer in conjunction with a computer driven fuel compensation unit. The electronic equipment was damaged beyond our testing capability and the aircraft and engine were released...with follow-up by the factory...the factory rep [sic] for NSI [engine]...stated that he believed the malfunction was the result of one or more computers. This accident had undetermined causes...."