# NTSB DFW08LA133: Piper PA-32R-300, N385WR, Emporia, KS, May 8, 2008 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Limited investigation · Final report - Date: May 8, 2008, 15:30 local (20:30 UTC) - Place: Emporia, KS - Coordinates: 38.409988, -96.189666 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=38.4100&lon=-96.1897&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Defining event: [Enroute-cruise: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341) - Highest injury: Minor injuries - Injuries: 1 minor - Status: Completed, report April 15, 2009 - Report: Approved by Office Director - Parties: FAA FSDO, Piper Aircraft Company - NTSB case key (mKey): 67971 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=DFW08LA133 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/67971/pdf - Page: https://openairdocs.org/ntsb/DFW08LA133 ## Probable cause A total loss of engine power due to fuel starvation as a result of a blocked fuel outlet caused by the peeling off of a previously approved fuel tank sealer. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Fuel system: fuel storage](https://openairdocs.org/ntsb-findings/01022810): Aircraft › Aircraft systems · Damaged/degraded (probable cause); cases with it: [Piper PA-32R-300, 1 case](https://openairdocs.org/ntsb-findings/01022810/cases.md?model=7103213), [All aircraft, 60 cases](https://openairdocs.org/ntsb-findings/01022810/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Enroute-cruise: Fuel contamination](https://openairdocs.org/ntsb-events/193); cases with it: [Piper PA-32R-300, 3 cases](https://openairdocs.org/ntsb-events/193/sequence.md?model=7103213), [All aircraft, 225 cases](https://openairdocs.org/ntsb-events/193/sequence.md) - [Enroute-cruise: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341) (defining event); cases with it: [Piper PA-32R-300, 14 cases](https://openairdocs.org/ntsb-events/341/sequence.md?model=7103213), [All aircraft, 3,820 cases](https://openairdocs.org/ntsb-events/341/sequence.md) - [Emergency descent: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [Piper PA-32R-300, 11 cases](https://openairdocs.org/ntsb-events/440/sequence.md?model=7103213), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md) ## Analysis The pilot was on a 330-nautical-mile cross-country flight in a single-engine airplane. About 30 miles from his destination, and at an altitude of 3,500 feet, he turned on the fuel boost pump and switched fuel tanks. At about 10 miles from his destination airport the "plane got quiet." The pilot cycled the magnetos and fuel tank selector "once or twice." Unable to restart the engine, the pilot then conducted a forced landing in a field. An on-site inspection noted that fuel was present in the airplane's fuel tanks. A follow-on inspection of the airplane found no mechanical or electrical problem with the engine. However, the left inboard fuel tank appeared to have large sections of "sloshing" compound peeling from the tanks walls, blocking the fuel tank outlet. A review of maintenance records revealed that the left inboard fuel tank was treated with (sloshing compound) fuel tank sealer in February 1996. At the time of the application, the procedure was acceptable per the airplane's manufacturers service manual. The review also noted that the manufacturer's service bulletin, dated May 16, 2005, no longer recognized the compound as an approved sealer, and that the sloshing procedure should be removed from all service manuals. Additionally, the service bulletin did not contain additional instructions with regards to tanks that had been previously repaired using the sealer. ## Factual narrative On May 8, 2008, approximately 1530 central daylight time, a single-engine, Piper PA-32R-300 airplane, N385WR, was substantially damaged upon impact with terrain following a loss of engine power while in cruise flight near Emporia, Kansas. The private pilot, sole occupant on board, received minor injures. The airplane was registered to TNJ Trucking, Inc. of Estherville, Iowa and operated by the pilot. Visual meteorological conditions prevailed for the 14 Code of Federal Regulations Part 91 flight. The flight departed Tradewinds airport (KTDW), Amarillo, Texas about 13:45 for the 330-nautical mile cross country flight. In a written statement, the pilot reported after he passed Cottonwood, Kansas (and less than 30 miles from Emporia) he turned on the fuel boost pump, and switched fuel tanks. About 10 miles from Emporia and at an altitude of 3,500 feet the pilot the "plane got quiet." The pilot cycled the magnetos and fuel tank selector "once or twice." Unable to restart the engine, the pilot conducted a forced landing in a field, about 10 miles west of Emporia. The Federal Aviation Administration (FAA) inspector, who responded to the accident site, reported that the aircraft received structural damage during the forced landing. The FAA inspector also noted that fuel was present in the airplane's fuel tanks. A follow-on inspection of the airplane found no mechanical or electrical problem with the engine. However, the left inboard fuel tank appeared to have large sections of "sloshing" compound peeling from the tanks walls blocking the fuel tank outlet. A review of maintenance records revealed that the left inboard fuel tank was treated with Randolph 802 (sloshing compound) sealer in February 1996. At the time of the application, the procedure was acceptable per the Piper Service Manual. The review also noted that Piper Service Bulletin 251C, dated May 16, 2005, no longer recognizes Randolph 802 as an approved sealer, and that the sloshing procedure should be removed from all Piper Service Manuals. Additionally, the service bulletin did not contain additional instructions with regards to tanks that had been previously repaired using this procedure. ## Aircraft - Registration: [N385WR](https://openairdocs.org/deregistered/N385WR-2013-04-17), registration cancelled 2013-04-17, S/N 32R-7680402, built 1976 (OpenAirDocs) - Reported make and model: PIPER PA-32R-300 - Registry model: [Piper PA-32R-300](https://openairdocs.org/model/piper-pa-32r-300) (registry code 7103213) (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: 32R-7680402 - Airframe hours: 4934 - Engines: LYCOMING TI0-540 SER 310 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: T-N-J Trucking Inc - Registered owner: T-N-J Trucking Inc - Airworthiness certificate: Standard, Normal - Last inspection: Annual, April 1, 2008 - Departed: KTDW, Tradewinds, TX - Destination: KEMP, Emporia, KS - Flight plan: Unknown ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 44; injuries: minor; private; airplane ratings: single-engine land; medical: class 2, with waivers/limitations; last flight review October 18, 2007; seat: left; flight hours: 112 total, 56 in this make and model, 112 as pilot in command, 20 in the last 90 days, 9 in the last 30 days, 2 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 190° at 5 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 72 °F, dew point 52 °F - Altimeter: 29.69 inHg - Observed at: KEMP ## 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 20080508835429A](https://openairdocs.org/incident/20080508835429A), May 8, 2008: Piper PA32R300, Emporia, KS, Substantial damage. (-23) While enroute from tdw to emp, approximately 16:30 and 10 miles from emp, N385WR experienced engine problems and landed in a field. The landing gear… 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.