Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

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.

FAQs

NTSB Report

May 31, 2014 · Cessna 172F · N8394U

Mount Pleasant, PA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
May 31, 2014
Injury Outcomes
1 injury (1 minor injury), 1 uninjured
Location
Mount Pleasant, PA
Aircraft
Cessna 172F (1964)
Tail Number
N8394U
Operator
Daniels Arvin R
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
ERA14CA278

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.

NTSB Probable Cause

The pilot's incorrect takeoff procedures from the soft grass runway and his delay in aborting the takeoff after recognizing slow acceleration.

Full Narrative

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.

Flight

Event TypeAccident
Event Time12:30 EDT
Nearest AirportMount Pleasant/Scottsdale (0nm)
Runway32
Runway Length1641 ft
Runway Width175 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172F
Tail NumberN8394U
Aircraft CategoryAir
DamageSubstantial
OperatorDaniels Arvin R
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsCont Motor · 0-300 SER · Reciprocating · 145
Seats4

People & Injuries

Injury Summary1 injury (1 minor injury), 1 uninjured
Fatal0
Serious0
Minor1
Uninjured1
Total2
Crew 1Age 73 · Third Class · Minor

Conditions

ConditionsVMC
LightDaylight
Wind350° @ 5 kt
Visibility10 sm
CeilingBroken clouds 5000 ft
Temperature / Dew Point52
Altimeter30.22 inHg
Observation Time16:40
Weather SourceWFAC

Appendix: Source Data