Gusting Crosswind on Short Final
Loss of directional control in a Piper Arrow during landing in gusty crosswind conditions — recognizing the limit and committing to a go-around
The scenario
Departing Zephyrhills Municipal Airport (KZPH), Zephyrhills, FL — Runway 19, landing in gusty crosswind conditions. Field elevation 90 ft MSL. Non-towered (CTAF); you self-announce on 122.8 MHz.
It is late afternoon in early spring: surface wind is reported as 240° at 18 gusts to 28 knots. Runway 19 is oriented 180°/360° — the wind is a direct crosswind, nearly perpendicular to the runway. The demonstrated crosswind capability of the PA-28R is approximately 15 knots in smooth air. You are looking at gusts to 28 knots — well beyond that limit. Visibility 10 SM, scattered clouds at 3,500 ft, VFR.
You are on short final to Runway 19, 400 ft AGL, configured for landing: gear down and locked, flaps 40°, airspeed 75 KIAS (Vref), descent rate 300 fpm. The runway is in sight. The wind is gusty — you feel the airplane being pushed left and right. You have been flying the PA-28R for 150 hours; you are current and proficient. You did not file a flight plan; this is a local VFR flight.
Aircraft: Piper PA-28R-200, solo, within weight and balance. Fuel: 40 gallons usable, left tank selected. Constant-speed prop is in cruise position (you will need to adjust it if you go around). Gear is down and locked; the green light is bright. Flaps are at 40°. You are stable on the glide slope.
Pilot: you — a Commercial pilot, current, roughly 500 hours total. You have landed in crosswind before, but not in gusts this strong. Your personal minimums are 15 knots demonstrated crosswind. You are aware of the limit, but you are also committed to this landing — you have been in the air for 2 hours and you want to land.
- {'label': 'Field', 'value': 'KZPH · Zephyrhills'}
- {'label': 'Runways', 'value': '19/1 · 5/23'}
- {'label': 'Elevation', 'value': '90 ft'}
- {'label': 'Aircraft', 'value': 'PA-28R'}
- {'label': 'Dominant phase', 'value': 'Landing / Cruise'}
The decision
Before we get into the decision tree — what do you already know about crosswind landings in the PA-28R? (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 due to a hydraulic fluid leak, which resulted in a runway excursion. However, the underlying factor was the pilot's attempt to land in conditions that were marginal for the aircraft and the pilot's experience level.
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. The accident resulted from the pilot's loss of directional control during the aborted landing in gusting crosswind conditions. The pilot attempted to recover during rollout instead of executing a go-around.
NTSB ERA21LA119 (2021): A Cessna 172R on a personal flight veered left off the runway during landing in gusting crosswind conditions and struck the ground with the propeller and left wing tip. The accident was attributed to the pilot's failure to maintain directional control during landing in a gusting crosswind. The pilot did not recognize that the conditions exceeded personal minimums.
NTSB GAA19CA170 (2019): A Piper PA-11 tailwheel aircraft lost directional control during landing roll in gusting crosswind conditions, veered off the runway, struck a ditch, and came to rest inverted. The accident was attributed to the pilot's failure to maintain directional control during the landing roll in gusting wind conditions. The pilot did not commit to a go-around early enough.
NTSB ERA10CA448 (2010): A Cessna 182E landed on runway 01 which had a direct crosswind and during landing rollout the crosswind pushed the aircraft off the runway to the left, causing it to nose over. The accident resulted from inadequate compensation for crosswind conditions. The pilot did not make an independent assessment of the wind and did not apply proper crosswind correction technique.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Zephyrhills Municipal Airport. KZPH has its own accident history (dominant pattern: forced landing 29.2%, loss of control in flight 29.2%, stall/spin 16.7%), but these specific crosswind-loss-of-control events happened elsewhere. The scenario is localized to KZPH to make the runway environment and off-field options real and consequential for you as a student here.
The consistent thread across all these events: pilots attempt landings in crosswind conditions that exceed the aircraft's demonstrated capability and their personal minimums. They do not recognize the limit early, or they recognize it but commit to the landing anyway. They lose directional control during the approach or rollout and exit the runway. The correct decision is to recognize the limit early, reduce flaps if needed to improve control authority, and if the approach is still unstable, execute a go-around. A go-around is not a failure — it is airmanship.
Key lesson — The PA-28R's demonstrated crosswind capability is approximately 15 knots in smooth air. Gusts beyond that are outside the envelope. Recognize the limit early. If the approach is unstable or the crosswind is beyond your demonstrated capability, execute a go-around — even from short final. Reducing flaps to 20° can improve directional control authority and allow a landing in stronger crosswind, but only if the approach remains stable. Hard braking during rollout reduces the airplane's responsiveness to wind gusts and can lead to loss of directional control. Smooth, progressive braking is more effective. Off Runway 19 at KZPH, the off-field environment is marginal (parks, developed areas, forest) — a runway excursion is survivable, but it is not acceptable when the correct decision (go-around) is available.
Debrief — teaching points
The PA-28R's demonstrated crosswind capability is approximately 15 knots in smooth air.
The POH for the PA-28R specifies a demonstrated crosswind capability of approximately 15 knots. This is a limit, not a guideline. Gusts beyond that are outside the aircraft's tested envelope. A surface wind of 240° at 18G28 to Runway 19 (180°/360°) is a direct crosswind with gusts to 28 knots — well beyond the limit. Recognize this early, in the weather briefing or on approach. Do not attempt a landing in conditions that exceed the demonstrated capability.
Reduce flaps to improve directional control authority in crosswind conditions.
Full flaps (40°) increase the aircraft's susceptibility to wind gusts and reduce directional control authority. Reducing flaps to 20° or less improves control responsiveness and makes the airplane more stable in crosswind. The trade-off is increased landing distance — but if you have 5,072 ft of runway (Runway 19 at KZPH), the extra distance is acceptable. Reduced flaps are a valid technique adjustment for crosswind landings, but only if the approach remains stable.
Recognize an unstable approach early and commit to a go-around.
An unstable approach is one in which the airplane is oscillating left and right, the descent rate is not constant, or the airspeed is not stable. If you are chasing the wind with control inputs, you are unstable. The correct action is to go around immediately — even from short final, even from 100 ft AGL. A go-around at low altitude is tight, but it is safer than a landing you cannot control. The NTSB accident corpus shows that pilots who attempt to recover during rollout (instead of going around) lose directional control and exit the runway.
The PA-28R has retractable gear and a constant-speed prop — both require management during a go-around.
In a go-around, you must advance the throttle to full power, raise the flaps (to 0° or 10°), retract the gear, and set the constant-speed prop to climb RPM. This is a multi-step procedure that requires focus and coordination. Practice go-arounds regularly so that the procedure is automatic. At low altitude in a crosswind, you do not have time to think — you must execute the procedure smoothly.
Smooth, progressive braking is more effective than hard braking during crosswind rollout.
Hard braking during rollout reduces the airplane's airspeed and responsiveness to control inputs. In a crosswind, this makes the airplane more susceptible to wind gusts. Smooth, progressive braking allows you to maintain control authority and respond to wind gusts with aileron and rudder. Apply brakes gently, increase pressure as the airplane slows, and use nosewheel steering to maintain centerline.
Off Runway 19 at KZPH, the off-field environment is marginal — recognize the geography.
The off-field environment off Runway 19's climb-out (heading 180°) is marginal: mostly open developed areas (parks, large lots), evergreen forest, and low-density development. A runway excursion off that end is survivable, but it is not acceptable when the correct decision (go-around) is available. Know the off-field environment before you depart. It may influence your decision to attempt a landing in marginal 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), CEN23LA417 (2023 PA-28RT gear retraction), CEN21LA269 (2021 PA-28R loss of directional control on takeoff), and crosswind-loss-of-control precedents GAA17CA105 (2016 PA-46 crosswind excursion), ERA21LA119 (2021 C172R crosswind landing), GAA19CA170 (2019 PA-11 crosswind rollout), ERA10CA448 (2010 C182E crosswind nose-over). Real events occurred at other airports — NOT at KZPH.
NTSB reports: WPR25LA178 · CEN24LA288 · CEN23LA417 · CEN21LA269 · GAA17CA105 · ERA21LA119 · GAA19CA170 · ERA10CA448
ACS tasks: PA.V.A — Preflight Inspection · PA.V.B — Cockpit Management · PA.VI.C — Takeoff and Climb · PA.VII.C — Approach and Landing · PA.VII.D — Go-Around / Rejected Landing · PA.IX.C — Emergency Approach and Landing · PA.I.H — Human Factors
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 KZPH