FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA22FA223 · Piper PA-24-250

11 May 2022 · Athens, GA, United States

Piper PA-24-250 · Accident on approach

From Triangle North Executive Airport (LHZ) to an unrecorded destination

Report a problem

Event

NTSB case
ERA22FA223
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
1 · all aircraft and ground
Ground fatalities
0
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

Piper PA-24-250

Aircraft type
Piper PA-24
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
N8007P
Operator
Unknown
Onboard fatalities
Unknown
Route
From Triangle North Executive Airport (LHZ), Louisburg, NCTo not recorded
Aircraft age
About 60 years (built 1962)
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
Unknown or undetermined
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft power plant

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot had recently purchased the airplane and wanted to fly with an instructor to familiarize himself with it before flying home to Texas. In the days before the accident, the pilot began two flights with a flight instructor in North Carolina in the accident airplane; however, both flights were cut short because the airplane was not producing full power and the engine was backfiring. On the day of the accident, the instructor contacted the accident pilot to inquire about the troubleshooting. The pilot reported, and logbook entries confirmed, that the spark plugs were cleaned and the fuel servo was adjusted, and that the airplane was returned to service. The pilot also stated to the instructor that he planned to depart to Texas that afternoon. When the instructor suggested that the pilot wait and get more experience in the airplane, the pilot stated that he “felt capable” and was departing in order to “beat the weather.” The accident occurred on the first leg of the pilot’s return flight to Texas. Automatic dependent surveillance – broadcast (ADS-B) data revealed that, about 2 hours and 20 minutes after departure, the pilot performed two 360° turns before proceeding toward a nearby airport, where he contacted the tower controller and received a landing clearance. About one mile from the runway, the pilot declared mayday and reported a loss of engine power. No further transmissions were received; the airplane impacted terrain and a postimpact fire ensued. Examination of the engine did not reveal any evidence of preimpact mechanical malfunctions or failures; however, the examination was limited in scope due to impact damage and thermal damage sustained in the postcrash fire. Recorded engine data revealed that the oil pressure briefly dropped to zero about 11 to 15 minutes before the reported loss of engine power, which corresponded with the two circles the pilot performed before contacting the tower controller; however, the pilot did not communicate any engine issues before the mayday call. Review of maintenance records revealed several entries regarding loss of manifold pressure or backfiring, starting several years before the accident. During the six years before the accident, the airplane accumulated about 22 hours. The most recent engine overhaul was completed almost 33 years before the accident. The manufacturer’s recommended time between engine overhaul was 12 calendar years. Given the repeated, documented maintenance issues before departure and for years before the accident, it is likely that the loss of engine power occurred due to an undiagnosed engine issue that the investigation was not able to identify.

Probable cause

A total loss of engine power for reasons that could not be determined based on the available information.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA22FA223
Event ID
20220512105070
Case number
ERA22FA223
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, cause areas. 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: 9b40854f4be86d379ec68177934cdc36289f0c79371c7e21adb370cb24a80e9e; retrieved 2026-09-15T07:44:15.651Z.