CEN24LA207

NTSB accident investigation · Cirrus SR20 · Aitkin, MN · June 1, 2024

Accident · Minor injuriesClass 3 · LimitedFinal report
Date
June 1, 2024, 12:18 local (17:18 UTC)
Place
Aitkin, MN
Injuries
1 minor, 2 uninjured
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N275RSCirrus SR20
Defining event
Approach-VFR go-around: Loss of control in flight
Weather
Visual (VMC) · Day
Status
Completed
Report
Approved by Office Director
Investigation class
Class 3
NTSB office
Central Region
Parties
FAA, Cirrus, Continental
FAA report
20240601008659A
Case key
194368

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

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.

Findings · 6

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Performance/control parameters: airspeedAircraft › Aircraft oper/perf/capability · Not attained/maintainedCirrus Design SR20: 13 casesAll aircraft: 1,681 casesProbable cause
Use of equip/info: aircraft controlPersonnel issues › Task performance · PilotCirrus Design SR20: 47 casesAll aircraft: 9,295 casesProbable cause
Performance/control parameters: angle of attackAircraft › Aircraft oper/perf/capability · Not attained/maintainedCirrus Design SR20: 8 casesAll aircraft: 990 casesProbable cause
Use of equip/info: use of equip/systemPersonnel issues › Task performance · PilotCirrus Design SR20: 4 casesAll aircraft: 1,391 casesProbable cause
Action: lack of actionPersonnel issues › Action/decision · PilotCirrus Design SR20: 2 casesAll aircraft: 792 casesProbable cause
Flight control systemAircraft › Aircraft systems · Not used/operatedCirrus Design SR20: 1 caseAll aircraft: 65 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

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.

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 engineperformance (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.

Aircraft

Registration
N275RS
Reported as
Cirrus SR20
Category
Airplane
Serial number
1280
Built
2003
Airframe hours
2,690
Engine
Teledyne Continental Motors IO-360-ES, 200 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Registered owner
Monaco Aviation LLC
Airworthiness certificate
Standard, Normal
Last inspection
100 hour · April 19, 2024
Destination
Same as departure
Airport
AIT · Aitkin Muni/Steve Kurtz Fld, runway 16/34, 4,000 × 75 ft, asphalt
Equipment
Auto-pilot, Airframe parachute, ADS-B, Stall warning system, Electronic multifunction display, Electronic flight bag or handheld device, Data recorder

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
29
Injuries
None
Certificate
Commercial
Airplane ratings
Single-engine land, Multi-engine land
Instrument ratings
Airplane
Medical
Class 2, With waivers/limitations
Last flight review
June 18, 2022
Seat
Left
Restraint
4-point
Flight hours
344 total · 198 in this make and model · 167 as pilot in command · 7 in the last 90 days · 5 in the last 30 days

Weather

Conditions
Visual (VMC) · Day
Wind
240° at 8 knots, gusting 16
Visibility
10 statute miles
Lowest ceiling
None
Temperature
72 °F, dew point 45 °F
Altimeter
29.92 inHg
Observed at
KAIT
METAR
KAIT 011715Z AUTO 24008G16KT 210V280 10SM CLR 22/07 A2992 RMK AO2

Docket · 13

The files NTSB released with the investigation on November 14, 2024, on NTSB’s docket system: statements, records, photos and specialists’ reports. 14.8 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.