Accident Piper PA-32-300 Cherokee Six N4027W,
ASN logo
ASN Wikibase Occurrence # 236795
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Wednesday 17 January 2018
Time:15:20
Type:Silhouette image of generic PA32 model; specific model in this crash may look slightly different    
Piper PA-32-300 Cherokee Six
Owner/operator:Private
Registration: N4027W
MSN: 32-40043
Year of manufacture:1966
Total airframe hrs:5979 hours
Engine model:Lycoming IO-540-K1G5D
Fatalities:Fatalities: 0 / Occupants: 2
Aircraft damage: Substantial
Category:Accident
Location:Reno, NV -   United States of America
Phase: Initial climb
Nature:Training
Departure airport:Reno, NV (RNO)
Destination airport:Hawthorne, NV (HTH)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
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.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: WPR18LA070
Status: Investigation completed
Duration: 2 years and 4 months
Download report: Final report

Sources:

NTSB

Location

Revision history:

Date/timeContributorUpdates
08-Jun-2020 08:37 ASN Update Bot Added

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org