NTSB CAROL · Event
Event ERA24FA050
Registry · N4187Q
FAA Aircraft Registry record.
Make / Model
PIPER PA-32R-301T
Year of manufacture
2001 · 22 years old at event
Engine
LYCOMING TI0-540 SER (310 hp)
Seats / Engines
7 seats · 1 engine
Last airworthiness date
20010328
ADS-B equipped
Yes — Mode-S A4F534
Registrant of record
AGGIE80 AIR LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
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.
Factual narrative
HISTORY OF FLIGHTOn November 27, 2023, about 1748 central standard time, a Piper PA-32R-301T airplane, N4187Q, was destroyed when it was involved in an accident near Attalla, Alabama. The private pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations (CFR) Part 91 personal flight. The pilot was on an instrument flight rules clearance from Scott Municipal Airport (SCX), Oneida, Tennessee, to H L Sonny Callahan Airport (CQF), Fairhope, Alabama. According to FAA ADS-B data and air traffic control audio information, after takeoff the airplane proceeded toward the destination while the pilot established contact with several air traffic control facilities appropriate for the route of flight. ADS-B data indicated that after 1743:03, the airplane began a descent that was not instructed by the controller or broadcast by the pilot. At that time, the flight was about 4 nm north-northeast from the approach end of runway 18 at Northeast Alabama Regional Airport (GAD), Gadsden, Alabama, flying on a south-southwesterly track. At 1743:35, while in contact with the South Radar position of the Birmingham Airport Traffic Control Tower, the pilot advised the controller, “I have lost um my rpm on my engine and so um I am declaring an emergency.” The controller advised the pilot that Albertville Regional Airport – Thomas J Brumlik Field (BFZ), Albertville, Alabama, was to his right at 12 miles and Birmingham-Shuttlesworth International Airport (BHM), Birmingham, Alabama, “would be twelve o’clock and about three zero miles say intentions.” ADS-B data reflected that about the time the controller provided the distances to the two airports, the airplane was actually located about 15 nm from the center of BFZ and about 45 nm from the center of BHM. Shortly after the pilot declared an emergency, the airplane turned right to a westerly track. While on that track, the pilot recognized that he was close to GAD and asked about it, but the controller advised him that the longer runway (6/24) was closed and the shorter runway (18/36) did not have any runway lights, “so that not gonna be feasible for us.” The pilot again questioned the controller about GAD and was again informed of the runway closure, and that runway 18/36 “has got work on it as well with no lights.” At 1744:58, when the flight was about 3 nm nearly due north from the approach end of runway 18 at GAD and 15 nm east-northeast from the center of 20A, the pilot asked the controller for a heading to the “closest one” and was given vectors to 20A. The airplane remained on a westerly track until 1745:43. At that time, while flying at 3,150 ft mean sea level (msl), the airplane turned left to a south-southwesterly track. The airplane continued descending on that same track when, at 1746:04, the pilot informed the controller that the airplane was at 3,000 ft msl. About 26 seconds later, the pilot advised the controller that he did not have any airport in sight. The flight continued, and the last ADS-B target was at 1746:34, when the airplane was at 2,300 ft msl. At 1747:32, the controller advised the pilot that radar contact was lost and asked if the pilot had a nearby highway in sight, to which the pilot replied “I,” but the rest of the comment was unintelligible. At 1748:02, the pilot’s last recorded transmission advised the controller that he had a terrain warning, and the airplane was at 1,100 ft msl. One witness, who was located about 1,083 ft north-northeast from the accident site, reported hearing an airplane flying low; the witness then heard an explosion and felt it shake the house. A second witness, who was located 2,020 ft northeast of the accident site, reported seeing a fireball after the accident. Security cameras about 4,000 ft northwest of the accident site depicted the airplane flying from left to right, with a large fireball recorded at 1748:10. The videos did not contain sound. The accident site was located about 3.7 nautical miles west-northwest from the center of GAD. AIRCRAFT INFORMATIONA factory-rebuilt engine equipped with a Slick by Champion model 6361 impulse coupling magneto in the left position was installed on the airplane on November 20, 2018, at airplane total time of 2214.0 hours. The magneto manufacturer called for a 500-hour inspection of the impulse coupling, as specified by Slick Service Bulletin SB1-86C. The 500-hour inspection required inspection of the impulse coupling pawl retaining rivets dimensionally and for looseness and any indications of movement. A review of engine maintenance records revealed that on April 15, 2022, at a reported airframe total time of 3,197.9 hours (983.9 hours since engine rebuild), a 500-hour inspection of the left and right magnetos was performed. According to an electronic pilot logbook that was current as of about 5 days before the accident, the pilot had operated the airplane for about 300 hours since the 500-hour magneto inspection had been performed. The airplane was equipped with an electrically-operated auxiliary fuel pump for use, in part, in case of failure of the engine-driven fuel pump, while the engine was equipped with two independent magnetos, each providing spark to one spark plug for each cylinder. Each magneto contained a gear retainer assembly with drive cushions and was installed onto the engine accessory case and driven by separate crankshaft idler gears. The left magneto also contained an impulse coupling, which was a mechanical device to assist in engine starting. At low cranking speed, the magneto impulse coupling would retard the magneto ignition timing and provide a brief acceleration that produced an intense spark for starting. After engine start, the impulse coupling would disengage and return the magneto to normal engine timing. The airplane Pilot’s Operating Handbook and FAA-Approved Airplane Flight Manual checklists for loss of engine power in-flight and engine-driven fuel pump failure both instructed the pilot to turn on the electric fuel pump. Based on pilot logbook information and ADS-B data, the airplane had been operated about 113 hours since the airplane’s last annual inspection. AIRPORT INFORMATIONA factory-rebuilt engine equipped with a Slick by Champion model 6361 impulse coupling magneto in the left position was installed on the airplane on November 20, 2018, at airplane total time of 2214.0 hours. The magneto manufacturer called for a 500-hour inspection of the impulse coupling, as specified by Slick Service Bulletin SB1-86C. The 500-hour inspection required inspection of the impulse coupling pawl retaining rivets dimensionally and for looseness and any indications of movement. A review of engine maintenance records revealed that on April 15, 2022, at a reported airframe total time of 3,197.9 hours (983.9 hours since engine rebuild), a 500-hour inspection of the left and right magnetos was performed. According to an electronic pilot logbook that was current as of about 5 days before the accident, the pilot had operated the airplane for about 300 hours since the 500-hour magneto inspection had been performed. The airplane was equipped with an electrically-operated auxiliary fuel pump for use, in part, in case of failure of the engine-driven fuel pump, while the engine was equipped with two independent magnetos, each providing spark to one spark plug for each cylinder. Each magneto contained a gear retainer assembly with drive cushions and was installed onto the engine accessory case and driven by separate crankshaft idler gears. The left magneto also contained an impulse coupling, which was a mechanical device to assist in engine starting. At low cranking speed, the magneto impulse coupling would retard the magneto ignition timing and provide a brief acceleration that produced an intense spark for starting. After engine start, the impulse coupling would disengage and return the magneto to normal engine timing. The airplane Pilot’s Operating Handbook and FAA-Approved Airplane Flight Manual checklists for loss of engine power in-flight and engine-driven fuel pump failure both instructed the pilot to turn on the electric fuel pump. Based on pilot logbook information and ADS-B data, the airplane had been operated about 113 hours since the airplane’s last annual inspection. WRECKAGE AND IMPACT INFORMATIONExamination of the accident site revealed the airplane impacted heavily wooded, mountainous terrain about 11 nm east-northeast from 20A, the airport to which the pilot was vectored. A postimpact fire started a forest fire, which burned several acres. Small fires remained burning among the wreckage throughout the on-site examination. Further examination of the accident site revealed impact-damaged trees at decreasing heights of about a 10° slope from the first impacted tree to the resting position of the main wreckage about 220 ft away. The damage to the trees was consistent with the airplane being in a wings-level attitude on an energy path of about 190° magnetic. Examination of the wreckage revealed the cockpit, cabin, empennage up to about 60 inches forward of the leading edge of the stabilator, and both wings were extensively damaged by postimpact fire. Both wing leading edges displayed damage consistent with tree strikes. The engine, which remained attached to the firewall by the engine mount, was upright, and the attached propeller sustained significant postimpact fire damage. No identifiable instruments, gauges, or switches were located in the cockpit. The airframe fuel system was largely destroyed by impact forces and postimpact fire. The fuel selector valve was heavily fire damaged; although it was found in the right tank position, its preimpact position could not be determined because portions of it were missing and it was free to move. The electric fuel pump was not located. Examination of the flight controls for roll, pitch, and yaw revealed no evidence of preimpact failure or malfunction. The stabilator trim actuator had one inch of threaded rod extension on the top of the drum, which equated to a slight nose-up trim setting. The electrically-driven flap actuator was found in the flaps 40° extended position. Examination of the engine revealed no evidence of preimpact failure or malfunction of the crankshaft, camshaft, valvetrain, air induction, exhaust, lubrication, turbocharger, or fuel metering systems. Following removal of the heat-damaged left magneto, which could not be operationally tested, the left gear retainer assembly (part number [P/N] LW19096) was observed to be fractured, and the drive cushions were damaged, sections of which were found in the oil sump along with ferrous parts. Additionally, the left crankshaft idler gear assembly (P/N 71668) and the fuel pump idler gear assembly (P/N 71664) exhibited damaged and missing teeth. The right magneto was heat damaged and the right gear retainer assembly (P/N LW19096) was in place and intact with one drive cushion intact and the other drive cushion fractured. The fractured left gear retainer assembly, gears with fractured teeth, ferrous components found in the oil sump, including fractured sections of a pawl retaining rivet, and the heat-damaged left magneto were retained for examination by the NTSB Materials Laboratory. Upon partial disassembly of the left magneto, both pawl retaining rivets were found to be fractured; remnants of each rivet remained loosely entrapped by the pawls. Both pawl retaining rivets exhibited indications of wear on the shafts, consistent with deformation on the respective holes of the impulse hub assembly. One of the rivet pieces found in the oil sump exhibited features consistent with fatigue cracking that had initiated at multiple locations along an area of wear. The other rivet fracture feature was consistent with torsional and shear overstress. Further examination of the left magneto revealed that the impulse shell was cracked and there was an outward tear in part of the skirt or side flange. Additionally, a wear mark with smearing and an impact mark consistent with contact by the magneto stop pin was noted, although there was no flattening of the stop pin. The fracture features of all fractured teeth and the left gear retainer assembly were consistent with overstress fracture with no indication of preimpact failure or malfunction. Examination of the propeller revealed all three blades remained secured inside the propeller hub and exhibited blade bending with no evidence of propeller preimpact failure or malfunction. ADDITIONAL INFORMATION14 CFR 91.3 (Responsibility and authority of the pilot in command) states, “in an in-flight emergency requiring immediate action, the pilot in command may deviate from any rule of [14 CFR 91] to the extent required to meet that emergency.” Section 3-3-2 (CLOSED/UNSAFE RUNWAY INFORMATION) of FAA Order JO 7110.65AA (Air Traffic Control) states: If an aircraft requests to takeoff, land, or touch-and-go on a closed or unsafe runway, inform the pilot the runway is closed or unsafe, and a. If the pilot persists in his/her request, quote him/her the appropriate parts of the NOTAM applying to the runway and inform him/her that a clearance cannot be issued. b. Then, if the pilot insists and in your opinion the intended operation would not adversely affect other traffic, inform him/her that the operation will be at his/her own risk.
PHRASEOLOGY
RUNWAY (runway number) CLOSED/UNSAFE. If appropriate, (quote NOTAM information), UNABLE TO ISSUE DEPARTURE/LANDING/TOUCH-AND-GO CLEARANCE. DEPARTURE/LANDING/TOUCH-AND-GO WILL BE AT YOUR OWN RISK. MEDICAL AND PATHOLOGICAL INFORMATIONAn autopsy of the pilot was performed by the Alabama Department of Forensic Sciences, Huntsville, Alabama. According to the autopsy report, the cause of death was probable blunt force injuries complicated by thermal injuries, and the manner of death was accident. Toxicology testing performed by the FAA Forensic Sciences Laboratory on the pilot’s specimens identified no evidence of impairing drugs. 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. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- — Aircraft-Aircraft power plant-Ignition system-Magneto/distributor-Fatigue/wear/corrosion
- — Aircraft-Aircraft power plant-Ignition system-Magneto/distributor-Failure
- — Aircraft-Aircraft power plant-Accessory gear-boxes-(general)-Damaged/degraded
- — Aircraft-Aircraft power plant-Power plant-(general)-Malfunction
- — Personnel issues-Action/decision-(general)-(general)-Pilot
- — Environmental issues-Operating environment-Airport facilities/design-Runway/landing area condition-Availability of related info
- — Environmental issues-Operating environment-Airport facilities/design-Runway lighting-Availability of related info
Verbatim from NTSB's published report. Source file
NTSB_2023_ERA24FA050.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (stall, maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2023 · Conference paper
The Value of Strong Partnerships to Build a Successful Aviation Maintenance Career Pathway Program for Transitioning Military Service Members
The aerospace industry is competing with other industries for a qualified workforce, and many of those competing industries are investing heavily in creating workforce development pipelines.
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- NASA NTRS 2026 · Conference Paper
Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
Browse the full corpus — academia portal ↗