ERA22LA028 · Piper PA-24-250
Piper PA-24-250 · Accident: loss of engine power (total) en route
From Youngstown Warren Regional Airport (YNG) to Hilton Head Airport (HXD)
Event
- NTSB case
- ERA22LA028
- 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
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
- N7371P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Youngstown Warren Regional Airport (YNG), Youngstown, OHTo Hilton Head Airport (HXD), Hilton Head Island, SC
- Aircraft age
- About 60 years (built 1961)
- 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
- En route · cruise
- 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
- Loss of engine power (total)
- 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 › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the pilot, he was in cruise flight when the engine lost full power. The pilot reported that he did not have enough time to attempt a restart of the engine or to switch fuel tanks, due to the low altitude of the airplane. He elected to conduct an off-field emergency landing. During the landing, the airplane impacted a tree, which resulted in substantial damage to the left outboard wing, right horizontal stabilizer and fuselage. Examination of the airplane by a Federal Aviation Administration inspector revealed the fuel selector was positioned on the right fuel tank- AUX position. The right fuel tank-AUX fuel tank was checked, and no fuel was discovered in the tank, however, about 75 gallons of fuel was drained from the remaining tanks. In a telephone interview with the pilot, he stated that took off on the right AUX tank. The post-accident examination did not reveal any mechanical malfunctions or anomalies that would have precluded normal operation.
Probable cause
A total loss of engine power due to fuel exhaustion as a result of the pilots mismanagement of fuel.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA22LA028
- Event ID
- 20211025104155
- Case number
- ERA22LA028
- 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, coordinates, 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: b397c17951841395f53083c619191b277265bd5b689dc970702c810a9f77dd46; retrieved 2026-09-16T14:41:52.305Z.