PIPER PA-32-300 near Elkader, IA — 2012-07-14
- Date
- 2012-07-14
- Location
- Elkader, IA, USA
- Airport
- I27
- Aircraft
- PIPER PA-32-300
- Registration
- N1127X
- Category
- Airplane
- Highest injury
- Serious
- Fatalities
- 0
- Phase of flight
- Landing
Probable cause
The pilot's failure to attain the proper touchdown point while landing on the wet grass runway.
NTSB narrative
The pilot reported that the airplane touched down on the first third of the wet grass runway, but the braking action was ineffective. He stated that because of the ineffective braking action and the short runway length, he applied full engine power to abort the landing. He reported that although the airplane initially cleared trees located off the departure end of the runway, it was inexplicably pushed down into the tree line. The airplane came to rest in a 100-foot deep wooded ravine located off the departure end of the runway. The pilot noted that there were no preaccident mechanical malfunctions or failures that would have precluded normal operation of the airplane. Based on the available weather radar data and witness observations, localized instrument flight rule conditions likely existed due to thunderstorms and heavy rain in the vicinity of the airport. An on-site investigation found tire marks on the grass runway consistent with the tire width of the accident airplane. The first of these tire marks was more than halfway down the 1,705-foot-long runway, about 741 feet from the departure end. These tire tracks continued past the departure threshold until a point where the terrain sloped away from the runway elevation, indicating that the airplane had not become airborne on the usable runway. The physical evidence was consistent with the airplane running off the end of the runway before descending into treetops that were at or below the runway elevation. Review of available performance data indicated that the expected landing distance for a wet grass runway would be in excess of 748 feet. The landing performance calculations established that there was sufficient runway available for a ground roll if the pilot had touched down within the first half of the runway.
Analysis
- Primary failure mode
- Controlled flight into terrain
- First missed decision gate
- Pilot could have diverted to alternate airport before landing attempt.
NTSB coding
Evidence available
- FDR / data
- ADS-B / radar
- 13 docket documents
Docket documents13
- Airfield Performance Considerations, Source: Civil Aviation Authority (CAA)form
- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1form
- FAA Inspector Statementsinterview
- Witness Statementsinterview
- Email Correspondence With FAA Inspectorother
- Global Positioning System Data Plotsother
- Meteorological Data Summaryother
- Piper PA-32-300 Pilot's Operating Manual, Excerptsother
- Return Confirmation For Pilot's Global Positioning System Receiverother
- Postaccident Runway Survey of Tire Track Markingsradar
- Weather Radar Data Plotsradar
- Clayton County Sheriff Investigative Report Summaryreport
- Transcript of Pilot's Preflight Weather Briefingtranscript
Related mishaps
- CESSNA A185F
2023-09-10 · Beluga, AK
- PIPER PA28
2022-05-31 · Simsbury, CT
- CESSNA T240
2020-05-06 · Gonazales, TX
- Aviat A1
2019-06-09 · Pingree, ID
- Cessna 402
2019-02-15 · Montague, CA
- Piper PA32
2018-07-25 · Avalon, CA