FlightEdge
Sample scenario-based training
SAMPLE SBTLanding

The Gust You Didn't Plan For

Crosswind, a deteriorating rollout, and the go-around that can hurt you

Cessna 172S · St. Petersburg Clearwater International Airport (KPIE) · Private · Landing

The scenario

Field: St. Petersburg–Clearwater International Airport (KPIE), Pinellas Park, FL — elevation 11 ft MSL. ATCT is active. You are landing Runway 04, magnetic heading 040°.

Aircraft: Cessna 172S, solo, within weight and balance limits. Fuel selector on BOTH. G1000 glass panel, all systems normal. Fixed gear, fixed-pitch prop, fuel-injected Lycoming IO-360 — no carburetor heat.

Weather: METAR at time of arrival — winds 070° at 14 knots, gusting to 24. That puts a right crosswind on Runway 04 with a gust spread of 10 knots. The C172S demonstrated crosswind component is 15 knots; the steady-state component is within limits, but the gusts push you right to the edge. Visibility 10 SM, clear below 12,000 ft. KPIE sits inside Tampa Class B airspace — the Class B floor here is 1,200 ft MSL, and you are operating under a Class D ceiling of 1,600 ft MSL. You have clearance to land.

Off-field reality: The Runway 04 climb-out corridor (040°) is mostly open water — Tampa Bay. An engine failure or runway excursion off the departure end puts you in a water environment. There are no suitable off-airport landing fields in that direction. Off the right side of the runway during rollout is developed ramp and taxiway infrastructure.

Pilot: You — a Private pilot, 95 hours total time, 12 hours in the C172S. You've done crosswind landings in training but this gust spread is near the top of your personal experience envelope. ATIS says the tower is offering Runway 18/36 as an alternative, but you've already been sequenced for Runway 04 and you're on a 3-mile final.

The decision

On a 3-mile final for Runway 04 at KPIE, gusts to 24 knots from the right — what's already in your head? (Pick all that apply — no wrong answers; this records your pre-landing mental model.)

What the record shows

What the NTSB files show

The accidents behind this scenario did not happen at KPIE — they occurred at airports in other states. But the conditions that produced them are present at KPIE on any afternoon when Tampa Bay sea-breeze winds push across Runway 04 with a 10-knot gust spread.

NTSB ERA21LA202 (2021, Cessna 172S): A C172S on short final in gusting crosswind conditions was high and slow. The pilot initiated a go-around, but applied aggressive back pressure as the power came in. The tail struck the runway, the airplane porpoised, and it departed the runway to the left into grass. The NTSB found the probable cause was 'the pilot's improper pitch control during a go-around in gusting crosswind conditions.' The go-around was the right call — the pitch technique was the failure.

NTSB CEN23LA159 (2023, Cessna 172S): A C172S with a tailwind on final attempted a go-around when the landing appeared long. The aircraft porpoised, the nose landing gear collapsed, and the aircraft departed the runway. The NTSB found the cause was 'the pilot's failure to maintain airplane control during an attempted go-around resulting in abnormal contact with the runway pavement and a runway excursion.'

The regional precedents reinforce the pattern: GAA17CA105 (Piper PA-46, Florida) — loss of directional control in gusting crosswind during landing rollout, exceeding demonstrated crosswind capability. ERA17CA149 (T-6G, Florida) — right wingtip contacted the runway during a go-around in gusting crosswind; the aircraft pivoted and nosed over. In every case, the accident was survivable — but preventable much earlier in the decision chain.

The consistent finding: the demonstrated crosswind component is a real limit, not a suggestion. Gust spreads of 10 knots or more near that limit create conditions where even a correctly initiated go-around can become an accident if pitch control is imprecise. The safest decision is made before you are committed — requesting the into-wind runway, or establishing a firm go-around gate and honoring it.

Key lesson — In gusting crosswind conditions near the demonstrated limit, the go-around is the right answer to a deteriorating approach — but the go-around itself requires disciplined pitch control. An aggressive pull with flaps extended and airspeed marginal produces a tail strike, not a climb. Smooth power, right rudder, controlled pitch attitude. And the best decision is made at 3 miles, not 3 feet.

Debrief — teaching points

The demonstrated crosswind component is a real limit — gust spread matters.

The C172S demonstrated crosswind component is 15 knots. That number applies to the steady-state component; gusts add instantaneous loads that can exceed it. A gust spread of 10 knots (14 gusting 24) means the crosswind component cycles between approximately 13 and 22 knots on Runway 04 with a 070° wind. When the gust spread pushes you past the demonstrated limit, the correct response is to use the into-wind runway — at KPIE, Runway 36 (351°, 9,730 ft) is almost always available and nearly eliminates the crosswind in these conditions. Request it before you are established on final.

Add half the gust spread to your approach speed — and know why.

In gusty conditions, the standard technique is to add half the gust spread to Vref. With a gust spread of 10 knots, that means targeting approximately 70 KIAS on final (Vref 65 + 5). This provides a speed buffer against the sudden airspeed loss when a gust drops off. Do not add more than half the gust spread — excess speed increases landing distance and rollout energy. With Vs0 at 40 KIAS and Vref at 65 KIAS, the margin is not as large as it feels.

A go-around in gusts requires controlled pitch — not an aggressive pull.

ERA21LA202 is the cautionary case: the go-around was the right decision, but the pilot pulled aggressively as power came in. With flaps 30° and airspeed marginal, the nose pitched steeply, airspeed bled toward Vs0 (40 KIAS), and the tail struck the runway. In a go-around, the correct pitch attitude is the attitude that maintains flying speed — roughly 10° nose-up, not maximum climb angle. Smooth, progressive power application; right rudder for coordination; controlled pitch. Flaps from 30° to 20° once a positive climb is established, then 10°, then up.

Once directional control is lost on rollout above ~40 knots, consider flying away.

When a gust lifts the upwind wing and pushes the airplane off centerline during rollout at 60 knots, the airplane is still above Vr (55 KIAS). Adding full power and flying off the runway is often safer than attempting to brake and steer back to centerline — differential braking at speed imposes lateral loads the nose gear is not designed for, and the off-field environment off the right side of Runway 04 is developed ramp infrastructure. The go-around from the ground roll is aggressive but survivable; a nose gear collapse into the taxiway environment is not trivially so.

The off-field environment at KPIE demands a different risk calculus.

Runway 04's departure end points at 040° — directly toward Tampa Bay. An engine failure or runway excursion off the departure end of Runway 04 is a ditching, not a field landing. There are no suitable off-airport landing areas in that direction. This means the cost of a runway excursion off the far end of Runway 04 is higher than at a field surrounded by open terrain. Runway 36's departure end (351°) also faces open water to the north. These environmental facts should inform your runway selection and your go-around decision altitude — at KPIE, there is no 'good' off-airport option in most directions.

Built from the real accident record

Scenario built from NTSB cases CEN23LA159, ERA21LA202, ERA11LA421, GAA17CA105, ERA17CA149, GAA16CA149, and CHI02TA149 — crosswind landing loss-of-control events in Cessna 172S and comparable single-engine aircraft. Events occurred at airports other than KPIE. Anonymized and localized for training.

NTSB reports: CEN23LA159 · ERA21LA202 · ERA11LA421 · GAA17CA105 · ERA17CA149 · GAA16CA149 · CHI02TA149

ACS tasks: PA.IV.B — Normal and Crosswind Approaches and Landings · PA.IV.N — Go-Around / Rejected Landing · PA.I.H — Human Factors · PA.VII.B — Power-Off Stalls

Relevant FARs: §91.3 · §91.13

Run this scenario yourself

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