The Gust You Didn't Plan For
A gusty crosswind, a late commitment, and the runway excursion that ends it
The scenario
Field: Tampa International Airport (KTPA), Tampa, FL — elevation 26 ft MSL. You are cleared to land Runway 28, a 6,999-ft PEM surface, magnetic heading 272°. KTPA is Class B airspace, towered 24 hours; you are operating under a Special VFR clearance for training, coordinated with Tampa Approach.
Aircraft: Cessna 172S, G1000 panel, Lycoming IO-360-L2A (fuel-injected, 180 hp), fixed gear, fixed-pitch prop. Two aboard, weight within limits. Fuel selector on BOTH. No mechanical squawks.
Weather: METAR KTPA 1553Z — wind 200° at 14 knots, gusting 24 knots. OAT 29°C, altimeter 29.92. VMC, scattered at 3,500 ft. The wind is a left crosswind on Runway 28 (crosswind component: approximately 13 knots steady, gusting to 22 knots). The C172S POH demonstrated crosswind component is 15 knots — you are at or beyond that limit on the gusts.
Pilot: you — a Private pilot with 180 hours total time, 40 hours in the C172S. You have flown crosswind landings before, but your personal best in this type is about 12 knots. You are current, rested, and flying with a safety pilot in the right seat who is not rated.
The situation: You are on a 3-mile final for Runway 28. The ATIS reported gusts when you copied it; Tampa Tower just updated the wind to 200° at 14 gusting 24. You are configured: flaps 20°, 80 KIAS on final, transitioning to 65 KIAS on short final. The runway ahead is 6,999 feet — plenty of pavement. The off-field environment off Runway 28's departure end is marginal at best: dense development and medium development to the west, with only scattered open developed areas (parks, large lots). There is nowhere good to go if something goes wrong off the end.
- {'label': 'Field', 'value': 'KTPA · Tampa'}
- {'label': 'Runways', 'value': '10/28 · 19L/01R · 19R/01L'}
- {'label': 'Elevation', 'value': '26 ft'}
- {'label': 'Aircraft', 'value': 'C172S'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
On a 3-mile final for Runway 28 with a gusty left crosswind, before you reach the threshold — which of these is actively in your thinking? (Pick all that apply — no wrong answers; this records your pre-landing mental model.)
What the record shows
What the NTSB files show
Crosswind landing loss of directional control is among the most common accident types in the C172S fleet. The NTSB record for this exact type includes ERA21LA202 (2021): a C172S on short final in gusting crosswind conditions, high and slow, initiated a go-around but improper pitch control caused a tail strike and runway excursion to the left into grass. The probable cause: 'the pilot's improper pitch control during a go-around in gusting crosswind conditions.' CEN23LA159 (2023): a C172S with a tailwind on final attempted a go-around when the landing appeared long; the aircraft porpoised, the nose gear collapsed, and the aircraft departed the runway.
The regional pattern reinforces the lesson. ERA21LA119 (2021), a C172R at a Florida airport: veered left off the runway in gusting crosswind, struck the ground with the propeller and left wingtip. GAA17CA105 (2016), a Piper PA-46 in the Tampa region: loss of directional control during landing rollout in gusts that exceeded the demonstrated crosswind component.
The common thread is not a single bad input — it is a chain: conditions at or near the demonstrated limit, a go-around decision made too late or executed improperly, and directional control lost on or near the runway surface. At KTPA, the off-field environment off Runway 28's west end is dense development with only marginal open areas. A runway excursion at rollout speed into that environment is not survivable without serious damage.
The C172S POH demonstrated crosswind component is 15 knots. 'Demonstrated' does not mean 'maximum safe' — it means the test pilot demonstrated a landing in that condition. Your personal limit, especially as a low-time private pilot, should be lower. The gust additive (half the gust spread added to Vref) and the go-around trigger set before the threshold are not optional techniques — they are the difference between a training flight and an accident report.
These events occurred at airports other than KTPA. The scenario is localized to KTPA to make the environment and consequences concrete for pilots who fly here.
Key lesson — Set your go-around trigger before you reach the threshold — a specific altitude, alignment, and control-authority criterion — and honor it. In a gusty crosswind at or beyond your personal limit, the go-around is not a failure; it is the correct outcome. At KTPA, the off-field environment off every runway end is marginal to poor. The pavement is your safety margin; a runway excursion removes it entirely.
Debrief — teaching points
The demonstrated crosswind component is not your personal limit.
The C172S POH lists 15 knots as the demonstrated crosswind component — the value a Cessna test pilot achieved during certification. It is not a guaranteed-safe limit for every pilot in every condition. A 180-hour private pilot with a personal best of 12 knots in this type has a personal limit of 12 knots. When the gust component reaches 22 knots, you are 10 knots above your personal limit. Recognize that number before you leave the ground, not on short final.
The gust additive is not optional.
In gusty conditions, add half the gust spread to Vref. With a steady wind of 14 and gusts to 24, the spread is 10 knots — add 5 knots. Fly 70 KIAS (65 + 5) on final instead of 65 KIAS. This preserves energy margin for the gust that arrives at 50 ft AGL. Vs0 in the C172S is 40 KIAS; Vref is 65 KIAS. That 25-knot margin sounds comfortable until a gust removes 10 of it in a second.
Set the go-around trigger before the threshold — and honor it.
The go-around decision made at 150 ft AGL is clean, safe, and leaves all options open. The go-around decision made at 10 ft AGL after a bad touchdown is dangerous, rushed, and may not succeed. Before every approach in challenging conditions, set a specific trigger: 'If I am not aligned, on speed, and in control by 100 ft AGL, I am going around.' Then honor it without negotiation. Continuation bias — 'I'll just make it work' — is the human factor in nearly every crosswind excursion.
Go-around execution in the C172S: technique matters.
ERA21LA202 is a C172S go-around that became a tail strike because of improper pitch control. The C172S go-around sequence: full power, carb heat OFF (not applicable — fuel-injected), establish a positive climb attitude (do not over-rotate), retract flaps from 30° to 20° to 10° to 0° incrementally as airspeed builds — never retract full flaps at once at low altitude. With flaps 20° on final, retract to 10° first, confirm positive climb, then to 0°. Vy is 74 KIAS; hold it in the climb. In a crosswind go-around, track the runway centerline extended — do not let the crosswind push you off.
At KTPA, the off-field environment demands you stay on the pavement.
Off the west end of Runway 28 is dense and medium development — airport infrastructure, taxiways, signage, and beyond that urban Tampa. There is no soft overrun, no open field, no forgiving surface. The same is true off Runways 19L and 19R to the south: dense development with only marginal pasture. A runway excursion at KTPA is not a 'gear in the grass' event — it is contact with hard infrastructure at rollout speed. This makes the go-around decision even more valuable: the 6,999 feet of Runway 28 pavement is your safety margin. Use it by landing in control, or preserve it by going around.
Built from the real accident record
Scenario built from NTSB CEN23LA159, ERA21LA202, ERA11LA421 (Cessna 172S), and regional precedents GAA17CA105, ERA21LA119, GAA19CA170, GAA17CA021. Real events occurred at other airports — not at KTPA.
NTSB reports: CEN23LA159 · ERA21LA202 · ERA11LA421 · GAA17CA105 · ERA21LA119 · GAA19CA170 · GAA17CA021
ACS tasks: PA.IV.B — Normal and Crosswind Approach and Landing · PA.IV.C — Soft-Field Approach and Landing · PA.IV.K — Go-Around / Rejected Landing · PA.I.H — Human Factors
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 172S scenarios · More scenarios at KTPA