NTSB CAROL · Event
Event CEN24FA340
Aircraft involved
Factual narrative
On September 6, 2024, about 0948 eastern daylight time, a Piper PA-46-350P airplane, N629AG, was destroyed when it was involved in an accident near Anderson, Indiana. The pilot, two pilot-rated passengers, and one passenger were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. Automatic Dependent Surveillance – Broadcast data revealed that the flight departed Fort Dodge Regional Airport (FOD), Fort Dodge, Iowa, at 0647 central daylight time. The airplane proceeded on an east-southeast course toward Anderson Municipal Airport-Darlington Field (AID), Anderson, Indiana, and climbed to flight level (FL) 210, which corresponded to a pressure altitude of 21,000 ft. About 0921, the pilot initiated a descent from FL210. About 0943, the Indianapolis approach controller instructed the pilot to descend to 3,000 ft msl and advised him to expect a visual approach to runway 12. The flight was about 13 miles west-northwest of AID at 7,000 ft msl at that time. About 3 minutes later, the pilot informed the controller that the airport was in sight, and the controller cleared the pilot for a visual approach. At that time, the flight was about 4 miles west-northwest of AID about 3,600 ft msl. About 0947:16, when the flight was 0.9 miles west of the runway and about 1,985 ft msl, the pilot informed the controller he needed to go around. The controller subsequently cancelled the approach clearance and instructed the pilot to turn right to a heading of 180° and climb to 3,000 ft msl. The airplane continued toward the airport, and at 0947:38, crossed the runway 12 threshold about 1,610 ft msl [730 ft above ground level (agl)]. The airplane flight track drifted slightly north-northeast of the runway centerline. About 0948:30, the airplane appeared to start a gradual right turn. At that time, the airplane was about 0.60 miles southeast of the departure end of runway 12 at an altitude of about 2,060 ft msl. The final ADS-B data point was recorded at 0948:55 with an associated altitude of 2,185 ft msl (1,349 feet agl). A witness, located about one-quarter mile from the accident site, observed the airplane come up above a tree line in a climb. Shortly afterward, the airplane stopped climbing “all of a sudden”, rolled to the right, and entered a descent. The engine was loud and sounded like it was “really revving;” adding that it seemed to be wide open. A second witness, located about one-eight mile from the accident site, reported hearing the airplane engine “revved up”, decreased, and then “revved up” again, before it cutout. He did not hear the sound of the impact with the ground. Figure 1 – Final Segment of Airplane Flight Path The accident site was located in a corn field about 1 mile southeast of the departure end of runway 12 at an elevation of 923 ft. This was about 547 ft southwest from the final ADS-B data point. The airplane came to rest upright on a northeast heading. The debris area extended about 50 ft southwest from the initial impact. The airframe was fragmented, and portions were consumed by a postimpact fire. The engine and forward fuselage were located adjacent to a 4 -foot diameter impact crater. All three propeller blades were separated at the blade roots and positioned near the crater. The cockpit area was located about 12 feet from the forward fuselage. The wings and center fuselage were positioned about 15 feet from the cockpit debris. The aft fuselage and empennage were located in position adjacent to the wings. Both main landing gear struts were in the extended position; the nose landing gear was separated. Figure 2 – Airplane Wreckage at Accident Site Major airframe structural components were located at the accident site. Portions of the airframe were consumed by the postimpact fire. Each flight control surface, including both wing flaps, either remained attached to the airframe or was separated and located within the debris path. The wing flap actuator was not observed and the flap position at the time of the accident could not be determined. However, based on the examination of the available wreckage, no evidence of an inflight structural failure was observed. The airplane was retained by the NTSB for further examination. The airplane was equipped with a Garmin G1000 system. However, a flight data card was not located at the accident site, nor is it known if a data card was installed. Additionally, a damaged Appareo Stratus 2S unit was recovered and sent to the NTSB recorder lab for evaluation. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2024_CEN24FA340.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). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- 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 …
- arXiv 2023 · arXiv preprint
Automating Bird Diverter Installation through Multi-Aerial Robots and Signal Temporal Logic Specifications
This paper tackles the task assignment and trajectory generation problem for bird diverter installation using a fleet of multi-rotors.
- arXiv 2023 · arXiv preprint
Variation of Critical Crystallization Pressure for the Formation of Square Ice in Graphene Nanocapillaries
Two-dimensional square ice in graphene nanocapillaries at room temperature is a fascinating phenomenon and has been confirmed experimentally.
- arXiv 2023 · arXiv preprint
Polycrystallinity enhances stress build-up around ice
Damage caused by freezing wet, porous materials is a widespread problem, but is hard to predict or control. Here, we show that polycrystallinity makes a great difference to the stress build-up process…
- arXiv 2022 · arXiv preprint
Enhanced Prediction of Three-dimensional Finite Iced Wing Separated Flow Near Stall
Icing on three-dimensional wings causes severe flow separation near stall. Standard improved delayed detached eddy simulation (IDDES) is unable to correctly predict the separating reattaching flow due…
- Embry-Riddle Scholarly Commons 2021 · Journal article (JAAER)
Analysis on the Negative Emotional, Physiological, and Cognitive Responses Elicited from of the Activation of a Stall Alarm
Failing to identify an aerodynamic stall can lead to the inability of an aircraft to sustain flight. To warn pilots of an impending or fully-developed stall, many aircraft have safety devices installe…
Browse the full corpus — academia portal ↗