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.
Englewood, FL
The pilot stated that prior to takeoff engine run-up was normal. He further stated that the initial takeoff roll on runway 30 was normal as well; however, about 2/3 of the length of the runway, the airspeed indicated 60 mph, so he aborted the takeoff. He said he retarded the throttle control, and applied the brakes, but the 2,040-ft runway consists of sod and sand, and it was rough and wet, so the braking action did not "work well." He said the airplane impacted the top of a 5 ft-high berm, and descended into a 8 to 10 ft-deep ditch, incurring substantial damage. On June 2, 2006, a post accident examination of the airplane and its engine was performed by an FAA inspector, as well as an FAA licensed airframe and powerplant mechanic. During the examination the engine was given a "test-run", and no preaccident anomalies were noted to exist.
The pilot's failure to abort the takeoff in time to stop on the remaining runway, which resulted in the airplane overrunning the runway.
On April 6, 2006, about 0845 eastern daylight time, an Aero Commander 100, N3602X, registered to and operated by a private individual, as a Title 14 CFR Part 91 personal flight, aborted the takeoff at Buchan Airport, Englewood, Florida. Visual meteorological conditions prevailed, and no flight plan was filed. The private-rated pilot and passenger were not injured, and the airplane incurred substantial damage. The flight was originating at the time of the accident. The pilot stated that prior to takeoff, the engine run-up was normal. He further stated that the initial takeoff roll on runway 30 was normal as well, however, about 2/3 of the length of the runway, the airspeed indicated 60 mph, so he aborted the takeoff. He said he retarded the throttle control, and applied the brakes, but the 2,040-ft runway consists of sod and sand, and it was rough and wet, so the braking action did not "work well." He said the airplane impacted the top of a 5 ft-high berm, and descended into a 8 to 10 ft-deep ditch, incurring substantial damage On June 2, 2006, a post accident examination of the airplane and its engine was performed by an FAA inspector, as well as an FAA licensed airframe and powerplant mechanic. During the examination the engine was given a "test-run", and no preaccident anomalies were noted to exist.