Pushed Off the Numbers
A gusty crosswind, a late go-around decision, and the runway excursion that follows
The scenario
Field: Venice Municipal Airport (KVNC), Venice, FL — elevation 18 ft MSL. You are returning from a local flight and plan to land Runway 13 (true heading 135°), the longer of the two runways at 5,640 ft. KVNC is non-towered Class G airspace; you are self-announcing on CTAF.
Aircraft: Cessna 172S, G1000 panel, fuel-injected IO-360-L2A, fixed gear, fixed-pitch prop. Solo, fuel full, well within weight and balance. Flaps 30° selected for landing.
Weather: ASOS is reporting winds 070° at 14 knots, gusting 22. That puts the crosswind component on Runway 13 at roughly 13 knots steady, gusting to approximately 20 — near the C172S's 15-knot demonstrated crosswind value and well into gust territory. Runway 04 would give a more favorable angle but you've already set up for 13 and traffic is light.
Pilot: you — a Private pilot with about 180 hours, current, comfortable at KVNC. You've landed in crosswinds before, but today the gusts are making the approach feel different from the moment you turned final.
The scenario begins on short final, Runway 13, approximately 200 ft AGL.
- {'label': 'Field', 'value': 'KVNC · Venice'}
- {'label': 'Runways', 'value': '4/22 · 13/31'}
- {'label': 'Elevation', 'value': '18 ft'}
- {'label': 'Aircraft', 'value': 'C172S'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
On short final for Runway 13, before you cross the threshold — which of these is actually in your head? (Pick all that apply; this records your starting mental model.)
What the record shows
What the NTSB files show
Crosswind-induced runway excursions in the Cessna 172 family are among the most consistent accident patterns in the NTSB database — and the events that seed this scenario are representative. In ERA21LA119 (a C172R in gusting crosswind conditions), the airplane veered left off the runway and struck the ground with the propeller and left wingtip. In ERA10CA448 (a C182 at a similar coastal Florida field), a direct crosswind pushed the airplane off the runway during rollout. In GAA17CA105 (a Piper PA-46 in gusting crosswind), the pilot lost directional control during an aborted landing rollout. These events occurred at other airports — not at KVNC — but the mechanism is identical to what KVNC's own accident corpus shows: LOSS_OF_CONTROL_GROUND is one of the field's top five accident categories.
The C172S-specific seeds add a second layer: CEN23LA159 shows a go-around attempt after a long landing that resulted in porpoising and nose gear collapse; ERA21LA202 shows improper pitch control during a go-around in gusting crosswind that produced a tail strike and excursion. Both events share a common thread — the go-around was initiated too late, from an already-compromised position, and the technique under gust load was imprecise.
The consistent NTSB finding: the accident was not caused by the crosswind. It was caused by continuation of an approach or landing that had already exceeded the pilot's effective control margin, without a committed decision point. Pilots who set and honor a go-around gate on final — 'not stabilized by 100 ft AGL means go around, no exceptions' — do not appear in these reports.
At KVNC specifically, Runway 04 (true heading 45°) would have offered a significantly more favorable crosswind angle for a 070° wind. Runway selection before entering the pattern is the first and cheapest intervention.
Key lesson — A crosswind landing excursion is almost never caused by the wind alone — it is caused by continuing past the point where a go-around was the correct answer. Set the go-around gate on final approach, honor it without negotiation, and treat runway selection as the first line of defense.
Debrief — teaching points
Calculate the crosswind component before you enter the pattern.
The C172S POH lists a demonstrated crosswind component of 15 knots — not a certified limit, but a real-world ceiling for most pilots. With KVNC ASOS reporting 070° at 14 gusting 22, the crosswind component on Runway 13 (135°) is approximately 13 knots steady and 20 knots on gusts — the latter exceeds the demonstrated value. The time to evaluate this is during preflight and again on the ATIS/ASOS call, not on short final. Runway 04 (true heading 45°) would have reduced the crosswind component substantially for a 070° wind. Runway selection is the first and cheapest crosswind intervention.
Add a gust factor to Vref — and hold it all the way to the flare.
In gusty conditions, the standard technique is to add half the gust spread to Vref. With a 14G22 wind, the gust spread is 8 knots; half is 4 knots. That puts your target approach speed at approximately 69 KIAS rather than 65 KIAS. The extra energy provides control authority through gust-induced airspeed fluctuations and prevents the airspeed from dropping below Vs0 (40 KIAS) if a gust suddenly eases on short final. Do not bleed this speed off early — carry it to the flare.
Set a go-around gate and honor it without negotiation.
A stabilized approach gate is only useful if it is non-negotiable. The standard gate for a non-precision approach is 500 ft AGL; for a visual approach in gusty crosswind conditions, many instructors set it at 100 ft AGL — if you are not on centerline, on speed, and aligned with the runway heading by 100 ft AGL, you go around. The events in this scenario's seed files share a common thread: the pilot continued past the point where a go-around was clearly the right answer. Decide the gate before you turn final.
A go-around in a gust requires immediate rudder — not just power.
The C172S go-around procedure is: full throttle, right rudder (the IO-360 produces significant left-turning tendency at full power), establish climb attitude, retract flaps from 30° to 10° once positive rate is confirmed, then clean up above 65 KIAS. In a gusty crosswind, the rudder demand at full power is higher than in calm conditions — the crosswind yaw and P-factor combine. ERA21LA202 shows what happens when pitch control is imprecise during a go-around in gusts: tail strike, excursion. Establish the climb attitude first; do not let the nose pitch up steeply before airspeed is established.
Hold crosswind aileron through the entire rollout — do not relax at low speed.
The most common rollout error in a crosswind is relaxing the upwind aileron as speed decreases, reasoning that 'the controls don't do much at low speed anyway.' In fact, the aileron must be held — and progressively increased — as speed decreases, because the wing is more susceptible to gust-induced lift at lower speeds relative to control authority. Full upwind aileron at taxi speed is correct technique. The moment you relax the aileron in a gust, the upwind wing rises, the downwind main unloads, and directional control degrades. Hold it until you clear the runway.
Built from the real accident record
Scenario built from NTSB CEN23LA159, ERA21LA202, ERA21LA119, ERA10CA448, and regional crosswind-excursion precedents. Anonymized and localized to KVNC.
NTSB reports: CEN23LA159 · ERA21LA202 · ERA11LA421 · GAA17CA105 · ERA21LA119 · GAA19CA170 · ERA10CA448
ACS tasks: PA.IV.A — Normal and Crosswind Approach and Landing · PA.IV.B — Soft-Field Approach and Landing · PA.IV.N — 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 KVNC