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.
Sutton, WV
The pilot reported that he was concerned with the field elevation, airplane weight, heat, and humidity before the flight. During the takeoff roll, the airplane had a slower acceleration and longer takeoff roll than normal. The pilot considered aborting the takeoff twice, but was concerned that there was not enough available runway to land, and felt that he would be able to out climb the terrain located at the end of the runway. After bouncing twice on the runway, the airplane began to climb in ground effect, about 100 feet per minute. When the pilot realized that he would not clear the terrain, he lowered the nose in an attempt to gain airspeed. He located an area of lower terrain, made a shallow right turn, and attempted to fly through the area; however, the airplane sank into the trees and rolled. The pilot stated that the engine sounded as if it was producing full power, and that he was unfamiliar with the airplane's high density altitude performance capabilities.
The pilot's failure to abort the takeoff in a timely manner. Factors included the high density altitude conditions, and the pilot's lack of familiarity with the airplane's high density altitude performance characteristics.
On June 13, 2003, at 1915 eastern daylight time, a Boeing Stearman PT17, N55175, was substantially damaged when it collided with trees and terrain during take-off from Braxton County Airport (48I), Sutton, West Virginia. The certificated airline transport pilot and the passenger were not injured. Visual meteorological conditions prevailed, and no flight plan was filed for the local personal flight conducted under 14 CFR Part 91. In a written statement, the pilot said he was concerned with the field elevation (1,270 feet msl), aircraft weight, heat, and humidity before the flight. He elected to depart to the north (runway 01) where the terrain appeared to be lower than to the south, and the winds appeared calm. During the takeoff roll, the pilot felt a "slightly slower acceleration than normal." After an "abnormally" long takeoff roll, and bouncing twice on the runway, the airplane began to climb in ground effect. The pilot said that he considered aborting the takeoff twice, but was concerned that there was not enough available runway to land, and felt that he would be able to out climb the terrain located at the end of the runway. As the airplane left ground effect, its climb rate was "barely" 100 feet per minute. When the pilot realized that he would not clear the terrain, he lowered the nose in an attempt to gain airspeed. He located an area of lower terrain, made a shallow right turn, and attempted to fly through the area. However, the airplane sank into the trees and rolled. During the flight, the pilot verified that the throttle was full forward and the engine instruments indicated full power. He said the engine sounded as if it was "normally producing full power." The pilot reported two causes of the accident; "the aircraft's heavy weight with 3/4 fuel and heavy weight of the crew", and "the pilot's unfamiliarity with the aircraft's performance in high-density altitude operations." The pilot also reported a total of 2,450 flight hours, of which, 12 flight hours were in make and model. Runway 01 was a 4,000-foot-long and 60-foot-wide asphalt runway. A Federal Aviation Administration (FAA) Inspector examined the wreckage on June 14, 2003. According to the inspector, the left top and bottom wings exhibited impact damage, and the right top and bottom wings were separated from the airplane. The propeller and tail control surfaces were also damaged. The weather at Braxton County Airport, at 1851, was reported as winds from 270 degrees at 5 knots, temperature 73 degrees F, dewpoint 63 degrees F, and barometric pressure setting of 29.92 inches Hg. The visibility was 10 statute miles and clear skies.