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.
Toms River, NJ
The flight instructor reported that, during an instructional flight, he told the student to set up for landing on runway 6. When they were at an altitude of about 400 ft above ground level, the flight instructor told him to apply full power since for a go-around. When the student applied full power, the engine did not respond. The flight instructor took control of the airplane and tried to land on runway 24. The flight instructor knew they would not make the runway, so he tried to land in the grass and the left wing contacted a fence and flipped the airplane over, which resulted in substantial damage to both wings, the vertical stabilizer and horizontal stabilizer. The flight instructor stated that he thought the throttle cable had become disconnected. A postaccident examination revealed that the throttle cable was not connected to the carburetor. An AN drilled bolt was found at the bottom of the cowling; however, the castellated nut was not located. Review of the maintenance logbooks revealed that the engine had been recently overhauled and installed in the airplane. Further conversations with the flight instructor, who was also the mechanic, stated that it is possible he forgot to install the cotter pin into the castellated nut and the bolt fell out.
Loss of engine power due to the throttle linkage becoming disconnected in flight due to improper maintenance.
The flight instructor reported that, during an instructional flight, he told the student to set up for landing on runway 6. When they were at an altitude of about 400 ft above ground level, the flight instructor told him to apply full power since for a go-around. When the student applied full power, the engine did not respond. The flight instructor took control of the airplane and tried to land on runway 24. The flight instructor knew they would not make the runway, so he tried to land in the grass and the left wing contacted a fence and flipped the airplane over, which resulted in substantial damage to both wings, the vertical stabilizer and horizontal stabilizer. The flight instructor stated that he thought the throttle cable had become disconnected. A postaccident examination revealed that the throttle cable was not connected to the carburetor. An AN drilled bolt was found at the bottom of the cowling; however, the castellated nut was not located. Review of the maintenance logbooks revealed that the engine had been recently overhauled and installed in the airplane. Further conversations with the flight instructor, who was also the mechanic, stated that it is possible he forgot to install the cotter pin into the castellated nut and the bolt fell out.