Float and Climb — The Go-Around Trap
Excessive landing float, aborted landing, and a stall at low altitude in the SR22 — the energy state is deceptive
The scenario
Departing Sarasota Bradenton International Airport (KSRQ), Sarasota, FL — Runway 14, landing after a 1.5-hour local flight. Elevation 30 ft MSL. It is a warm, humid Florida afternoon in late spring: OAT 32°C, dew point 24°C, altimeter 29.88. Density altitude approximately 2,100 ft — well above field elevation, which means the airplane will perform as if it is 2,070 ft higher than it actually is. Winds are light and variable, 3–5 knots. Visibility 10 SM. KSRQ tower is active (0600–0000 local); you are in Class C airspace (ceiling 4,000 MSL).
You are on short final to Runway 14 (true heading 134°), 500 ft AGL, configured for landing: flaps 100% (full), landing gear fixed (always down on the SR22), airspeed 77 KIAS (Vref, short-field approach speed). The runway is 9,500 ft long — plenty of room. The approach is stable and on glide path.
At 50 ft AGL, you begin the landing flare. The airplane is floating — the nose is high, the main gear has not touched down, and you are drifting down the runway. You add a touch of power to arrest the descent, but the float continues. You are now at 30 ft AGL, 1,000 ft down the runway, still floating. The airplane is not settling.
Aircraft: Cirrus SR22, solo, full fuel, within limits. Continental IO-550-N, 310 hp, constant-speed prop, glass Perspective panel, fixed gear, fixed-pitch flaps (100% full). The airplane is airworthy; nothing was written up. Density altitude is high — the airplane is performing sluggishly in the warm, dense air.
Pilot: you — a Private pilot, current, roughly 250 hours total, with 60 hours in the SR22. You have landed the SR22 at KSRQ before, but not in high density altitude conditions. You are familiar with the airplane's tendency to float on landing, but today the float is more pronounced than usual. You are now faced with a decision: continue the float and land farther down the runway, or abort the landing and go around.
- {'label': 'Field', 'value': 'KSRQ · Sarasota Bradenton'}
- {'label': 'Runways', 'value': '4/22 · 14/32'}
- {'label': 'Elevation', 'value': '30 ft'}
- {'label': 'Aircraft', 'value': 'SR22'}
- {'label': 'Dominant phase', 'value': 'Takeoff / Landing'}
The decision
Before we get into the decision tree — what do you already know about landing float and go-around procedures in the SR22? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB WPR11LA169 (2011): A Cirrus SR-22 on return to Falcon Field (Phoenix, AZ) encountered excessive float during landing flare. The pilot aborted the landing and retracted flaps to climb out, but the aircraft stalled at low altitude and lost control. The airplane struck the runway, veered left, and collided with a parked Cessna 172. The probable cause was the pilot's attempt to correct a landing float by adding power, followed by his premature attempt to climb the airplane out of ground effect during a balked landing, which resulted in an aerodynamic stall. Contributing to the accident was the pilot's failure to properly configure the flaps for the balked landing attempt.
NTSB WPR20FA019 (2019, FATAL): A Cirrus SR22 stalled during landing approach while maneuvering in the traffic pattern at low airspeed and descended into a residential area. The probable cause was the pilot's exceedance of the airplane's critical angle of attack while maneuvering for landing, which resulted in an aerodynamic stall and loss of control. The pilot did not deploy CAPS.
NTSB CEN18FA204 (2018, FATAL): A Cirrus SR22 on a personal flight stalled during initial climb at 200 feet and entered an uncontrollable descent, impacting terrain. The probable cause was an inadvertent stall, with contributing factors including high density altitude and the student pilot's limited experience. The pilot did not deploy CAPS.
NTSB ATL06LA035 (2006): A Cirrus SR22 on a business flight encountered icing conditions while climbing to 9,000 feet in an area where the aircraft was not certified to operate. The accident resulted from inadequate preflight planning, failure to obtain current weather information, and continued flight into known icing conditions, leading to ice accumulation, airspeed decay, stall, and spin. The probable cause was the pilot's inadequate preflight planning, failure to obtain a current weather briefing, and his decision to operate the airplane into a known area of icing outside the airplanes certification standards.
The real accidents cited above occurred at other airports and in other aircraft types — NOT at Sarasota Bradenton International Airport (KSRQ). KSRQ's dominant accident pattern includes LOSS_OF_CONTROL_GROUND (19.2%), FORCED_LANDING (15.4%), and RUNWAY_EXCURSION (11.5%), but the specific stall/spin accidents referenced here happened elsewhere. The scenario is localized to KSRQ to make the landing environment and density altitude real and consequential for you as a student here.
The consistent thread across all these events: the SR22's high-performance engine and constant-speed prop create a fast, energy-rich airplane that floats on landing in high density altitude. A go-around after a float requires precise flap management and airspeed control — retract flaps too quickly or too much at low altitude and low airspeed, and the airplane will stall. The SR22's CAPS parachute is the designed recovery for an unrecoverable stall at low altitude; it is not a substitute for proper technique, but it is the last line of defense when control inputs alone cannot prevent impact.
Key lesson — In high density altitude conditions at KSRQ, the SR22 will float on landing — the airplane performs as if it is 2,000+ feet higher than it actually is. Accept the float and land farther down the runway, or abort the landing and go around with precise flap management. If you abort, retract flaps gradually (50% first, then 0%) while maintaining airspeed above stall (70 KIAS clean, 59 KIAS landing). A go-around with full flap retraction at low altitude and low airspeed is a stall trap. If a stall occurs at low altitude, deploy CAPS — it is the designed recovery.
Debrief — teaching points
High density altitude makes the SR22 float on landing.
Density altitude at KSRQ on a warm, humid Florida afternoon can exceed 2,000 ft. The airplane performs as if it is 2,000+ feet higher than it actually is. Expect a longer landing distance, a shallower descent rate, and a pronounced float in the landing flare. The SR22's high power and constant-speed prop make it particularly prone to floating. Plan for a landing distance of 3,000+ ft in high density altitude, not the 2,500 ft you might expect in standard conditions. If you are floating and have plenty of runway, accept the float and land farther down. Do not try to force the airplane down with forward pressure on the yoke — that is a stall trap.
A go-around after a float requires precise flap management.
If you abort a landing and go around, you must retract flaps gradually. Retract to 50% first, establish a positive climb rate, then retract to 0%. Full flap retraction at low altitude and low airspeed (77 KIAS) causes a sudden loss of lift and a pitch-down that can lead to a stall if you pitch up to recover. The SR22's stall speed in landing configuration (full flaps) is 59 KIAS; in clean configuration it is 70 KIAS. The margin between 77 KIAS and 70 KIAS is only 7 knots — very small at 50 ft AGL. Retract flaps gradually to avoid this trap.
Airspeed is your margin in a go-around.
During a go-around, maintain airspeed above stall. In the SR22, that means at least 70 KIAS in clean configuration, 59 KIAS in landing configuration. At 50 ft AGL with full flaps, you are at 77 KIAS — only 18 knots above stall. A turn, a gust, or a pitch input can trigger a stall. Establish a positive climb rate and accelerate to 88 KIAS (best glide) before retracting flaps to 0%. The extra airspeed is your margin for error.
CAPS is the designed recovery for an unrecoverable stall at low altitude.
The SR22's whole-airframe parachute (CAPS) is not a substitute for proper technique, but it is the last line of defense when control inputs alone cannot prevent impact. If you stall at 50 ft AGL and cannot recover by lowering the nose and increasing airspeed, deploy CAPS. The parachute will arrest the descent and allow the airplane to impact at a survivable vertical speed. NTSB WPR20FA019 and CEN18FA204 were both fatal because the pilots did not deploy CAPS. Know the CAPS handle location and be prepared to use it if a stall occurs at low altitude.
Runway 14 at KSRQ is 9,500 ft long — use it.
Runway 14 at KSRQ is 9,500 ft long. A landing at 2,500–3,000 ft down the runway leaves you with 6,500–7,000 ft to stop. That is plenty of room. Do not try to force the airplane down in the first 1,500 ft if it is floating. Accept the float, land farther down, and use the available runway. A go-around in high density altitude is riskier than a float landing on a 9,500 ft runway.
Built from the real accident record
Scenario built from NTSB WPR11LA169 (2011 SR22 stall during go-around after landing float, collision with parked aircraft), WPR20FA019 (2019 SR22 stall during landing approach, loss of control), CEN18FA204 (2018 SR22 stall during initial climb at 200 ft, high density altitude), and ATL06LA035 (2006 SR22 icing/stall/spin). Anonymized and localized to KSRQ.
NTSB reports: WPR11LA169 · WPR20FA019 · CEN18FA204 · ATL06LA035
ACS tasks: PA.II.F — Approach and Landing · PA.II.E — Go-Around / Rejected Landing · PA.II.C — Slow Flight · PA.I.H — Human Factors · PA.IX.C — Emergency Approach and Landing
Relevant FARs: §91.3 · §91.13 · §91.9
Step through the full decision tree, make the calls, and see where each choice leads — then debrief it with your CFI.
Open the interactive scenario →All sample scenarios · More Cirrus SR22 scenarios · More scenarios at KSRQ