FlightEdge
Sample scenario-based training
SAMPLE SBTLanding

Drifting Right

A gusty crosswind, a late correction, and the runway edge that ends it

Cessna 172S · Zephyrhills Municipal Airport (KZPH) · Private · Landing

The scenario

Field: Zephyrhills Municipal Airport (KZPH), Zephyrhills, FL — elevation 90 ft MSL. You are returning from a local flight and plan to land Runway 01, the 5,072-ft north-south strip. KZPH is non-towered Class G; CTAF is active with one other aircraft in the pattern ahead of you.

Aircraft: Cessna 172S with a G1000 panel, fixed gear, fixed-pitch prop, and a Lycoming IO-360 fuel-injected engine. Full fuel, solo, well within weight and balance. Everything is normal — no squawks.

Weather: AWOS at KZPH is reporting winds 060° at 14 knots, gusting to 22. That puts the wind roughly 60° off the Runway 01 heading (360°), producing a right-to-left crosswind component of approximately 12 knots steady, gusting near 19. The C172S POH lists a demonstrated crosswind component of 15 knots — you are at or above it on the gusts.

Pilot: You — a Private pilot with about 180 hours, mostly in this airplane. You have flown in crosswinds before, but your personal experience in gusty conditions above 15 knots is limited. The previous aircraft in the pattern reported 'a little squirrelly on short final but manageable.' You are already on a 3-mile final.

Off-field reality: Off the north end of Runway 01 (your climb-out direction if you go around) the terrain is good — pasture, hay fields, and open developed land. Off the south end (Runway 19 direction) the environment is more marginal — open developed lots and evergreen forest. That context matters if you ever need to put it down off-airport.

The decision

On a 3-mile final for Runway 01 with a gusty right crosswind — before you touch down, which of these are in your head? (Pick all that apply — no wrong answers; this records your pre-landing awareness.)

What the record shows

What the NTSB files show

Crosswind landing loss of directional control is one of the most common accident types in the Cessna 172 fleet — and in the local accident record at fields like KZPH. The events are remarkably consistent: a crosswind at or above the demonstrated limit, a pilot who continued past the point where a go-around was the obvious answer, and a rollout where directional control inputs were too late, too small, or abandoned entirely.

NTSB ERA21LA119 (a Cessna 172R at a Florida field) is a near-exact parallel: gusty crosswind, veer left during rollout, propeller and wingtip strike. The probable cause was 'the pilot's failure to maintain directional control during landing in a gusting crosswind.' ERA10CA448 (a Cessna 182 on Runway 01 at a similar field) shows the same mechanism — crosswind pushed the aircraft off the runway to the left during rollout, nose-over.

ERA21LA202 adds a critical nuance: a C172S pilot who initiated a go-around in gusty crosswind conditions but used improper pitch control, resulting in a tail strike and runway excursion to the left. The go-around itself is not automatically safe — it must be executed correctly, with proper pitch attitude and a deliberate flap retraction sequence.

The demonstrated crosswind component in the C172S POH (15 knots) is exactly that — demonstrated, not a guaranteed limit. Gusts above that value in a pilot with limited gusty-crosswind experience are a legitimate reason to use a different runway, divert, or wait. KZPH's Runway 05 (043° true) is almost always a better option when the wind is from the northeast.

NOTE: The specific accidents cited above occurred at other airports, not at KZPH. The scenario is localized to KZPH for training purposes.

Key lesson — Crosswind technique is continuous — from final approach through the last foot of rollout. The go-around window opens at 200 ft AGL and closes at the runway edge; every second of hesitation narrows it. When the crosswind component is at or above the demonstrated limit and your gusty-crosswind experience is limited, the correct answer is often a different runway, not a better flare.

Debrief — teaching points

The demonstrated crosswind component is a capability ceiling, not a target.

The C172S POH lists 15 knots as the demonstrated crosswind component. 'Demonstrated' means a Cessna test pilot showed it was possible under controlled conditions — it is not a guarantee that any pilot in any conditions can handle it. When gusts push the crosswind component to 19 knots and your personal gusty-crosswind experience is limited, that number is telling you something. At KZPH, Runway 05 (043° true) nearly aligns with a 060° wind — use it.

Add half the gust spread to Vref — and know why.

With winds 14G22, the gust spread is 8 knots; half is 4 knots. Fly Vref (65 KIAS) plus 4 = 69 KIAS on final. The additive ensures that when the gust drops out at the flare, you don't fall below approach speed. Do not carry the full gust additive all the way to the flare — bleed it off progressively so you don't float. The C172S Vs0 is 40 KIAS; Vref of 65 gives you 25 knots of margin above stall in landing configuration.

Crosswind technique does not end at touchdown.

The most common failure point in crosswind excursions is not the flare — it is the rollout. As the airplane decelerates, aerodynamic control effectiveness decreases and the crosswind's weathervaning tendency increases. Upwind aileron (into the wind) and downwind rudder must be actively maintained and progressively increased through the entire rollout until taxi speed. Relaxing inputs at touchdown is the trigger for the departure from pavement.

The go-around window: know when it opens and when it closes.

The go-around decision belongs at 200 ft AGL if the approach is not stabilized — not at 50 ft, not at the flare, not during the rollout. That said, a go-around is available at any point before the airplane departs the pavement, provided it is executed correctly: full power, arrest the descent, then retract flaps from 30° to 20° once a positive climb rate is confirmed, then 10°, then up. ERA21LA202 is the warning: a go-around with improper pitch control in a gusty crosswind produced a tail strike and excursion. The go-around must be flown, not just initiated.

Continuation bias: the pressure to land is not a checklist item.

In every one of the reference accidents, the pilot had at least one clear opportunity to go around before the excursion and did not take it. The pressure to complete the landing — fuel is fine, the runway is right there, the previous pilot said it was manageable — is a human factors trap, not an aeronautical argument. Under §91.3, the PIC is the final authority. That authority includes the authority to go around, use a different runway, or divert. Use it.

Built from the real accident record

Scenario built from NTSB CEN23LA159, ERA21LA202, ERA11LA421, GAA17CA105, ERA21LA119, GAA19CA170, and ERA10CA448 — crosswind landing loss-of-control events in Cessna 172-class aircraft and comparable singles. Anonymized and localized to KZPH.

NTSB reports: CEN23LA159 · ERA21LA202 · ERA11LA421 · GAA17CA105 · ERA21LA119 · GAA19CA170 · ERA10CA448

ACS tasks: PA.IV.B — Normal and Crosswind Approach and Landing · PA.IV.K — Go-Around / Rejected Landing · PA.I.H — Human Factors · PA.II.A — Pilot Self-Assessment

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 KZPH