Piper PA 32-300 accident near Reno, Nevada, January 17, 2018
On January 17, 2018 at about 11:20 pm local time, a 1966 Piper PA 32-300, registered N4027W, was substantially damaged in an accident during initial climb near Reno, Nevada (Reno/Tahoe Intl airport). It was an instructional 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
A total loss of engine power due to fuel starvation. Contributing to the accident was the failure of the pilot/owner to ensure that the airplane was airworthy before flight.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- January 17, 2018 · about 11:20 pm local time
- Place
- Reno, Nevada · Reno/Tahoe Intl · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA 32-300 301, built 1966 · all PA 32-300s on the register
- Registration
- N4027W · no longer on the register · serial 32-40043
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The private pilot, who owned the airplane and also partially owned the maintenance facility, arrived at the maintenance facility with his flight instructor on the day of the accident for a cross-country instructional flight to accomplish an insurance checkout requirement. He removed the airplane from the hangar without discussing it with the maintenance team. The pilot and flight instructor did not observe any anomalies during the engine run-up; they then departed with the pilot flying. During the initial climb, the engine experienced a total loss of power, at which point the instructor took control of the airplane to return to the airport. The pilot subsequently reclaimed the controls after he observed the stall warning light. He then lowered the nose and flared when the airplane was over a gravel area. The airplane impacted the ground, slid, and came to rest between two taxiways. Examination of the fuel sump revealed several ounces of fuel that resembled low lead aviation-grade gasoline that did not contain any water contamination or debris. During the postaccident engine examination, the engine was tested and started normally. The throttle was advanced to three separate power settings and, when the fuel pump was engaged, an excessive quantity of fuel was expelled from the engine-driven fuel pump hose. The engine-driven fuel pump was examined and tested. The examination revealed wear on the drive shaft and pinion. Further, the unit failed the external leakage and seal leakage tests, as flow testing showed that the seal behind the drive pinion leaked profusely. While the pump failed two discharge pressure tests, it functioned during each test and failed by a margin of 3%. A photograph revealed that the fuel pump inlet line was disconnected from the fuel pump. The mechanic who was responsible for the disconnected inlet line reported that he had been asked to install an engine monitor on the accident airplane but did not have the required equipment to complete the installation of the fuel flow sending unit the day before the accident; he chose to secure the inlet line fitting to the pump without applying the required torque until he could complete the work. Although the mechanic subsequently misinformed the director of maintenance (DOM) that the fuel line had been tightened, the DOM had not returned the airplane to service when the pilot came to retrieve the airplane. The pilot never asked the mechanic if the airplane had been returned to service or was ready to fly. The examination did not reveal any other mechanical malfunctions or failures that would have precluded normal operation. Thus, the loss of engine power was most likely due to fuel starvation as a result of fuel being expelled from the unsecured fuel pump inlet line.
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
- Fuel starvation during initial climb defining event
- Loss of engine power (total) during initial climb
- Collision with terrain or object (not controlled flight into terrain) during emergency descent
The NTSB's findings
- cause Aircraft › Fluids/misc hardware › Fluids › Fuel › Fluid level
- factor Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Pilot
- factor Personnel issues › Task performance › Inspection › Preflight inspection › Pilot
- Aircraft › Aircraft power plant › Engine fuel and control › Fuel pump › Incorrect service/maintenance
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 110 hours in all; 0 in this make and model
- Last flight review: October 30, 2017
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: no injuries
Flight instructor
- Certificate: flight instructor, commercial pilot
- Ratings: single-engine land; instructor: airplane single-engine; instrument: airplane
- Flight time: 916 hours in all; 38 in this make and model; 27 in the last 90 days; 12 in the last 30 days; 732 as pilot in command; 12 on instruments
- Last flight review: December 21, 2017
- Medical certificate: Class 2 (with waivers/limitations)
- Seat: rgt
- Injury: no injuries
The aircraft
- Airframe total time: 5,979 hours
- Last inspection: annual inspection, December 1, 2017; 6 hours since
- Maximum gross weight: 3,400 lb
- Seats: 6
- Landing gear: fixed
- Engine: Lycoming IO-540-K1G5D (piston); 5,979 hours total
The flight
- Departed from: RNO Reno NV at 11:20 pm
- Destination: HTH Hawthorne NV
- Flight plan: none
- Runway 16L, 9,000 ft by 150 ft
- A second pilot was aboard
Weather at the time
- Light: daylight
- Wind: from 270° at 3 knots
- Visibility: 10 statute miles
- Sky: overcast at 24,000 ft; a few clouds at 12,000 ft
- Temperature: 59°F (15°C), dew point 36°F (2°C)
- Altimeter: 30.21 inHg
- Observation at 11:39 pm from RNO
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 2 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
12 documents, released by the NTSB on September 6, 2019. 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, 9 pages | View Download |
| 2 | Weather Reports and Records | PDF, 2 pages | View Download |
| 3 | Record of Conversations | PDF, 7 pages | View Download |
| 4 | Statement from Mechanic to FAA | PDF, 1 page | View Download |
| 5 | NTSB Aircraft Examination Report | PDF, 4 pages | View Download |
| 6 | Fuel Pump Examination Report | PDF, 5 pages | View Download |
| 7 | Aircraft Logbook | PDF, 7 pages | View Download |
| 8 | Engine Logbook | PDF, 6 pages | View Download |
| 9 | Fuel Line Nut Torque Specifications from FAA | PDF, 5 pages | View Download |
| 10 | Statement of Party Representatives to NTSB Investigation | PDF, 1 page | View Download |
| 11 | Release of Aircraft Wreckage, NTSB Form 6120.15 | PDF, 3 pages | View Download |
| 12 | Accident Photographs | PDF, 5 pages | 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.
