Crosswind Surprise on Runway 09
Gusting wind, directional control, and the decision to go around — or push through
The scenario
Departing Brooksville–Tampa Bay Regional Airport (KBKV), Brooksville, FL — Runway 09, a 7,001-foot concrete runway aligned 090° magnetic. Field elevation 76 ft MSL. You are a Private pilot with roughly 180 hours total, current and proficient. This is a local VFR flight — a 45-minute round trip to a nearby field and back.
ATIS reports: winds 120° at 12 knots, gusting to 18. Runway 09 is aligned 090°; a 120° wind is a right crosswind of approximately 10 knots steady, gusting to 16. The C172S has a demonstrated crosswind capability of 12 knots. You are at the edge of limits, and the gusts are pushing past it.
You are on downwind for Runway 09, 800 ft AGL, 2 nm from the field. The tower has cleared you to land. You can see the runway ahead — it looks stable from altitude. Your plan: descend on a normal left downwind, turn base, establish on short final at 65 KIAS (Vref), add full flaps, and land. The wind feels manageable from the air.
Aircraft: Cessna 172S, solo, 1,800 lb (within limits), full fuel. Glass panel (G1000), fuel-injected Lycoming IO-360-L2A, fixed gear, fixed-pitch prop. The airplane is airworthy; nothing was written up. You have 180 hours total time, 40 hours in the C172S, and 8 landings in crosswind conditions (all under 10 knots steady). This will be your first landing in gusting crosswind near the demonstrated limit.
The off-field environment around Runway 09 is good: mostly open developed areas (parks, large lots), pasture/hay, and medium development. If you lose directional control on the runway, you will likely depart into grass or a developed area — not water, not mountains. But a runway excursion at 60+ knots is still a loss-of-control accident.
- {'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
Before we enter the decision tree — what do you already know about crosswind landings in the C172S and loss of directional control? (Pick all that apply.)
What the record shows
What the NTSB files show
NTSB CEN23LA175 (2023): A Cessna 172S student pilot on her third solo flight lost directional control during takeoff in gusting wind conditions. The aircraft drifted left off the runway and struck a runway approach light, substantially damaging the left wing. The probable cause was the student pilot's failure to maintain pitch and directional control during the takeoff roll, with contributing factors including the student pilot's delay in relinquishing control and the instructor's delayed reaction.
NTSB CEN23LA122 (2023): A Cessna 172S on takeoff from a snow and ice-covered runway with a right crosswind slid left during the takeoff roll. The pilot aborted but the airplane continued pulling left and impacted terrain. The probable cause was the pilot's failure to maintain directional control during the takeoff roll, with contributing factors including runway condition and crosswind.
NTSB CEN23LA102 (2023): A Cessna 172S student pilot lost directional control during the takeoff roll of a touch-and-go landing, veering left into a snowbank. The probable cause was the pilot's failure to maintain directional control during the takeoff roll.
NTSB ERA21LA282 (2021): A Cessna 172S bounced during landing with a right crosswind correction, yawed left, and departed the runway into grass after the pilot could not realign with the runway. The probable cause was the pilot's loss of aircraft control following the bounced landing.
NTSB GAA17CA105 (2016, Piper PA-46): A pilot experienced loss of directional control during landing rollout in gusting crosswind conditions that exceeded the aircraft's demonstrated crosswind capability. The pilot did not recognize the limit and did not commit to a go-around early.
NTSB ERA21LA119 (2021, Cessna 172R): A pilot veered left off the runway during landing in gusting crosswind conditions and struck the ground with the propeller and left wing tip. The probable cause was the pilot's failure to maintain directional control during landing in a gusting crosswind. The pilot did not recognize that technique adjustments (reduced flaps, extra airspeed) have limits.
The consistent thread across all these events: loss of directional control in crosswind conditions, often exacerbated by gusts that exceed the demonstrated capability of the aircraft. The pilots did not recognize the limit, did not commit to a go-around early, or did not apply corrective rudder immediately when a skid developed. At Brooksville–Tampa Bay Regional Airport, the off-field environment around Runway 09 is good (open developed areas, pasture, medium development) — but a runway excursion at 60+ knots is still a loss-of-control accident, and the airplane can be substantially damaged.
The real accidents cited above occurred at other airports and in other aircraft — NOT at KBKV. This field has its own accident history (hard landings, forced landings, runway excursions), but these specific NTSB events happened elsewhere. The scenario is localized to KBKV to make the crosswind decision real and consequential for you as a student here.
Key lesson — The C172S has a demonstrated crosswind capability of 12 knots. When gusts exceed that limit, the airplane is operating outside its tested envelope. Recognize the limit, know your personal minimums, and commit to a go-around or diversion early — before the approach becomes unstable. If a skid develops on the runway, apply corrective rudder immediately to stop the yaw; braking alone will not recover directional control. A go-around is not a failure; it is the correct decision when conditions exceed capability.
Debrief — teaching points
Demonstrated crosswind capability is not a hard limit — it is a tested maximum.
The C172S has a demonstrated crosswind capability of 12 knots. This means the manufacturer tested the airplane in 12-knot crosswind conditions and found it controllable. It does NOT mean the airplane will be uncontrollable in 13 knots; it means the manufacturer did not test beyond 12 knots. When gusts exceed the demonstrated capability (e.g., 120° at 12 gusting to 18), you are operating outside the tested envelope. Your personal minimums should be lower than the demonstrated capability — perhaps 10 knots steady, no gusts beyond 12. Know your limit and respect it.
Crosswind technique reduces but does not eliminate risk when wind exceeds demonstrated limits.
Crabbing on approach and wing-low on touchdown are correct crosswind techniques, and they work well within the demonstrated capability. But technique has limits. When gusts exceed the demonstrated capability, technique alone cannot guarantee control. A pilot with perfect crosswind technique can still lose directional control if the wind is too strong. Recognize when the wind is beyond technique and commit to a go-around or diversion.
A go-around is the correct decision when the approach is unstable or conditions exceed personal minimums.
A go-around is not a failure; it is the correct decision when the approach is unstable, when the wind is gusting, or when conditions exceed your personal minimums. The NTSB precedents show that pilots who pushed through unstable approaches in crosswind conditions lost directional control. Pilots who went around early did not. If you are correcting for drift multiple times on short final, if the wind is gusting and the approach is not stable, go around. The runway will be there for another attempt, or you can divert to a better airport.
If a skid develops on the runway, apply corrective rudder immediately to stop the yaw.
If the airplane begins to yaw left on the runway, apply right rudder to stop the yaw. Do not rely on braking alone to recover directional control — braking will slow the airplane but will not stop the yaw. Apply rudder first to align the nose with the runway, then apply brakes to decelerate. If you do not apply corrective rudder, the skid will continue and the airplane will depart the runway into the off-field environment.
Recognize when switching runways is not solving the problem.
If you request a different runway because of crosswind, but the new runway has a crosswind from the opposite direction of similar magnitude, you have not solved the crosswind problem — you have only changed which wing is being lifted. If the wind is the problem, switching runways may not help. Recognize when the wind is the issue and commit to a diversion to a nearby airport with more favorable wind.
At KBKV, the off-field environment around Runway 09 is good, but a runway excursion is still a loss-of-control accident.
The off-field environment around Runway 09 at KBKV is mostly open developed areas (parks, large lots), pasture/hay, and medium development — not water, not mountains. If you lose directional control and depart the runway, you will likely land in grass or a developed area. But a runway excursion at 60+ knots can still substantially damage the airplane and injure the occupants. Avoid the excursion by recognizing the crosswind limit and committing to a go-around or diversion early.
Built from the real accident record
Scenario built from NTSB CEN23LA175, CEN23LA122, CEN23LA102 (C172S loss of directional control on takeoff/landing), ERA21LA282 (C172S bounced landing / loss of control), and regional crosswind precedents GAA17CA105, ERA21LA119, GAA19CA170. Localized to Brooksville–Tampa Bay Regional Airport (KBKV).
NTSB reports: CEN23LA175 · CEN23LA122 · CEN23LA102 · ERA21LA282 · GAA17CA105 · ERA21LA119 · GAA19CA170
ACS tasks: PA.I.F — Weather Information · PA.II.A — Preflight Assessment · PA.III.A — Takeoff and Climb · PA.III.B — Approach and Landing · PA.I.H — Human Factors · PA.IX.C — Emergency Approach and Landing
Relevant FARs: §91.3 · §91.13 · §91.209
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