WPR10CA346 · Piper PA-32RT-300
Piper PA-32RT-300 · Accident: collision with terrain/object (non-CFIT) during takeoff
From Johnson Creek Airport (3U2) to West Fork Lodge Airport (4U7)
Event
- NTSB case
- WPR10CA346
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Piper PA-32RT-300
- Aircraft type
- Piper PA-32
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N2185K
- Operator
- Charles D Eldridge III · private individual
- Onboard fatalities
- Unknown
- Route
- From Johnson Creek Airport (3U2), Yellow Pine, IDTo West Fork Lodge Airport (4U7), Conner, MT
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Takeoff · rejected takeoff
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Collision with terrain/object (non-CFIT)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB 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….”
Probable cause
The pilot's delayed decision to abort the takeoff. Contributing to the accident was the wet condition of the grass runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR10CA346
- Event ID
- 20100712X85702
- Case number
- WPR10CA346
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 6ee5493377395ca1bc628a406ca17708a2717bc36f0e62bfc9f3012bd98c3590; retrieved 2026-09-15T14:41:10.966Z.