Crosswind Surprise on Runway 04
A gusting crosswind, a bounced landing, and the razor-thin margin between recovery and a groundloop — directional control is everything
The scenario
Departing St. Petersburg Clearwater International Airport (KPIE), Pinellas Park, FL — Runway 04, a 6,000-foot asphalt runway with a true heading of 040°. Field elevation 11 ft MSL. You are on a local VFR flight, solo, within limits.
It is mid-afternoon; the surface wind is reported as 080° at 12 knots with gusts to 18 knots. Runway 04 is the active runway — a left crosswind of roughly 10–12 knots steady, with gusts pushing 15–18 knots. The tower is open and active (KPIE operates 0600–2300 local). Visibility is 10 SM, scattered clouds at 3,500 ft. A typical Florida afternoon — warm, gusty, and workable if you stay sharp.
You have completed a touch-and-go landing on Runway 04 and are climbing out. The takeoff roll was firm but manageable; you held the centerline with crosswind correction. At 400 ft AGL, you level off briefly to configure, then request a downwind for another touch-and-go. Tower clears you to make another approach.
Aircraft: Cessna 172S, solo, full fuel, within limits. Glass panel (G1000), fuel-injected Lycoming IO-360-L2A, fixed gear, fixed-pitch prop. Everything is normal.
Pilot: you — a Private pilot, roughly 250 hours total, current, with about 40 hours in the C172S. You have crosswind experience but not in gusts this strong. You are comfortable with the airplane and the field. This is a routine practice session.
- {'label': 'Field', 'value': 'KPIE · St. Petersburg Clearwater'}
- {'label': 'Runways', 'value': '4/22 · 18/36'}
- {'label': 'Elevation', 'value': '11 ft'}
- {'label': 'Aircraft', 'value': 'C172S'}
- {'label': 'Dominant phase', 'value': 'Takeoff / Landing'}
The decision
Before we get into the decision tree — what do you already know about crosswind landings and directional control in the C172S? (Pick all that apply; this records your baseline.)
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 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 LAX89LA222 (1989, FATAL): A Grumman AA-1C aborted an approach and entered a low unstable pattern in gusting crosswind conditions, stalled on final approach, and impacted the ocean short of the runway. The probable cause was the pilot's failure to maintain sufficient airspeed to prevent a stall at an altitude too low for recovery. This fatal accident occurred at a coastal airport in California — NOT at KPIE — but the mechanism (unstable approach in crosswind, low altitude, stall) is directly relevant to your decision-making here.
The consistent thread across all these events: loss of directional control on the ground in crosswind conditions is a cascade failure. It begins with an unstable approach or a hard landing. The pilot then tries to salvage the landing by forcing it down or by continuing to land after a bounce. Once directional control is lost — the airplane is yawed, the wing is low, the pilot is no longer aligned with the runway — recovery on the ground is marginal at best. A groundloop or nose-over is the likely outcome.
The decision point is always the same: on short final, if a gust balloons you up or if the approach becomes unstable, GO AROUND immediately. After a bounce, if the airplane is not aligned and stable, GO AROUND immediately. Do not try to salvage the landing. The runway will still be there for the next approach. A groundloop will not.
Key lesson — Crosswind landings in a C172S demand continuous directional control and immediate recognition of instability. The demonstrated crosswind component is roughly 12 knots; gusts beyond that are outside the envelope. If the approach becomes unstable — a gust balloons you up, the airplane is yawed, the wing is low — GO AROUND immediately. Do not force the landing. After a bounce, if the airplane is not aligned and stable, GO AROUND immediately. Once directional control is lost on the ground, a groundloop is the likely outcome. Prevention is the only option.
Debrief — teaching points
Crosswind limits are real — the C172S has a demonstrated crosswind component of roughly 12 knots.
The C172S POH lists a demonstrated crosswind component of approximately 12 knots. Gusts beyond that are outside the demonstrated envelope. A surface wind of 080° at 12 knots gusting to 18 knots on Runway 04 (heading 040°) is a left crosswind of roughly 10–12 knots steady, with gusts to 15–18 knots. The gusts are at or beyond the demonstrated limit. This is a marginal situation that demands heightened awareness and a low threshold for diverting to a more favorable runway.
An unstable approach on short final is a go-around, not a landing.
If you are on short final and a gust balloons you up, or if the airplane is not aligned with the runway, or if the descent rate is unstable — GO AROUND immediately. Add full power, raise the flaps to 10° (not full retract — you are low), and climb out. Advise the tower. The runway will still be there for the next approach. Trying to salvage an unstable approach by pushing forward and forcing the landing is the beginning of a cascade failure that ends in a groundloop or nose-over.
A bounced landing is a critical moment — immediate go-around is the correct recovery.
A bounce after a hard landing means the landing is unstable. The airplane is low, slow, and potentially yawed. The correct response is to add full power, raise the flaps to 10°, and go around immediately. Do not try to land again. Do not try to hold altitude and 'stabilize' the airplane. Go around. The second approach will be more stable and you will land safely. A series of bounces is a cascade failure that ends in loss of directional control.
Directional control on the ground depends on rudder authority and nosewheel steering — crosswind gusts can overwhelm both.
The C172S's directional control on the ground depends on the rudder and nosewheel steering. In a crosswind, the rudder must counteract the wind's tendency to push the tail downwind. If the airplane is slow, the rudder is less effective. If the airplane is yawed, the nosewheel steering is less effective. A gust can overwhelm both. Once the airplane is yawed and the wing is low, recovery on the ground is marginal. Prevention — recognizing instability early and going around — is the only reliable option.
Diverting to a longer runway with a more favorable wind is not a failure — it is airmanship.
If the crosswind on the active runway is marginal or beyond the demonstrated limit, request a divert to a longer runway with a more favorable wind component. KPIE has four runways: 04/22 (6,000 ft) and 18/36 (9,730 ft). If the wind is a strong crosswind on Runway 04, it will be a headwind component on Runway 18. The longer runway and headwind component make the landing much more manageable. Diverting is not a failure; it is the correct decision.
Built from the real accident record
Scenario built from NTSB CEN23LA175, CEN23LA122, CEN23LA102 (C172S loss-of-control-ground events), ERA21LA282 (C172S bounced landing / directional control loss), and regional precedents LAX89LA222, ERA10CA300, ATL83LA356. Localized to KPIE.
NTSB reports: CEN23LA175 · CEN23LA122 · CEN23LA102 · ERA21LA282 · LAX89LA222 · ERA10CA300 · ATL83LA356
ACS tasks: PA.I.F — Weather Information · PA.II.D — Takeoff and Climb · PA.III.D — Approach and Landing · PA.III.E — Go-Around / Rejected Landing · PA.I.H — Human Factors
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 KPIE