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.
Clarksville, MD
The aircraft veered off the runway during the takeoff roll and collided with trees. According to the pilot, "we did a normal run up at the point half way up the hill on runway 13. Everything looked okay, controls worked okay, carburetor heat and magnetos checked okay. We taxied to the top of the hill and attempted to take off. Within seconds after we started to roll on runway 13, the airplane veered to the left. I applied full right rudder. The airplane straightened out but it had gone too far left. With the right pedal on the floor, the airplane had straightened out fairly close to a line of small pine trees on the left side of the runway. The airplane continued parallel to the trees for about 100 feet even though I continued full right rudder. Finally, the airplane turned left into the trees." The pilot further stated that he "should have pulled power immediately when [the] airplane went out of control."
The pilot's failure to maintain directional control and failure to abort the takeoff.
On February 20, 1997, about 1645 eastern standard time, a Cessna 150, N11438, was substantially damaged when it collided with trees during the takeoff roll at the Haysfield Airport, Clarksville, Maryland. The certificated private pilot and passenger were not injured. Visual meteorological conditions prevailed for the local flight. There was no flight plan for the personal flight conducted under 14 CFR Part 91. In a statement submitted by the pilot, he stated: "We did a normal run up at the point half way up the hill on runway 13. Everything looked okay, controls worked okay, carburetor heat and magnetos checked okay. We taxied to the top of the hill and attempted to take off. Within seconds after we started to roll on runway 13, the plane veered to the left. I applied full right rudder. The plane straightened out but it had gone too far left. With the right peddle on the floor, the plane had straightened out fairly close to a line of small pine trees on the left side of the runway. The plane continued parallel to the trees for about 100 feet even though I continued full right rudder. Finally, the plane turned left into the trees." The pilot further stated that he "should have pulled power immediately when [the] plane went out of control." Examination of the wreckage by a Federal Aviation Administration Inspector did not disclose evidence of mechanical malfunction with the airplane, nor did the pilot report any. In the NTSB Form 6120.1/2, the pilot reported that the winds were from 310 degrees at 12 knots, gusting to 16.