Piper PA 32R-301 accident near Boulder City, Nevada, June 22, 2015
On June 22, 2015 at about 12:15 pm local time, a 1979 Piper PA 32R-301, registered N35590, was substantially damaged in an accident during enroute (cruise) near Boulder City, Nevada. It was a personal flight under general aviation rules (Part 91). No one was hurt; 4 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
A total loss of engine power during cruise flight for reasons that could not be determined based on the available evidence.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 22, 2015 · about 12:15 pm local time
- Place
- Boulder City, Nevada · map
- Type
- Accident
- Injuries
- No one was hurt; 4 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA 32R-301, built 1979 · all PA 32R-301s on the register
- Registration
- N35590 · registry record · serial 32R-8013020
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The private pilot reported that, while in cruise flight during the personal flight, the engine started to "sputter" and lose power. During troubleshooting efforts, the engine lost total power. The pilot then attempted to restart the engine without success and subsequently initiated a forced landing on a nearby beach. A postaccident engine examination revealed that the engine crankshaft would not rotate manually. Disassembly of the engine revealed evidence of wear and heat damage to the Nos. 1 and 2 crankshaft bearing halves. The oil filter contained no contaminants or metallic particles. No further evidence of a preexisting mechanical malfunction was noted during the examination of the engine and airframe. Damage to main bearings can occur from multiple sources, including oil contamination, excessive loads, or disruption of the lubrication between the bearing face and the main journal. Given that the Nos. 1 and 2 bearings were the only damaged bearings throughout the engine, it is unlikely that oil contamination caused the damage. In addition, given that the Nos. 1 and 2 bearings are located in the forward area of the engine and experience lighter loads than those located in the aft area of the engine, it is unlikely that excessive loads caused the damage. Although a propeller strike could result in an abnormal loading and lubrication of the bearings, a review of the airframe and engine maintenance records revealed no evidence of a reported propeller strike. Absent one of the above issues, it is likely that a disruption of the lubrication between the bearing face and the main journal resulted in the wear of the Nos. 1 and 2 bearing halves. However, no evidence of oil passage blockage, leaks, or excessive clearance between the bearings and the crankshaft journals was observed; therefore, the reason for the likely lubrication disruption or whether it caused the loss of engine power could not be determined. In addition, the accident bearings had an aluminum-tin intermediate layer, which makes the bearings less robust than those with a copper-alloy intermediate layer; thus, the wear and heat damage could have been preceded by delamination of the aluminum-tin intermediate layer. However, postaccident examination could not determine whether this occurred.
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
- Loss of engine power (total) during enroute (cruise) defining event
The NTSB's findings
- cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
- Aircraft › Aircraft power plant › Engine (reciprocating) › (general) › Fatigue/wear/corrosion
- Aircraft › Aircraft power plant › Engine (reciprocating) › (general) › Damaged/degraded
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 195 hours in all; 7 in this make and model; 20 in the last 90 days; 9 in the last 30 days; 105 as pilot in command
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: no injuries
Passenger
- Seat: rgt
- Injury: no injuries
Passenger
- Seat: rgt
- Injury: no injuries
Passenger
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 3,136.2 hours
- Last inspection: annual inspection, July 24, 2015
- Maximum gross weight: 3,600 lb
- Seats: 6
- Landing gear: retractable
- Engine: Lycoming IO-540-K1G5D (piston); 0 hours total
The flight
- Departed from: VGT Las Vegas NV
- Destination: KELP El Paso TX
- Flight plan: VFR
Weather at the time
- Light: daylight
- Wind: from 260° at 6 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 84°F (29°C), dew point 32°F (0°C)
- Altimeter: 29.87 inHg
- Observation at 12:15 pm from KBVU, 2 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 3 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Other NTSB records under N35590 the same tail number, which may have belonged to a different aircraft at the time
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.
