Drifting Right
A gusty crosswind, a late correction, and the runway that runs out of forgiveness
The scenario
Field: Brooksville–Tampa Bay Regional Airport (KBKV), Brooksville, FL — elevation 76 ft MSL. Tower is open (0700–2200 local). You're returning from a solo cross-country and are cleared to land Runway 09, a 7,001-ft concrete runway with a true heading of 090°.
Aircraft: Cessna 172S, N-number your school's, fuel-injected IO-360, G1000 glass panel, fixed gear, fixed-pitch prop. Single pilot, within weight and balance limits. Flaps 30° selected on short final.
Weather: METAR KBKV 1755Z: winds 160° at 14 gusting 22 knots. ATIS confirms the gust factor. With Runway 09 in use, that puts the wind roughly 70° off the runway heading — a significant crosswind component. The demonstrated crosswind for the C172S is 15 knots; the current gust peak of 22 knots is above that value.
Pilot: you — a Private pilot with about 120 hours total time, 15 hours in the C172S. You've done crosswind landings in training, but always with an instructor. Today is your first solo return in gusty conditions. You're tired from a 2.5-hour cross-country and eager to be done.
The setup: on short final, you're high and slightly fast — 72 KIAS where you want 65 KIAS — and the gusts are making the airplane dance. You're using a wing-low (sideslip) crosswind technique, left wing down, right rudder. The runway is long and wide. What you do in the next 30 seconds determines the outcome.
- {'label': 'Field', 'value': 'KBKV · Brooksville–Tampa Bay'}
- {'label': 'Runways', 'value': '3/21 · 9/27'}
- {'label': 'Elevation', 'value': '76 ft'}
- {'label': 'Aircraft', 'value': 'C172S'}
- {'label': 'Dominant phase', 'value': 'Landing / Cruise'}
The decision
Short final, gusty crosswind, high and fast. Before we get to the decision — which of these are already in your head? (Pick all that apply; this records your pre-scenario mental model.)
What the record shows
What the NTSB files show
The events that built this scenario happened at other airports — not at KBKV — but the airplane, the conditions, and the chain of decisions are drawn directly from real NTSB case files in the C172S fleet.
NTSB ERA21LA202 (2021): A C172S on short final in gusting crosswind conditions was high and slow. The pilot initiated a go-around but applied improper pitch control — the result was a tail strike and runway excursion to the left into grass. The probable cause: improper pitch control during a go-around in gusting crosswind conditions. The lesson: a go-around in gusty conditions demands precise pitch discipline; over-rotating causes a tail strike, under-rotating keeps you on the ground.
NTSB 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 probable cause: failure to maintain airplane control during the attempted go-around, resulting in abnormal contact with the runway and a runway excursion. The lesson: a go-around from a bounce or porpoise requires smooth, deliberate power application and pitch control — not an abrupt pull.
Regional precedent NTSB ERA21LA119 (2021): A C172R veered left off the runway during landing in gusting crosswind conditions and struck the ground with the propeller and left wing tip. Probable cause: failure to maintain directional control during landing in a gusting crosswind. The lesson: technique adjustments (reduced flaps, added airspeed) have limits; when wind conditions exceed personal minimums, the go-around must be executed before touchdown.
The consistent thread across all these events: pilots continued approaches in conditions that had already exceeded their control authority, then attempted corrections — go-arounds, braking, rudder — that were too late and too aggressive. The go-around is the right answer, and it must be made early.
Key lesson — The C172S demonstrated crosswind component is 15 knots. When the gust peak exceeds that value, the go-around decision belongs on final — not on rollout. High, fast, and drifting in a gust is three independent reasons to go around; any one of them is sufficient. A go-around executed early is routine; a go-around from a bounce or rollout excursion is an emergency.
Debrief — teaching points
The demonstrated crosswind component is a real limit, not a suggestion.
The C172S POH lists a demonstrated crosswind component of 15 knots. 'Demonstrated' means a Cessna test pilot showed it was controllable — it is not a guaranteed safe limit for all pilots in all conditions. When the gust peak of 22 knots was on the ATIS, the go-around decision was already justified before you ever turned final. Personal minimums for crosswind should be set below the demonstrated value, especially for low-time or solo pilots.
High and fast on short final is a compounding problem, not a minor deviation.
At 72 KIAS (7 knots above Vref of 65 KIAS) with flaps 30°, touchdown speed and rollout distance both increase. In a crosswind, higher touchdown speed means more kinetic energy to manage while simultaneously fighting drift — the two problems multiply each other. A stabilized approach in a C172S means on speed (65 KIAS on short final), on path, and on centerline. Any single deviation is a go-around candidate; all three together is a mandatory go-around.
Go-around pitch discipline: smooth power, controlled attitude, no over-rotation.
The C172S go-around procedure: full power smoothly (not abruptly), simultaneously right rudder to counteract left-turning tendency, establish a positive climb attitude without over-rotating, retract flaps from 30° to 20° immediately, then retract fully as a positive climb rate is confirmed. Vx is 62 KIAS until obstacles are clear; Vy is 74 KIAS for the climb. Over-rotating causes a tail strike (see ERA21LA202); under-rotating keeps you on the ground. The go-around from a bounce or porpoise requires the same smooth inputs — not a pull.
Directional control on rollout: rudder first, brake second.
In a crosswind rollout, the primary directional control tool is the rudder — not the brakes. Braking asymmetrically at high speed in a crosswind can induce a yaw that the rudder cannot overcome, and hard braking with a main wheel off the pavement loads the nose gear asymmetrically. As speed decreases below about 40 KIAS, aileron into the wind (upwind aileron up) becomes increasingly important to keep the upwind wing from lifting. If the airplane is departing the pavement, the goal is to keep the nose straight and the speed as low as possible — a slow, straight excursion into grass is survivable; a high-speed, yawing excursion is not.
Fatigue and get-home-itis are crosswind multipliers.
A 2.5-hour solo cross-country followed by a gusty crosswind approach is exactly the scenario where continuation bias kills. Fatigue degrades the speed and quality of decisions — the pilot who is tired is the pilot most likely to continue a bad approach rather than go around, because the go-around means more work and more time. Recognize this bias explicitly: when you are tired and eager to be done, apply more conservative standards, not fewer. The runway at KBKV will be there for the second approach.
Built from the real accident record
Composite scenario built from NTSB crosswind landing loss-of-control events in Cessna 172S and comparable single-engine aircraft. Real events occurred at other airports; see outcome_reveal.
NTSB reports: CEN23LA159 · ERA21LA202 · ERA11LA421 · GAA17CA105 · ERA21LA119 · GAA19CA170 · ERA10CA448
ACS tasks: PA.IV.B — Normal and Crosswind Approach and Landing · PA.IV.N — Go-Around / Rejected Landing · PA.I.H — Human Factors · PA.II.A — Preflight Assessment
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 KBKV