The Gust You Didn't Plan For
Crosswind landing at KTPF — when to correct, when to go around, and when it's already too late
The scenario
Field: Peter O Knight Airport (KTPF), Tampa, FL — a non-towered field on Davis Islands in Hillsborough Bay, elevation 8 ft MSL. You are landing Runway 04 (true heading 37°). CTAF is active; no other traffic in the pattern.
Aircraft: Cessna 172S, N-number assigned by your school, two aboard (you and a passenger), within weight and balance limits. G1000 panel, Lycoming IO-360-L2A fuel-injected engine, fixed gear, fixed-pitch prop. Flaps 30° selected on short final.
Weather: METAR KTPF: winds 060° at 14 gusting 22 knots. That puts you in a right crosswind of roughly 12–18 knots on Runway 04, with gusts that have been irregular — sometimes the sock goes nearly straight, sometimes it swings hard. ATIS at nearby KTPA confirms the instability. Visibility 10 SM, clear skies. Density altitude near field elevation — no performance penalty from heat today.
Situation: You've been flying touch-and-goes for an hour. The first three landings were fine; the wind was steadier. This is your fourth approach. You're comfortable — maybe a little too comfortable. On short final, the G1000 groundspeed readout is fluctuating, and the airplane is drifting right of centerline despite your crab correction.
Critical geography: Runway 04 is 3,583 ft of asphalt. Off the departure end of Runway 04 (climb-out heading 37°) is dense urban development — there is no viable off-field landing option in that direction. The runway itself is your only real estate. Off the approach end, Runway 22 side, is open water (Hillsborough Bay). This field is surrounded by water and development; a runway excursion or overrun has nowhere forgiving to go.
- {'label': 'Field', 'value': 'KTPF · Peter O Knight'}
- {'label': 'Runways', 'value': '4/22 · 18/36'}
- {'label': 'Elevation', 'value': '8 ft'}
- {'label': 'Aircraft', 'value': 'C172S'}
- {'label': 'Dominant phase', 'value': 'Landing / Approach'}
The decision
On short final for Runway 04, before the scenario unfolds — which of these is already in your head? (Pick all that apply — this records your mental model, not a grade.)
What the record shows
What the NTSB files show
The accidents that built this scenario did not happen at Peter O Knight Airport. They happened at other fields — but the airplane, the conditions, and the chain of decisions are identical to what KTPF's own accident corpus shows.
In NTSB CEN23LA159 (2023), a Cessna 172S pilot encountered a tailwind on final, recognized the approach was long, and initiated a go-around. The go-around itself caused the accident: the airplane porpoised, the nose gear collapsed, and the aircraft departed the runway. The go-around decision was correct; the execution — improper pitch control at low altitude — was not.
In NTSB ERA21LA202 (2021), a Cessna 172S on short final in gusting crosswind conditions was high and slow. The pilot initiated a go-around but applied improper pitch control, causing a tail strike and a runway excursion to the left into grass. Again: the decision to go around was correct; the pitch technique was the failure.
In NTSB ERA11LA421 (2011), a C172S with an electrical failure landed long at high airspeed and ran off the end of the runway into a guardrail. The lesson: a long, fast touchdown on a runway with no forgiving overrun is not a recoverable error if braking is inadequate.
The regional precedents reinforce the same pattern. A Piper PA-46 at a nearby Florida field (GAA17CA105) lost directional control in gusting crosswinds that exceeded demonstrated crosswind capability — the pilot continued when a go-around was the answer. A Mooney M20J (ERA11CA212) landed on Runway 18 in a crosswind, veered 90 degrees left, departed the runway, struck a seawall, and came to rest nose-down in salt water. At KTPF, that seawall scenario is not hypothetical — Hillsborough Bay is immediately adjacent.
The consistent finding across all these events: the go-around decision was either made too late, or the go-around execution introduced a new hazard (tail strike, pitch oscillation, departure at sub-flying speed). The window to go around cleanly is wide on final and narrow on rollout. At KTPF, with dense urban development off Runway 04's departure end and open water off the other ends, there is no margin for a runway excursion.
Key lesson — A crosswind landing requires technique through the entire rollout — not just at touchdown. The go-around is the right answer to a developing problem on final, but it must be executed with smooth, positive pitch control. At KTPF, the off-field environment off every runway end is either open water (ditching) or dense development (no survivable forced landing) — the runway is your only real estate. Protect it by going around early, landing on speed, and holding crosswind correction until the airplane is stopped.
Debrief — teaching points
Go-around execution is a skill, not just a decision.
Two of the three C172S seed accidents (CEN23LA159, ERA21LA202) were caused not by the decision to go around — which was correct — but by improper pitch control during the go-around itself. From a crosswind approach with flaps 30°, the C172S go-around requires smooth, positive pitch to a climb attitude, then incremental flap retraction: 30° to 10° first, then 0° as climb is established. A sudden pull causes a tail strike; a hesitant pitch produces a porpoise. Practice the go-around as a precision maneuver, not an emergency escape.
Crosswind technique does not end at touchdown — it intensifies.
As the C172S decelerates on rollout, aerodynamic control authority (aileron, rudder) decreases while the crosswind's weathervaning tendency remains constant. The correct response is to progressively increase into-wind aileron deflection through the rollout — not relax it. At taxi speed, the aileron should be near full deflection into the wind. Releasing crosswind correction after touchdown is one of the most common causes of rollout excursions in light aircraft.
Add a gust factor to Vref in gusty conditions.
The C172S Vref on short final is 65 KIAS. In gusty conditions, a common technique is to add half the gust spread to Vref — with winds 14 G22, the gust spread is 8 knots, so add 4 knots: fly 69 KIAS on final. This provides a buffer against the airspeed excursion a gust can cause. Do not add more than half the gust spread; excess speed causes floating and long landings. The tradeoff is deliberate: a slightly faster approach vs. a balloon or a stall in the gust.
At KTPF, the runway is your only real estate.
Peter O Knight Airport sits on Davis Islands in Hillsborough Bay. Off Runway 22 (climb-out 217°): open water — a ditching. Off Runway 18 (173°): open water — a ditching. Off Runway 36 (353°): open water and low-density development — a ditching. Off Runway 04 (37°): dense urban development — no viable off-field option. A runway excursion or overrun at KTPF does not end in a grass field. This geography makes go-around decisions and landing technique non-negotiable, not optional.
The go-around window is wide on final and narrow on rollout.
At 200 ft AGL on final, a go-around is a routine maneuver with full energy and altitude available. At the threshold, it is still viable but requires immediate, correct execution. On rollout below approximately 40 KIAS, a go-around attempt in a crosswind with flaps 30° risks departing the runway before reaching flying speed — the power surge adds P-factor and torque to an already-directionally-unstable situation. Decide early. The NTSB cases in this scenario are dominated by pilots who delayed the go-around decision until the window had closed.
Built from the real accident record
Scenario built from NTSB cases CEN23LA159, ERA21LA202, ERA11LA421 (Cessna 172S crosswind/go-around runway excursions) and regional precedents GAA17CA105, CHI02TA149, GAA17CA021, ERA11CA212. Anonymized and localized to KTPF.
NTSB reports: CEN23LA159 · ERA21LA202 · ERA11LA421 · GAA17CA105 · CHI02TA149 · GAA17CA021 · ERA11CA212
ACS tasks: PA.IV.B — Normal and Crosswind Approach and Landing · PA.IV.E — Go-Around / Rejected Landing · PA.I.H — Human Factors · PA.IX.A — Emergency Descent / Loss of Control Awareness
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 KTPF