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.
Hagatna
The airplane was climbing through 1,500 feet when the engine began to run rough. The pilot tried to smooth it out using the mixture; however, its condition worsened, and it stopped producing power altogether. The pilot could not glide to shore, and he ditched in a nearby bay. Examination of the engine revealed a hole in the top of the case at the number four cylinder. The number four connecting rod fractured and separated. After being in the salt water, the engine had corroded and could not be further disassembled. Moreover, the corrosion obscured the connecting rod fracture faces. Review of the maintenance records found that the engine had flown 1,500 hours past the manufacturer's recommended time between overhaul.
The failure of the number four connecting rod during takeoff-initial climb.
On July 15, 2006, about 1810 coordinated universal time, a pilot ditched a Cessna R172K II, N1209V, near Hagatna, Guam. Micronesia Aviation Systems, Inc., was operating the airplane under the provisions of 14 Code of Federal Regulations (CFR) Part 91. The certificated commercial pilot and two passengers sustained minor injuries; the airplane sustained substantial damage to the firewall. The local sight seeing flight departed Guam International Airport in Hagatna about 1805. Visual meteorological conditions prevailed, and no flight plan had been filed. The pilot reported to the Federal Aviation Administration that the airplane was climbing through 1,500 feet. The engine began to run rough, and he tried to smooth it out using the mixture. It began sputtering as he tried to return to the airport for a landing on runway 06L. However, it's condition worsened, and then the engine quit producing power. He ditched in a nearby bay. A Federal Aviation Inspector supervised examination of the airframe and engine. The airplane sustained damage to the firewall where the engine cradle attaches to the airframe. The cradle tweaked to the right, wrinkling the airframe just a little aft of the firewall. He observed a hole in the top of the case at the number four cylinder. He noted that the number four connecting rod fractured and separated. After being in the salt water, he reported that the engine had corroded and could not be further disassembled. The engine had been flown 1,500 hours past the manufacturer's recommended time between overhaul.