Gusts on Short Final
Crosswind landing in gusty conditions — recognizing when directional control is lost and committing to the go-around before structural damage
The scenario
Departing Sarasota Bradenton International Airport (KSRQ), Runway 14, on a personal flight to a nearby field. Elevation 30 ft MSL. You are a commercial pilot with 800 hours total time, current and proficient. The Piper Arrow is familiar — you have 120 hours in type.
It is late afternoon. ATIS reports winds 160° at 14 gusting to 22 knots. Runway 14's magnetic heading is 134°. The crosswind component is roughly 12–14 knots steady, with gusts to 20 knots. The Arrow's demonstrated crosswind capability is 13 knots. You are at the limit, and the gusts are exceeding it.
You are on short final to Runway 14, 200 ft AGL, 1.2 nm out. Gear is down and locked (three green lights), flaps are 40°, airspeed is 75 KIAS (Vref). The runway is in sight. ATC has cleared you to land. The approach has been stable until now.
At 100 ft AGL, a gust hits from the left. The left wing drops. You apply right aileron and right rudder to correct. The airplane responds, but the gust is strong. Another gust, from a slightly different angle. The nose is drifting left of the runway centerline. You are correcting with full right rudder and aileron, but the airplane is not responding as expected. You are 50 ft AGL.
Aircraft: Piper PA-28R-200, solo, within weight and balance limits. Constant-speed prop, retractable gear, fuel-injected Lycoming IO-360. The airplane is airworthy; nothing is written up. You have not flown into KSRQ before — this is your first landing here.
The off-field environment: Runway 14's climb-out (heading 134°) is dense development and low-density development — not a safe forced-landing option. Runway 32's climb-out (heading 314°) is medium development, dense development, and marsh. Off Runway 04 (heading 38°) is marginal — wooded wetland and low-density development. Off Runway 22 (heading 218°) is open water and low-density development — a ditching environment. You are committed to landing on Runway 14.
- {'label': 'Field', 'value': 'KSRQ · Sarasota Bradenton'}
- {'label': 'Runways', 'value': '4/22 · 14/32'}
- {'label': 'Elevation', 'value': '30 ft'}
- {'label': 'Aircraft', 'value': 'PA-28R'}
- {'label': 'Dominant phase', 'value': 'Takeoff / Landing'}
The decision
Before we get into the decision tree — what do you already know about crosswind landings in the Piper Arrow and loss of directional control? (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. A hydraulic fluid leak resulted in loss of braking authority. The aircraft exited the runway and collided with a fence. The probable cause was the failure of the brake system due to the hydraulic fluid leak. The runway excursion was a consequence of the loss of braking authority, not directional control — but the outcome (off the runway, structural damage) is the same.
NTSB CEN24LA288 (2024): A Piper PA-28R-180 landed with the left and nose landing gear not fully locked. The pilot failed to extend the gear before landing due to distractions from skydiving operations and failure to conduct the Before Landing checklist. The aircraft landed gear-up, sustaining substantial damage. The probable cause was the pilot's failure to conduct the checklist and his failure to recognize the gear was not down.
NTSB CEN23LA417 (2023): A Piper PA-28RT-201 experienced partial retraction of the right main and nose landing gear during landing rollout. The cause of the gear retraction could not be determined despite extensive testing. The right wing scraped the runway and the aircraft exited the runway. The outcome — runway excursion, structural damage — is identical to a loss-of-directional-control scenario, but the root cause was mechanical.
NTSB CEN21LA269 (2021): A Piper PA-28R-180 on a personal flight experienced loss of directional control during the takeoff roll. The pilot failed to maintain directional control and struck runway signs and lights. The probable cause was the pilot's failure to maintain directional control. This event occurred on takeoff, not landing, but the mechanism — loss of directional control, structural damage — is the same.
NTSB GAA17CA105 (2016, regional precedent): A Piper PA-46-350P experienced loss of directional control during landing rollout in gusting crosswind conditions that exceeded the aircraft's demonstrated crosswind capability (13 knots for the PA-46 is comparable to the PA-28R). The pilot attempted to recover during rollout rather than committing to a go-around early. The accident resulted in structural damage.
NTSB ERA17CA149 (2017, regional precedent): 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.
NTSB GAA16CA149 (2016, regional precedent): An American AA-1 sustained substantial damage when the pilot lost directional control during landing and nosed over. The pilot exceeded the aircraft's maximum demonstrated crosswind component (13 knots) during both takeoff and landing. The probable cause was the pilot's failure to recognize directional control loss early and abort the landing.
NTSB CHI02TA149 (2002, regional precedent): A Cessna A185F veered off the runway during landing rollout when a wind gust forced the aircraft into an uncontrollable turn. The accident was attributed to directional control not being maintained, with gusting winds as a contributing factor.
The consistent thread: Loss of directional control during landing in crosswind conditions is preventable. The key is recognizing when the gusts exceed the airplane's demonstrated capability (13 knots for the PA-28R) and committing to the go-around early — at 100 ft AGL, not 50 ft AGL, and certainly not during rollout. Attempting to recover during rollout risks structural damage (wingtip strike, nose gear collapse, nose-over). The go-around is not a failure; it is airmanship.
At KSRQ, the off-field environment off Runway 14 (dense and low-density development) makes a forced landing unattractive. Off Runway 22 (open water) is a ditching. The runway is the only safe landing option. If the approach becomes unstable due to crosswind, the go-around is the correct decision — not an attempt to recover during rollout.
Key lesson — The Piper Arrow's demonstrated crosswind capability is 13 knots. When gusts exceed that limit, the airplane may not respond to full control inputs — directional control can be genuinely lost. Recognize this early in the approach (100 ft AGL) and commit to the go-around before structural damage occurs. Attempting recovery during landing rollout risks wingtip strike, nose gear collapse, or nose-over. The go-around decision must be made early and executed decisively.
Debrief — teaching points
The Piper Arrow's demonstrated crosswind capability is 13 knots — that is the limit, not a suggestion.
The PA-28R's demonstrated crosswind component is 13 knots. This is the maximum crosswind the manufacturer tested and certified the airplane for. When steady-state winds exceed this limit, or when gusts exceed it, the airplane may not respond to full control inputs. Directional control can be genuinely lost, not just difficult. At KSRQ today, the steady wind was 12–14 knots with gusts to 20 knots — you were at the limit in steady wind and well beyond it in gusts. Recognizing this before you commit to the approach is the first step.
When gusts exceed the demonstrated crosswind, the airplane may not respond to full rudder and aileron.
In a violent gust, full rudder and aileron may be insufficient to maintain directional control. The control authority of the airplane is fixed; the gust force is not. When the gust force exceeds the control authority, the airplane will drift regardless of control input. This is not a failure of technique — it is a failure of the airplane's capability in those conditions. Recognizing that point and committing to the go-around is the correct decision.
The go-around decision must be made early — at 100 ft AGL, not 50 ft AGL.
The decision to go around must be made when you still have altitude and control authority to execute the maneuver safely. At 100 ft AGL with a marginal approach, you have time to advance the throttle, raise the flaps, and establish a climb. At 50 ft AGL, the margin is thin — a late go-around risks wingtip strike or structural damage as you climb out. The NTSB ERA17CA149 (T-6G) and GAA17CA105 (PA-46) both involved pilots who delayed the go-around decision and sustained structural damage. Make the decision early.
Attempting to recover directional control during landing rollout risks structural damage.
Once the airplane is on the runway and rolling out, the options are limited. If directional control is lost and the nose gear is tracking off the runway edge, the pilot's choices are: (1) reduce braking and apply rudder to steer back toward the centerline (requires quick thinking and good control technique), or (2) accept the runway excursion and focus on stopping the airplane before it flips. Attempting to recover with full brakes and full rudder may result in the nose gear dropping off the runway edge and collapsing. The NTSB WPR25LA178, CEN23LA417, and GAA16CA149 all involved runway excursions resulting from loss of directional control during rollout.
Braking reduces airspeed and control authority — in a crosswind rollout, reduce braking and use rudder to steer.
Rudder authority is proportional to airspeed. As the airplane slows during rollout, the rudder becomes less effective. If you apply full brakes immediately, the airspeed drops rapidly and the rudder loses authority just when you need it most. In a crosswind rollout that is becoming unstable, reduce brake pressure and use rudder to steer the airplane back toward the centerline. Once the airplane is straightened out and the airspeed is low, then apply full brakes to stop.
At KSRQ, the off-field environment makes the runway the only safe option.
Off Runway 14 (your landing runway today): dense development and low-density development — not a safe forced-landing option. Off Runway 22: open water — a ditching. Off Runway 04: marginal — wooded wetland and low-density development. Off Runway 32: poor — medium development, dense development, and marsh. The runway is the only safe landing surface. If the approach becomes unstable due to crosswind, the go-around is the correct decision — not an attempt to recover during rollout.
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 / distraction), CEN23LA417 (2023 PA-28RT gear retraction / runway excursion), CEN21LA269 (2021 PA-28R loss of directional control on takeoff), and regional crosswind-loss-of-control precedents GAA17CA105 (2016 PA-46 crosswind / go-around), ERA17CA149 (2017 T-6G crosswind / nose-over), GAA16CA149 (2016 AA-1 crosswind / directional control loss), and CHI02TA149 (2002 A185F wind gust / uncontrollable turn). Localized to KSRQ.
NTSB reports: WPR25LA178 · CEN24LA288 · CEN23LA417 · CEN21LA269 · GAA17CA105 · ERA17CA149 · GAA16CA149 · CHI02TA149
ACS tasks: PA.VII.A — Normal Approach and Landing · PA.VII.B — Forward Slip · PA.VII.C — Go-Around / Rejected Landing · PA.I.H — Human Factors · PA.VIII.A — Loss of Control Inflight
Relevant FARs: §91.3 · §91.13 · §91.103
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 KSRQ