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.
Bakersfield, CA
According to the pilot, he configured the flaps to 20° while he waited for the aerial application airplane to take on 50 gallons of fuel and 400 pounds of fertilizer. He taxied onto the 2,600 ft long asphalt runway, for his 4th aerial application flight of the day. The pilot applied brakes and full power before he released the brakes to initiate the takeoff roll. About 1,300 ft down the runway, the airplane remained on the ground. The pilot applied back pressure to the control stick and the airplane ascended about 10 feet above ground level. The airplane would not climb, and the pilot applied full flaps. The airplane subsequently settled back onto the remaining 1/3rd of the runway. The pilot reported that he did not observe any cockpit instrument cautions or warnings illuminated. The airplane overran the departure end of the runway and collided with trees. The manufacturer’s airplane flight manual (AFM) contains a warning that stated, when taking off from a short-field runway, full flaps should not be used during the takeoff sequence. The use of full flaps creates large amounts of drag, lengthens the ground roll, and impairs climb performance. The pilot submitted an NTSB Form 6120.1, Pilot Aircraft Accident Report, but did not include pages 9 and 10, which encompassed the pilot’s narrative, and his assertion regarding a mechanical malfunction during the sequence of events.
The pilot’s improper use of flaps during the takeoff sequence which resulted in a runway overrun and collision with trees.
According to the pilot, he configured the flaps to 20° while he waited for the aerial application airplane to take on 50 gallons of fuel and 400 pounds of fertilizer. He taxied onto the 2,600 ft long asphalt runway, for his 4th aerial application flight of the day. The pilot applied brakes and full power before he released the brakes to initiate the takeoff roll. About 1,300 ft down the runway, the airplane remained on the ground. The pilot applied back pressure to the control stick and the airplane ascended about 10 feet above ground level. The airplane would not climb, and the pilot applied full flaps. The airplane subsequently settled back onto the remaining 1/3rd of the runway. The pilot reported that he did not observe any cockpit instrument cautions or warnings illuminated. The airplane overran the departure end of the runway and collided with trees. The manufacturer’s airplane flight manual (AFM) contains a warning that stated, when taking off from a short-field runway, full flaps should not be used during the takeoff sequence. The use of full flaps creates large amounts of drag, lengthens the ground roll, and impairs climb performance. The pilot submitted an NTSB Form 6120.1, Pilot Aircraft Accident Report, but did not include pages 9 and 10, which encompassed the pilot’s narrative, and his assertion regarding a mechanical malfunction during the sequence of events.