# NTSB ERA14CA278: Cessna 172F, N8394U, Mount Pleasant, PA, May 31, 2014 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Data collection · Final report - Date: May 31, 2014, 12:30 local (16:30 UTC) - Place: Mount Pleasant, PA - Coordinates: 40.10889, -79.546943 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=40.1089&lon=-79.5469&mi=10 - Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping) - Defining event: [Takeoff-rejected takeoff: Runway excursion](https://openairdocs.org/ntsb-events/300) - Highest injury: Minor injuries - Injuries: 1 minor, 1 uninjured - Status: Completed, report September 2, 2014 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 89356 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA14CA278 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/89356/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=89356 - Page: https://openairdocs.org/ntsb/ERA14CA278 ## Probable cause The pilot's incorrect takeoff procedures from the soft grass runway and his delay in aborting the takeoff after recognizing slow acceleration. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Action: delayed action](https://openairdocs.org/ntsb-findings/02041025): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna 172F, 2 cases](https://openairdocs.org/ntsb-findings/02041025/cases.md?model=2072414), [All aircraft, 894 cases](https://openairdocs.org/ntsb-findings/02041025/cases.md) - [Flight control system: tE flap control system](https://openairdocs.org/ntsb-findings/01022750): Aircraft › Aircraft systems · Not used/operated (probable cause); cases with it: [Cessna 172F, 1 case](https://openairdocs.org/ntsb-findings/01022750/cases.md?model=2072414), [All aircraft, 74 cases](https://openairdocs.org/ntsb-findings/01022750/cases.md) - [Runway/land/takeoff/taxi surface: soft surface](https://openairdocs.org/ntsb-findings/03023020): Environmental issues › Physical environment · Effect on operation; cases with it: [Cessna 172F, 1 case](https://openairdocs.org/ntsb-findings/03023020/cases.md?model=2072414), [All aircraft, 264 cases](https://openairdocs.org/ntsb-findings/03023020/cases.md) - [Object/animal/substance: fence/fence post](https://openairdocs.org/ntsb-findings/03022047): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Cessna 172F, 2 cases](https://openairdocs.org/ntsb-findings/03022047/cases.md?model=2072414), [All aircraft, 313 cases](https://openairdocs.org/ntsb-findings/03022047/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Takeoff-rejected takeoff: Runway excursion](https://openairdocs.org/ntsb-events/300) (defining event); cases with it: [Cessna 172F, 7 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2072414), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Takeoff-rejected takeoff: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 172F, 22 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072414), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis 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. ## Factual 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. ## Aircraft - Registration: [N8394U](https://openairdocs.org/deregistered/N8394U-2018-03-07), registration cancelled 2018-03-07, S/N 17252294, built 1964 (OpenAirDocs) - Reported make and model: CESSNA 172F - Registry model: [Cessna 172F](https://openairdocs.org/model/cessna-172f) (registry code 2072414) (OpenAirDocs) - Registry engine: [Continental 0-300 series](https://openairdocs.org/engine/continental-0-300-series) (registry code 17022, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17252294 - Year built: 1964 - Airframe hours: 3926 - Engines: CONT MOTOR 0-300 SER 145 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Daniels Arvin R - Registered owner: Daniels Arvin R - Airworthiness certificate: Standard, Utility; Standard, Normal - Last inspection: Annual, May 21, 2014 - Departed: P45, Mount Pleasant, PA - Destination: P45, Mount Pleasant, PA - Airport: P45, Mount Pleasant/Scottsdale, runway 32, 1,641 × 175 ft, grass/turf - Equipment: Stall warning system ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 73; injuries: minor; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review August 16, 2013; seat: left; restraint: lap only; flight hours: 282 total, 69 in this make and model, 205 as pilot in command, 6 in the last 90 days, 1 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 350° at 5 knots - Visibility: 10 statute miles - Lowest ceiling: 5,000 ft broken - Temperature: 72 °F, dew point 52 °F - Altimeter: 30.22 inHg - Observed at: LBE, 12 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20140531008369A](https://openairdocs.org/incident/20140531008369A), May 31, 2014: Cessna 172F, Mt Pleasant, PA, Substantial damage. The pilot stated - on the takeoff roll the aircraft could not accelerate to lift-off speed (vr) due to the high grass (3-4 inches) runway length 1640 feet.… ## Docket (7 files) The files NTSB released with the investigation on August 20, 2014, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=89356. 18.3 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 399 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40415250&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Weather Report and Record (item 2, .PDF, 100 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40415251&FileExtension=.PDF&FileName=Weather%20Report%20and%20Record-Master.PDF - Diagram Provided by FAA (item 3, .PDF, 904 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40415252&FileExtension=.PDF&FileName=Diagram%20Provided%20by%20FAA-Redacted.PDF - Record of NTSB Conversations (item 4, .PDF, 58 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40415253&FileExtension=.PDF&FileName=Record%20of%20NTSB%20Conversations-Redacted.PDF - Excerpts from Owner's Manual (item 5, .PDF, 336 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40415254&FileExtension=.PDF&FileName=Excerpts%20from%20Owner%27s%20Manual-Master.PDF - Photo 1 - Resting Location of Airplane (Photo Courtesy of FAA) (item 6, .PDF, 7.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40415255&FileExtension=.PDF&FileName=Photo%201%20-%20Resting%20Location%20of%20Airplane%20(Photo%20Courtesy%20of%20FAA)-Master.PDF - Photo 2 - Resting Location of Airplane (Photo Courtesy of FAA) (item 7, .PDF, 9.1 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40415256&FileExtension=.PDF&FileName=Photo%202%20-%20Resting%20Location%20of%20Airplane%20(Photo%20Courtesy%20of%20FAA)-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.