ERA12CA276

NTSB accident investigation · Piper PA-28-151 · Iuka, MS · April 10, 2012

Accident · Minor injuriesData collectionFinal report
Date
April 10, 2012, 16:25 local (21:25 UTC)
Place
Iuka, MS
Injuries
2 minor
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N43003Piper PA-28-151
Defining event
Enroute-cruise: Fuel exhaustion
Weather
Visual (VMC) · Day
Status
Completed · report October 15, 2012
Report
Approved by Office Director
NTSB office
Eastern Region Aviation
Parties
FAA/FSDO
FAA report
20120410005989A
Case key
83361

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 preflight planning and inflight fuel management, which resulted in a total loss of engine power due to fuel exhaustion.

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.

Planning/preparation: fuel planningPersonnel issues › Task performance · PilotPiper PA-28-151: 1 caseAll aircraft: 719 casesProbable cause
Fluids: fuelAircraft › Fluids/misc hardware · Fluid managementPiper PA-28-151: 2 casesAll aircraft: 1,695 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

On the day before the accident, the pilot and passenger flew the airplane 575 miles from their home airport to conduct business. The pilot reported that during that flight he observed a discrepancy with the airplane's fuel quantity indicating gauges but that the gauges seemed to work correctly when he "pushed" on the edge of the instrument panel. After landing, the pilot requested that the airplane be refueled, but when he returned the next day to prepare for the return flight, the fuel tanks had not been filled. The pilot visually observed the fuel quantity in both fuel tanks and estimated that there was sufficient fuel for about 3.5 hours of flying, so he decided to take off and stop for fuel during the return flight. About 2.5 hours and 300 miles into the flight, the plot began searching for an airport where he could land and refuel the airplane. Shortly thereafter, the airplane's engine began losing power, so the pilot switched fuel tanks and diverted to nearest airport, which was about 14 miles away. About 4 miles from the airport, the engine lost all power, and the pilot performed a forced landing in a field. The airplane struck several trees during the landing roll, shearing the wings from the fuselage. The pilot reported no preimpact mechanical malfunctions or failures of the airplane, with the exception of the accuracy of the airplane's fuel gauges. Examination of the wreckage at the accident scene revealed no evidence of any fuel, fuel spillage, fuel leakage, or odor of fuel.

Factual narrative

On the day prior to the accident flight, the pilot and the passenger flew the accident airplane 575 miles from their home airport to conduct business. During that flight the pilot reported that there was a discrepancy with the airplane's fuel quantity indicating gauges, and that they seemed to work correctly when he "pushed" on the edge of the instrument panel. After landing, the pilot had requested that the airplane be serviced with fuel, but when he returned the following day for the return flight, the fuel tanks had not been filled. Prior to departing on the accident flight, the pilot visually observed the fuel quantity in both fuel tanks and assumed that the quantity of fuel was sufficient for about 3.5 hours of flying. About 2.5 hours and 300 miles into the flight, with the airplane's fuel gauges displaying that 10 and 7 gallons remained in the left and right fuel tanks, respectively, the plot began searching for an airport where he could land and refuel the airplane. Shortly thereafter, the airplane's engine began losing power, so the pilot switched fuel tanks and diverted to nearest airport, which was about 14 statute miles away. About 4 miles from the airport, the engine lost all power, and the pilot performed a forced landing to a field below. The airplane struck several trees during the landing roll, shearing the wings from the fuselage. The pilot reported no pre-impact mechanical malfunctions or failures of the airplane, with the exception being the accuracy of the airplane's fuel gauges. Examination of the wreckage at the accident scene revealed no evidence of any fuel, fuel spillage, fuel leakage, or odor of fuel.

Aircraft

Registration
N43003
Reported as
Piper PA-28-151
Category
Airplane
Serial number
28-7415407
Engine
Lycoming O-320, 150 horsepower, reciprocating
Damage
Substantial damage
Flight
Business · Part 91
Operator
Siherb Aviation Corp
Registered owner
Siherb Aviation Corp
Airworthiness certificate
Standard, Normal
Departed
HDC · Hammond, LA
Destination
3FK · Franklin, IN

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
61
Injuries
Minor
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, With waivers/limitations
Seat
Left
Flight hours
549 total · 412 in this make and model · 549 as pilot in command · 6 in the last 90 days · 6 in the last 30 days · 6 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
340° at 7 knots
Visibility
10 statute miles
Lowest ceiling
7,500 ft broken
Temperature
70 °F, dew point 45 °F
Altimeter
30.09 inHg
Observed at
CRX, 23 nm away

Docket · 6

The files NTSB released with the investigation on August 10, 2012, on NTSB’s docket system: statements, records, photos and specialists’ reports. 1.4 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.