CEN11LA117

NTSB accident investigation · Piper PA-46-350P · Lake Elmo, MN · December 18, 2010

Accident · Minor injuriesLimited investigationFinal report
Date
December 18, 2010, 17:05 local (23:05 UTC)
Place
Lake Elmo, MN
Injuries
2 minor
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N92358Piper PA-46-350P
Defining event
Enroute-cruise: Fuel starvation
Weather
Visual (VMC) · Night
Status
Completed · report July 21, 2011
Report
Approved by Office Director
NTSB office
Central Region
Parties
FAA Minneapolis FSDO
FAA report
20101218054619A
Case key
78031

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 pilot's improper fuel management which resulted in the loss of engine power due to fuel starvation. Contributing to the accident was the distraction of the cabin depressurization.

Findings · 3

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.

Fluids: fuelAircraft › Fluids/misc hardware · Fluid managementPiper PA 46-350P: 2 casesAll aircraft: 1,695 casesProbable cause
Action: incorrect action performancePersonnel issues › Action/decision · PilotPiper PA 46-350P: 8 casesAll aircraft: 1,386 casesProbable cause
Workload management: task allocationPersonnel issues › Task performance · PilotPiper PA 46-350P: 1 caseAll aircraft: 12 casesProbable cause

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

About an hour after takeoff the airplane was in cruise flight at 16,500 feet mean sea level (msl) when the pilot heard a loud noise followed by a rapid cabin depressurization. The pilot rapidly descended to 10,500 feet msl. The pressurization stabilized and he continued to his destination airport. About 3 hours and 25 minutes after takeoff, the airplane was approaching the destination airport and was about 1,500 feet above ground level when the engine suddenly lost power. The pilot attempted to restart the engine by putting the mixture, propeller, and throttle controls full forward. He turned on the emergency fuel pump and engaged the starter button, but the engine did not start. The pilot executed a forced landing at night to a field that had about 2 - 2.5 feet of snow in it. During the landing roll, the left wing separated from the fuselage. The inspection of the airplane revealed that the right wing fuel tank was empty. The left wing fuel tank was intact and appeared to be full of fuel. The fuel selector was found on the left tank. The pilot reported that he was certain that he had switched tanks sometime during the climb, but was not certain if he had switched tanks after that. The pilot reported that the loss of engine power was the result of fuel starvation.

Factual narrative

On December 18, 2010, at 1705 central standard time (all times cst), a Piper PA-46-350P, N92358, sustained substantial damage during a forced landing to a snow filled field near Lake Elmo, Minnesota, after a loss of engine power in cruise flight. The private pilot and passenger received minor injuries. The 14 Code of Federal Regulations Part 91 personal flight departed Bowling Green-Warren County Regional Airport (BWG), Bowling Green, Kentucky, about 1340 with Anoka County-Blaine Airport (ANE), Anoka, Minnesota, as the intended final destination. Night visual meteorological conditions prevailed at the time of the accident. No flight plan was filed, but the pilot was receiving VFR flight following from air traffic control (ATC). The pilot reported that about an hour after departing BWG, the airplane was in cruise flight at 16,500 feet mean sea level (msl) when he heard a "loud pop" and the airplane had a rapid decompression. The pilot made a rapid descent to 10,500 feet msl. The pressurization stabilized and the pilot continued the flight to ANE. He tried to troubleshoot the pressurization problem by checking the flight manual and making adjustments to the pressurization controls. About 1530, he climbed to 12,500 feet msl to check if the cabin pressurization remained steady. The pilot reported that it remained steady at 5.2 psi with a cabin pressure set at 1,000 feet. About 1615, the pilot started the descent to ANE utilizing VFR flight following. The pilot reported that he was near Hudson, Wisconsin, which is located about 20 nautical miles east-northeast of the Minneapolis-St.Paul International Airport (MSP), at 2,500 feet msl (about 1,500 feet above ground level [agl]), when the engine lost power. He attempted to regain engine power by putting the mixture, propeller, and throttle controls full forward. He turned the emergency fuel pump on and engaged the starter button, but the engine did not restart. He attempted 2 - 3 times to contact MSP Approach Control to declare an emergency but did not get a reply. The pilot then initiated a forced landing to a snow filled field. He made another attempt to contact approach control and was successful. He informed ATC that the airplane was about 200 - 300 feet agl and he was executing a forced landing to a field. He reported that he switched fuel tanks prior to ground impact. The pilot lowered the landing gear and flaps and the stall warning horn was sounding as the airplane touched down in the field that had about 2 - 2.5 feet of snow in it. During the landing roll, the left wing separated from the fuselage. The airplane decelerated quickly and came to rest about 120 feet from the initial touchdown point. The pilot made a phone call to 911, and emergency personnel arrived about 5 - 10 minutes later. A Federal Aviation Administration inspector examined the airplane at the accident site. The inspection of the airplane revealed that the right fuel tank was empty. The left wing had separated from thefuselage, but the left fuel tank was still intact and appeared to be full of fuel. The amount of fuel remaining in the left fuel tank was not measured, and the fuel selector was found on the left tank. The pilot was questioned whether he had switched fuel tanks during the flight. He reported that he was certain that he had switched tanks sometime during the climb, but was not certain if he had switched tanks after that. When asked if fuel starvation had led to the loss of engine power, the pilot reported, "After hearing about the fuel situation in both wings, I have to agree with your assessment of fuel starvation." The Piper PA-46-350P holds 120 gallons of fuel and has a maximum range of 1,261 nautical miles. The pilot reported that the airplane had 120 gallons of fuel on board when he departed BWG.

Aircraft

Registration
N92358
Reported as
Piper PA-46-350P
Category
Airplane
Serial number
4622147
Airframe hours
1,754
Engine
Lycoming TIO-540-AE2A, 350 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
Richard Davidson
Registered owner
Guardian Eagle Company
Airworthiness certificate
Standard, Normal
Last inspection
Annual · May 25, 2010
Departed
BWG · Bowling Green, KY
Destination
ANE · Anoka, MN

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
68
Injuries
Minor
Certificate
Private
Airplane ratings
Multi-engine land, Single-engine sea, Single-engine land
Instrument ratings
Airplane
Medical
Class 3, With waivers/limitations
Seat
Left
Flight hours
5,800 total · 50 in this make and model · 5,700 as pilot in command · 70 in the last 90 days · 25 in the last 30 days · 7 in the last 24 hours

Weather

Conditions
Visual (VMC) · Night
Wind
260° at 6 knots
Visibility
10 statute miles
Lowest ceiling
9,000 ft overcast
Temperature
16 °F, dew point 10 °F
Altimeter
29.92 inHg
Observed at
ANE, 17 nm away

Docket · 9

The files NTSB released with the investigation on June 8, 2011, on NTSB’s docket system: statements, records, photos and specialists’ reports. 2.3 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.