# NTSB CHI02LA019: Piper PA-32-301T, N82813, Phillips, WI, November 4, 2001 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: November 4, 2001, 15:20 local (21:20 UTC) - Place: Phillips, WI - Coordinates: 45.690727, -90.389381 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=45.6907&lon=-90.3894&mi=10 - Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 5 uninjured - Status: Completed, report April 23, 2003 - Report: Approved by Office Director - Parties: Federal Aviation Administration - NTSB case key (mKey): 53747 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CHI02LA019 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/53747/pdf - Page: https://openairdocs.org/ntsb/CHI02LA019 ## Probable cause The fuel starvation encountered on takeoff and unsuitable terrain the pilot encountered during the forced landing. A factor was the fuel selector valve malfunction. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of engine power(total) - nonmechanical, takeoff - procedures/directives - not followed, pilot in command - fluid,fuel - starvation (cause) - fuel system,selector/valve - malfunction (contributing factor) - Forced landing, emergency landing after takeoff - On ground/water encounter with terrain/water, emergency landing after takeoff - unsuitable terrain or takeoff/landing/taxi area - encountered, pilot in command (cause) - terrain condition - rough/uneven ## Analysis The airplane sustained substantial damage on impact with terrain during a forced landing following an in-flight loss of engine power during takeoff. The pilot and four passengers were uninjured. The pilot purchased 42 gallons of fuel. He said, "During initial climbout I noted a change in exhaust noise, and the engine began running rough. The engine was running rough, but still developing enough power to execute a shallow, climbing, left turn, providing me the opportunity to use the airport environment behind me for a landing. On a wide left downwind for runway 19, at approximately 250 ft. AGL, the engine ceased developing power. I chose a touchdown point in the field on the runway environment immediately south of runway 06/24. The field was cut grass, but soft, wet, and rutted. During the rollout the nosegear and the left main gear collapsed." The airplane was equipped with an engine monitor. The monitor recorded a fuel flow between 10.2 and 13.5 gallons per hour and used .5 gallons during the run up. During start of the takeoff, the monitor recorded .9 gallons of fuel used. The monitor's last six takeoff entries showed the aircraft used 1.7 gallons of fuel. The engine was test run and no anomalies were found. The mechanic who repaired the aircraft stated, "During repairs to the above referenced aircraft, we discovered that the fuel selector lever would go past the selected fuel tank detent. Upon further investigation, the 'off' stop was not operating properly." The PA-32-301T's POH stated, "ENGINE POWER LOSS DURING TAKEOFF ... If sufficient altitude has been gained to attempt a restart: Maintain safe airspeed Fuel selector...switch to tank containing fuel, Electric fuel pump...check on, Mixture...check RICH, Alternate air...OPEN, ... 3.9 ENGINE POWER LOSS DURING TAKEOFF ... If engine failure was caused by fuel exhaustion, power will not be regained after switching fuel tanks until the empty fuel lines are filled. This may require up to ten seconds." ## Factual narrative On November 4, 2001, about 1520 central standard time, a Piper PA-32-301T, N82813, piloted by a private pilot, sustained substantial damage on impact with wet, rutted terrain during a forced landing following an in-flight loss of engine power during takeoff from runway 1 (5,000 feet by 75 feet, asphalt) at Price County Airport (PBH), near Phillips, Wisconsin. The personal flight was operating under 14 CFR Part 91. Visual meteorological conditions prevailed at the time of the accident. The pilot and four passengers were uninjured. A VFR flight plan was on file and was activated. The flight was originating from PBH at the time of the accident and was destined for Campbell Airport (C81), near Grayslake, Illinois. The pilot stated: The flight to PHB was routine in every respect. Included in my panel is a JPI-EDM 800 that provides detailed engine performance information. The monitor indicated normal operation. We arrived PBH at 12:15 CST. I purchased 42 gallons 100 LL on arrival. We arrived at the airport (PBH) for our return flight to C81 at 14:40 CST. I performed a detailed pre-flight check using the checklist. All systems checked normally. At 15:00 CST, upon completion of passenger boarding and briefing, I started the engine and taxied to a safe area to perform the engine run-up and equipment checklist. Every function on the checklist performed normally. I taxied to the hold line for runway 06, performed the normal takeoff checklist, then opened my VFR flight plan with FSS [Flight Service Station] at 15:16 CST. I announced myself on Unicom taxing to runway 01 for immediate departure to the Southeast. Upon arriving runway 01, I again performed the normal takeoff checklist and applied full power indicated by 34 Inches of manifold pressure as prescribed by the POH [pilot operating handbook]. The plane accelerated normally and rotated at 80 knots. During initial climbout I noted a change in exhaust noise, and the engine began running rough. I surveyed the area in front of me and determined that I was too high to return to the runway and land safely. The terrain in front of me, from East to West, was dense tree cover. The engine was running rough, but still developing enough power to execute a shallow, climbing, left turn, providing me the opportunity to use the airport environment behind me for a landing. On a wide left downwind for runway 19, at approximately 250 ft. AGL [above ground level], the engine ceased developing power. I chose a touchdown point in the field on the runway environment immediately south of runway 06/24. Considerations were a large berm and a mature tree line on the edge of the field. The field was cut grass, but soft, wet, and rutted. During the rollout the nosegear and the left main gear collapsed. ... Included in the enclosed package is a copy of the flight profile downloaded from the JPI-EDM800 engine monitor. ... I have made notes in the margin indicating the stages of flight. As you can see, all the indications are normal during the run-up. The problem occurs after application of full power as shown by #2 EGT, then one minute later with #2 CHT, which corresponds with changes in fuel flow, RPM, manifold pressure, and % horsepower. The pilot's package of engine monitor data printouts was reviewed. The pilot noted ten entries as "runup." The pilot stated that "FF = fuel flow, USD = fuel used, and MAP = manifold [pressure]." The runup entries follow. TIME FF USD RPM MAP 21:03:50 10.2 0.3 1694 19.6 21:03:56 13.3 0.3 1991 19.6 21:04:02 13.3 0.3 1991 19.6 21:04:08 13.3 0.3 1984 19.6 21:04:14 13.5 0.3 1984 19.6 21:04:20 13.5 0.3 1995 19.6 21:04:26 13.5 0.3 1995 19.6 21:04:32 13.5 0.5 1995 19.6 21:04:38 13 0.5 1875 21 21:04:44 13.5 0.5 1987 19.9 Excerpts noted as "takeoff", follow. TIME FF USD RPM MAP 21:12:14 10.4 0.9 1677 20 21:12:20 35.9 1.1 2646 32.9 21:12:26 37.7 1.1 2630 34.4 21:12:32 37.7 1.1 2613 34.4 21:12:38 37.3 1.3 2637 34.4 21:12:44 37.7 1.3 2617 34.4 21:12:50 37.7 1.3 2629 34.4 21:12:56 36.3 1.5 2614 33.6 21:13:02 36.3 1.5 2626 33.6 21:13:08 36.3 1.5 2626 33.6 21:13:14 34.2 1.5 2636 30.9 21:13:20 8.7 1.7 2064 11.8 21:13:26 5 1.7 1777 9.5 21:13:32 4.7 1.7 1620 9.5 21:13:38 4.5 1.7 1590 9.5 21:13:44 1.4 1.7 1320 6.7 21:13:50 9.2 1.7 2023 15.8 The remaining entry excerpts follow. The first excerpt entry was circled and noted as "landing." TIME FF USD RPM MAP 21:13:56 1.5 1.7 30 28.7 21:14:02 1.2 1.7 0 28.7 21:14:08 0.3 1.7 0 28.7 21:14:14 0 1.7 0 28.7 21:14:20 0 1.7 0 28.7 21:14:26 0 1.7 0 28.7 21:14:32 0 1.7 0 28.7 21:14:38 0 1.7 0 28.7 21:14:44 0 1.7 0 28.7 21:14:50 0 1.7 0 28.7 21:14:56 0 1.7 0 28.7 21:15:02 0 1.7 0 28.7 21:15:08 0 1.7 0 28.7 21:15:14 0 1.7 0 28.7 21:15:20 0 1.7 0 28.7 21:15:26 0 1.7 0 28.7 21:15:32 0 1.7 0 28.7 21:15:38 0 1.7 0 28.7 21:15:44 0 1.7 0 28.7 21:15:50 0 1.7 0 28.7 21:15:56 0 1.7 0 28.7 21:16:02 0 1.7 0 28.7 21:16:08 0 1.7 0 28.7 Federal Aviation Administration inspectors examined the wreckage on-scene. The engine was test run. No anomalies were found during the test run. The engine monitor manufacturer was asked to graph the data from the accident airplane's monitor. The graphs are appended to this report. The aircraft was repaired. The fixed base operator that performed the repairs stated the following. During repairs to the above referenced aircraft, we discovered that the fuel selector lever would go past the selected fuel tank detent. Upon further investigation, the 'off' stop was not operating properly. After airframe repairs were complete and engine reinstalled the aircraft was ground run in that fuel selected position with no noticeable drop in fuel flow at full power on the ground. Then the selector was operated between the detent and the noted position above - again, no noticeable fuel flow was noted at full power on the ground. While at full power, we were able to go to the 'off' position and the engine quit immediately. The PA-32-301T's POH stated the following. 3.3 EMERGENCY PROCEDURES CHECKLIST ... ENGINE POWER LOSS DURING TAKEOFF ... If sufficient altitude has been gained to attempt a restart: Maintain safe airspeed Fuel selector...............................switch to tank containing fuel Electric fuel pump...........................................................check on Mixture...........................................................................check RICH Alternate air............................................................................OPEN 3.9 ENGINE POWER LOSS DURING TAKEOFF ... If engine failure was caused by fuel exhaustion, power will not be regained after switching fuel tanks until the empty fuel lines are filled. This may require up to ten seconds 3.39 ENGINE ROUGHNESS ... Switch the fuel selector to another tank to see if fuel contamination is the problem. ## Aircraft - Registration: [N82813](https://openairdocs.org/aircraft/N82813), registered now, S/N 32-8124001, built 1980 (OpenAirDocs) - Reported make and model: Piper PA-32-301T - Registry model: [Piper PA-32-301T](https://openairdocs.org/model/piper-pa-32-301t) (registry code 7103209) (OpenAirDocs) - Registry engine: [Lycoming TI0-540 series](https://openairdocs.org/engine/lycoming-ti0-540-series) (registry code 41533, turbo-prop) (OpenAirDocs) - Category: Airplane - Serial number: 32-8124001 - Airframe hours: 1588 - Engines: Lycoming TIO-540-S1AD 300 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: KRZ Co. - Airworthiness certificate: Standard, Normal - Last inspection: Annual, August 10, 2001, 41 hours before - Departed: PBH, Phillips, WI - Destination: C81, GRAYSLAKE, IL - Flight plan: VFR - Airport: PBH, Price County ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 53; injuries: none; private; airplane ratings: single-engine land; medical: class 3, valid medical--w/ waivers/lim; last flight review December 6, 2000; seat: left; flight hours: 536 total, 259 in this make and model, 279 as pilot in command, 40 in the last 90 days, 15 in the last 30 days, 4 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 350° at 5 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 52 °F, dew point 9 °F - Altimeter: 30.31 inHg - Observed at: PBH ## 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 20011104030659A](https://openairdocs.org/incident/20011104030659A), Nov 4, 2001: Piper PA32301T, Phillips, WI, No damage. (.19) On November 4, 2001, about 1500 central standard time, a Piper PA-32-301T, N82813, piloted by a private pilot, sustained substantial damage on impact… 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.