LAX06CA176

NTSB accident investigation · Piper PA-24-250 · Carson City, NV · May 19, 2006

Accident · No injuriesData collectionFinal report
Date
May 19, 2006, 11:15 local (18:15 UTC)
Place
Carson City, NV
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N7857PPiper PA-24-250
Weather
Visual (VMC) · Day
Status
Completed · report December 20, 2007
Report
Approved by Office Director
Parties
Federal Aviation Administration
FAA report
20060519008749A
Case key
63735

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The loss of engine power due to the pilot's inadequate fuel system management, which resulted in fuel starvation and the loss of engine power.

Sequence of events

NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.

Loss of engine power(total) - nonmechanicalCruise
In-flight planning/decision - inadequatePilot in commandCause
Fluid,fuel - starvationCause
Fuel management - inadequatePilot in commandCause
Forced landingEmergency descent/landing
On ground/water encounter with terrain/waterEmergency landing
Terrain condition - open field

Analysis

The airplane landed gear up during a forced landing in a field following an in-flight loss of engine power. The airplane experienced a loss of engine power after about an hour's flight. The pilot pulled the carburetor heat on first, and then turned on the auxiliary fuel pump, but power was not restored. The pilot then turned the fuel selector from the left main fuel tank to the left auxiliary tank and waited for 1 minute. Power was still not restored. He switched to the right auxiliary fuel tank but still nothing happened. The pilot attempted to restore power by using the primer to pump fuel to the engine. The pilot committed to an off-field landing in an alfalfa field after failing to restore engine power. After clearing power lines, the pilot extended full flaps and opted not to extend his landing gear. An inspection performed at the scene of the accident by Federal Aviation Administration inspectors revealed that both main fuel tanks were completely dry and both auxiliary fuel tanks were full. An inspector placed the fuel selector on the auxiliary tank position and turned on the boost pump. After several seconds, the fuel system pressurized and operated normally. No mechanical problems were found with the fuel system or the airplane.

Factual narrative

On May 19, 2006, about 1115 Pacific daylight time, a Piper PA-24-250, N7857P, performed a gear up forced landing following a loss of engine power near Carson City, Nevada. The owner was operating the airplane under the provisions of 14 CFR Part 91. The private pilot, the sole occupant, was not injured; the airplane sustained substantial damage. The cross-country flight departed Rio Vista, California, municipal airport about 1010, with a planned destination of Minden, Nevada. Visual meteorological conditions prevailed, and no flight plan had been filed.

The pilot submitted a written report. He departed Rio Vista and flew north of Reno at 9,000 feet to avoid bad weather over Lake Tahoe. He contacted Reno approach control 10 miles east of Truckee, California, and stayed in contact with them throughout the flight. At this point, the pilot experienced a loss of engine power. He pulled the carburetor heat on first, and then turned on the auxiliary fuel pump, but power was not restored. The pilot then turned the fuel selector from the main fuel tank to the left auxiliary tank and waited for 1 minute. Power was still not restored. He switched to the right auxiliary fuel tank, but still nothing happened. The pilot attempted to restore power by using the primer to pump fuel to the engine. While troubleshooting the problem, the pilot was in contact with Reno approach control about his situation. After failing to restore engine power, the pilot committed himself to an emergency landing in an alfalfa field east of Washoe Lake. After clearing power lines, the pilot extended full flaps and opted not to extend his landing gear.

A Federal Aviation Administration inspector examined the airplane at the accident site, and submitted a written report. The inspection revealed that both main fuel tanks were completely dry and both auxiliary fuel tanks were full. The inspector placed the fuel selector on the auxiliary tank, and turned on the boost pump. After several seconds, the fuel system pressurized, and operated normally. He found no mechanical problems with the fuel system or the airplane.

According to the Piper Comanche, PA-24-250, Pilot Operating Handbook, the most common cause of an engine failure is mismanagement or malfunction of the fuel system. In this situation, the handbook says the first thing the pilot should do is "move the fuel selector valve to the tank not being used." This will often keep the engine running if there is no fuel system malfunction. If switching the fuel selector does not restore the engine, the pilot should check fuel pressure, turn on the electric fuel pump, push mixture control to full "RICH," apply carburetor heat, and check the ignition switch.

Aircraft

Registration
N7857P
Reported as
Piper PA-24-250
Category
Airplane
Serial number
243080
Engine
Lycoming O-540-A, 250 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
Dennis M. Hope
Registered owner
Lester A. Conklin
Airworthiness certificate
Standard, Normal
Last inspection
Annual · December 1, 2005
Departed
088 · Rio Vista, CA
Destination
MEV · Minden, NV

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
58
Certificate
Private
Airplane ratings
Single-engine land, Multi-engine land
Medical
Class 3
Flight hours
1,605 total · 1,000 in this make and model

Weather

Conditions
Visual (VMC) · Day
Visibility
10 statute miles
Lowest ceiling
6,500 ft overcast

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.

Other investigations on N7857P · 2

Matched to the same aircraft by N-number and date.