Gusts on Short Final
Crosswind landing in a Cirrus SR22 — recognizing loss of directional control early and committing to recovery before the runway is lost
The scenario
Departing Zephyrhills Municipal Airport (KZPH), Zephyrhills, FL — Runway 19, approaching the landing phase after a 45-minute local flight. Elevation 90 ft MSL. You are a Private pilot with roughly 180 hours total, 35 hours in the SR22. This is a familiar field; you have landed here a dozen times.
Current conditions: OAT 24°C, wind reported by a departing Cessna as 'variable 15 to 22 knots, gusting to 28.' The active runway is 19 (magnetic heading 180°). The wind is from the northeast — roughly 090° — which means a direct crosswind on Runway 19. The demonstrated crosswind capability of the SR22 is approximately 17 knots in calm air; in gusts, the effective limit is lower. The wind is at or beyond your comfort zone.
You are on a 3-mile final approach to Runway 19, descending through 800 ft AGL, airspeed 90 KIAS (slightly above Vref of 77 KIAS for short-field landing, to maintain control authority in the gusts). The approach is stable but the airplane is being pushed left by the crosswind. You are holding a crab angle of roughly 15° to the right to track the runway centerline. The runway is in sight; it looks narrow from this angle.
Aircraft: Cirrus SR22, solo, within weight and balance limits. Fuel is adequate. The constant-speed prop is set for cruise; you have not yet adjusted it for landing. Flaps are at 50% (Vfe 119 KIAS). The side-yoke is responsive; the airplane feels normal.
Pilot: you — a Private pilot, current, 180 hours total, 35 hours SR22 time. You have landed in crosswinds before, but not in gusts this strong. You are confident in the airplane and your ability. You have not briefed a go-around; you are committed to landing.
- {'label': 'Field', 'value': 'KZPH · Zephyrhills'}
- {'label': 'Runways', 'value': '19/1 · 5/23'}
- {'label': 'Elevation', 'value': '90 ft'}
- {'label': 'Aircraft', 'value': 'SR22'}
- {'label': 'Dominant phase', 'value': 'Landing / Cruise'}
The decision
Before we get into the decision tree — what do you already know about crosswind landings in the SR22? (Pick all that apply; this records your baseline.)
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 gusting crosswind. The student pilot and instructor fought over the flight controls; the student failed to relinquish control when directed to go around. The probable cause was the student pilot's failure to maintain control during the crosswind landing and his failure to relinquish control when directed by the instructor to execute a go-around. The accident occurred at a different airport; the mechanism — loss of yaw control in gusts during landing — is the same.
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 probable cause was the student pilot's loss of airplane control during the short-field takeoff in gusting crosswind conditions, and the designated pilot examiner's delayed remedial action. The accident occurred at a different airport; the lesson is the same: crosswind control is marginal in gusts, and early intervention (go-around, diversion) 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 probable cause was the pilot's failure to maintain a stabilized approach with a tailwind and subsequent loss of yaw control during an attempted go-around. The accident occurred at a different airport; the mechanism — loss of yaw control in the flare — is the same.
NTSB ERA18LA253 (2018): A Cirrus SR22 lost directional control during takeoff when the pilot seat slid backward during rotation. The pilot could not reach the pedals and lost directional control. The probable cause was the pilot's failure to properly secure the seat before flight. This accident occurred at a different airport; the lesson is different (preflight discipline), but the outcome — loss of directional control — is the same.
Regional precedents (NTSB GAA17CA105, ERA21LA119, GAA19CA170, ERA10CA448) all document loss of directional control during landing in gusting crosswind conditions. The consistent thread: pilots attempted landings in crosswinds that exceeded demonstrated capability or personal minimums, failed to recognize instability early, and did not commit to a go-around until it was too late.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Zephyrhills Municipal Airport (KZPH). KZPH has its own accident history (see field dominant patterns: FORCED_LANDING 29.2%, LOSS_OF_CONTROL_INFLIGHT 29.2%, STALL_SPIN 16.7%). The scenario is localized to KZPH to make the off-field environment real and the decision-making consequential for you as a student here.
The consistent thread across all these events: crosswind landing accidents in the SR22 result from loss of directional control in the flare — the most critical phase when control authority is marginal and airspeed is low. The fix is early recognition of instability and commitment to a go-around BEFORE the airplane is low and slow over the runway.
Key lesson — In a gusting crosswind, the SR22's demonstrated crosswind capability (~17 knots calm) is exceeded by gust components. Recognize this early, brief a go-around, and commit to it if the approach becomes unstable below 500 ft AGL. The flare is the most critical phase — control authority is marginal, airspeed is low, and a gust can cause sudden yaw and loss of directional control. A go-around at 500 ft AGL is safe and recoverable; a loss of control at 50 ft AGL is not. Know your personal minimums and do not exceed them.
Debrief — teaching points
The SR22's demonstrated crosswind capability is approximately 17 knots in calm air; gusts reduce the effective limit significantly.
A gust of 28 knots with a mean wind of 15 knots represents a 13-knot gust component — well beyond the demonstrated capability. The effective crosswind limit in gusts is much lower than the calm-air number. Know this before you line up on the runway. If the reported wind is variable with gusts, calculate the gust component and compare it to your personal minimums. If it exceeds your limit, go around or divert.
Brief a go-around BEFORE you descend below 500 ft AGL in marginal crosswind conditions.
A go-around at 500 ft AGL is safe and recoverable. A loss of control at 50 ft AGL is not. Before you descend below 500 ft AGL in a gusting crosswind, brief yourself: 'If the approach becomes unstable, I will advance power, retract flaps, and go around.' Know your abort plan before you need it. Do not commit to landing until the approach is stable and you are confident you can land safely.
The flare is the most critical phase of a crosswind landing — control authority is marginal and airspeed is low.
In the flare, the airplane is slow (near Vs0 59 KIAS), control authority is reduced, and the airplane is sensitive to control inputs. A gust can cause sudden yaw and loss of directional control. Keep the airplane aligned with the runway using rudder; use aileron to keep the wings level. If a gust causes yaw, apply rudder immediately to correct. If you cannot maintain directional control, execute a go-around — advance power, retract flaps, and climb away.
De-crab the airplane (align nose with runway) BEFORE touchdown, not during the flare.
Crabbing on approach is acceptable, but the airplane must be de-crabbed before touchdown. If you land in a crab (nose offset from the runway), the crosswind will continue to push the airplane left, and you will drift off the runway. De-crab by reducing the crab angle and aligning the nose with the runway as you descend through 300 ft AGL. By the time you touch down, the airplane should be aligned with the runway.
Maintain directional control during landing rollout using rudder and aileron — do not rely on brakes to steer.
In a crosswind landing rollout, the crosswind continues to push the airplane left. Use rudder to keep the nose straight and aileron to keep the wings level. Aggressive braking locks the main gear and reduces your ability to steer with the nosewheel. Apply moderate brakes and maintain control inputs as the airplane slows. Directional control is your priority; stopping is secondary.
Know your personal minimums for crosswind landings and do not exceed them.
Your personal minimums should be lower than the demonstrated capability — especially in gusts. If you are not comfortable landing in a particular crosswind, go around or divert. There is no shame in diverting to a nearby airport with more favorable wind alignment. A diversion is a safe decision; a loss of control is an accident.
Built from the real accident record
Scenario built from NTSB CEN21LA051 (2020 SR22 loss of directional control / dual-control conflict during crosswind landing), ANC20CA012 (2020 SR22 loss of control during soft-field takeoff in crosswind), GAA19CA142 (2019 SR22 loss of yaw control during landing flare), and ERA18LA253 (2018 SR22 seat-slide loss of control during takeoff). Regional precedents: GAA17CA105, ERA21LA119, GAA19CA170, ERA10CA448 (crosswind landing loss-of-control events in comparable aircraft). Anonymized and localized to KZPH.
NTSB reports: CEN21LA051 · ANC20CA012 · GAA19CA142 · ERA18LA253 · GAA17CA105 · ERA21LA119 · GAA19CA170 · ERA10CA448
ACS tasks: PA.I.F — Weather Information · PA.I.H — Human Factors · PA.II.E — Takeoff and Departure · PA.III.C — Approach and Landing · PA.IX.C — Emergency Approach and Landing
Relevant FARs: §91.3 · §91.13 · §91.21
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 KZPH