DFW07CA034

NTSB accident investigation · Piper PA-24-250 · Jacksboro, TX · December 3, 2006

Accident · No injuriesData collectionFinal report
Date
December 3, 2006, 15:45 local (21:45 UTC)
Place
Jacksboro, TX
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N5697PPiper PA-24-250
Weather
Visual (VMC) · Day
Status
Completed · report March 26, 2007
Report
Approved by Office Director
FAA report
20061203025909A
Case key
64965

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 NTSB’s determination of the probable cause, and any contributing factors.

The pilot's improper fuel calculations, which resulted in a loss of engine power due to fuel exhaustion. A factor was the unsuitable terrain encountered during the emergency landing.

Analysis

The 385-hour private pilot reported that the fuel tanks on the single engine airplane were topped off with 90 gallons of aviation fuel for the 874.6 nautical mile cross country flight that originated at 0900. At 1530, while the airplane was in cruise flight about 10 minutes from his intended destination, the engine lost power. The pilot elected to execute a forced landing to a rough, mesquite covered field. The airplane sustained structural damage during the forced landing; however, the pilot and his passenger were able to egress from the airplane unassisted. The FAA inspector who traveled to the accident site discovered that the fuel cells were empty. The pilot added that he "ran out of fuel" and he had relied on a fuel computer that indicated there was 14 gallons (1.1 hours) of fuel remaining when the engine lost power. He added that the engine power loss could have been prevented if he had used a fuel burn rate of 13 gallons per hour and had restricted his endurance to a maximum of 6 hours.

Factual narrative

The 385-hour private pilot reported that the fuel tanks on the single engine airplane were topped off with 90 gallons of aviation fuel for the 874.6 nautical mile cross country flight that originated at 0900. At 1530, while the airplane was in cruise flight about 10 minutes from his intended destination, the engine lost power. The pilot elected to execute a forced landing to a rough, mesquite covered field. The airplane sustained structural damage during the forced landing; however, the pilot and his passenger were able to egress from the airplane unassisted. The FAA inspector who traveled to the accident site discovered that the fuel cells were empty. The pilot added that he "ran out of fuel" and he had relied on a fuel computer that indicated there was 14 gallons (1.1 hours) of fuel remaining when the engine lost power. He added that the power loss could have been prevented if he had used a fuel burn rate of 13 gallons per hour and had restricted his flight to a maximum of 6 hours.

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 power(total) - nonmechanicalCruise
Fuel consumption calculations - improperPilot in commandCause
Fluid,fuel - exhaustionCause
Forced landingEmergency descent/landing
On ground/water encounter with terrain/waterEmergency landing
Terrain condition - none suitableFactor
Terrain condition - rough/uneven

Aircraft

Registration
N5697P
Reported as
Piper PA-24-250
Category
Airplane
Serial number
24770
Engine
Lycoming 0-540, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Registered owner
Billie Joe Eaton
Airworthiness certificate
Standard, Normal
Departed
VGT · North Las Vegas, NV
Destination
XPB · Bridgeport, TX

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
48
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3
Flight hours
385 total · 67 in this make and model

Weather

Conditions
Visual (VMC) · Day

FAA reports on this event · 1

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

Other investigations on N5697P · 3

Matched to the same aircraft by N-number and date.