LAX01LA097

NTSB accident investigation · Piper PA-24-250 · Petaluma, CA · February 14, 2001

Accident · No injuriesLimited investigationFinal report
Date
February 14, 2001, 12:30 local (20:30 UTC)
Place
Petaluma, CA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N8286PPiper PA-24-250
Weather
Visual (VMC) · Day
Status
Completed · report November 6, 2001
Report
Approved by Office Director
Parties
FEDERAL AVIATION ADMINISTRATION
FAA report
20010214003459A
Case key
51734

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

Failure of non-airframe and powerplant mechanic/certificated owners to properly install a new mixture cable that became entangled in the nose landing gear during its extension for landing, resulting in a 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 powerLanding
Maintenance,installation - improperUnqualified personCause
Mixture control,linkage - disengagedCause
Forced landingDescent - emergency
In flight collision with objectGo-around (vfr)
Object - tree(s)
Hard landingEmergency landing
Terrain condition - open field

Analysis

During landing, the engine lost power. The airplane collided with trees, and made a hard landing in an open dirt field in the ensuing forced landing. On the downwind leg for landing, the pilot lowered the landing gear, and the engine began to run rough. He noted that the landing gear stopped about halfway down. He attempted to add power, but did not receive a corresponding power increase, and set up for an emergency landing. A visual external examination of the engine revealed that the mixture cable was entangled in the nose landing gear. When the landing gear was lowered the mixture cable was pulled out of its sleeve, which allowed the engine to be in a full lean position. Mixture, throttle, and propeller cables were recently installed by the pilot and his two partners. The pilot and his partners were not certificated A & P mechanics, and a certified mechanic had not returned the airplane to service after the cable installation. The last entry in the logbook was made 6 months prior to the accident,.

Factual narrative

On February 14, 2001, at 1230 hours Pacific standard time, a Piper PA-24-250, N8286P, experienced a loss of power during landing at the Petaluma Muni Airport, Petaluma, California. The airplane collided with a tree and impacted the ground 100 yards short of the runway. The airplane was owned and operated by the private pilot under the provisions of 14 CFR Part 91 as a personal flight, and sustained substantial damage. The pilot was not injured. Visual meteorological conditions prevailed. No flight plan had been filed. The flight departed the Sonoma County Airport, Santa Rosa, California, at 1145, and was scheduled to terminate at the Petaluma airport.

An inspector from the Federal Aviation Administration (FAA) interviewed the pilot. The pilot stated that he conducted the prelanding checklist on downwind for runway 11, which included reducing power and lowering the landing gear. He saw the instrument panel flex forward and the engine began to run rough. He attempted to add power, but there was not a corresponding power increase. The pilot stated that he set the airplane up for best glide and continued the flight to the airport. About 300 yards from the end of runway 29 the airplane struck a tree. The airplane continued over a street and fence, where it came to rest about 150 yards from the departure end of runway 29.

In the pilot's written statement to the Safety Board he indicated that the landing gear stopped about halfway down and then he felt a "severe" vibration. After the engine quit he continued in the pattern to set up for an emergency landing in an open field on airport property.

The airplane was inspected on scene by an FAA inspector. He visually inspected the fuel tanks. Each outboard fuel tank had half a tank of fuel, and the main fuel tanks were full.

During the inspection of the airplane, the FAA inspector noted that the mixture cable was entangled in the nose landing gear. When the landing gear was lowered, it pulled the mixture cable "out of its holder," which allowed the engine to be in a full lean position.

The pilot informed the FAA inspector that he and his two partners had recently installed the mixture, throttle, and propeller cables. The FAA inspector reported that the pilot and his partners were not certified airframe and power plant (A & P) mechanics. He further noted that a certificated A & P mechanic had not returned the airplane to service.

A review of the airplane logbook by the Safety Board investigator disclosed that the last entry was made on September 18, 2000.

Aircraft

Registration
N8286P
Reported as
Piper PA-24-250
Category
Airplane
Serial number
24-3538
Airframe hours
2,339
Engine
Lycoming O-540-A1D5, 250 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Registered owner
Thomas A. Conroy
Airworthiness certificate
Standard, Normal
Last inspection
Annual · March 3, 2000
Departed
STS · Santa Rosa, CA
Destination
O69 · Petaluma, CA
Airport
O69 · Petaluma Muni, runway 11, 3,600 × 75 ft, asphalt

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
38
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, Valid Medical--no waivers/lim.
Last flight review
March 18, 2000
Seat
Left
Flight hours
331 total · 241 in this make and model · 294 as pilot in command · 3 in the last 90 days · 1 in the last 30 days

Weather

Conditions
Visual (VMC) · Day
Wind
200° at 5 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
54 °F, dew point 32 °F
Altimeter
30.05 inHg
Observed at
STS, 22 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.