Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

March 24, 2014 · Cessna 172 Undesignat · N4214F

Carlisle, PA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
March 24, 2014
Injury Outcomes
1 injury (1 serious injury)
Location
Carlisle, PA
Aircraft
Cessna 172 Undesignat (1958)
Tail Number
N4214F
Operator
Charles Mcclure
Injuries
Serious
Aircraft Damage
Substantial
NTSB Number
ERA14CA171

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.

NTSB 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.

Full 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.

Flight

Event TypeAccident
Event Time11:45 EDT
Nearest Airport0nm
Flight Plan FiledVFR
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172 Undesignat
Tail NumberN4214F
Aircraft CategoryAir
DamageSubstantial
OperatorCharles Mcclure
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsCont Motor · O-300-A · Reciprocating · 145
Seats2

People & Injuries

Injury Summary1 injury (1 serious injury)
Fatal0
Serious1
Minor0
Uninjured0
Total1
Crew 1Age 59 · Third Class · Serious

Conditions

ConditionsVMC
LightNight
Wind40° @ 3 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point30 C / 5 C
Altimeter30.13 inHg
Observation Time03:56
Weather SourceWFAC

Appendix: Source Data