# NTSB WPR10CA346: Piper PA-32RT-300, N2185K, Yellow Pine, ID, July 12, 2010

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: July 12, 2010, 08:30 local (14:30 UTC)
- Place: Yellow Pine, ID
- Coordinates: 44.912223, -115.485557
- Nearby events: https://openairdocs.org/map.md?lat=44.9122&lon=-115.4856&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: 2 uninjured
- Status: Completed, report December 20, 2010
- Report: Approved by Office Director
- NTSB office: Western Pacific Region
- Parties: FAA Boise FSDO
- NTSB case key (mKey): 76598
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR10CA346
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/76598/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=76598
- Page: https://openairdocs.org/ntsb/WPR10CA346

## Probable cause

The pilot's delayed decision to abort the takeoff. Contributing to the accident was the wet condition of the grass runway.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Piper PA-32RT-300, 7 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=7103215), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md)
- [Runway/land/takeoff/taxi surface: wet surface](https://openairdocs.org/ntsb-findings/03023010): Environmental issues › Physical environment · Response/compensation (probable cause); cases with it: [Piper PA-32RT-300, 1 case](https://openairdocs.org/ntsb-findings/03023010/cases.md?model=7103215), [All aircraft, 141 cases](https://openairdocs.org/ntsb-findings/03023010/cases.md)
- [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Piper PA-32RT-300, 4 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=7103215), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/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: [Piper PA-32RT-300, 5 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=7103215), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md)

## Analysis

The pilot reported that while loading the airplane he noticed the airport manager installing sprinkler heads along the entire length of the grass runway. The pilot requested that the airport manager delay turning on the sprinklers until he departed the airport; however, the sprinklers were turned on prior to departure. The pilot stated that he remained on the right half of the runway to keep clear of the sprinklers during the takeoff roll. As the airplane approached midfield during the takeoff roll, the pilot determined that the airplane was not "moving fast enough" to continue the take off. The pilot stated that he aborted the takeoff by pulling back on the throttle and applying the brakes. He added that during the aborted takeoff, the airplane began skidding on the wet grass and he shut the engine off. Subsequently, the airplane exited the departure end of the runway and struck a sign and a boulder, which resulted in substantial damage to the right and left wings. The pilot reported no mechanical malfunctions or failures with the airplane prior to the accident. According to the Northwest U.S. Airport/Facility Directory, runway 35, a grass runway, is 3,400 feet long and 150 feet wide. At the reported weight of the airplane, in the weather conditions of the airport at the time of the accident, the airplane had a calculated takeoff ground roll of about 2,000 feet, with a landing ground roll of 880 feet. These numbers are calculated for a dry, paved, level runway, with two notches of flaps used for the takeoff. The airplane took off on a wet, grass, down-slope airstrip, with only one notch of flaps. The Performance Section of the Pilot Operating Handbook for this airplane states that the “effects of conditions not considered on the charts must be evaluated by the pilot, such as the effect of soft or grass runway surface on takeoff or landing performance….”

## Factual narrative

The pilot reported that while loading the airplane he noticed the airport manager installing sprinkler heads along the entire length of the grass runway. The pilot requested that the airport manager delay turning on the sprinklers until he departed the airport; however, the sprinklers were turned on prior to departure. The pilot stated that he remained on the right half of the runway to keep clear of the sprinklers during the takeoff roll. As the airplane approached midfield during the takeoff roll, the pilot determined that the airplane was not "moving fast enough" to continue the take off. The pilot stated that he aborted the takeoff by pulling back on the throttle and applying the brakes. He added that during the aborted takeoff, the airplane began skidding on the wet grass and he shut the engine off. Subsequently, the airplane exited the departure end of the runway and struck a sign and a boulder, which resulted in substantial damage to the right and left wings. The pilot reported no mechanical malfunctions or failures with the airplane prior to the accident. According to the Northwest U.S. Airport/Facility Directory, runway 35, a grass runway, is 3,400 feet long and 150 feet wide. At the reported weight of the airplane, in the weather conditions of the airport at the time of the accident, the airplane had a calculated takeoff ground roll of about 2,000 feet, with a landing ground roll of 880 feet. These numbers are calculated for a dry, paved, level runway, with two notches of flaps used for the takeoff. The airplane took off on a wet, grass, down-slope airstrip, with only one notch of flaps. The Performance Section of the Pilot Operating Handbook for this airplane states that the “effects of conditions not considered on the charts must be evaluated by the pilot, such as the effect of soft or grass runway surface on takeoff or landing performance….”

## Aircraft

- Registration: [N2185K](https://openairdocs.org/aircraft/N2185K), registered now, S/N 32R-7985061, built 1978 (OpenAirDocs)
- Reported make and model: PIPER PA-32RT-300
- Registry model: [Piper PA-32RT-300](https://openairdocs.org/model/piper-pa-32rt-300) (registry code 7103215) (OpenAirDocs)
- Registry engine: [Lycoming IO-540 series](https://openairdocs.org/engine/lycoming-io-540-series) (registry code 41530, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 32R-7985061
- Airframe hours: 2460
- Engines: Lycoming IO-540 Series 300 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Operator: Charles D Eldridge III
- Registered owner: Eldridge Charles D III
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, January 8, 2010, 18 hours before
- Departed: 3U2, Yellow Pine, ID
- Destination: 4U7, Conner, MT
- Airport: 3U2, Johnson Creek, runway 35, 3,400 × 150 ft, grass/turf

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 72; injuries: none; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, without waivers/limitations; last flight review April 30, 2010; seat: left; flight hours: 2,650 total, 2,460 in this make and model, 2,600 as pilot in command, 15 in the last 90 days, 7 in the last 30 days

## Weather

- Conditions: Visual (VMC), Day
- Wind: calm
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 61 °F, dew point 50 °F
- Altimeter: 29.90 inHg
- Observed at: KMYL, 26 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 20100712038959A](https://openairdocs.org/incident/20100712038959A), Jul 12, 2010: Piper PA-32RT-300, Yellow Pine, ID, Substantial damage. During the takeoff roll, the pilot determined the aircraft had not reached a safe liftoff speed by the pilot's predetermined go/no-go spot. At that point the…

## Docket (1 files)

The files NTSB released with the investigation on August 16, 2010, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=76598. 740 KB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 740 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40333829&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.