LAX98LA027

NTSB accident investigation · Piper PA-32R-300 · Santa Rosa, CA · October 31, 1997

Accident · No injuriesLimited investigationFinal report
Date
October 31, 1997, 09:25 local (17:25 UTC)
Place
Santa Rosa, CA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N1655HPiper PA-32R-300
Weather
Visual (VMC) · Day
Status
Completed · report June 21, 2000
Report
Approved by Office Director
FAA report
19971031044369A
Case key
29990

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 NTSB’s determination of the probable cause, and any contributing factors.

Loss of engine power for undetermined reasons.

Analysis

While executing an instrument landing system approach to Sonoma County Airport, the airplane experienced a loss of engine power. The airplane was substantially damaged during a forced landing in a vineyard about 1/2 mile short of runway 32. The on-site FAA investigator stated that there was no smell of fuel when he arrived on scene, but the fire department personnel had reported smelling fuel when they arrived at the scene. Both the left and right fuel gauges read zero when the aircraft master switch was on. There was no indication that the propeller was turning when the airplane struck the ground.

Factual narrative

On October 31, 1997, at 0925 hours Pacific standard time, a Piper PA-32R-300, N1655H, was substantially damaged during a forced landing following a sudden engine stoppage 1/2 mile short of runway 32 at Sonoma County Airport, Santa Rosa, California. The solo commercial pilot was not injured. The flight departed Oakland, California, en route to Santa Rosa on a visual flight plan. The flight was being operated by Ameriflight, Inc., of Burbank, California, as an on-demand charter and cargo service. Visual meteorological conditions prevailed at the time and an instrument flight plan had been filed.

The Federal Aviation Administration inspector stated in his report that, although the fire department personnel had smelled fuel when they arrived at the scene, both the left and right fuel tanks were empty. When the master switch was turned on and the fuel selector placed in the left and right tank positions, both fuel gages read zero.

The aircraft engine was subsequently inspected at an aircraft salvage yard and no incorrect assembly, internal failure, or excessively worn parts were found. The magnetos had proper internal and external timing and the ignition harness was intact and functional. Following the inspection, the engine was hooked up to an auxiliary fuel supply, a dummy prop installed, and then started. The engine ran normally up to 20 inches of manifold pressure and 2,200 rpm, the highest that could be safely evaluated on the test stand, with no observed malfunctions.

Following the engine run, the fuel supply can was tipped to uncover the suction tube and interrupt the fuel supply simulating running a tank dry. As soon as the engine started to sputter, the can was righted and the electric boost pump turned on. Although indicated fuel pressure returned to normal, the engine continued to run rough for about 2 minutes and there was no response to throttle or mixture control movements. After approximately 3 minutes, the engine resumed normal operation. This whole process was then repeated with identical results. (The results of this experiment roughly approximated the symptoms described by the pilot that occurred just prior to the forced landing.)

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 powerApproach - vfr pattern - final approach
Reason for occurrence undeterminedCause
Forced landingEmergency descent/landing
In flight collision with terrain/waterEmergency landing
Terrain condition - high vegetation

Aircraft

Registration
N1655H
Reported as
Piper PA-32R-300
Category
Airplane
Serial number
32R-7780170
Airframe hours
3,900
Engine
Lycoming IO-540-K1G5D, 300 horsepower, reciprocating
Damage
Substantial damage
Flight
Part 135
Registered owner
Ameriflight, Inc.
Airworthiness certificate
Standard, Normal
Last inspection
AAIP · October 29, 1997 · 1 hours before
Departed
OAK · Oakland, CA
Destination
STS · CA
Flight plan
VFR

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
28
Certificates
Commercial, Flight instructor
Airplane ratings
Multi-engine land, Single-engine land
Instrument ratings
Airplane
Medical
Class 1, Valid Medical--no waivers/lim.
Seat
Left
Flight hours
1,889 total · 114 in this make and model · 1,734 as pilot in command · 137 in the last 90 days · 57 in the last 30 days · 2 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
5° at 5 knots
Visibility
7 statute miles
Lowest ceiling
None
Temperature
64 °F, dew point 61 °F
Altimeter
30.00 inHg
Observed at
STS, 1 nm away

FAA reports on this event · 1

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