# NTSB WPR25LA131: Piper PA-32-260, N3797W, Green Valley, AZ, April 13, 2025 - Type: NTSB accident investigation - Classification: Accident · No injuries · Class 3 · Limited · Final report - Date: April 13, 2025, 13:42 local (20:42 UTC) - Place: Green Valley, AZ - Coordinates: 31.903151, -111.07858 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=31.9032&lon=-111.0786&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Defining event: [Enroute: Fuel starvation](https://openairdocs.org/ntsb-events/191) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report December 10, 2025 - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Western Pacific Region - Parties: FAA - NTSB case key (mKey): 200016 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR25LA131 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/200016/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=200016 - Page: https://openairdocs.org/ntsb/WPR25LA131 ## Probable cause The pilot's improper fuel management, which resulted in a total loss of engine power due to fuel starvation. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Use of equip/info: use of equip/system](https://openairdocs.org/ntsb-findings/02063015): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Piper PA-32-260, 9 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md?model=7103206), [All aircraft, 1,391 cases](https://openairdocs.org/ntsb-findings/02063015/cases.md) - [Fluids: fuel](https://openairdocs.org/ntsb-findings/01071010): Aircraft › Fluids/misc hardware · Fluid management (probable cause); cases with it: [Piper PA-32-260, 12 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md?model=7103206), [All aircraft, 1,695 cases](https://openairdocs.org/ntsb-findings/01071010/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Enroute: Fuel starvation](https://openairdocs.org/ntsb-events/191) (defining event); cases with it: [Piper PA-32-260, 10 cases](https://openairdocs.org/ntsb-events/191/sequence.md?model=7103206), [All aircraft, 733 cases](https://openairdocs.org/ntsb-events/191/sequence.md) - [Landing: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [Piper PA-32-260, 19 cases](https://openairdocs.org/ntsb-events/440/sequence.md?model=7103206), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md) ## Analysis The pilot reported that, while conducting a cross-country flight, he noted that the airplane’s generator breaker was malfunctioning. He chose to continue the flight on battery backup, cycling the battery power on and off throughout the remainder of the flight to conserve power. While the airplane was climbing through 6,300 ft mean sea level (msl) about 20 miles north of the planned rest stop, the engine began to sputter. While troubleshooting, the pilot turned on the electric fuel pump and switched fuel tanks. Despite his attempts to troubleshoot, the engine lost total power. The pilot determined that the airplane could not maintain flight to reach the nearest airport. He initiated a forced landing to a dirt road, during which the airplane’s left wing struck a dirt berm and sustained substantial damage. Although the airplane was equipped with an engine monitor capable of recording numerous parameters related to engine operation, the unit contained no data. It is likely that, due to the electrical power interruption during the flight, the engine monitor did not record any data. Examinations of the recovered airframe and engine, which included an engine run, revealed no preaccident mechanical malfunction or failure that would have precluded normal operation. About 20 to 25 gallons of fuel was recovered from the left main tank, but the right main and both tip tanks were devoid of fuel. The fuel selector lever was found positioned to the right tip tank. Continuity of the fuel system was established from the main fuel tanks throughout the system to the fuel servo. During a leak test, the left main, right main, and right tip tanks showed no evidence of leakage, and the leakage observed from the left tip tank was consistent with impact damage to the fuel sump. Based on the available information, it is likely that the pilot failed to select a fuel tank that contained fuel, which resulted in fuel starvation and a total loss of engine power. ## Factual narrative On April 13, 2025, about 1342 mountain standard time, a Piper PA-32-260, N3797W, was substantially damaged when it was involved in an accident near Green Valley, Arizona. The pilot and passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported that he was conducting a cross-country flight from the Puerto Penasco Mar De Cortes Airport (MMPE), Sonora, Mexico, to the Phoenix Deer Valley Airport (DVT), Phoenix, Arizona, with a planned rest stop at the Nogales International Airport (OLS), Nogales, Arizona. Shortly after departing from MMPE, he noticed that the generator breaker was having issues. He chose to continue the flight to DVT using the battery backup, cycling the battery power on and off throughout the remainder of the flight to conserve battery power. After departing from OLS, while the airplane was climbing through 6,300 ft msl about 20 miles north of OLS, the engine began to sputter. While troubleshooting, the pilot turned on the electric fuel pump and switched fuel tanks. The passenger noted that the fuel pressure gauge fluctuated between 0 and 30 lbs. The engine sputtering progressively got worse, and the engine lost total power. The pilot determined that the airplane was unable to maintain altitude to reach the nearest airport, so he chose to make an off-airport landing on a dirt road. During the landing roll, the airplane encountered a wind gust and became airborne. The airplane’s left wing and main landing gear impacted a dirt berm, and the airplane came to rest upright. According to recovery personnel, about 20 to 25 gallons of fuel was drained from the left main fuel tank. No fuel was recovered from the right main, left tip, and right tip tanks. Examination of the recovered airframe revealed that recovery personnel had removed both wings from the fuselage for transport. A visual examination of the fuel system revealed no breaches. The fuel selector lever was observed positioned to the right tip tank. Continuity of the fuel system was confirmed from the wings to the fuel servo. To facilitate a leak test, both wings’ fuel inlet lines were capped, and all four fuel tanks were filled with water. Water leakage from the left tip tank was consistent with impact damage to the fuel sump. No other water leakage from any tanks was observed. Continuity of the throttle and mixture control cables was established from the cockpit controls to the carburetor, and all levers moved freely from stop to stop when actuated by hand. To facilitate an engine run, an external fuel tank was attached to the airframe inlet port. During the first attempt to start the engine, the engine rotated but did not start. Additional fuel priming of the engine was conducted, and, on the second attempt, the engine started. Due to vibrations from the damaged propeller, the engine run was limited to about 3 minutes and about 1,000 rpm. The engine was subsequently equipped with a substituteconstant-speed propeller, and it ran uneventfully through various power settings for about 5 minutes. A functional check of the magnetos revealed a change of about 50 rpm during the left and right magneto checks. The throttle was advanced to the full forward position, and a static rpm of about 2,700 rpm was observed. Postaccident examination of the airframe and engine revealed no preaccident mechanical malfunction or failure that would have precluded normal operation. The airplane was equipped with a J. P. Instruments EDM-730/830 engine monitor that was capable of recording and storing data for up to 24 parameters related to engine operation. The engine monitor was removed at sent to the NTSB Vehicle Recorder Laboratory. Examination of the engine monitor revealed no visible damage to the exterior of the unit. The device powered on normally, but, when downloading data from the unit, no files were recovered. ## Aircraft - Registration: [N3797W](https://openairdocs.org/aircraft/N3797W), registered now, S/N 32-725, built 1966 (OpenAirDocs) - Reported make and model: PIPER PA-32-260 - Registry model: [Piper PA-32-260](https://openairdocs.org/model/piper-pa-32-260) (registry code 7103206) (OpenAirDocs) - Registry engine: [Lycoming 0-540 series](https://openairdocs.org/engine/lycoming-0-540-series) (registry code 41532, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 32-725 - Year built: 1966 - Airframe hours: 6268.1 - Engines: LYCOMING O-540-E4B5 250 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Last inspection: Annual, March 26, 2025 - Departed: OLS, Nogales, AZ - Destination: DVT, Phoenix, AZ - Equipment: Stall warning system, Angle of attack indicator, ADS-B ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 58; injuries: none; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; seat: front; restraint: 3-point; flight hours: 345 total ## Weather - Conditions: Visual (VMC), Day - Wind: 250° at 12 knots, gusting 24 - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 91 °F, dew point 18 °F - Altimeter: 29.95 inHg - Observed at: KTUS, 15 nm away - METAR: KTUS 132053Z 25012G24KT 10SM CLR 33/M08 A2995 RMK AO2 SLP093 T03281078 56007 ## 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 20250413005739A](https://openairdocs.org/incident/20250413005739A), Apr 13, 2025: Piper PA-32-260, Green Valley, AZ, Substantial damage. On April 13, 2025, about 1342 mountain standard time, a Piper PA-32-260, was substantially damaged when it was involved in an accident near Green Valley,… ## Docket (5 files) The files NTSB released with the investigation on December 10, 2025, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=200016. 6.9 MB in all. - Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 10 pages, 1.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19219430&FileExtension=pdf&FileName=NTSB%20Form%206120_Redacted-Rel.pdf - Engine data monitor - specialist's factual report (item 2, PDF, 4 pages, 1 photo, 190 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=18974237&FileExtension=pdf&FileName=Engine%20Data%20Monitor%20-%20Specialist%27s%20Factual%20Report-Rel.pdf - Airframe and engine examination (item 3, PDF, 10 pages, 934 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19284335&FileExtension=pdf&FileName=Airframe%20and%20Engine%20Examination_Redacted-Rel.pdf - Photo array (item 4, PDF, 4 pages, 1.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19225692&FileExtension=pdf&FileName=Photo%20Array_redacted-Rel.pdf - Wreckage release (item 5, PDF, 1 page, 2.5 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19219280&FileExtension=pdf&FileName=Wreckage%20Release_OUO-Rel.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.