# NTSB CEN13CA386: Piper PA-28-140, N6674W, Climax Springs, MO, June 30, 2013 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: June 30, 2013, 14:30 local (19:30 UTC) - Place: Climax Springs, MO - Coordinates: 38.11639, -93.076942 - Nearby events: https://openairdocs.org/map.md?lat=38.1164&lon=-93.0769&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: No injuries - Injuries: 1 uninjured - Status: Completed, report October 21, 2013 - Report: Approved by Office Director - NTSB office: Central Region - NTSB case key (mKey): 87354 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN13CA386 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/87354/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=87354 - Page: https://openairdocs.org/ntsb/CEN13CA386 ## Probable cause The pilot’s inadequate planning and poor decision to attempt to take off on a runway from which the airplane could not obtain flight. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Planning/preparation: flight planning/navigation](https://openairdocs.org/ntsb-findings/02061025): Personnel issues › Task performance · Pilot (probable cause); cases with it: [All aircraft, 179 cases](https://openairdocs.org/ntsb-findings/02061025/cases.md) - [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md) - [Runway/land/takeoff/taxi surface](https://openairdocs.org/ntsb-findings/03023000): Environmental issues › Physical environment · Effect on operation; cases with it: [All aircraft, 253 cases](https://openairdocs.org/ntsb-findings/03023000/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: [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: [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis The day prior to the accident flight, the pilot landed at the private grass airstrip that was no longer maintained. The airstrip had a 2,600 foot long runway with 2- to 3-feet tall grass the length of the runway. On the day of the accident flight, the pilot twice attempted to depart the overgrown runway using a “short-field” takeoff technique. During the first takeoff, he exceeded his predetermined “No-Go” point on the runway and aborted the takeoff. On the second takeoff, the airplane attained 60 to 65 mph and lifted off the ground, but settled back on the runway past the “No-Go” point. The pilot was unable to stop the airplane before it went off the end of the runway and impacted trees. The pilot reported that there was no malfunction or system failure of the airplane before the accident. ## Factual narrative The day prior to the accident flight, the pilot landed at the private grass airstrip that was no longer maintained. The airstrip had a 2,600 foot long runway with 2 to 3 foot tall grass the length of the runway. On the day of the accident flight, the pilot twice attempted to depart the overgrown runway using a “short-field” takeoff technique. During the first takeoff, he exceeded his predetermined “No-Go” point on the runway and aborted the takeoff. On the second takeoff, the airplane attained 60 to 65 mph and lifted off the ground, but settled back on the runway past the “No-Go” point. The pilot was unable to stop the airplane before it went off the end of the runway and impacted trees. The pilot reported that there was no malfunction or system failure of the airplane before the accident. ## Aircraft - Registration: N6674W (not matched to a registry record) - Reported make and model: PIPER PA-28-140 - Category: Airplane - Serial number: 28-20781 - Airframe hours: 7960 - Engines: LYCOMING O-320EA2 150 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Michael J. Magee - Registered owner: Magee Michael J Trustee - Airworthiness certificate: Standard, Normal - Last inspection: Annual, June 13, 2012 - Departed: MO99, Climax Springs, MO - Destination: K34, Gardner, KS - Airport: MO99, Miller Airport, runway 25, 2,600 × 100 ft, grass/turf ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 48; injuries: none; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review May 15, 2013; flight hours: 460 total, 354 in this make and model, 3 in the last 90 days, 1 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 75 °F - Observed at: MO99 ## 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 20130630014329A](https://openairdocs.org/incident/20130630014329A), Jun 30, 2013: Piper PA-28-140, Climax Springs, MO, Substantial damage. The pilot departed under VFR, with no flight plan, from a privately-owned unimproved airstrip that he landed on earlier in the day. He estimated the grass to… ## Docket (1 files) The files NTSB released with the investigation on September 25, 2013, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=87354. 866 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 866 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40396493&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.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.