NTSB CAROL · Event
Event CEN24LA207
Registry · N275RS
FAA Aircraft Registry record.
Make / Model
CIRRUS DESIGN SR20
Year of manufacture
2003 · 21 years old at event
Engine
CONT MOTOR IO-360 SER (300 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
20030206
ADS-B equipped
Yes — Mode-S A2BA97
Registrant of record
MONACO AVIATION LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot’s failure to maintain adequate airspeed, which resulted in a loss of airplane control during the go-around. Contributing to the accident was the pilot’s failure to properly configure the airplane’s flaps during the go-around.
Factual narrative
On June 1, 2024, about 1218 central daylight time, a Cirrus SR20 airplane, N275RS, sustained substantial damage when it was involved in an accident near Aitkin, Minnesota. The pilot and one passenger were not injured, and a second passenger sustained minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. According to the pilot, he departed the Aitkin Municipal Airport (AIT), Aitkin, Minnesota, about 1130, for a short flight, and he noted no anomalies during the flight. During the landing at AIT on runway 16 with mild wind gusts, the airplane touched down, bounced, and the pilot elected to perform a go-around. The pilot reported that he “followed all procedures to execute the maneuver [and] upon applying full power, the engine didn’t respond resulting in very little power.” The pilot determined the airplane would not properly climb and he initiated an emergency landing, including a low-altitude activation of the Cirrus Airframe Parachute System (CAPS). The airplane came to rest upright in the swamp vegetation adjacent to the runway. The airplane’s right wing and fuselage sustained substantial damage. Recovery personnel reported they drained about 30 gallons of fuel from the airplane during recovery from the swamp. One of the passengers stated to local law enforcement that the approach and landing were bumpy, and the pilot conducted a go-around after touchdown. During the go-around, the pilot had the engine at full throttle. Above the end of the runway, the airplane encountered a wind gust, and it did not seem like the airplane had enough power. The passenger felt that the airplane was going to go inverted, and the pilot pulled the airplane parachute. Postaccident examination of the airplane revealed the flaps were at the 100% extended position. The three propeller blades were bent aft about 25-40°. The engine crankshaft was manually rotated with no anomalies. The engine oil filter was punctured and replaced with a new replacement filter to accommodate an engine functional test. A remote fuel source was connected to the airframe fuel boost pump inlet. The airframe was secured to a cart assembly, and a functional engine test was performed. The engine immediately started, and only 1,400 rpm were achieved due to bent propeller blades and excessive vibration. The damaged propeller was removed and replaced with a minimally damaged (slight aft bend in all three blades), larger diameter propeller (typically installed on an IO-520 series engine). Another engine functional test was performed. The engine immediately started and was test run through a wide range of rpms. The engine went to 2,400 rpm with no hesitation during a simulated quick power increase. The Avidyne multi-function display (MFD) was removed and sent to the National Transportation Safety Board Vehicle Recorders Laboratory for data extraction. The logged engine data during the accident flight go-around revealed no anomalies with engine performance (see Figure 1). A review of the engine performance data during the go-around was consistent with the engine performance data of the earlier takeoff from AIT. Figure 1. Avidyne MFD data plotted on Google Earth. According to the Cirrus Pilot’s Operating Handbook, during a go-around, the flap setting should be reduced to the 50% position. The pilot’s calculated weight and balance, using 18 gallons of fuel, was near the forward center of gravity limit, and he reported the airplane was about 142 pounds under the gross weight at the time of the accident. An examination of the CAPS revealed the rocket and D-bag were located near the end of runway 16. The rear harness remained snubbed, with break stitches in place, and the reefing line cutters were not activated. The forward section of the right and left CAPS straps remained stowed in the CAPS channel. The remaining CAPS straps, risers, suspension lines, and parachute were found lying across the swamp terrain. Indications of parachute inflation or aerodynamic load were not present. The pilot departed for a local flight and noted no anomalies during the flight. During the landing with mild wind gusts, the airplane touched down, bounced, and the pilot elected to perform a go-around. The pilot reported that he “followed all procedures to execute the maneuver [and] upon applying full power, the engine didn’t respond resulting in very little power.” The pilot determined the airplane could not properly climb and he initiated an emergency landing by activating the airplane’s parachute system at a low altitude. The airplane came rest upright in swamp vegetation adjacent to the runway and sustained substantial damage to the right wing and fuselage. During the attempted go-around, the pilot did not retract the flaps from the 100% extended position to the 50% position as directed in the pilot’s operating handbook. In addition, the airplane’s calculated weight and balance was near the forward center of gravity limit. Postaccident examination of the airframe and engine, engine performance data, and a functional engine test revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation. Based on available evidence, it is likely the airplane’s climb performance was degraded due to inadequate airspeed and failure to retract the wing flaps from the full extended position, which resulted in a loss of airplane control during the go-around. 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 oper/perf/capability-Performance/control parameters-Airspeed-Not attained/maintained
- — Personnel issues-Task performance-Use of equip/info-Aircraft control-Pilot
- — Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Angle of attack-Not attained/maintained
- — Personnel issues-Task performance-Use of equip/info-Use of equip/system-Pilot
- — Personnel issues-Action/decision-Action-Lack of action-Pilot
- — Aircraft-Aircraft systems-Flight control system-(general)-Not used/operated
Verbatim from NTSB's published report. Source file
NTSB_2024_CEN24LA207.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, go-around). 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 …
- NASA NTRS 2025 · Conference Paper
A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World
Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- 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…
Browse the full corpus — academia portal ↗