ERA11CA423

NTSB accident investigation · Piper PA-28-161 · Quinton, VA · July 26, 2011

Accident · Minor injuriesData collectionFinal report
Date
July 26, 2011, 04:15 local (08:15 UTC)
Place
Quinton, VA
Injuries
1 minor
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N81917Piper PA-28-161
Defining event
Approach-IFR missed approach: Fuel exhaustion
Weather
Instrument (IMC) · Night
Status
Completed · report November 3, 2011
Report
Approved by Office Director
NTSB office
Eastern Region Aviation
Parties
FAA/FSDO
FAA report
20110726015519A
Case key
81229

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 preflight planning and 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-161: 2 casesAll aircraft: 719 casesProbable cause
Fluids: fuelAircraft › Fluids/misc hardware · Fluid managementPiper PA-28-161: 11 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

Originally the pilot was going to depart earlier on the day of the accident and had planned to stop enroute to his destination for more fuel. After receiving a weather briefing, he decided to delay his departure until later that evening due to the possibility of thunderstorms being present in the vicinity of his destination airport at his planned time of arrival. Prior to departure that evening, he had the fuel tanks filled to capacity. During the flight, and despite his previous flight planning, he did not stop for more fuel. When he was approximately 64 miles from his destination, the pilot noticed that his fuel gauges were indicating that he had less fuel than he anticipated. Upon arrival at his destination, he flew an instrument approach and advised the air traffic controller that he was low on fuel. Due to the visibility, he was unable to see the runway environment and executed a missed approach. He was then instructed by the air traffic controller to climb to 2,000 feet mean sea level (msl). During the climb, the engine lost power and the airplane began to descend, but the pilot was able to restart the engine. He then began climbing back up to 2,000 feet msl; however, the engine lost power again. The airplane once again began to descend, but this time the pilot was unable to restart the engine. The airplane then struck trees and came to rest after falling approximately 20 feet to the ground. Total duration of the flight was approximately 4 hours and 43 minutes. Postaccident examination of the airplane revealed that the firewall and left wing were substantially damaged and both fuel tanks were absent of fuel. There was no evidence of any preimpact mechanical failure or malfunction of the airplane or engine. Correlation of radar and weather data revealed that the pilot would have encountered a headwind for the majority of the flight. When asked by a state trooper how the accident occurred, the pilot advised him that he had run out of fuel.

Factual narrative

Originally the pilot was going to depart earlier on the day of the accident and had planned to stop enroute to his destination for more fuel. After receiving a weather briefing he decided instead to delay his departure until later that evening due to the possibility of thunderstorms being present at his time of arrival in the vicinity of his destination airport. Prior to departure that evening he had the fuel tanks filled to capacity. During the flight despite his previous flight planning, he did not stop for more fuel. When he was approximately 64 miles from his destination, he noticed that his fuel gauges were indicating that he had less fuel than he anticipated. Upon arrival at his destination he flew an instrument approach and advised air traffic control that he was fuel critical, as he had exceeded his estimated flight time, his fuel gauges were indicating a low fuel state, and other aircraft were also landing. Due to the visibility, he was unable to see the runway environment and executed a missed approach. He was then instructed by Air Traffic Control to climb to 2,000 feet above mean sea level (msl). During the climb the engine lost power and the airplane began to descend. The pilot executed the engine restart procedure and was able to get the engine to restart. He then began climbing back up to 2,000 feet msl however, the engine lost power again. The airplane once again began to descend but this time; the pilot was unable to get the engine to restart. The airplane then struck trees and came to rest after falling approximately 20 feet to the ground. Total duration of flight was approximately 4 hours and 43 minutes. Post-accident examination of the airplane by a Federal Aviation Administration inspector revealed that the firewall and left wing were substantially damaged and both fuel tanks were absent of fuel. There was no evidence of any preimpact mechanical failure or malfunction of the airplane or engine. Correlation of radar and weather data revealed that the pilot for the majority of the flight would have encountered headwinds. The airplane was also not equipped with wheel fairings which according to the manufacturer would have further reduced its range by up to 7 percent. When asked how the accident occurred by a state trooper, the pilot advised him that he had run out of fuel.

Aircraft

Registration
N81917
Reported as
Piper PA-28-161
Category
Airplane
Serial number
28-8216139
Airframe hours
13,107
Engine
Lycoming 0-320-D3G, 180 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
Wings of Carolina Flying Club
Registered owner
Fcs Aviation LLC
Airworthiness certificate
Standard, Normal
Last inspection
Annual · July 9, 2011
Departed
CQX · Chatham, MA
Destination
RIC · Richmond, VA
Flight plan
IFR
Airport
RIC · Richmond International Airport, runway 25, 5,326 × 100 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
29
Injuries
Minor
Certificate
Private
Airplane ratings
Single-engine land
Instrument ratings
Airplane
Medical
Class 3, With waivers/limitations
Last flight review
July 21, 2011
Seat
Left
Flight hours
239 total · 29 in this make and model · 169 as pilot in command · 39 in the last 90 days · 22 in the last 30 days

Weather

Conditions
Instrument (IMC) · Night
Wind
220° at 4 knots
Visibility
6 statute miles
Lowest ceiling
600 ft overcast
Temperature
75 °F, dew point 73 °F
Altimeter
29.76 inHg
Observed at
RIC, 6 nm away

Docket · 7

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