Gusts on Short Final
Crosswind landing in deteriorating conditions — when to commit to a go-around and how to recover directional control
The scenario
Departing Tampa Executive Airport (KVDF), Tampa, FL — Runway 23, landing on Runway 23. Elevation 22 ft MSL. This is a non-towered field; you are operating on CTAF (122.8) with self-announced traffic advisories.
It is a late afternoon in early summer: OAT 31°C, dew point 24°C, altimeter 29.89. Scattered clouds at 3,500 ft AGL. Visibility 10 SM. The surface wind is reported as 220° at 12 knots, gusting to 18 knots. Runway 23 is aligned 222° true. The crosswind component is roughly 8–10 knots steady, gusting to 14–16 knots — within the Piper Arrow's demonstrated crosswind capability of 17 knots, but the gusts are notable and the wind is variable.
You are on short final to Runway 23, 400 ft AGL, 1.2 nm from the runway threshold. Gear down and locked (three green lights), flaps 20°, airspeed 85 KIAS (slightly above Vref of 75 KIAS for a stabilized approach). The runway is in sight. The approach has been stable until now.
Aircraft: Piper PA-28R-200 Arrow, solo, within weight and balance limits. Fuel-injected Lycoming IO-360, constant-speed prop (RPM set for approach), retractable gear (down and locked). Brakes are serviceable; no maintenance write-ups.
Pilot: you — a Commercial pilot, current, roughly 800 hours total with 150 hours in complex aircraft. You are familiar with the Piper Arrow's handling in crosswinds. You have landed at KVDF twice before. You are not fatigued. This is a routine approach.
- {'label': 'Field', 'value': 'KVDF · Tampa Executive'}
- {'label': 'Runways', 'value': '5/23 · 18/36'}
- {'label': 'Elevation', 'value': '22 ft'}
- {'label': 'Aircraft', 'value': 'PA-28R'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before we get into the decision tree — what do you know about crosswind landing technique and go-around decision-making in the Piper Arrow? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB GAA17CA105 (2016): A Piper PA-46 on a personal flight experienced loss of directional control during landing rollout in gusting crosswind conditions that exceeded the aircraft's demonstrated crosswind capability. The pilot did not maintain directional control during the rollout and the aircraft exited the runway. The probable cause was the pilot's loss of directional control during the landing rollout in gusting crosswind conditions.
NTSB ERA17CA149 (2017): A North American T-6G aircraft landed hard during a go-around attempt in gusting crosswind conditions. The right wingtip contacted the runway, the aircraft pivoted right, and nosed over. The probable cause was the pilot's failure to maintain directional control during the landing roll and go-around in gusting wind conditions. The teaching point: maintain adequate airspeed and control authority during go-around in gusty crosswind; recognize when a landing is unstable and commit to abort early.
NTSB GAA16CA149 (2016): An American AA-1 sustained substantial damage when the pilot lost directional control during landing and nosed over after the nose gear was damaged during takeoff in crosswind conditions. The pilot exceeded the aircraft's maximum demonstrated crosswind component of 13 knots during both takeoff and landing. The lesson: know and respect aircraft demonstrated crosswind limits; abort takeoff if directional control is lost early in the roll; plan landing approach accordingly.
NTSB WPR25LA178 (2025): A Piper PA-28R-200 on a test flight following annual inspection experienced brake system failure during landing rollout due to a hydraulic fluid leak. The aircraft exited the runway and collided with a fence. The probable cause was a failure of the brake system during landing due to a hydraulic fluid leak. The teaching point: brakes are a tool for slowing down, not for maintaining directional control. Directional control must be established first with rudder; brakes are applied only after the nose is aligned with the runway.
NTSB CEN21LA269 (2021): A Piper PA-28R on a personal flight experienced loss of directional control during the takeoff roll and struck runway signs and lights. The probable cause was the pilot's failure to maintain directional control during the takeoff roll. The lesson applies equally to landing rollout: directional control is the pilot's responsibility, and it must be maintained with prompt, full rudder authority.
The real accidents cited above occurred at other airports and in various aircraft types — NOT at Tampa Executive Airport (KVDF). KVDF has its own accident history (see field dominant patterns: LOSS_OF_CONTROL_GROUND 18.4%, HARD_LANDING 18.4%, FORCED_LANDING 15.8%). The scenario is localized to KVDF to make the runway environment and off-field consequences real for you as a student here. Runway 23's off-field environment to the right (heading 222°) is a mix of pasture/hay, open water, and medium development — a runway excursion to the right is a real hazard, not a theoretical one.
The consistent thread across all these events: loss of directional control in crosswind conditions is a ground-based accident that kills or injures pilots and damages aircraft. The fix is simple: (1) know your aircraft's demonstrated crosswind limit (Piper Arrow: 17 knots); (2) recognize when conditions approach or exceed that limit; (3) commit to a go-around early if the approach is unstable; (4) in the rollout, use full rudder authority promptly to maintain directional control; (5) do not apply brakes until the nose is aligned with the runway. Hesitation and tentative corrections are the enemy.
Key lesson — Crosswind landing loss of control is a preventable ground accident. The Piper Arrow's demonstrated crosswind component is 17 knots — that is the limit of testing, not a hard ceiling. Gusts that exceed that limit can overwhelm directional control. If the approach becomes unstable or directional control is marginal, execute a go-around immediately. In the rollout, use full rudder authority promptly to maintain directional control; do not apply brakes until the nose is aligned with the runway. At KVDF Runway 23, an excursion to the right puts you in a mix of fields and open water — a real hazard.
Debrief — teaching points
Know your aircraft's demonstrated crosswind limit — and respect it.
The Piper Arrow's demonstrated crosswind component is 17 knots. This is the limit of testing by the manufacturer — the maximum crosswind in which the aircraft was tested and found to be controllable. It is not a hard ceiling, but it is a boundary. Gusts that exceed the demonstrated crosswind limit can overwhelm directional control, especially during landing rollout when airspeed is low and control authority is marginal. If the surface wind is 220° at 12 kt gusting 18 kt and Runway 23 is 222°, the crosswind component is roughly 8–10 kt steady, gusting 14–16 kt — within limits, but the gusts are notable. Be aware of the margin.
Recognize when an approach is becoming unstable — and commit to a go-around early.
An unstable approach is one in which the airplane is not tracking the runway centerline, the descent rate is not stable, or directional control is marginal. If you experience a gust that pushes the airplane off centerline and you have to fight to correct it, that is a sign the conditions may be marginal. If a second gust hits and you are losing control, that is the moment to execute a go-around — not to try to salvage the landing by flaring early or landing off-center. A go-around at 250 ft AGL with adequate airspeed is safe; a landing in marginal directional control is not. Commit to the go-around early, before you are too low to recover safely.
In the landing rollout, directional control is the priority — not braking.
During landing rollout in a crosswind, the airplane is vulnerable to loss of directional control. The rudder is your primary tool for maintaining alignment with the runway. Use full left rudder authority promptly when the airplane drifts right. Do not apply brakes until the nose is aligned with the runway and directional control is established. Braking while the airplane is drifting actually reduces your directional control authority — the rudder is less effective at lower speeds, and the braking may cause the airplane to pivot further off the runway. Establish directional control first; brake second.
Use full control deflections in a crosswind landing — not tentative corrections.
A common mistake in crosswind landings is to make small, tentative corrections with the rudder and aileron. A gust that pushes the left wing down and the nose right requires a prompt, full response: full left rudder and right aileron to level the wing and correct the drift. Hesitation or small inputs will not overcome the gust. The airplane will continue to drift. At 250 ft AGL, you do not have time for tentative corrections — use full control authority and trust the airplane's handling.
The crabbed landing technique is correct for crosswind conditions.
In a crosswind landing, the correct technique is to crab the airplane into the wind — that is, to align the nose with the runway (using rudder) while allowing the fuselage to be at an angle to the wind (using aileron to keep the wing level). This is different from a slip, where the nose is pointed away from the runway. The crabbed approach allows you to maintain directional control with the rudder while the aileron keeps the wing level. Practice this technique in calm conditions so it becomes automatic in gusty conditions.
Built from the real accident record
Scenario built from NTSB WPR25LA178 (2025 PA-28R brake failure / runway excursion), CEN24LA288 (2024 PA-28R gear-up landing / distractions), CEN23LA417 (2023 PA-28RT gear retraction / runway excursion), CEN21LA269 (2021 PA-28R loss of directional control / takeoff), and crosswind-loss-of-control precedents GAA17CA105 (2016 PA-46 crosswind excursion), ERA17CA149 (2017 T-6G crosswind go-around), GAA16CA149 (2016 AA-1 crosswind nose-over), CHI02TA149 (2002 A185F wind gust / rollout. Localized to Tampa Executive Airport (KVDF).
NTSB reports: WPR25LA178 · CEN24LA288 · CEN23LA417 · CEN21LA269 · GAA17CA105 · ERA17CA149 · GAA16CA149 · CHI02TA149
ACS tasks: PA.VII.A — Preflight Inspection · PA.VII.B — Cockpit Management · PA.VIII.A — Takeoff and Climb · PA.VIII.B — Approach and Landing · PA.VIII.C — Go-Around / Rejected Landing · PA.I.F — Weather Information · PA.I.H — Human Factors
Relevant FARs: §91.3 · §91.13 · §91.175 · §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 Piper Arrow scenarios · More scenarios at KVDF