Gusts on Short Final at Clearwater
Crosswind landing in a high-performance Cirrus — when to commit to a go-around and how to execute it cleanly
The scenario
Departing Clearwater Air Park (KCLW), Clearwater, FL — Runway 34, a 4,108 ft asphalt runway on a true heading of 335°. Field elevation 71 ft MSL. You are a Private pilot with 180 hours total, 45 hours in the SR22, and current. This is a local flight — a 45-minute round trip to a nearby field and back.
Weather: VFR, scattered clouds at 3,500 ft, visibility 10 SM. Wind is reported from 310° at 12 knots, gusting to 18 knots. That is a 25° crosswind to Runway 34 (335° heading). The demonstrated crosswind capability of the SR22 is 17 knots. The gusts are at the edge of your demonstrated limit — not beyond it, but marginal. The field is non-towered (CTAF); you will self-announce on 122.8.
You have completed your approach briefing. You are on a 3-mile final to Runway 34, descending through 500 ft AGL, airspeed 90 KIAS (slightly above Vref of 77 KIAS for short-field landing, to maintain control authority in the gusts). The Cirrus Perspective glass panel is clear and responsive. The constant-speed prop is set for descent. Fuel selector is on RIGHT (you switched from LEFT at the top of descent). You are configured: gear fixed (it is always down on the SR22), flaps 50%, trim set.
At 300 ft AGL, a gust hits from the left. The airplane drifts right of centerline. You correct with left aileron and left rudder. The drift stops. You are back on centerline. You continue the descent.
At 200 ft AGL, another gust — this time stronger. The airplane yaws left and drifts left of centerline. You apply right rudder and right aileron to correct. The airplane responds, but the correction feels sluggish. You are now 50 ft AGL, 0.3 nm from the runway threshold, and the gusts are continuous. The airplane is drifting left again. You have a decision to make: commit to landing and manage the drift, or execute a go-around.
Aircraft: Cirrus SR22, solo, full fuel (approximately 3,400 lb gross weight), within limits. Nothing was written up; the airplane is airworthy. The constant-speed prop is functioning normally. Fuel selector is on RIGHT.
Pilot: you — a Private pilot, current, 180 hours total, 45 hours in the SR22. You have landed in crosswinds before, but never in gusts this strong. You are not a CFI; you are a single pilot. Your personal minimums are 15 knots crosswind. The gusts are at 18 knots — above your personal minimums.
- {'label': 'Field', 'value': 'KCLW · Clearwater Air Park'}
- {'label': 'Runways', 'value': '16/34'}
- {'label': 'Elevation', 'value': '71 ft'}
- {'label': 'Aircraft', 'value': 'SR22'}
- {'label': 'Dominant phase', 'value': 'Landing / Approach'}
The decision
Before we get into the decision tree — what do you know about crosswind landings in the SR22 and when to go around? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB CEN21LA051 (2020): A Cirrus SR22 on a Part 91 instructional flight experienced a loss of directional control during landing when the student pilot and instructor fought over the flight controls. The student pilot failed to maintain control during a crosswind landing and failed to relinquish control when directed by the instructor to execute a go-around. The probable cause was the student pilot's failure to maintain control and his failure to go around when directed. The accident highlights the danger of dual-control conflict during a critical phase of flight, but also the underlying issue: the student did not recognize when conditions exceeded his capability and did not commit to a go-around early.
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, with the right wingtip striking the runway. The student pilot was unable to maintain control in crosswind conditions, and the designated pilot examiner delayed remedial action. The probable cause was the student pilot's loss of airplane control during a short-field takeoff in gusting crosswind conditions and the examiner's delayed intervention. The accident shows that loss of directional control in crosswind gusts can occur during takeoff as well as landing, and that early intervention (or in this case, a go-around) is critical.
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, impacting the ground. The pilot failed to maintain a stabilized approach with a tailwind and subsequently failed to maintain yaw control during an attempted go-around. The probable cause was the pilot's failure to maintain a stabilized approach and his failure to maintain yaw control during the go-around. The accident shows that a poorly executed go-around (in this case, with a tailwind and a stall) is as dangerous as a poorly executed landing.
NTSB ERA18LA253 (2018): A Cirrus SR22 on a personal cross-country flight experienced loss of directional control during takeoff when the pilot seat slid backward during rotation. The pilot failed to properly secure the seat before flight, which allowed it to slide back as the aircraft accelerated. The probable cause was the pilot's failure to properly secure the seat, which resulted in the seat sliding back, the pilot's inability to reach the pedals, and the subsequent loss of directional control. The accident is a reminder that even a well-executed takeoff can fail if the airplane is not properly configured before flight.
Regional precedents show the same pattern: NTSB GAA17CA105 (Piper PA-46, 2016) and ERA21LA119 (Cessna 172R, 2021) both involved loss of directional control during landing in gusting crosswind conditions that exceeded the aircraft's demonstrated crosswind capability or the pilot's personal minimums. The common thread: the pilots attempted to land in conditions that exceeded their limits, rather than recognizing the limits early and committing to a go-around or diversion.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Clearwater Air Park. KCLW has its own accident history (see field dominant patterns: FORCED_LANDING 22.2%, LOSS_OF_CONTROL_INFLIGHT 18.5%, GEAR_UP_LANDING 18.5%), but these specific NTSB events happened elsewhere. The scenario is localized to KCLW to make the off-field environment real and consequential for you as a student here.
The consistent thread across all these events: loss of directional control in crosswind conditions is a function of three factors: (1) wind conditions that exceed the aircraft's demonstrated capability or the pilot's personal minimums, (2) a pilot who does not recognize the limits early, and (3) a delayed decision to go around or divert. The SR22 is a high-performance, high-energy airplane; it floats in a crosswind landing and is slow to decelerate on the ground. Early recognition and a clean go-around at 50 ft AGL — not at 20 ft AGL — is the entire lesson.
Key lesson — Crosswind gusts at 18 knots exceed the SR22's demonstrated crosswind capability (17 knots) and your personal minimums (15 knots). Recognize this early — at 50 ft AGL on short final, not at 20 ft AGL — and execute a clean go-around: reduce power, maintain 77 KIAS (Vref), retract flaps to 25%, and climb to pattern altitude. If the conditions do not improve, divert to a nearby airport with a more favorable wind. Off Runway 34 at KCLW, the off-field environment is low-density and medium development — not a safe forced-landing option. The decision to go around or divert is the correct one when conditions exceed your personal minimums.
Debrief — teaching points
Demonstrated crosswind capability is a tested limit, not a target.
The SR22's demonstrated crosswind capability is 17 knots — that is the maximum crosswind in which the airplane was tested and found to be controllable by an average pilot. Gusts above that are beyond the tested limit. Your personal minimums should be lower than the demonstrated capability — typically 3–5 knots lower. If gusts are at 18 knots and your personal minimum is 15 knots, the gusts exceed your personal limit. The go-around or diversion is the correct decision, not an attempt to land.
Recognize the limit early — at 50 ft AGL, not at 20 ft AGL.
In this scenario, you recognized the drift at 200 ft AGL and again at 50 ft AGL. At 50 ft AGL, you had a clear decision point: commit to a go-around or attempt the landing. A go-around at 50 ft AGL is safe and clean. A go-around at 20 ft AGL is survivable but marginal. A late abort at 40 ft AGL without a clean go-around profile is dangerous. Recognize the limit early and execute a clean go-around before the airplane is committed to landing.
A clean go-around profile is: reduce power, maintain airspeed, retract flaps, climb.
The SR22's go-around procedure is: (1) Reduce power to idle (or a reduced setting for a shallow go-around), (2) Maintain 77 KIAS (Vref) to preserve control authority, (3) Retract flaps from 50% to 25% (or full retraction if altitude permits), (4) Climb to pattern altitude. Do not pitch up abruptly without reducing flaps or establishing a stable airspeed — that invites a stall. Do not add power without reducing flaps — that causes a float and a slow climb. Execute the procedure cleanly and the go-around is safe.
The SR22 is a high-performance, high-energy airplane — it floats in a crosswind landing.
The SR22 has a constant-speed prop, a fuel-injected Continental IO-550-N (310 hp), and a glass Perspective panel. It is fast, responsive, and energy-rich. In a crosswind landing, the airplane floats — it does not want to touch down. The high energy state means you need more runway, more altitude margin, and more control authority to manage a crosswind. Recognize that the SR22 is not a forgiving airplane in marginal conditions; it requires precise control and early decision-making.
If you go around once, be prepared to divert if conditions do not improve.
In this scenario, you went around at 50 ft AGL because the gusts exceeded your personal minimums. You re-entered the pattern and found the same wind conditions — 310° at 12 gusting 18 knots. The conditions did not improve. The correct decision at that point was to divert to a nearby airport with a more favorable wind, not to attempt a second or third approach in the same marginal conditions. Recognize when conditions are not going to improve and commit to a diversion early.
Off Runway 34 at KCLW, the off-field environment is low-density and medium development — not a safe forced-landing option.
The off-field environment off Runway 34's climb-out (heading 335°) is low-density development, medium development, and open developed areas (parks/large lots). It is not open water, but it is not a safe forced-landing option either. If you lose directional control during landing and veer off the runway, you will impact terrain, structures, or obstacles. The correct decision is to go around and divert, not to attempt a landing in marginal conditions and hope for the best.
Built from the real accident record
Scenario built from NTSB CEN21LA051 (2020 SR22 loss of directional control during crosswind landing, dual-control conflict), ANC20CA012 (2020 SR22 loss of control during soft-field takeoff in gusting crosswind, wingtip strike), GAA19CA142 (2019 SR22 loss of yaw control during landing flare with tailwind), and ERA18LA253 (2018 SR22 loss of directional control during takeoff due to unsecured seat). Regional precedents: GAA17CA105, ERA21LA119, GAA19CA170, ERA10CA448 (crosswind loss-of-control events in comparable aircraft). Localized to KCLW.
NTSB reports: CEN21LA051 · ANC20CA012 · GAA19CA142 · ERA18LA253 · GAA17CA105 · ERA21LA119 · GAA19CA170 · ERA10CA448
ACS tasks: PA.I.F — Weather Information · PA.I.G — Cross-Country Flight Planning · PA.II.D — Takeoff and Departure · PA.III.A — Approaches and Landings · PA.III.C — Go-Around / Rejected Landing · PA.I.H — Human Factors
Relevant FARs: §91.3 · §91.13 · §91.103
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 KCLW