FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA21FA333 · Piper PA24 250

20 Aug 2021 · Wadesboro, NC, United States

Piper PA24 250 · Accident: loss of engine power (partial) during initial climb

From an unrecorded airport to La Belle Municipal Airport (X14)

Report a problem

Event

NTSB case
ERA21FA333
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
2 · 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 PA24 250

Aircraft type
Piper PA24
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
N8262P
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo La Belle Municipal Airport (X14), LaBelle, FL
Aircraft age
About 58 years (built 1963)
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
Initial climb
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 (partial)
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 oper/perf/capability
  • Not determined › Not determined
  • 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 previous owner of the airplane, he sold it to the pilot about 2 weeks before the accident. The pilot, who held and mechanic certificate and an inspection authorization, planned to complete repairs, perform an annual inspection, and fly the airplane to his home airport. The repairs included replacing hoses, rebuilding a jammed fuel selector valve, repairing a corroded fuel line, and removing and checking a magneto. On the day of the accident, the pilot flew the airplane uneventfully for about 30 minutes, from the location where the airplane had been based to an airport along the route home, to purchase fuel. Witnesses reported that, during startup, the engine sputtered and backfired and that, shortly after takeoff, the engine sputtered and backfired again. The airplane then turned left back toward the airport and descended nose down into wooded terrain, where a postcrash fire ensued. The wreckage came to rest in a compact area, about 0.5 miles from the runway departure end, with no debris path observed, consistent with an aerodynamic stall and relatively low-energy impact. One propeller blade remained attached to the propeller hub, and the other blade had separated and was located underneath the engine. Both blades exhibited tip curling and leading-edge damage. Examination of the engine revealed no evidence of any preimpact mechanical malfunctions or failures. Fire damage precluded testing of the carburetor and magnetos. Testing of the airport fuel supply revealed no anomalies, and no issues were reported with other airplanes that received airport fuel that day. The engine sputtering and backfiring reported by the witnesses, as well as the signatures observed on the propeller blade, was consistent with a partial loss of engine power. The reason that the engine lost partial power could not be determined based on the available evidence. Toxicological testing of the pilot identified ethanol in his muscle and brain specimens; however, the difference in the levels of ethanol and the presence of two other alcohols (both primarily produced postmortem) indicated that the ethanol was most likely from postmortem production rather than ingestion. Meclizine, which is often used to treat motion sickness, was found in the pilot’s liver specimens. Although meclizine can cause drowsiness, it likely did not play a role in this accident given that the airplane was observed maneuvering during the final moments of the flight.

Probable cause

A partial loss of engine power during takeoff for reasons that could not be determined. Contributing was the pilot’s loss of airplane control, resulting in an aerodynamic stall and impact with trees and terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA21FA333
Event ID
20210820103731
Case number
ERA21FA333
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: 94a1f78d944664cc0a058ecebe311fd48d2c668cee195706da23a8550cfb0a27; retrieved 2026-09-15T07:33:18.964Z.