ERA14CA171 · Cessna 172 UNDESIGNAT
Cessna 172 UNDESIGNAT · Accident: fuel exhaustion on approach
From Pittsfield Municipal Airport (PSF) to Charlotte, NC
Event
- NTSB case
- ERA14CA171
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 172 UNDESIGNAT
- Aircraft type
- Cessna 172
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N4214F
- Operator
- Charles McClure
- Onboard fatalities
- Unknown
- Route
- From Pittsfield Municipal Airport (PSF), Pittsfield, MATo Charlotte, NC
- Aircraft age
- About 56 years (built 1958)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach · VFR pattern final
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Fuel exhaustion
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft systems
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB 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.
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14CA171
- Event ID
- 20140325X21134
- Case number
- ERA14CA171
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: b2425f4c244ece3112f3d06bbf12e25d29fa24967d10bce109c7364a5808ed85; retrieved 2026-09-15T23:26:58.525Z.