ERA13CA362

NTSB accident investigation · Piper PA-28R-180 · Fredericksburg, VA · August 12, 2013

Accident · No injuriesData collectionFinal report
Date
August 12, 2013, 05:57 local (09:57 UTC)
Place
Fredericksburg, VA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N4969JPiper PA-28R-180
Defining event
Enroute: Fuel exhaustion
Weather
Instrument (IMC) · Night
Status
Completed · report September 12, 2013
Report
Approved by Office Director
NTSB office
Eastern Region Aviation
Parties
FAA/FSDO
FAA report
20130812014539A
Case key
87746

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 pre-flight and in-flight planning and his failure to obtain a weather briefing at his intermediate stops, resulting in a missed approach at his destination and subsequent fuel exhaustion. The pilot’s fatigue due to lack of sleep may have been a factor.

Findings · 5

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: weather planningPersonnel issues › Task performance · PilotPiper PA-28R-180: 3 casesAll aircraft: 156 casesProbable cause
Fluids: fuelAircraft › Fluids/misc hardware · Fluid levelPiper PA-28R-180: 2 casesAll aircraft: 1,695 cases
Planning/preparation: fuel planningPersonnel issues › Task performance · PilotPiper PA-28R-180: 1 caseAll aircraft: 719 casesProbable cause
Alertness/Fatigue: lack of sleepPersonnel issues › Physical · PilotPiper PA-28R-180: 1 caseAll aircraft: 26 casesProbable cause
Ceiling/visibility/precip: low visibilityEnvironmental issues › Conditions/weather/phenomena · Contributed to outcomePiper PA-28R-180: 2 casesAll aircraft: 175 cases

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

According to the pilot, he initiated the first leg of a three-leg cross country flight at night without obtaining a weather briefing, nor did he obtain a briefing at either intermediate stop. Approaching his destination, he checked the weather and was informed that it included one-quarter mile visibility, 200 vertical feet visibility, and the runway was closed. He decided to wait and hold for the runway to open, which was about 30 to 40 minutes, and attempted an ILS approach. He performed the approach but executed a missed approach due to the low visibility conditions. After conferring with air traffic control, he elected to divert, but exhausted his fuel supply prior to performing an approach at the diversion airport. He executed a forced landing in instrument meteorological conditions. The airplane touched down in a grassy area and collided with a curb adjacent to the parking lot of a gas station. An inspector from the Federal Aviation Administration examined the airplane and confirmed that the fuel supply was exhausted and substantial damage was confirmed to the wings and fuselage. The pilot reported no pre-impact mechanical malfunctions or failures with the airplane that would have precluded normal operation. He also reported that he may have been fatigued since he elected to fly all night after working the previous day.

Factual narrative

According to the pilot, he initiated the first leg of a three-leg cross country flight at night without obtaining a weather briefing, nor did he obtain a briefing at either intermediate stop. Approaching his destination, he checked the weather and was informed that it included one quarter mile visibility, 200 vertical feet visibility, and the runway was closed. He decided to wait and hold for the runway to open, which was about 30 to 40 minutes, and attempted an ILS approach. He performed the approach but executed a missed approach due to the low visibility conditions. After conferring with air traffic control, he elected to divert, but exhausted his fuel supply prior to performing an approach at the diversion airport. He executed a forced landing in instrument meteorological conditions. The airplane touched down in a grassy area and collided with a curb adjacent to the parking lot of a gas station. An inspector from the Federal Aviation Administration examined the airplane and confirmed that the fuel supply was exhausted and substantial damage was confirmed to the wings and fuselage. The pilot reported no pre-impact mechanical malfunctions or failures with the airplane that would have precluded normal operation. He also reported that he may have been fatigued since he elected to fly all night after working the previous day.

Aircraft

Registration
N4969J
Reported as
Piper PA-28R-180
Category
Airplane
Serial number
28R-30720
Airframe hours
2,573
Engine
Lycoming I0360 SER, 180 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Standard, Normal
Last inspection
Annual · June 15, 2013 · 54 hours before
Departed
SAV · Savannah, GA
Destination
CHO · Charlottesville, VA
Flight plan
IFR
Airport
EZF · Shannon Airport

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
33
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Instrument ratings
Airplane
Medical
Class 3, Without waivers/limitations
Last flight review
November 1, 2012
Seat
Left
Flight hours
233 total · 71 in this make and model · 175 as pilot in command · 50 in the last 90 days · 15 in the last 30 days · 7 in the last 24 hours

Weather

Conditions
Instrument (IMC) · Night
Wind
Calm
Visibility
2 statute miles
Lowest ceiling
300 ft broken
Temperature
70 °F, dew point 70 °F
Altimeter
30.01 inHg
Observed at
EZF, 1 nm away

Docket · 6

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

Other investigations on N4969J · 1

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