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.
Fremont, OH
The pilot of the aerial application airplane reported that the airplane was near its maximum gross weight with chemicals and fuel onboard. He attempted to take off from a turf and asphalt runway that was 2,650 ft long, beginning with asphalt and then becoming turf about one-third down the runway. The pilot further stated that all engine parameters looked normal during the takeoff roll, but when he attempted to rotate, the airplane did not leave the ground. As the airplane neared the end of the runway, he “pulled” the airplane into the air to clear an 8-ft dike at the end of the runway. The airplane cleared the dike but then settled into a marshy area beyond it, contacting trees and coming to rest upright. The airplane’s fuselage and empennage were substantially damaged during the accident sequence. The pilot stated that there were no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation and that in the future, when winds are variable, it would be wise to re-assess airplane loading.
The pilot’s inadequate takeoff performance planning, which resulted in a runway overrun and collision with terrain.
The pilot of the aerial application airplane reported that the airplane was near its maximum gross weight with chemicals and fuel onboard. He attempted to take off from a turf and asphalt runway that was 2,650 ft long, beginning with asphalt and then becoming turf about one-third down the runway. The pilot further stated that all engine parameters looked normal during the takeoff roll, but when he attempted to rotate, the airplane did not leave the ground. As the airplane neared the end of the runway, he “pulled” the airplane into the air to clear an 8-ft dike at the end of the runway. The airplane cleared the dike but then settled into a marshy area beyond it, contacting trees and coming to rest upright. The airplane’s fuselage and empennage were substantially damaged during the accident sequence. The pilot stated that there were no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation and that in the future, when winds are variable, it would be wise to re-assess airplane loading.