FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA24FA050 · Piper PA32R 301T

27 Nov 2023 · Attalla, AL, United States

Piper PA32R 301T · Accident: powerplant system/component malfunction/failure en route

From Scott Municipal Airport (SCX) to H L Sonny Callahan Airport (CQF)

Report a problem

Event

NTSB case
ERA24FA050
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 PA32R 301T

Aircraft type
Piper PA32
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
N4187Q
Operator
Unknown
Onboard fatalities
Unknown
Route
From Scott Municipal Airport (SCX), Oneida, TNTo H L Sonny Callahan Airport (CQF), Fairhope, AL
Aircraft age
About 22 years (built 2001)
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
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
Powerplant system/component malfunction/failure
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
  • Environmental issues › Operating environment

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

While on a night cross-country flight in visual meteorological conditions, the airplane began descending, then the pilot declared an emergency and informed the controller of a loss of engine power. The controller advised the pilot of his proximity to two airports and after turning onto a westerly heading consistent with flying toward Robbins Field Airport (20A), Oneonta, Alabama, which was located about 16 nm west-southwest from the airplane’s position, the pilot realized he was closer to Northeast Alabama Regional Airport (GAD), Gadsden, Alabama, whose runways were both closed by NOTAM. The pilot twice asked about GAD, and the controller informed him both times that GAD’s longer runway was closed, and its shorter runway did not have lights. The controller also told the pilot that work was being performed on GAD’s runways, and landing there would not be feasible.

The flight continued in the general direction of 20A but was unable to reach it due to the distance, altitude, and descent rate of the airplane with reduced engine power. While maintaining controlled flight in a wings-level, slightly nose-low descent, the airplane impacted trees in mountainous terrain about 11 nm and 3.7 nm from 20A and GAD, respectively. The airplane was destroyed by a postcrash fire.

Postaccident examination of the engine revealed that one pawl retaining rivet of the left magneto impulse coupling exhibited fatigue fracture features that originated at areas of heavy wear along the shaft, followed by overload fracture. The other pawl retaining rivet also exhibited wear on the rivet shaft and subsequently fractured due to torsional and shear overstress. Deformation on the respective holes of the impulse hub assembly was noted, consistent with relative movement of the impulse hub assembly. Additional overload fractures occurred in the left magneto gear retainer assembly and multiple gear teeth of multiple gears in the accessory section of the engine, including the fuel pump idler gear assembly.

Although the airplane was equipped with an independent right magneto that was capable of operating and producing spark to one spark plug of each cylinder and an auxiliary fuel pump that was capable of providing adequate fuel to the engine in the event of an engine-driven fuel pump failure, the switch positions and operational status of these components could not be determined due to the extent of the postcrash fire. Thus, the loss of engine power was likely the result of the cascading effects from the fracturing of the left magneto gear retainer assembly and multiple gear teeth of multiple gears in the accessory section, including the fuel pump idler gear assembly.

Although both rivets and holes of the left magneto impulse hub assembly exhibited wear consistent with being loose relative to each other, the investigation could not determine when that wear or fatigue initiated, or if either was present at the last impulse coupling inspection performed about 1.5 years and 300 hours before the accident, in accordance with a non-mandatory service bulletin.

At the time the pilot declared an emergency, all construction personnel for a runway sealcoating project at GAD had left the airport, one runway was free of equipment, and both runways had operable pilot-controlled lighting. Based on the airplane’s distance flown after the pilot declared an emergency and the actual status of GAD’s runways, it is likely that the pilot could have conducted an emergency landing at GAD had he expeditiously diverted there. However, because GAD is a non-towered airport and no airport personnel were present, it would have been difficult for the controller to obtain details about the current runway conditions at GAD (beyond what the NOTAMs provided) and to relay this information to the pilot in a timely manner. Although the pilot could have exercised his authority as pilot-in-command in an emergency situation to land at GAD after being advised by the controller that its runways were closed, the information available to the pilot likely led him to proceed toward 20A instead.

Probable cause

The undetected wear of both pawl retaining rivets of the left magneto impulse coupling and fatigue failure of one pawl retaining rivet, which led to cascading fractures of the second pawl retaining rivet, left gear retainer assembly, and gear teeth of multiple gears in the accessory section of the engine and resulted in a loss of engine power. Contributing to the accident was the lack of current information available to the pilot regarding the status of a nearby airport’s closed runways.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA24FA050
Event ID
20231128193432
Case number
ERA24FA050
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: c1b8874e34d99504376941c7d7ec5d9433e5dd901486becab988e4a1cf1e191a; retrieved 2026-09-15T08:08:32.110Z.