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.
Mount Pleasant, PA
The pilot stated that the preflight and engine run-up were satisfactory prior to the departure from the 1,641 foot long grass runway; the grass was a little high (estimated to be 5 to 6 inches) and soft due to rain from earlier that week. He consulted the POH and confirmed no flaps for the takeoff. After the engine run-up he taxied onto runway 32 and with the flaps retracted, applied full throttle noting 2,200 rpm, then released the brakes; the wind was from the northwest at 3 to 5 knots. He did not begin the takeoff roll utilizing soft field takeoff procedure of aft control input but did as the takeoff roll continued; later reporting that he "probably didn't initially have the yoke back enough." After a little more than ½ way down the runway at an airspeed less than 50 mph, he aborted the takeoff. Unable to stop, the airplane impacted a guard rail at the end of the runway causing the airplane to nose over. He further stated that there was no preimpact mechanical failures or malfunctions with the airplane that would have precluded normal operation. He did state in the Recommendation Section of the submitted NTSB Pilot/Operator Aircraft Accident/Incident report that the accident might have been prevented by better assessment of the conditions/effects of the grass (softness) and length of the runway, and to either not initiate takeoff or abort sooner. He also indicated that the accident might have been prevented if, "…a perfect soft/short field technique was used." Postaccident inspection of the airplane by a Federal Aviation Administration airworthiness inspector revealed substantial damage to the right wing spar and structure adjacent to the left main landing gear attach point. Another FAA inspector reported no obstructions at the departure end of runway 32. A review of the airplane Owner's Manual indicates 0 flap extension is specified for normal and maximum performance takeoff; however, 10 degrees of flaps is specified to be used for minimum ground runs or for takeoff from soft or rough fields with no obstacles ahead. The takeoff performance chart does not indicate distances for grass runway. Excerpts of the Owner's Manual are contained in the NTSB public docket.
The pilot's incorrect takeoff procedures from the soft grass runway and his delay in aborting the takeoff after recognizing slow acceleration.
The pilot stated that the preflight and engine run-up were satisfactory prior to the departure from the 1,641 foot long grass runway; the grass was a little high (estimated to be 5 to 6 inches) and soft due to rain from earlier that week. He consulted the POH and confirmed no flaps for the takeoff. After the engine run-up he taxied onto runway 32 and with the flaps retracted, applied full throttle noting 2,200 rpm, then released the brakes; the wind was from the northwest at 3 to 5 knots. He did not begin the takeoff roll utilizing soft field takeoff procedure of aft control input but did as the takeoff roll continued; later reporting that he "probably didn't initially have the yoke back enough." After a little more than ½ way down the runway at an airspeed less than 50 mph, he aborted the takeoff. Unable to stop, the airplane impacted a guard rail at the end of the runway causing the airplane to nose over. He further stated that there was no preimpact mechanical failures or malfunctions with the airplane that would have precluded normal operation. He did state in the Recommendation Section of the submitted NTSB Pilot/Operator Aircraft Accident/Incident report that the accident might have been prevented by better assessment of the conditions/effects of the grass (softness) and length of the runway, and to either not initiate takeoff or abort sooner. He also indicated that the accident might have been prevented if, "…a perfect soft/short field technique was used."Postaccident inspection of the airplane by a Federal Aviation Administration airworthiness inspector revealed substantial damage to the right wing spar and structure adjacent to the left main landing gear attach point. Another FAA inspector reported no obstructions at the departure end of runway 32. A review of the airplane Owner's Manual indicates 0 flap extension is specified for normal and maximum performance takeoff; however, 10 degrees of flaps is specified to be used for minimum ground runs or for takeoff from soft or rough fields with no obstacles ahead. The takeoff performance chart does not indicate distances for grass runway. Excerpts of the Owner's Manual are contained in the NTSB public docket.