Gusting Crosswind on Short Final
Directional control, wind limits, and the decision to go around — a C172R at Sarasota Bradenton in gusty conditions
The scenario
Departing Sarasota Bradenton International Airport (KSRQ), Sarasota, FL — Runway 14, a 9,500 ft asphalt runway aligned 134° true. Elevation 30 ft MSL. The field is towered and active; Class C airspace ceiling 4,000 MSL.
It is a breezy Florida afternoon: surface wind 160° at 18 gusts 28 knots. Runway 14 is nearly perpendicular to the wind — a crosswind component of roughly 17–26 knots depending on the gust. The C172R's demonstrated crosswind capability is 12 knots. You are well above that limit. Visibility 10 SM, scattered clouds at 3,500 ft, VFR.
You are on short final to Runway 14, 400 ft AGL, 65 KIAS (Vref, short-field approach speed), full flaps (30°), configured for landing. The runway is made; you are stable. Then a gust hits from the right (north). The airplane yaws left; the right wing rises. You correct with right aileron and right rudder. The gust passes. You are still on glide path, still 65 KIAS, but the approach is no longer smooth.
Aircraft: Cessna 172R, solo, 1,800 lb (well within limits), fuel 40 gal. Lycoming IO-360-L2A, fuel-injected, fixed-pitch prop, fixed gear, steam panel. Nothing was written up; the airplane is airworthy.
Pilot: you — a Private pilot, current, roughly 180 hours total. You have 12 hours in the C172R. You have landed in crosswinds before, but not in gusts this strong. You did not check the demonstrated crosswind limit before requesting the approach. You are committed to landing.
- {'label': 'Field', 'value': 'KSRQ · Sarasota Bradenton'}
- {'label': 'Runways', 'value': '4/22 · 14/32'}
- {'label': 'Elevation', 'value': '30 ft'}
- {'label': 'Aircraft', 'value': 'C172R'}
- {'label': 'Dominant phase', 'value': 'Takeoff / Landing'}
The decision
Before we get into the decision tree — what do you know about crosswind limits and directional control in the C172R? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB WPR11FA242 (2011, FATAL): A Cessna 172R stalled during a downwind turn while executing a go-around from a landing attempt at Wendover Airport. The pilot did not maintain adequate airspeed during the downwind turn, resulting in an aerodynamic stall, in-flight loss of control, and spin. Contributing factors included inadequate preflight planning and exceedance of the approved weight and balance envelope. The accident was fatal.
NTSB CEN22LA014 (2021): A Cessna 172R on a personal flight encountered gusting winds during landing approach and experienced a hard, bounced landing that collapsed the nose gear. The probable cause was the pilot's failure to maintain control of the airplane while landing in gusting wind conditions. The airplane was substantially damaged.
NTSB ERA23LA339 (2023): A Cessna 172R on a solo instructional flight lost control during a soft-field takeoff when an unexpected wind gust caught the pilot off guard. The probable cause was the pilot's inadequate compensation for the prevailing wind conditions. The accident resulted in a collision with trees.
NTSB GAA17CA105 (2016, Piper PA-46): A Piper PA-46 experienced loss of directional control during landing rollout in gusting crosswind conditions that exceeded the aircraft's demonstrated crosswind capability. The pilot did not commit to a go-around early; instead, attempted recovery during rollout. The accident demonstrates the critical importance of recognizing when crosswind conditions exceed aircraft limits and committing to go-around early rather than attempting recovery during landing.
NTSB ERA17CA149 (2017, North American T-6G): A North American T-6G aircraft landed hard during a go-around attempt in gusting crosswind conditions; the right wingtip contacted the runway, the aircraft pivoted right, and nosed over. The probable cause was the pilot's failure to maintain directional control during the landing roll and go-around in gusting wind conditions. The lesson: maintain crosswind correction technique through all phases of landing rollout; recognize when a gust has overcome control authority and commit to go-around before structural damage occurs.
NTSB GAA16CA149 (2016, Grumman AA-1): An American AA-1 sustained substantial damage when the pilot lost directional control during landing and nosed over after the nose gear was damaged during takeoff in crosswind conditions. The pilot exceeded the aircraft's maximum demonstrated crosswind component of 13 knots during both takeoff and landing. The lesson: recognize directional control loss early during takeoff roll and abort immediately; understand how damage sustained during takeoff affects landing options and control authority.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Sarasota Bradenton International Airport. KSRQ has its own accident history (dominant pattern: loss of control ground 19.2%, forced landing 15.4%, runway excursion 11.5%), but these specific events happened elsewhere. The scenario is localized to KSRQ to make the off-field environment real and consequential for you as a student here.
The consistent thread across all these events: crosswind conditions that exceed the demonstrated limit can overcome the airplane's control authority. The C172R's demonstrated crosswind capability is 12 knots. Gusts that exceed this limit, especially in combination with a crosswind component near the limit, can cause loss of directional control. The correct response is to recognize this early — on the approach or during the landing roll — and commit to a go-around before the situation becomes unrecoverable. Attempting to recover during landing, or continuing an approach when control is marginal, leads to nose-overs, cartwheels, and loss of control accidents.
Key lesson — The C172R's demonstrated crosswind capability is 12 knots. Wind conditions that exceed this limit — especially gusts that exceed it — can overcome the airplane's control authority. Recognize this early in the approach or landing roll. If you lose directional control or the approach becomes unstable due to wind, go around immediately. Do not attempt to recover during landing. Do not try to 'make it work' by pushing harder on the controls. Commit to the go-around, climb to pattern altitude, and either request another approach to a runway more aligned to the wind, or divert to a nearby airport with calmer conditions. Off Runway 14 at KSRQ, the off-field environment is dense development — a loss-of-control accident there is likely to be severe. Recognize your limits, make a conservative decision, and live to fly another day.
Debrief — teaching points
The C172R's demonstrated crosswind capability is 12 knots — this is a hard limit, not a guideline.
The demonstrated crosswind capability is the maximum crosswind component the manufacturer tested and certified for the airplane. It is not a suggestion; it is a limit. Exceeding it significantly increases the risk of loss of directional control, especially in gusts. The C172R at KSRQ with a surface wind of 160° at 18 gusts 28 knots on Runway 14 (aligned 134°) has a crosswind component of roughly 17–26 knots — well above the 12-knot limit. This is not a marginal situation; it is a clear exceedance. Recognize this before you request the approach. Check the wind, calculate the crosswind component, and make a decision on the ground — not in the air.
A gust that exceeds the demonstrated limit can overcome the airplane's control authority.
The rudder and aileron have finite authority. A gust that exceeds the demonstrated crosswind limit can overcome that authority. When this happens, the airplane will not respond to control inputs the way you expect. The right wing will rise, the nose will yaw left, and you will not be able to correct it with the available control inputs. This is not a control problem; it is a physics problem. The airplane is doing what it is designed to do when control authority is exceeded. Recognize this early — on the approach or during the landing roll — and go around immediately.
Recognize loss of directional control early and commit to a go-around before the situation becomes unrecoverable.
Loss of directional control in a crosswind typically begins with a gust that causes the right wing to rise and the nose to yaw left (or vice versa, depending on the gust direction). Your first correction with aileron and rudder will be effective. But if the gust is strong or sustained, your control inputs will become larger and less effective. At this point — when you notice that your control inputs are large and the airplane is not responding as quickly as you expected — you should go around. Do not wait for the situation to become worse. Do not try to 'make it work' by pushing harder on the controls. Go around immediately. The go-around is not a failure; it is the correct decision.
The go-around decision window is short — recognize it and act immediately.
At 400 ft AGL on short final, the go-around decision window is measured in seconds. If you lose directional control at 400 ft, you have roughly 30 seconds before you are below 200 ft AGL and the go-around becomes marginal. If you lose directional control at 300 ft, you have roughly 20 seconds. If you lose directional control at 200 ft, you may not have time to go around safely. Recognize the loss of control early — at 400 ft or above — and commit to the go-around immediately. Do not wait to see if the next gust will be smaller. Do not try to recover during the landing roll. Go around.
Divert to a runway more aligned to the wind, or divert to a nearby airport with calmer conditions.
If the wind conditions at your destination exceed the demonstrated limit for one runway, request a different runway that is more aligned to the wind. At KSRQ, if Runway 14 is too gusty, request Runway 32 (aligned 314°), which would put the wind more on the nose. If no runway at your destination is suitable, divert to a nearby airport with calmer conditions. This is not a failure; it is airmanship. The alternative — pushing it and losing control — is not acceptable.
Preflight planning includes checking the wind and calculating the crosswind component.
Before you request an approach, check the wind and calculate the crosswind component. Use the formula: crosswind component = wind speed × sin(angle between wind and runway). For a 160° wind at 18 knots on Runway 14 (aligned 134°), the angle is 26°, and the crosswind component is 18 × sin(26°) ≈ 8 knots. For gusts of 28 knots, the crosswind component is 28 × sin(26°) ≈ 12 knots — right at the demonstrated limit. For gusts of 30 knots, the crosswind component is 30 × sin(26°) ≈ 13 knots — exceeding the limit. Make this calculation before you request the approach. If the crosswind component exceeds the demonstrated limit, request a different runway or divert.
Built from the real accident record
Scenario built from NTSB WPR11FA242 (2011 C172R stall/spin on go-around), CEN22LA014 (2021 C172R hard landing in gusting crosswind), ERA23LA339 (2023 C172R loss of control on soft-field takeoff in wind gust), and regional precedents GAA17CA105, ERA17CA149, GAA16CA149 (crosswind control loss). Anonymized and localized to KSRQ.
NTSB reports: WPR11FA242 · NYC05FA075 · ERA23LA339 · CEN22LA014 · GAA17CA105 · ERA17CA149 · GAA16CA149
ACS tasks: PA.I.F — Weather Information · PA.I.G — Cross-Country Flight Planning · PA.II.E — Takeoff and Departure · PA.III.A — Normal Approach and Landing · PA.III.B — Forward Slip to a Landing · 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 Cessna 172R scenarios · More scenarios at KSRQ