FlightEdge
Sample scenario-based training
SAMPLE SBTLanding / Takeoff

Gusts and Directional Control

A crosswind landing at KSPG in gusty conditions — when to commit to a go-around and how to maintain control on the ground

Cirrus SR22 · Albert Whitted Airport (KSPG) · Private / Commercial · Landing / Takeoff

The scenario

Departing Albert Whitted Airport (KSPG), St. Petersburg, FL — Runway 25, landing approach in gusty crosswind conditions. Elevation 7 ft MSL. You are a Private pilot with 350 hours total time, 120 hours in the SR22. You are current and proficient, but crosswind landings in the SR22 — a high-performance, constant-speed, glass-panel airplane — demand respect: the energy state is fast, the float is long, and directional control in gusts is unforgiving.

Current conditions: Wind 240° at 18 gusting to 28 knots. Runway 25 is aligned 242° true. The crosswind component is roughly 15–20 knots steady, with gusts pushing toward 25 knots. The SR22's demonstrated crosswind capability is 17 knots. You are at or above that limit, and the gusts are exceeding it. Visibility 10 SM, scattered clouds at 3,500 ft, light turbulence in the pattern. KSPG tower is active (1430 local, within 0700–2100 operating hours).

You are on a 4-mile final for Runway 25, 1,200 ft AGL, descending at 500 fpm. The approach is stable: 88 KIAS (best glide speed, appropriate for a stabilized approach in these conditions), 20° flaps, constant descent. The runway is in sight. The tower has cleared you to land. You have not declared any emergency, and the airplane is performing normally.

Aircraft: Cirrus SR22, solo, within weight and balance limits. Continental IO-550-N, 310 hp, constant-speed prop, glass Perspective panel, fixed gear. Fuel selector on RIGHT tank (you switched from LEFT at top of descent). The airplane is airworthy; nothing was written up.

Pilot: You — Private pilot, 350 hours total, 120 hours SR22. You have made crosswind landings before, but not in gusts this strong. You are confident in your ability to handle the airplane, and you are committed to landing today.

The decision

Before the decision tree — what do you know about crosswind landings in the SR22 and loss of directional control on the ground? (Pick all that apply.)

What the record shows

What the NTSB files show

NTSB CEN21LA051 (2020): A Cirrus SR22 on an instructional flight experienced loss of directional control during landing in a crosswind. The student pilot and instructor fought over the flight controls, and the student failed to relinquish control when directed to go around. The accident resulted from the student's failure to maintain control and his failure to follow the instructor's command to abort the landing. The airplane sustained substantial damage.

NTSB ANC20CA012 (2020): A Cirrus SR22 flown by a student pilot on a private checkride experienced loss of control during a soft-field takeoff in gusting crosswind conditions. The right wingtip struck the runway. The accident resulted from the student's inability to maintain control in crosswind conditions and the designated pilot examiner's delayed remedial action. The airplane sustained substantial damage.

NTSB GAA19CA142 (2019): A Cirrus SR22 on a business flight lost yaw control during landing flare, stalled, and yawed violently left during a go-around attempt. The accident resulted from the pilot's failure to maintain a stabilized approach with a tailwind and subsequent loss of yaw control. The airplane impacted the ground.

NTSB ERA18LA253 (2018): A Cirrus SR22 experienced loss of directional control during takeoff when the pilot's seat slid backward during rotation. The pilot failed to properly secure the seat before flight, which allowed it to slide back as the airplane accelerated. The pilot was unable to reach the pedals and lost directional control. The airplane impacted trees and shrubs.

Regional precedents show a consistent pattern: NTSB GAA17CA105 (PA-46 crosswind landing loss of control), ERA17CA149 (T-6G go-around loss of control in gusts), GAA16CA149 (AA-1 crosswind excursion), and CHI02TA149 (A185F landing rollout loss of directional control) all involve pilots who either failed to recognize when crosswind conditions exceeded their aircraft's demonstrated capability or failed to commit to a go-around early enough. The common thread: early recognition and commitment to a go-around is the correct decision.

The real accidents cited above occurred at other airports and in other aircraft — NOT at Albert Whitted Airport (KSPG). KSPG's own dominant accident pattern includes LOSS_OF_CONTROL_INFLIGHT (20%), FORCED_LANDING (16.4%), and LOSS_OF_CONTROL_GROUND (14.5%) — loss of control is a significant risk at this field. The scenario is localized to KSPG to make the off-field environment real: off Runway 25's departure end (heading 242°) is dense development; off Runway 07 is open water (Tampa Bay). A loss of control on takeoff or landing has real consequences at this field.

The consistent lesson across all these events: the SR22 is a high-performance airplane with a long float and high energy state. Crosswind landings in gusts demand respect. The demonstrated crosswind capability is 17 knots — that is the tested limit. Winds exceeding that, especially with gusts, are beyond the envelope. The correct decision is to recognize the limit early, commit to a go-around, and divert if necessary. Attempting to force a landing in marginal conditions invites loss of directional control.

Key lesson — The SR22's demonstrated crosswind capability is 17 knots. Winds at or above that limit, especially with gusts, are beyond the tested envelope. Recognize the limit early. If the approach is unstable or directional control is marginal, commit to a go-around before the flare. If crosswind conditions at your destination exceed the SR22's capability, divert to a nearby airport with more favorable wind conditions. Attempting to force a landing in marginal conditions invites loss of directional control on the ground — a survivable outcome if you accept a runway excursion, but a catastrophic one if you apply aggressive control inputs that risk a stall or structural damage.

Debrief — teaching points

The SR22's demonstrated crosswind capability is 17 knots — that is the tested limit.

The SR22 POH specifies a demonstrated crosswind component of 17 knots. This is the maximum crosswind the airplane has been tested and proven to handle safely. Winds exceeding this limit are beyond the tested envelope. Gusts that push the instantaneous crosswind component above 17 knots are particularly dangerous because they exceed the airplane's control authority. Recognize this limit before you line up on final approach. If the forecast or reported wind is at or above 17 knots crosswind, plan to divert or request a runway more aligned with the wind.

The SR22 has a long float and high energy state — it is not a Cessna 172.

The SR22 is a high-performance, constant-speed, 310 hp airplane. It carries significantly more energy into the landing than a fixed-pitch, 160 hp trainer. The float is longer, the descent rate is harder to control, and the airplane is more sensitive to wind gusts. Crosswind corrections that work in a 172 may be insufficient in an SR22. Understand that the SR22 demands more precise control inputs and a more stabilized approach. If the approach is unstable, go around early — do not attempt to salvage an unstable approach with aggressive control inputs.

Commit to a go-around early — before the flare — if the approach is unstable or directional control is marginal.

The NTSB precedents show that pilots who attempt to salvage unstable approaches by fighting the wind with aggressive control inputs often end up with loss of directional control. The correct decision is to recognize instability early — at 400–500 ft AGL — and go around before the flare. A go-around costs time and fuel, but it resets the approach and gives you another chance. Attempting to force a landing in marginal conditions is a gamble that often loses.

If crosswind conditions exceed the SR22's demonstrated capability, divert to a nearby airport.

The SR22 is a capable airplane, but it has limits. If the crosswind conditions at your destination exceed 17 knots, or if gusts are pushing the instantaneous crosswind above that limit, divert to a nearby airport with a runway more aligned with the wind or lower wind speeds. This is not a failure — it is airmanship. The NTSB data shows that pilots who attempt to land in marginal crosswind conditions often end up with loss of directional control. Diverting is the safer choice.

During landing rollout, accept a runway excursion rather than apply aggressive rudder that risks a stall or structural damage.

If you lose directional control during landing rollout, the correct response is to ease off the aggressive control inputs and accept a controlled runway excursion. The NTSB precedents (GAA17CA105, ERA17CA149, CHI02TA149) show that pilots who apply full rudder in an attempt to stay on the runway often end up with worse outcomes — nose-overs, structural damage, or loss of control. A runway excursion to the grass is survivable; a stall or structural damage is not. Recognize the limit of control authority and accept the excursion.

At KSPG, the off-field environment is critical to your decision-making.

Off Runway 25's departure end (heading 242°) is dense development — a loss of control on takeoff would result in impact with buildings or terrain. Off Runway 07 (heading 062°) is open water — Tampa Bay — a loss of control on takeoff would result in a ditching. Off Runway 18 and 36 are also water or development. The off-field environment at KSPG is unforgiving. Loss of directional control on the ground is a survivable outcome if you stay on or near the runway; a loss of control on takeoff or a go-around that results in impact with terrain or water is not. This reinforces the importance of recognizing crosswind limits and committing to a go-around early.

Dual control confusion and delayed intervention are accident factors — communicate clearly with your instructor or examiner.

NTSB CEN21LA051 involved a student pilot and instructor fighting over the flight controls during a crosswind landing. The student failed to relinquish control when the instructor directed a go-around. Clear communication is essential: if you are an instructor, take control decisively and communicate your intention. If you are a student or less-experienced pilot, listen to your instructor's commands and relinquish control immediately. Confusion over who is flying the airplane in a critical phase is a recipe for loss of control.

Built from the real accident record

Scenario built from NTSB CEN21LA051 (2020 SR22 loss of directional control during landing, dual control confusion), ANC20CA012 (2020 SR22 loss of control during soft-field takeoff in crosswind), GAA19CA142 (2019 SR22 yaw control loss during landing flare), and ERA18LA253 (2018 SR22 seat-slide loss of control during takeoff). Regional precedents: GAA17CA105 (PA-46 crosswind landing loss of control), ERA17CA149 (T-6G go-around loss of control in gusts), GAA16CA149 (AA-1 crosswind excursion), CHI02TA149 (A185F landing rollout loss of directional control). Real events occurred at other airports — NOT at KSPG.

NTSB reports: CEN21LA051 · ANC20CA012 · GAA19CA142 · ERA18LA253 · GAA17CA105 · ERA17CA149 · GAA16CA149 · CHI02TA149

ACS tasks: PA.I.F — Weather Information · PA.V.A — Preflight Inspection · PA.VIII.A — Approach and Landing · PA.VIII.B — Go-Around / Rejected Landing · PA.I.H — Human Factors

Relevant FARs: §91.3 · §91.13 · §91.103

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 KSPG