Piper PA-32-260 accident near Green Valley, Arizona, April 13, 2025
On April 13, 2025 at about 8:42 pm local time, a 1966 Piper PA-32-260, registered N3797W, was substantially damaged in an accident during enroute near Green Valley, Arizona. It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's improper fuel management, which resulted in a total loss of engine power due to fuel starvation.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- April 13, 2025 · about 8:42 pm local time
- Place
- Green Valley, Arizona · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-32-260, built 1966 · all PA-32-260s on the register
- Registration
- N3797W · registry record · serial 32-725
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
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.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Off-field or emergency landing during landing
- Fuel starvation during enroute defining event
The NTSB's findings
- Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
- Aircraft › Fluids/misc hardware › Fluids › Fuel › Fluid management
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 345 hours in all
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: frt
- Injury: no injuries
Passenger
- Seat: rgt
- Injury: no injuries
The aircraft
- Airframe total time: 6,268.1 hours
- Last inspection: annual inspection, March 26, 2025
- Seats: 6
- Landing gear: fixed
- Engine: Lycoming O-540-E4B5 (piston); 0 hours total
The flight
- Departed from: OLS Nogales AZ at 8:00 pm
- Destination: DVT Phoenix AZ
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 250° at 12 knots, gusting 24
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 91°F (33°C), dew point 18°F (-8°C)
- Altimeter: 29.95 inHg
- Observation at 1:53 pm from KTUS, 15 miles away
Weather report (METAR): KTUS 132053Z 25012G24KT 10SM CLR 33/M08 A2995 RMK AO2 SLP093 T03281078 56007
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Photographs from the investigation 3 pictures from the NTSB's docket, as the NTSB released them
Photograph 1 – Front view of accident airplane
Photograph 2 – View of left wing damage
Photograph 3 – View of left wing damageThe NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.
Documents from the investigation the NTSB's docket: the evidence folder behind the report
5 documents, released by the NTSB on December 10, 2025. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 10 pages | View Download |
| 2 | Engine Data Monitor - Specialist's Factual Report | PDF, 4 pages | View Download |
| 3 | Airframe and Engine Examination | PDF, 10 pages | View Download |
| 4 | Photo Array | PDF, 4 pages · our copy | View Download |
| 5 | Wreckage Release | PDF, 1 page | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
