FlightEdge
Sample scenario-based training
SAMPLE SBTLanding / Go-Around

Float and Climb — The Stall Trap

A balked landing in the SR22, improper flap configuration, and a low-altitude stall in the traffic pattern — the margin is measured in feet

Cirrus SR22 · Venice Municipal Airport (KVNC) · Private · Landing / Go-Around

The scenario

Departing Venice Municipal Airport (KVNC), Venice, FL — Runway 22, a local VFR flight. Elevation 18 ft MSL. The day is clear, winds light and variable, visibility unlimited. You are returning to your home base after a short cross-country to a nearby field.

You are on final approach to Runway 22 (heading 225° true). The runway is 5,000 ft long, plenty of room. You are configured for landing: flaps 50%, airspeed 77 KIAS (Vref, short-field approach speed), descent rate steady at 300 ft/min. The runway is made; you are committed to the landing.

At 200 ft AGL, you begin the flare. The SR22 floats — the nose is high, the airplane is not sinking as expected. You are still 50 ft above the runway, burning runway, and the airspeed is decaying. You have a choice: land long on the remaining runway, or abort the landing and go around.

Aircraft: Cirrus SR22, solo, 3,200 lb (within limits). Continental IO-550-N, 310 hp, constant-speed prop, glass Perspective panel, CAPS system armed. Nothing was written up; the airplane is airworthy. You are a Private pilot with 250 hours total, 80 hours in type.

Pilot: You. You have landed the SR22 many times at KVNC. Today, you are slightly distracted — you are thinking about the approach briefing you just gave yourself, and you are not fully focused on the flare. The float caught you off-guard.

The decision

Before the decision tree — what do you know about the SR22's stall characteristics and the go-around procedure? (Pick all that apply.)

What the record shows

What the NTSB files show

NTSB WPR11LA169 (2011): A Cirrus SR22 on return to its home base at Falcon Field (Arizona) encountered excessive float during landing flare. The pilot aborted the landing, applied full power, and retracted flaps to climb out. The airplane stalled at low altitude (200 ft AGL) and lost control. The pilot's failure to properly configure the flaps for the balked landing (he retracted them fully and too quickly) and his attempt to climb out of ground effect at insufficient airspeed resulted in an aerodynamic stall. The aircraft struck the runway, veered left, and collided with a parked Cessna 172. The probable cause was the pilot's improper flap configuration during the go-around and his attempt to climb at insufficient airspeed.

NTSB WPR20FA019 (2019, FATAL): A Cirrus SR22 stalled during landing approach while maneuvering in the traffic pattern at low airspeed. The pilot exceeded the critical angle of attack while maneuvering for landing. The airplane 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, resulting in an aerodynamic stall and loss of control.

NTSB CEN18FA204 (2018, FATAL): A Cirrus SR22 on a personal flight stalled during initial climb at 200 ft AGL 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 pilot's inadequate preflight planning, failure to obtain a current weather briefing, and decision to operate into known icing resulted in ice accumulation, airspeed decay, stall, and spin. The airplane impacted trees.

The real accidents cited above occurred at other airports and in other aircraft — NOT at Venice Municipal Airport (KVNC). KVNC has its own accident history (see field dominant patterns: LOSS_OF_CONTROL_INFLIGHT 24.4%, FORCED_LANDING 12.2%, SPATIAL_DISORIENTATION 12.2%, HARD_LANDING 12.2%, LOSS_OF_CONTROL_GROUND 12.2%), but these specific NTSB events happened elsewhere. The scenario is localized to KVNC to make the traffic pattern and runway environment real and consequential for you as a student here.

The consistent thread across all these events: the SR22's stall characteristics are unforgiving at low altitude. The airplane has significant energy and floats in the flare. A go-around requires deliberate, coordinated flap management — gradual retraction, airspeed established above Vx (78 KIAS) before climbing aggressively. A stall at low altitude is unrecoverable by control inputs alone. The SR22's POH and training emphasize: CAPS is the primary recovery tool for unrecoverable stalls and loss of control at low altitude. Pushing the nose down to break a stall is the correct control input, but at 150 ft AGL, there is no altitude to recover. CAPS is the answer.

Off Runway 22 at KVNC, the off-field environment is open terrain and sparse development — a forced landing or stall impact would be survivable if the airplane is under control. But a stall at 150 ft AGL in a steep descent is not survivable without CAPS. Know the stall characteristics of the SR22. Know the go-around procedure. Know when to deploy CAPS.

Key lesson — The SR22 floats in the flare due to its high energy and performance. A go-around requires gradual flap retraction and airspeed established above Vx (78 KIAS) before climbing. A stall at low altitude is unrecoverable by control inputs — CAPS is the primary recovery tool. In an unrecoverable stall at low altitude, deploy CAPS immediately. Do not pull back on the yoke; push the nose down or deploy CAPS.

Debrief — teaching points

The SR22 floats in the flare — accept it and land long.

The SR22 is a high-performance airplane with significant energy. In the landing flare, it floats — the nose is high, the descent rate is shallow, and the airplane does not sink as expected. This is normal. The correct response is to accept the float, relax the back pressure, and land long on the runway. A 5,000 ft runway at KVNC provides plenty of room. Landing long is always safer than attempting a go-around at low altitude with marginal airspeed.

A go-around requires gradual flap retraction and airspeed management.

If you decide to go around, apply full power and full prop RPM (the constant-speed prop cycles automatically). Retract flaps gradually — to 25%, then 0° — while monitoring airspeed. Do not retract flaps fully in one motion; the sudden loss of lift and increase in drag will pitch the nose down and create a stall trap. Establish airspeed above Vx (78 KIAS) before climbing aggressively. The SR22 POH is explicit: improper flap configuration during a go-around is a primary cause of stalls.

Stall speed in the landing configuration is 59 KIAS — your margin is thin.

Approach speed (Vref) is 77 KIAS. Stall speed (landing) is 59 KIAS. Your margin is 18 knots. In a go-around with flaps still extended, stall speed is higher (59–70 KIAS depending on flap setting). Airspeed decay is rapid at low altitude. Monitor the angle-of-attack indicator on the glass panel — it is the primary reference for stall avoidance. The airspeed indicator is secondary.

An uncoordinated turn at low altitude raises the stall speed.

In the traffic pattern, maintain coordinated flight — aileron and rudder in balance. An uncoordinated turn (aileron without rudder) causes the airplane to slip, which raises the angle of attack and the stall speed. At 300 ft AGL with airspeed near 72 KIAS, an uncoordinated turn can trigger a stall. Coordinate the turn, reduce the angle of attack, and maintain airspeed above Vx (78 KIAS).

A stall at low altitude is unrecoverable by control inputs — CAPS is the primary recovery tool.

The SR22 POH is clear: in an unrecoverable stall or loss of control at low altitude, deploy CAPS. The whole-airframe parachute descends at 17 ft/sec and is designed to save your life when recovery by control inputs is not possible. A stall at 150 ft AGL requires 1,000+ ft to recover by pushing the nose down — you do not have that altitude. Deploy CAPS. CAPS is not a failure; it is the SR22's primary recovery system for loss of control.

If you do recover from a stall by pushing the nose down, you will be at very low altitude.

If a stall occurs at 200 ft AGL and you push the nose down to break it, you will descend to 80–100 ft AGL. You will have no altitude to climb. Your only option is to land straight ahead on the runway or deploy CAPS. Know this before you are in the situation. A stall at low altitude is a CAPS event, not a control-input event.

Built from the real accident record

Scenario built from NTSB WPR11LA169 (2011 SR22 balked landing stall), WPR20FA019 (2019 SR22 stall during landing approach), CEN18FA204 (2018 SR22 stall on initial climb), and ATL06LA035 (2006 SR22 icing/stall). Anonymized and localized to KVNC.

NTSB reports: WPR11LA169 · WPR20FA019 · CEN18FA204 · ATL06LA035

ACS tasks: PA.VIII.A — Preflight Inspection · PA.VIII.C — Engine Starting · PA.VIII.D — Taxiing · PA.VIII.E — Takeoff and Climb · PA.VIII.F — Cruise · PA.VIII.G — Descent · PA.VIII.H — Landing · PA.VIII.I — Go-Around / Balked Landing · PA.IX.C — Emergency Approach and Landing · PA.I.H — Human Factors

Relevant FARs: §91.3 · §91.13 · §91.185

Run this scenario yourself

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 KVNC