CHI02LA052

NTSB accident investigation · Piper PA-34 · Clinton, MO · December 17, 2001

Accident · Minor injuriesLimited investigationFinal report
Date
December 17, 2001, 08:15 local (14:15 UTC)
Place
Clinton, MO
Injuries
2 minor, 1 uninjured
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N4354APiper PA-34
Weather
Instrument (IMC) · Day
Status
Completed · report July 15, 2002
Report
Approved by Office Director
Parties
FAA
FAA report
20011217034529A
Case key
53917

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 inadequate prefight, his failure to feather the propellers, and the fuel exhaustion.

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 powerCruise
Preflight planning/preparation - inadequatePilot in commandCause
Fuel system - starvation
Forced landingDescent - emergency
In flight collision with terrain/waterApproach - vfr pattern - final approach
Emergency procedure - not performedPilot in commandCause
Fuel system - exhaustionCause
Terrain condition - crop

Analysis

The airplane sustained substantial damage during a forced landing to a field, 500 feet short of the runway. While in cruise flight at 8,000 feet msl on an IFR flight plan, the airplane lost power on one engine. An emergency was declared and the airplane was given radar vectors to an airport. The pilot made a visual approach to the airport, but on final approach, the airplane lost power to the remaining engine and landed short of the runway. The pilot reported that during preflight he did not visually verify the fuel load by removing the fuel caps and looking into the fuel tanks, since there was "...standing water in the fuel caps and a moderate rainfall at near freezing [temperatures] and I did not want to contaminate my fuel." He reported that during taxi for takeoff the fuel gages read 1/2 full. He reported he expected to be able to return "...with just over an hour of fuel on board and leaving on a 45 minute flight." He reported that, "20 minutes into the flight my fuel gages began falling to empty." He reported, "30 miles west of GLY the right engine quit [.] I secured the engine and declared the emergency." The pilot requested radar vectors for GLY. The pilot reported he found a hole in the clouds and descended through it. He reported he was, "...getting established on a short final [when] the left engine quit with the aircraft settling short of the runway." The inspection of the airplane revealed there was no fuel in the tanks and neither propeller was found in the feathered position.

Factual narrative

On December 17, 2001, at 0815 central standard time, a Piper PA-34, N4354A, sustained substantial damage during a forced landing to a field, 500 feet short of runway 22 at the Clinton Memorial Airport (GLY), Clinton, Missouri. The 14 CFR Part 91 business flight departed Springfield Downtown Airport (3DW), Springfield, Missouri, at 0715 on an instrument flight rules (IFR) flight plan en route to Kansas City Downtown Airport (MKC), Kansas City, Missouri. While in cruise flight at 8,000 feet msl and approximately 30 miles west GLY, the airplane lost power on one engine. An emergency was declared and the airplane was given radar vectors to GLY. The pilot made a visual approach to the airport, but on final approach, the airplane lost power to the remaining engine and landed short of the runway. The commercial pilot was not injured and the two passengers received minor injuries. At 0737, Whiteman AFB, located 24 nautical miles to the north of GLY, was reporting instrument meteorological conditions. The flight was on an IFR flight plan.

The pilot reported that during preflight he did not visually verify the fuel load by removing the fuel caps and looking into the fuel tanks, since there was "...standing water in the fuel caps and a moderate rainfall at near freezing temps [temperatures] and I did not want to contaminate my fuel." He reported that during taxi for takeoff the fuel gages read 1/2 full. He reported he expected to be able to return "with just over an hour of fuel on board and leaving on a 45 minute flight."

He reported that, "20 minutes into the flight my fuel gages began falling to empty... ." He reported, "...30 miles west of GLY the right engine quit [.] I secured the engine and declared the emergency." The pilot requested radar vectors for GLY. The pilot reported he found a hole in the clouds and descended through it. He reported he was, "...getting established on a short final [when] the left engine quit with the aircraft settling short of the runway."

The inspection of the airplane revealed there was no fuel in the tanks or fuel lines, and neither propeller was found in the feathered position.

Aircraft

Registration
N4354A
Reported as
Piper PA-34
Category
Airplane
Serial number
34-8433041
Engine
Continental TSIO360 KB, 220 horsepower, reciprocating
Damage
Substantial damage
Flight
Business · Part 91
Registered owner
Great Southern Bank
Airworthiness certificate
Standard, Normal
Departed
3DW · Springfield, MO
Destination
MKC · Kansas City, MO
Flight plan
IFR
Airport
GLY · Clinton Memorial Airport, runway 22, 4,000 × 60 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
36
Injuries
None
Certificate
Commercial
Airplane ratings
Multi-engine land, Single-engine land
Instrument ratings
Airplane
Medical
Class 1, Valid Medical--no waivers/lim.
Last flight review
November 30, 2001
Seat
Left
Flight hours
6,803 total · 1,439 in this make and model · 6,091 as pilot in command · 99 in the last 90 days · 42 in the last 30 days

Weather

Conditions
Instrument (IMC) · Day
Wind
310° at 12 knots
Visibility
3 statute miles
Lowest ceiling
800 ft broken
Temperature
43 °F, dew point 37 °F
Altimeter
29.95 inHg
Observed at
SZL, 24 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.