Gusts on Short Final
Crosswind landing in deteriorating conditions — directional control, go-around decision, and the cost of delay
The scenario
Departing Albert Whitted Airport (KSPG), St. Petersburg, FL — Runway 25, inbound on a local VFR flight. Elevation 7 ft MSL. You are a Private pilot with roughly 180 hours total; this is your third landing at KSPG in the past month.
It is a late afternoon in early summer: OAT 31°C, wind reported by tower as 240° at 12 knots, gusting to 18. Runway 25 is oriented 242° true. The wind is nearly aligned with the runway — a headwind component of roughly 11 knots, a crosswind component of roughly 3–4 knots. Within limits, but the gusts are notable. Visibility 10 SM, scattered clouds at 3,500 ft. VFR all the way.
You are on a 3-mile final for Runway 25, descending through 800 ft AGL, airspeed 70 KIAS (slightly above Vref of 63 KIAS for a stabilized approach). The tower has cleared you to land. You are configured: flaps 20°, landing gear down (fixed), mixture rich, fuel selector BOTH. The runway is in sight, the approach is stable.
Aircraft: Cessna 172M, solo, within limits. Lycoming O-320-E2D, 150 hp, carbureted, 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 landed at KSPG twice before. You have crosswind experience, but not in gusts above 15 knots. The tower's wind report (240° at 12, gusting to 18) is in the back of your mind, but you are committed to the landing.
- {'label': 'Field', 'value': 'KSPG · Albert Whitted'}
- {'label': 'Runways', 'value': '7/25 · 18/36'}
- {'label': 'Elevation', 'value': '7 ft'}
- {'label': 'Aircraft', 'value': 'C172M'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before we get into the decision tree — what do you know about crosswind limits and go-around decision-making in the C172M? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB WPR25LA061 (2024): A Cessna 172M on an instructional touch-and-go flight lost directional control during takeoff when the student pilot failed to compensate for the aircraft's left-turning tendency. The aircraft exited the left side of the runway, struck a sign with its landing gear, and the nose gear collapsed. The probable cause was the student pilot's failure to maintain directional control during a touch-and-go.
NTSB CEN23LA154 (2023): A Cessna 172M on an instructional flight bounced during landing with a left crosswind, drifted right, and nosed over in the grass after the flight instructor commanded a go-around. The accident resulted from the student pilot's failure to maintain directional control during landing and the flight instructor's delayed remedial response.
NTSB CEN24LA174 (2024): A Cessna 172M being held short of the runway by a flight instructor during a heavy precipitation storm encountered a wind gust that lifted the right wing and pushed the aircraft to the right, resulting in an overturn. The accident was attributed to the flight instructor's failure to maintain control during the wind encounter.
NTSB GAA17CA105 (2016, regional precedent): 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 lost directional control during the aborted landing in gusting crosswind conditions.
NTSB CHI02TA149 (2002, regional precedent): A Cessna A185F veered off the runway during landing rollout when a wind gust forced the aircraft into an uncontrollable turn. The accident was attributed to directional control not being maintained, with gusting winds as a contributing factor. The key lesson: accept the runway excursion rather than attempt aggressive recovery that risks structural damage or flip.
All of these real accidents occurred at other airports — NOT at Albert Whitted Airport (KSPG). KSPG's own dominant accident pattern shows LOSS_OF_CONTROL_INFLIGHT (20%), FORCED_LANDING (16.4%), LOSS_OF_CONTROL_GROUND (14.5%), DITCHING (12.7%), and STALL_SPIN (12.7%). The scenario is localized to KSPG to make the off-field environment real: Runway 25's departure end (heading 242°) is dense development — a runway excursion there is a collision risk, not an open-field landing.
The consistent thread across all these events: loss of directional control in crosswind conditions, especially during landing and rollout, is a ground-handling accident. The C172M's demonstrated crosswind capability is roughly 10–12 knots; gusts above 15 knots total wind speed warrant caution. The decision to go around should be made early — by 500 ft AGL — not during rollout or after touchdown. And when a bounce occurs, the correct response is immediate go-around, not an attempt to salvage the landing.
Key lesson — Crosswind landing loss of control in the C172M is a ground-handling accident that kills through delay and aggressive recovery. Recognize crosswind limits early (demonstrated capability ~10–12 knots; gusts above 15 knots warrant caution). Commit to go-around by 500 ft AGL if conditions are marginal. If a bounce occurs, go around immediately — do not attempt to salvage the landing. If you drift off the runway, accept the excursion and land in the grass; do not apply aggressive control inputs that risk a nose-over or flip. Off Runway 25 at KSPG, the off-field environment is dense development — a runway excursion there is a collision risk, not a field landing. Know the off-field environment before you line up.
Debrief — teaching points
Crosswind limits are real — the C172M's demonstrated crosswind capability is roughly 10–12 knots.
The C172M POH does not publish a specific demonstrated crosswind component, but fleet experience and the NTSB case record show that 10–12 knots is the practical limit for most pilots in calm conditions. Gusts complicate this: a 12-knot steady wind gusting to 18 knots means 6-knot gusts, which can exceed demonstrated capability. The gust factor is the difference between the steady wind and the peak gust. Know your limits and the field's wind conditions before you commit to landing.
The go-around decision should be made early — by 500 ft AGL — not during rollout.
At 500 ft AGL, you have altitude and airspeed to climb out safely. At 250 ft AGL, you are marginal. At 50 ft AGL, you are committed. The NTSB cases show that pilots who delay the go-around decision and attempt to salvage a marginal landing at low altitude end up in loss-of-control accidents. If you are uncomfortable at 500 ft AGL, go around. The runway will be there for another approach.
A bounce during landing is a sign the landing is unstable — go around immediately.
A bounce means the airplane rebounded from the runway at low altitude. The correct response is immediate go-around: advance the throttle to full power, raise the flaps to 10°, and establish a climb at Vy (78 KIAS). Do not attempt to salvage the landing by reducing power and landing again. The NTSB CEN23LA154 case shows that attempting to salvage a bounce in crosswind conditions leads to loss of directional control and nose-over.
If you drift off the runway during landing, accept the excursion — do not apply aggressive control inputs.
Aggressive aileron and rudder inputs at low altitude to force the airplane back toward the runway risk a wing strike and nose-over. The NTSB CHI02TA149 and WPR25LA061 cases show that accepting the runway excursion and landing in the grass is the correct decision. The airplane may sustain minor damage to the gear or fuselage, but it will be upright and repairable. A nose-over or flip is structural damage and potential injury.
Off Runway 25 at KSPG, the off-field environment is dense development — a runway excursion is a collision risk.
The USGS NLCD ground cover off Runway 25's departure end (heading 242°) is dense development, medium development, and low-density development. There are no open fields, no parks, no roads suitable for landing. A runway excursion off Runway 25 is a collision with buildings or structures, not a field landing. This is why Runway 07 (with open water off the departure end) is a better choice for crosswind landings when the wind is from the west — it provides a headwind with minimal crosswind.
Request a runway with more favorable wind alignment when crosswind conditions are marginal.
At KSPG, Runway 07 is oriented 062° true. A 240° wind is a headwind for Runway 07, with minimal crosswind component. If the wind is 240° at 12, gusting to 18, Runway 07 is the better choice. Runway 25 (heading 242°) is nearly aligned with the wind, but the crosswind component is still 3–4 knots — within limits, but marginal in gusts. Know all available runways and their wind alignment before you commit to landing.
Built from the real accident record
Scenario built from NTSB WPR25LA061 (2024 C172M loss of directional control during takeoff), CEN24LA174 (2024 C172M wind gust overturn while holding short), CEN23LA154 (2023 C172M bounce and nose-over in crosswind landing), ERA25LA092A (2024 C172M taxi collision from inadequate directional control), and regional precedents GAA17CA105, ERA17CA149, GAA16CA149, CHI02TA149. Localized to KSPG.
NTSB reports: ERA25LA092A · WPR25LA061 · CEN24LA174 · CEN23LA154 · GAA17CA105 · ERA17CA149 · GAA16CA149 · CHI02TA149
ACS tasks: PA.II.E — Crosswind Takeoff and Landing · PA.II.F — Slip to a Landing · PA.II.G — Go-Around / Rejected Landing · PA.I.H — Human Factors · PA.IX.C — Emergency Approach and Landing
Relevant FARs: §91.3 · §91.13 · §91.207
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 172M scenarios · More scenarios at KSPG