Piper PA-28-140 accident near Rochester, Nevada, June 17, 2023
On June 17, 2023 at about 5:57 am local time, a 1967 Piper PA-28-140, registered N3508K, was substantially damaged in an accident during enroute (cruise) near Rochester, Nevada. It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries; 2 others were unhurt. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
A broken fuel line fitting that 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
- June 17, 2023 · about 5:57 am local time
- Place
- Rochester, Nevada · map
- Type
- Accident
- Injuries
- 1 person had minor injuries; 2 others were unhurt.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-28-140, built 1967 · all PA-28-140s on the register
- Registration
- N3508K · registry record · serial 28-23594
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot was on a cross-country flight when the engine lost power during cruise flight. He said the engine rpm initially decreased from 2,400 rpm to 950 rpm, before decreasing until the engine lost all power. The pilot stated that he did not hear any unusual noises from the engine at the time it lost power, but he observed the fuel flow initially increase from 7.2 gallons per hour (gph) to 9 gph, before continuing to increase to 15 gph. He performed the emergency checklist for loss of engine power inflight but was unable to restart the engine. The pilot had the left fuel tank selected when the loss of power occurred. The pilot initiated a forced landing to an area of flat terrain. During the landing, all three landing gear collapsed, which resulted in substantial damage to the right wing and fuselage. The engine and fuel system were examined and the fuel line fitting connecting the fuel second flow sensor to the fuel line that ran to the carburetor was found broken. About 15 gallons of fuel remained in the left fuel tank and the right fuel tank was breached during the impact. No additional anomalies were noted during the examination of the engine and airframe. The pilot’s observations of the fuel flow readings increasing as the engine lost power and his inability to restart the engine are consistent with the fuel line fitting breaking inflight, resulting in a total loss of engine power due to fuel starvation. Complete maintenance records were not available to determine when the fuel flow sensors had been installed or if any maintenance had been performed on the suspect fuel fitting after installation.
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
- Aircraft maintenance event during prior to flight
- Sys/Comp malf/fail (non-power) during enroute (cruise) defining event
The NTSB's findings
- Aircraft › Aircraft systems › Fuel system › Fuel distribution › Failure
- Aircraft › Aircraft power plant › Engine fuel and control › Fuel distribution › Unknown/Not determined
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Altitude › Attain/maintain not possible
Pilot
- Certificate: private
- Ratings: multi-engine land; single-engine land
- Flight time: 330 hours in all; 200 in this make and model; 10 in the last 90 days; 8 in the last 30 days; 251 as pilot in command
- Last flight review: March 14, 2022
- Medical certificate: Class 2 (without waivers/limitations)
- Seat: left
- Injury: no injuries
Passenger
- Seat: rgt
- Injury: no injuries
The aircraft
- Airframe total time: 3,773 hours
- Last inspection: annual inspection, July 7, 2022; 30 hours since
- Maximum gross weight: 2,150 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming (piston); 0 hours total
The flight
- Departed from: U42 South Valley UT at 2:00 am
- Flight plan: none
Weather at the time
- Light: night
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 59°F (15°C), dew point 36°F (2°C)
- Altimeter: 30.09 inHg
- Observation at 10:53 pm from KLOL, 27 miles away
Weather report (METAR): KLOL 170553Z AUTO 00000KT 10SM CLR 15/02 A3009 RMK AO2 SLP161 T01500022 10267 20150 51006
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | 1 | ||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
8 documents, released by the NTSB on February 26, 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, 11 pages | View Download |
| 2 | Wreckage Examination Report | PDF, 8 pages | View Download |
| 3 | Photos | PDF, 8 pages | View Download |
| 4 | Electronic Flight Information System - Specialist's Factual Report | PDF, 6 pages | View Download |
| 5 | Electronic Flight Information System - Specialist's Factual - Attachment 1 - Tabular Data | data file | Download |
| 6 | Electronic Flight Information System - Specialist's Factual - Attachment 2 - Tabular Data | data file | Download |
| 7 | Maintenance Records - Mfr | PDF, 1 page | View Download |
| 8 | Release of Aircraft Wreckage, NTSB Form 6120.15 | 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.
