Gusts on Short Final
Crosswind landing in deteriorating conditions — when to go around, and how to recognize the limits of directional control
The scenario
Departing St. Petersburg Clearwater International Airport (KPIE), Pinellas Park, FL — Runway 18, a 9,730 ft concrete runway. Elevation 11 ft MSL. You are on a personal flight, solo, returning from a neighboring field after a 1.5-hour cross-country. The flight has been routine; you are current and proficient.
Weather: VFR, scattered clouds at 3,500 ft, visibility 10 SM. Surface wind reported by KPIE tower as 160° at 12 knots, gusting to 18 knots. Runway 18 is aligned 171° true (roughly 168° magnetic). The crosswind component is approximately 10–12 knots steady, gusting to 16–18 knots. The Piper Arrow's demonstrated crosswind capability is 12 knots. You are at the edge of limits, and the gusts are pushing beyond.
You are on a 3-mile final approach to Runway 18, descending through 800 ft AGL, airspeed 90 KIAS (Vy), landing gear down and locked, flaps 20°. The approach has been stable until the last 30 seconds. Now the wind is noticeably gusty — the airplane is being pushed left (south) by crosswind gusts, and you are correcting with right aileron and right rudder. The wing is cocked into the wind; the nose is pointed slightly right of the runway centerline to maintain alignment.
Aircraft: Piper PA-28R-200 (Arrow), solo, within limits, full fuel, retractable gear down and locked, constant-speed prop in cruise configuration (you have not yet cycled it for landing). The airplane is airworthy; nothing was written up.
Pilot: You — a Commercial pilot, current, roughly 800 hours total. You have 120 hours in the Arrow. You have landed in crosswinds before, but not in gusts this strong. Your personal minimums are 15 knots demonstrated crosswind; the current conditions are marginal to your limits. You did not brief a go-around decision point before entering the approach.
- {'label': 'Field', 'value': 'KPIE · St. Petersburg Clearwater'}
- {'label': 'Runways', 'value': '4/22 · 18/36'}
- {'label': 'Elevation', 'value': '11 ft'}
- {'label': 'Aircraft', 'value': 'PA-28R'}
- {'label': 'Dominant phase', 'value': 'Takeoff / Landing'}
The decision
Before we enter the decision tree — what do you know about crosswind landings in the Piper Arrow and when to go around? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
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. The scenario here focuses on the loss-of-control aspect that preceded the brake failure — the crosswind and the pilot's decision-making.
NTSB GAA17CA105 (2016): A Piper PA-46 experienced loss of directional control during landing rollout in gusting crosswind conditions that exceeded the aircraft's demonstrated crosswind capability (12 knots). The pilot attempted to land in 18-knot gusts and lost directional control. The probable cause was the pilot's loss of directional control during landing in crosswind conditions that exceeded the aircraft's demonstrated capability. The key lesson: recognize when conditions exceed aircraft limits and commit to go-around early.
NTSB ERA17CA149 (2017): A North American T-6G 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 lesson: go-around itself can be unstable in gusts if airspeed is marginal — commit to the go-around early, when you have altitude and control.
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: respect aircraft demonstrated crosswind limits; they are not suggestions.
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 mechanism — loss of directional control in marginal conditions — is the same trap that kills pilots on landing.
The real accidents cited above occurred at other airports and in other aircraft — NOT at KPIE. St. Petersburg Clearwater International Airport has its own accident history (see field dominant patterns: 21.2% loss of control in flight, 15.2% loss of control on ground, 12.1% stall/spin). The scenario is localized to KPIE to make the runway environment and the crosswind decision real and consequential for you as a student here.
The consistent thread across all these events: crosswind loss of control is preventable. The decision to go around must be made early — on downwind or base, when you have altitude and control. Once you are on short final at 300 ft AGL, the margin for error is gone. The demonstrated crosswind limit is the limit tested by the manufacturer; gusts that exceed it mean the airplane is being pushed beyond its tested capability. That is the signal to go around.
Key lesson — The Piper Arrow's demonstrated crosswind capability is 12 knots. When steady crosswind is at or near that limit, gusts that exceed it are a signal to go around. The decision to go around must be made early — on downwind or base, when you have altitude and control. Once you are on short final at 300 ft AGL, the margin for error is gone. If you are fighting directional control, go around. If the gusts are exceeding the demonstrated limit, go around. If you have not briefed a go-around decision point before entering the approach, go around. Recognize your personal minimums and respect them — they are more conservative than demonstrated limits for a reason.
Debrief — teaching points
The Piper Arrow's demonstrated crosswind capability is 12 knots — that is the limit tested by the manufacturer.
The demonstrated crosswind capability is not a suggestion or a guideline; it is the limit tested by the manufacturer in controlled conditions. When steady crosswind is at or near 12 knots, and gusts exceed that limit, the airplane is being pushed beyond its tested capability. This is the signal to go around. Your personal minimums should be more conservative — if you set 15 knots as your limit, you should not land in 12-knot steady crosswind with gusts to 18. Respect the numbers.
The decision to go around must be made early — on downwind or base, when you have altitude and control.
A go-around at 600 ft AGL is straightforward: advance throttle, raise flaps, establish a climb at Vx (78 KIAS with gear down). A go-around at 300 ft AGL on short final in a gust is unstable and risky. Brief a go-around decision point before entering the approach — 'If the gusts exceed the limit or I lose directional control, I will go around at 500 ft AGL.' Commit to that decision. Once you are on short final, the margin for error is gone.
Crosswind correction does not end at touchdown — it continues through rollout until the airplane is slow enough that the wind no longer has authority.
In a crosswind landing, maintain aileron and rudder correction as the airspeed decreases through rollout. The wind is still pushing the airplane left; the right aileron and rudder keep it tracking straight down the runway. As the airspeed decreases below 40 knots, the wind's authority diminishes and you can reduce the control inputs. Relaxing the correction too early invites a runway excursion.
When conditions exceed your limits, diversion or requesting an alternate runway are valid options.
If the wind at your destination is 160° at 12G18 knots and Runway 18 is aligned 171°, the crosswind is marginal to your limits and the gusts exceed the demonstrated limit. Requesting Runway 36 (aligned 351°) changes the crosswind component from 10–12 knots to only 3–4 knots — well within limits. If both runways are marginal, diversion to a nearby field with more favorable wind is a sound decision. You have fuel; use it.
The constant-speed prop in the Arrow requires attention during the approach.
The constant-speed prop should be cycled to high RPM (full forward) on short final to prepare for go-around or landing. In the scenario, you did not cycle the prop during the approach — it was in cruise configuration. This is a procedural miss that should be corrected in your pre-landing checklist. Gear down, flaps as needed, prop high RPM — that is the sequence.
Loss of directional control on landing is a spiral descent — level the wings and regain control of the flight path.
If you find yourself in a spiral descent at low altitude (200 ft AGL), the immediate action is to level the wings with aileron and reduce the bank angle. Once the wings are level, apply back pressure to raise the nose and reduce the descent rate. If the airplane is still in a descent and altitude is critically low, apply full power and climb out — abort the landing and go around. A spiral descent is a loss-of-control situation that should never have developed; the decision to go around at 600 ft AGL would have prevented it.
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), CEN23LA417 (2023 PA-28RT gear retraction / runway excursion), CEN21LA269 (2021 PA-28R loss of directional control on takeoff), and crosswind-loss-of-control precedents GAA17CA105, ERA17CA149, GAA16CA149, CHI02TA149. Anonymized and localized to KPIE.
NTSB reports: WPR25LA178 · CEN24LA288 · CEN23LA417 · CEN21LA269 · GAA17CA105 · ERA17CA149 · GAA16CA149 · CHI02TA149
ACS tasks: PA.II.E — Approach and Landing · PA.II.F — Go-Around / Rejected Landing · PA.I.F — Weather Information · PA.I.H — Human Factors · PA.IX.C — Emergency Approach and Landing
Relevant FARs: §91.3 · §91.13 · §91.175
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 KPIE