ERA14CA171

NTSB accident investigation · Cessna 172 · Carlisle, PA · March 24, 2014

Accident · Serious injuriesData collectionFinal report
Date
March 24, 2014, 11:45 local (15:45 UTC)
Place
Carlisle, PA
Injuries
1 serious
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N4214FCessna 172
Defining event
Approach-VFR pattern final: Fuel exhaustion
Weather
Visual (VMC) · Night
Status
Completed · report July 30, 2014
Report
Approved by Office Director
NTSB office
Eastern Region Aviation
Parties
FAA/FSDO, Cessna Aircraft Company
FAA report
20140324009189A
Case key
88967

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 decision to depart with a known mechanical malfunction and his improper fuel planning, which resulted in a total loss of engine power due to fuel exhaustion and subsequent impact with terrain during an off-airport landing.

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.

Electrical power system: battery/chargerAircraft › Aircraft systems · MalfunctionCessna 172: 1 caseAll aircraft: 37 casesProbable cause
Planning/preparation: fuel planningPersonnel issues › Task performance · PilotCessna 172: 2 casesAll aircraft: 719 casesProbable cause
Fluids: fuelAircraft › Fluids/misc hardware · Fluid levelCessna 172: 7 casesAll aircraft: 1,695 casesProbable cause
Object/animal/substance: tree(s)Environmental issues › Physical environment · Contributed to outcomeCessna 172: 8 casesAll aircraft: 933 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 had purchased the airplane and planned to fly it across the country "via the southern route." The aircraft seller informed the pilot that the battery held a limited charge, but asserted that the airplane could be flown if the pilot charged the battery and disengaged the master after takeoff. Prior to departure, a mechanic charged the battery for about an hour. The pilot had planned to depart, fly for about 4 hours and then begin to look for an airport to land and obtain fuel. Once he reached his cruising altitude the pilot disengaged the "master." After about 4 hours of flight and in nighttime conditions the pilot found an airport beacon, reengaged the "master" and attempted to activate the runway lights. After several unsuccessful attempts and with the cockpit lights beginning to dim the pilot elected to conserve battery power and find a new airport. About thirty minutes later the pilot found another airport beacon. The airplane "ran out of gas" over a residential area three miles from the pilot's final destination. The pilot made a turn to line the airplane up with a street; however, during the descent to land the airplane collided with tree tops and subsequently impacted the ground resulting in substantial damage to the engine firewall and both wings. The pilot reported the "electrical system failed in the last few minutes of flight" as the only mechanical failure.

Factual narrative

According to the pilot he had purchased the airplane and planned to fly it across the country "via the southern route." The aircraft seller informed the pilot that the battery held a limited charge, but asserted that the airplane could be flown if the pilot charged the battery and disengaged the master after takeoff. Prior to departure, a mechanic charged the battery for about an hour. The pilot had planned to depart, fly for about 4 hours and then begin to look for an airport to land and obtain fuel. Once he reached his cruising altitude the pilot disengaged the "master." After about 4 hours of flight and in nighttime conditions the pilot found an airport beacon, reengaged the "master" and attempted to activate the runway lights. After several unsuccessful attempts and with the cockpit lights beginning to dim the pilot elected to conserve battery power and find a new airport. About thirty minutes later the pilot found another airport beacon. The airplane "ran out of gas" over a residential area three miles from the pilot's final destination. The pilot made a turn to line the airplane up with a street; however, during the descent to land the airplane collided with tree tops and subsequently impacted the ground resulting in substantial damage to the engine firewall and both wings. The pilot reported the "electrical system failed in the last few minutes of flight" as the only mechanical failure.

Aircraft

Registration
N4214F
Reported as
Cessna 172 (UNDESIGNAT)
Category
Airplane
Serial number
46114
Built
1958
Engine
Cont Motor O-300-A, 145 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
Charles McClure
Registered owner
Spurlin Edgar
Airworthiness certificate
Standard, Normal
Departed
PSF · Pittsfield, MA
Destination
Charlotte, NC
Flight plan
VFR

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
59
Injuries
Serious
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, Without waivers/limitations
Seat
Left
Restraint
Lap only
Flight hours
156 total

Weather

Conditions
Visual (VMC) · Night
Wind
40° at 3 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
30 °F, dew point 5 °F
Altimeter
30.13 inHg
Observed at
CXY, 15 nm away

Docket · 5

The files NTSB released with the investigation on June 17, 2014, 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.