FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR18LA070 · Piper PA 32-300 301

17 Jan 2018 · Reno, NV, United States

Piper PA 32-300 301 · Accident: fuel starvation during initial climb

From Reno Tahoe International Airport (RNO) to Hawthorne Industrial Airport (HTH)

Report a problem

Event

NTSB case
WPR18LA070
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Piper PA 32-300 301

Aircraft type
Piper PA-32
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N4027W
Operator
Unknown
Onboard fatalities
Unknown
Route
From Reno Tahoe International Airport (RNO), Reno, NVTo Hawthorne Industrial Airport (HTH), Hawthorne, NV
Aircraft age
About 52 years (built 1966)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Initial climb
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Fuel starvation
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Fluids/miscellaneous hardware

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

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.

Probable cause

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR18LA070
Event ID
20180117X85029
Case number
WPR18LA070
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: d1a95bb4998ee15d1fad4cf445d20c35012d3db057cd32a8f63b4183a10eafeb; retrieved 2026-09-16T06:19:52.546Z.