WPR10LA051

NTSB accident investigation · Piper PA-32R-300 · Tucson, AZ · November 8, 2009

Accident · No injuriesLimited investigationFinal report
Date
November 7, 2009, 17:00 local (Nov 8, 2009, 00:00 UTC)
Place
Tucson, AZ
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N2165MPiper PA-32R-300
Defining event
Enroute-cruise: Loss of engine power (partial)
Weather
Visual (VMC) · Day
Status
Completed · report April 20, 2012
Report
Approved by Office Director
NTSB office
Western Pacific Region
Parties
Federal Aviation Administration
FAA report
20091107022299A
Case key
75036

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

A loss of engine power for undetermined reasons.

Findings · 2

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Not determinedNot determined › Not determined · Unknown/Not determinedPiper PA-32R-300: 5 casesAll aircraft: 2,247 casesProbable cause
Object/animal/substance: sign/markerEnvironmental issues › Physical environment · Contributed to outcomePiper PA-32R-300: 1 caseAll aircraft: 214 cases

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

While descending for landing, the engine lost partial power and the airplane could not maintain altitude. The pilot attempted to divert to a nearby airport; however, he was not able to arrest the airplane's descent and had to make a forced landing to a road. The pilot stated that about 20 feet above the ground, he believes the engine lost all power. The airplane landed hard, struck a road sign, departed the paved surface, and came to rest on the desert floor. A postaccident examination of the airplane and the fuel-injected engine revealed no mechanical anomalies that would have precluded normal operation.

Factual narrative

On November 7, 2009, at 1700 mountain standard time, a Piper PA-32R-300, N2165M, experienced a partial loss of engine power in cruise flight and made an emergency landing on a highway about 32 miles northwest of the Tucson International Airport (TUS), Tucson, Arizona. The owner/pilot operated the airplane under the provisions of 14 Code of Federal Regulation Part 91, as a personal flight. The private pilot and one passenger were not injured. The airplane sustained structural damage to the fuselage after departing the highway and impacting a road sign and cacti prior to coming to rest upright. Visual meteorological conditions prevailed for the local area flight that departed Phoenix-Mesa Gateway Airport (IWA), Phoenix, Arizona, at 1616. No flight plan had been filed. According to the pilot's written statement, he had been cleared direct to TUS via global positioning system (GPS) at 6,500 feet mean sea level (msl). About 35 miles northwest of TUS, he started the descent to 4,500 feet msl. As the airplane passed through 5,000 feet, he configured the manifold pressure and rpm (24/2,400) per the airplane's pilot operating handbook (POH) for 4,000 feet at 75 percent power. Shortly thereafter, he felt the airplane 'lurch,' as if the engine had lost rpm's. He increased the engine power, the fuel mixture, and moved the propeller to the FULL in position in an attempt to get more engine power. The pilot stated that the engine continued to run, and the propeller was still spinning, it just was not enough power to hold altitude; he noted a 500-foot-per-minute descent that he was not able to arrest. The pilot radioed TUS to report a partial engine failure and his current position. TUS tower personnel gave him vectors to a closer airport; however, as he made the turn toward the airport, the airplane lost altitude too quickly and he knew that the airplane would not make the airport. The pilot stated that there was a road below the airplane and he attempted to land on the road. He believes that about 20 feet above the ground, the engine quit, and the airplane landed hard. Upon touchdown, he heard a 'thud' and ascertained that the airplane had departed the roadway and onto the adjacent desert floor. After the accident, the pilot reported that the airplane had struck a road sign. An engine inspection was performed by investigators from the National Transportation Safety Board (NTSB) and from Lycoming Engines. Under the supervision of the NTSB investigator, the cowling was removed. There were no obvious signs of a mechanical failure. All fuel lines were secure, and no fluid leaks were observed. The magnetos were secure and tight on their respective mounting pads. Manual rotation of the propeller produced thumb compression in all six cylinders. The servo plug remained in place and was secured by safety wire. No mechanical anomalies were noted that would have precluded normal operation.

Aircraft

Registration
N2165M
Reported as
Piper PA-32R-300
Category
Airplane
Serial number
32R-7880053
Airframe hours
15,362
Engine
Lycoming Engines IO-540-K1G5, 300 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Standard, Normal
Last inspection
Annual · April 1, 2009 · 23 hours before
Departed
IWA · Mesa, AZ
Destination
TUS · Tucson, AZ
Airport
TUS · Tucson International Airport

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, Without waivers/limitations
Last flight review
October 8, 2009
Seat
Left
Flight hours
121 total · 22 in this make and model · 30 as pilot in command · 33 in the last 90 days · 2 in the last 30 days

Weather

Conditions
Visual (VMC) · Day
Wind
Calm
Visibility
10 statute miles
Lowest ceiling
None
Temperature
82 °F, dew point 27 °F
Altimeter
29.87 inHg
Observed at
TUS, 32 nm away

Docket · 5

The files NTSB released with the investigation on March 1, 2012, on NTSB’s docket system: statements, records, photos and specialists’ reports. 3.1 MB in all.

FAA reports on this event · 1

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