Gusts Over the Gulf
Crosswind landing in a high-performance single with a constant-speed prop — the energy state is fast, the runway is narrow, and the wind is not cooperating
The scenario
Departing Venice Municipal Airport (KVNC), Venice, FL — Runway 22, landing approach in gusty crosswind conditions. Field elevation 18 ft MSL. You are a Private pilot with 180 hours total time, 45 hours in the Cirrus SR22. This is a personal flight; you are solo.
The weather is VFR but deteriorating. Surface wind is 310° at 18 knots, gusting to 26 knots. Runway 22 (true heading 225°) is a right crosswind — roughly 15 knots steady, gusting to 23 knots. The SR22's demonstrated crosswind capability is 17 knots. You are at the limit, and the gusts are exceeding it. Visibility 8 SM, scattered clouds at 3,500 ft, temperature 24°C, dew point 18°C. KVNC is non-towered (CTAF); you self-announce on 122.775 MHz.
You are on a 3-mile final for Runway 22, descending through 800 ft AGL. The approach has been stable until now, but the wind is noticeably gusty — the airplane is drifting right, then left, then right again. You are correcting with aileron and rudder, but the corrections are getting larger. Your airspeed is 85 KIAS (5 knots above Vref of 77 KIAS short-field), full flaps (50%), and you are committed to the landing.
Aircraft: Cirrus SR22, solo, within limits. Continental IO-550-N fuel-injected engine, constant-speed prop, glass Perspective panel, fixed gear. Fuel selector on RIGHT tank (you switched to RIGHT 15 minutes ago on downwind). Nothing was written up; the airplane is airworthy.
Pilot: you — a Private pilot, current, 180 hours total, 45 hours SR22. You have landed in crosswinds before, but not in gusts this strong. Your personal minimums are 15 knots demonstrated crosswind; you are now exceeding them. You did not brief a go-around decision point before entering the approach.
- {'label': 'Field', 'value': 'KVNC · Venice'}
- {'label': 'Runways', 'value': '4/22 · 13/31'}
- {'label': 'Elevation', 'value': '18 ft'}
- {'label': 'Aircraft', 'value': 'SR22'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
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 when the student pilot and instructor fought over the flight controls in a crosswind. The student pilot failed to maintain control during the approach and failed to relinquish control when directed by the instructor to go around. The accident resulted from the student's failure to maintain control in crosswind conditions and the instructor's delayed intervention.
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 crosswind component exceeded the aircraft's demonstrated capability.
NTSB GAA19CA142 (2019): A Cirrus SR22 on a business flight lost yaw control during landing flare when the pilot failed to maintain a stabilized approach with a tailwind. The airplane stalled and yawed violently left during a go-around attempt, impacting the ground. The accident resulted from the pilot's failure to maintain a stabilized approach and his subsequent failure to maintain yaw control.
NTSB ERA18LA253 (2018): A Cirrus SR22 on a personal cross-country flight experienced loss of directional control during takeoff when the pilot's seat slid backward during rotation. The pilot could not reach the pedals and lost directional control. The airplane impacted trees and shrubs. The accident resulted from the pilot's failure to properly secure the seat before flight.
Regional precedents (GAA17CA105, ERA21LA119, GAA19CA170, ERA10CA448) show a consistent pattern: loss of directional control during landing in gusting crosswind conditions. The common thread is the pilot's failure to recognize when crosswind conditions exceed the aircraft's demonstrated capability and the failure to commit to a go-around early rather than attempting recovery during the approach or landing.
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 crosswind challenge real and consequential for you as a student here.
The consistent lesson across all these events: the SR22 is a high-performance single with 310 hp and a constant-speed prop. It carries more energy into the landing than a Cessna 172 and floats longer. Crosswind handling is more demanding. The demonstrated crosswind capability is 17 knots. When gusts exceed that limit, the pilot's control authority is exhausted — the airplane will weathervane into the wind and yaw cannot be corrected with available rudder. The correct response is a go-around decision made BEFORE the approach, not during it. Waiting until 300 ft AGL to recognize the problem is waiting too long.
Key lesson — The SR22's demonstrated crosswind capability is 17 knots. When gusts exceed that limit, loss of directional control is inevitable — the airplane will weathervane into the wind and available rudder authority is insufficient to correct it. The go-around decision must be made before entering the approach, not during the flare. If the wind is gusting beyond limits, commit to a go-around early or divert to a runway with a more favorable orientation. Full flaps in a crosswind reduces control authority — consider reducing flaps to 25% to increase airspeed and control margin. At KVNC, Runway 22 (225° true) and Runway 04 (45° true) are both crosswind to a 310° wind. If the crosswind component exceeds 17 knots in gusts, divert to a nearby airport with a more favorable runway alignment.
Debrief — teaching points
The SR22's demonstrated crosswind capability is 17 knots — this is a hard limit, not a guideline.
When gusts exceed 17 knots, the airplane's rudder authority is exhausted. The airplane will weathervane into the wind and yaw cannot be corrected with available control deflection. This is not a recovery challenge — it is a loss of control. The NTSB cases CEN21LA051 and ANC20CA012 show this exact sequence: crosswind exceeds demonstrated limit, loss of directional control, runway excursion or impact. The go-around decision must be made before entering the approach, not during the flare. If the wind is gusting beyond 17 knots, commit to a go-around early or divert.
Full flaps in a crosswind is a trap — reduce flaps to increase control authority.
In strong crosswinds, reducing flaps from 50% to 25% increases airspeed and control authority. The SR22 at 95 KIAS with 25% flaps has more control margin than at 85 KIAS with 50% flaps. The trade-off is landing distance — but Runway 22 at KVNC is 5,000 ft, and you will use roughly 2,500 ft at 95 KIAS. Control authority is more important than the slowest possible touchdown speed when the wind is gusting beyond limits. Full flaps in a crosswind reduces your ability to correct drift — avoid it.
The SR22 carries more energy into the landing than a Cessna 172 — crosswind handling is more demanding.
The SR22's 310 hp Continental IO-550-N and constant-speed prop give it higher cruise speed and longer float on approach. It is a high-performance single. Crosswind handling requires more anticipation and larger control inputs than in a lower-performance airplane. The airplane will drift and yaw more aggressively in gusts. Recognize this and plan accordingly — reduce flaps, increase airspeed, and give yourself more control margin.
CAPS is not a recovery tool for a crosswind landing gone wrong — it is for unrecoverable spins at altitude.
CAPS (the whole-airframe parachute) is designed for unrecoverable spins and loss of control at altitude. At 300 ft AGL, there is not enough altitude for the parachute to fully arrest the descent. Deploying CAPS at low altitude will result in a hard impact. The correct response to loss of directional control at 300 ft AGL is to level the wings with aileron and push the throttle forward to climb — not to deploy CAPS. Know the limits of your emergency systems.
The go-around decision must be made before the approach, not during the flare.
Evaluate the wind before descending on final. If the crosswind component is gusting beyond 17 knots, do not enter the approach — go around or divert. At 3 miles final and 800 ft AGL, you still have time to make a safe go-around. At 300 ft AGL in the flare, you are out of options. The decision window is short — make it early.
At KVNC, both Runway 22 and Runway 04 are crosswind to a 310° wind — know your runway options.
Runway 22 (225° true) is a right crosswind to 310°. Runway 04 (45° true) is a left crosswind to 310°. Both have roughly the same crosswind component. If the crosswind component exceeds 17 knots in gusts, neither runway is suitable. Divert to a nearby airport with a more favorable runway alignment. Know your diversion options before you depart.
Built from the real accident record
Scenario built from NTSB CEN21LA051 (2020 SR22 loss of directional control during landing, crosswind + dual-control conflict), ANC20CA012 (2020 SR22 loss of control during soft-field takeoff in gusting crosswind), GAA19CA142 (2019 SR22 loss of yaw control during landing flare with tailwind), ERA18LA253 (2018 SR22 seat-slide loss of control during takeoff), and regional crosswind-accident precedents GAA17CA105, ERA21LA119, GAA19CA170, ERA10CA448. Localized to KVNC.
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.C — Takeoff and Departure · PA.III.C — Approach and Landing · PA.I.H — Human Factors · PA.IX.C — Emergency Approach and Landing
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 KVNC