The Turn to Final
A base-to-final stall in a Cirrus SR20 — energy management, crosswind, and the parachute decision at 400 feet
The scenario
Departing Tampa Executive Airport (KVDF), Tampa, FL — Runway 23, a 5,000-foot asphalt runway. Elevation 22 ft MSL. You are on a VFR training flight in a Cirrus SR20, solo, within weight and balance. The field is non-towered (CTAF); you self-announce on 122.775 MHz.
It is a warm Florida afternoon: OAT 29°C, winds from 210° at 12 knots gusting to 18 knots. Runway 23 is aligned 222° magnetic; the wind is a 12-knot crosswind with gusts. Visibility 10 SM, scattered clouds at 3,500 ft, light turbulence in the pattern. You have completed three full-stop landings and are on your fourth approach of the afternoon.
You are on base leg, 600 feet AGL, heading roughly 130° (left base for Runway 23). Airspeed is 90 KIAS, flaps are 50% (Vfe 120 KIAS is the limit for 50% flaps). The wind is gusty; you have been hand-flying the approach and managing crosswind drift. The runway is in sight, 1.2 nm ahead. You are about to turn final.
Aircraft: Cirrus SR20, fuel-injected Continental IO-360, constant-speed prop, glass panel (Avidyne Perspective), fixed gear. The defining feature of the SR20 is the whole-airframe parachute (CAPS) — it is the primary response to loss of control or an unrecoverable spin at adequate altitude. The wing is slippery; energy management is unforgiving. Best glide is 96 KIAS; approach speed (Vref, full flaps) is 80 KIAS. Stall speed clean is 65 KIAS; stall speed landing (Vs0, full flaps) is 56 KIAS.
Pilot: you — a Private or Commercial pilot, current, roughly 250–400 hours total. You are familiar with the SR20, but crosswind landings and energy management in the pattern are still areas where you concentrate. You have not flown crosswind approaches in gusting conditions recently. The pattern is busy; there is another SR20 on downwind 2 miles out, and a Piper Cherokee on base 1 mile out. You are feeling a bit rushed.
- {'label': 'Field', 'value': 'KVDF · Tampa Executive'}
- {'label': 'Runways', 'value': '5/23 · 18/36'}
- {'label': 'Elevation', 'value': '22 ft'}
- {'label': 'Aircraft', 'value': 'SR20'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before we get into the decision tree — what do you already know about stall risk in the SR20 on approach? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB WPR20LA152 (2020, FATAL): A Cirrus SR20 flown by a student pilot on a solo cross-country flight stalled during a steep descending turn to final approach at low altitude. The accident resulted from the pilot's exceedance of the airplane's critical angle of attack during the steep and descending turn. The parachute was deployed, but at 150 feet AGL — too late for the parachute to inflate and slow the descent before impact. The probable cause was the pilot's failure to maintain adequate airspeed during the approach maneuver.
NTSB ERA23FA358 (2023, FATAL): A Cirrus SR20 student pilot on a solo night flight impacted trees during initial climb after the fourth takeoff of the evening. The accident was attributed to the pilot's failure to maintain a positive climb rate after takeoff due to spatial disorientation (somatogravic illusion). While this accident occurred during climb-out, not approach, the underlying cause — loss of control due to inadequate airspeed management and spatial disorientation — is the same trap that kills pilots on approach in gusty conditions.
NTSB GAA19CA099 (2018): A Cirrus SR20 on a training flight stalled during a go-around when the student pilot aggressively pitched up after being instructed to abort the landing. The accident resulted from the student pilot's exceedance of the critical angle of attack during the go-around, and the flight instructor's delayed remedial action. The lesson: aggressive pitch-up maneuvers at low altitude in the SR20 are stall traps.
Local precedent NTSB LAX89LA222 (1989, FATAL): A Grumman AA-1C aborted an approach to Runway 23 and entered a low unstable pattern for Runway 5 in gusting crosswind conditions, stalled on final approach, and impacted the ocean short of the runway. The accident resulted from the pilot's failure to maintain sufficient airspeed to prevent a stall at an altitude too low for recovery. The setting — Runway 23 at a coastal Florida airport in crosswind conditions — is identical to this scenario.
Local precedent NTSB ERA10CA300 (2010): A Piper PA-18-135 stalled and entered a spin during a climbing right turn on final approach when the pilot attempted to perform a 360-degree turn per ATC spacing request. The accident was attributed to the pilot's failure to maintain adequate airspeed during the climbing turn. The lesson: do not attempt maneuvers (climbing turns, steep descents) that exceed the airplane's capability at low altitude.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Tampa Executive Airport (KVDF). KVDF has its own accident history (see field dominant patterns: LOSS_OF_CONTROL_GROUND 18.4%, HARD_LANDING 18.4%, FORCED_LANDING 15.8%, LOSS_OF_CONTROL_INFLIGHT 13.2%). The scenario is localized to KVDF to make the crosswind environment and the off-field reality (open water off Runway 36, wooded wetland and development off other ends) consequential for you as a student here.
The consistent thread across all these events: stall/spin on approach happens in seconds. The warning signs are subtle — a steep turn, a marginal airspeed, a high angle of attack, a gust-induced airspeed loss. By the time the stall warning activates, it is often too late for control-input recovery at low altitude. The SR20's CAPS parachute is designed for exactly this scenario — but it requires altitude to work. The correct response is to recognize the unstable approach early and go around, or to maintain adequate airspeed and a stable descent throughout the approach.
Key lesson — In the SR20 on approach in crosswind and gusty conditions, maintain a stable descent rate (200–300 fpm), adequate airspeed margin above stall speed (at least 85 KIAS on final, 90 KIAS on base), and a shallow bank angle (15° or less). Recognize the signs of an unstable approach — a steep turn, a high angle of attack, a marginal airspeed, or a descent rate above 400 fpm — and go around rather than continue. If you do stall at low altitude, CAPS is your primary recovery tool, but it requires altitude to work. A go-around at 400 ft is always better than a stall at 200 ft.
Debrief — teaching points
A descending turn at low altitude is a stall trap — especially in crosswind conditions.
The base-to-final turn combines three risk factors: reduced power (descent), a bank angle (turn), and low altitude (no recovery margin). In crosswind and gusty conditions, the wind shear can drop airspeed suddenly. A gust followed by a wind shear can drop airspeed from 90 KIAS to 75 KIAS in seconds. In the SR20, stall speed landing is 56 KIAS; a margin of 20 KIAS is thin. The descending turn is where most stall/spin accidents happen. Recognize the risk and fly a shallow, stable turn with adequate airspeed margin.
Airspeed alone is not enough — use the angle-of-attack indicator.
The SR20's glass panel includes an angle-of-attack (AOA) indicator. It is the primary tool for recognizing stall risk during approach. Airspeed can be misleading in a turn — the airplane can be flying at 90 KIAS but at a very high angle of attack due to the bank angle and the descent. The AOA indicator shows the true stall risk. If the AOA is in the yellow or red zone, you are close to stall, regardless of what the airspeed indicator shows. Monitor the AOA continuously during the approach, especially in turbulence and crosswind.
Crosswind and gusts increase stall risk — maintain extra airspeed margin.
In calm conditions, 80 KIAS on final (Vref) is adequate. In crosswind and gusty conditions, maintain 85–90 KIAS on final and 90–95 KIAS on base. The extra airspeed gives you a buffer against wind shear and gusts. A 12-knot crosswind with gusts to 18 knots is not extreme, but it is enough to drop airspeed suddenly if you are not vigilant. The SR20's slippery wing makes energy management unforgiving — maintain extra margin.
Recognize the signs of an unstable approach and go around early.
An unstable approach is one where the descent rate is above 400 fpm, the airspeed is below 85 KIAS on final or 90 KIAS on base, the bank angle is above 20°, the angle of attack is in the yellow or red zone, or you feel rushed or uncomfortable. If any of these conditions exist, go around. A go-around at 400 ft is always better than a stall at 200 ft. The pattern will be there for another approach. Do not continue a marginal approach to the landing.
CAPS is the primary recovery tool for loss of control in the SR20 — but it requires altitude.
The SR20 is not certified for intentional spin recovery by control inputs. If you stall and enter a spin at low altitude, CAPS is your primary recovery tool. The parachute will slow your descent from 3,000+ fpm (uncontrolled spin) to 1,500 fpm (under parachute). At 300 ft AGL, that gives you 12 seconds to impact — survivable. At 150 ft AGL, you have 6 seconds — marginal. At 100 ft AGL, you have 4 seconds — likely fatal. CAPS works, but only if you have altitude. Do not rely on CAPS to save you from a low-altitude stall — prevent the stall in the first place.
Flap management is critical — add flaps gradually, not all at once.
In the SR20, adding full flaps (100%) at once can drop the airspeed by 10–15 KIAS in seconds. On base leg, use 50% flaps and maintain 90 KIAS. On final, add full flaps at 300 ft AGL when the runway is made and the descent is stable. Do not add full flaps during the turn or in turbulence — the sudden airspeed loss can trigger a stall. Flap management is energy management. Respect the flap speeds and add flaps gradually.
Off Runway 36 at KVDF, the off-field environment is open water — a ditching, not a field landing.
The off-field environment off Runway 36's departure end (heading 360°) is mostly medium development, wooded wetland, and open water. An engine failure or loss of control on the Runway 36 departure at low altitude is a ditching. Off Runway 23's departure end (heading 222°), the environment is pasture/hay, open water, and medium development — better options, but still water and development. Off Runway 05 (heading 42°) and Runway 18 (heading 180°), the environment is wooded wetland, development, and parks — marginal to good forced-landing options. Know the off-field environment before you depart. It affects your go-around and emergency-landing decisions.
Built from the real accident record
Scenario built from NTSB WPR20LA152 (2020 SR20 stall on base-to-final in steep descending turn), ERA23FA358 (2023 SR20 spatial disorientation / loss of control), GAA19CA099 (2018 SR20 stall during go-around), and local precedents LAX89LA222 (1989 AA-1C stall on final in crosswind), ERA10CA300 (2010 PA-18 stall in climbing turn), and ATL83LA356 (1983 C172 stall on short final). Anonymized and localized to KVDF.
NTSB reports: ERA23FA358 · WPR20LA152 · WPR12FA235 · GAA19CA099 · LAX89LA222 · ERA10CA300 · ATL83LA356 · FTW99LA205
ACS tasks: PA.VIII.C — Approach and Landing · PA.VIII.D — Go-Around / Rejected Landing · PA.I.H — Human Factors · PA.V.A — Stall Recognition and Recovery · PA.V.B — Spin Entry, Spins, and Recovery
Relevant FARs: §91.3 · §91.13 · §91.119
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 SR20 scenarios · More scenarios at KVDF