Gusts on Short Final
Crosswind landing in deteriorating conditions at a water-surrounded field — directional control and go-around decision-making under pressure
The scenario
Departing Albert Whitted Airport (KSPG), St. Petersburg, FL — Runway 25, landing in a gusty crosswind. Elevation 7 ft MSL; the runway is essentially at sea level.
It is late afternoon on a breezy Gulf Coast day: OAT 26°C, wind 180° at 12 knots, gusting to 18. Runway 25 is oriented 242° (magnetic). The crosswind component is roughly 10–12 knots steady, with gusts to 16–17 knots. The Piper Arrow's demonstrated crosswind capability is 15 knots. You are at the edge of limits, and the gusts are pushing into the red. Visibility is 10 SM, scattered clouds at 3,000 ft. Class D airspace; tower is open and active (1530 local, within 0700–2100 operating hours).
You are inbound from a local flight, 8 nm southwest of KSPG. Fuel is adequate (1.5 hours remaining). The airplane is within weight and balance. You have logged 650 hours total, 180 in complex aircraft (retractable gear, constant-speed prop). You are current and proficient. This is not your home field, but you have landed here twice before — both times in calm conditions.
Aircraft: Piper PA-28R-200 Arrow, solo, full fuel, within limits. Lycoming IO-360 fuel-injected engine, retractable gear, constant-speed prop. The airplane was released from annual inspection this morning. The brake system was serviced as part of the annual; the logbook shows a full hydraulic fluid top-off and brake-pad replacement. Nothing was written up.
Pilot: you — a Commercial pilot, current, roughly 650 hours total, 180 in complex aircraft. You have not landed in crosswind conditions exceeding 12 knots in the past six months. Your personal minimums are 15-knot crosswind (demonstrated capability). The gusts are at the edge of that limit.
- {'label': 'Field', 'value': 'KSPG · Albert Whitted'}
- {'label': 'Runways', 'value': '7/25 · 18/36'}
- {'label': 'Elevation', 'value': '7 ft'}
- {'label': 'Aircraft', 'value': 'PA-28R'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
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 accidents? (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 (likely from the post-maintenance brake service) resulted in loss of braking authority. The pilot attempted to keep the airplane on the runway and collided with a fence. The probable cause was brake system failure due to a hydraulic leak, compounded by the pilot's decision to fight the airplane on the runway rather than accept the excursion.
NTSB CEN24LA288 (2024): A Piper PA-28R-180 landed with the left and nose landing gear not fully locked. The pilot had failed to extend the gear before landing due to distractions and failure to conduct the before-landing checklist. The accident resulted from the pilot's failure to extend the landing gear.
NTSB CEN23LA417 (2023): A Piper PA-28RT-201 experienced partial retraction of the right main and nose landing gear during landing rollout. The cause could not be determined despite extensive testing. The right wing scraped the runway and the aircraft exited the runway.
NTSB CEN21LA269 (2021): A Piper PA-28R-180 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.
Regional crosswind precedents (GAA17CA105, ERA17CA149, GAA16CA149, CHI02TA149) consistently show the same failure mode: a pilot exceeds demonstrated crosswind limits or loses directional control in gusting conditions, then fights the airplane on the runway rather than executing a go-around. The NTSB GAA17CA105 pilot lost directional control in gusting crosswind conditions that exceeded the aircraft's demonstrated capability; the ERA17CA149 pilot failed to maintain directional control during landing rollout and go-around in gusting winds; the GAA16CA149 pilot exceeded the aircraft's maximum demonstrated crosswind component during both takeoff and landing.
The local environment at KSPG makes this scenario particularly consequential: Runway 25's off-field environment is dense development — buildings, streets, parking lots. A runway excursion off Runway 25 is not a soft-field landing; it is a collision with urban terrain. Off Runway 07, the environment is open water (Tampa Bay) — a brake failure on that runway would force a ditching, not an excursion. The field's own accident history shows LOSS_OF_CONTROL_INFLIGHT (20%), FORCED_LANDING (16.4%), and LOSS_OF_CONTROL_GROUND (14.5%) as dominant patterns — this scenario addresses the ground-control failure mode.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Albert Whitted Airport. KSPG has its own accident history, but these specific events happened elsewhere. The scenario is localized to KSPG to make the off-field environment real and consequential for you as a student here.
The consistent thread across all these events: crosswind loss-of-control accidents in complex aircraft (retractable gear, constant-speed prop) are often compounded by post-maintenance issues (brake failure, gear malfunction) and pilot decision-making under pressure. The Piper Arrow's demonstrated crosswind limit is 15 knots — that is a limit, not a suggestion. Gusts to 16–17 knots exceed that limit. The correct decision is a go-around or diversion, not a fight to stay on the runway.
Key lesson — The Piper Arrow's demonstrated crosswind capability is 15 knots. Gusts to 16–17 knots exceed that limit. At KSPG Runway 25, the off-field environment is dense development — a runway excursion is a collision, not a field landing. If directional control is marginal on short final, execute a go-around. If braking is lost on rollout, accept the excursion and steer toward the least-damaging area — do not fight the airplane on the pavement. Post-maintenance brake failures are real; the NTSB WPR25LA178 pilot faced exactly this scenario.
Debrief — teaching points
The Piper Arrow's demonstrated crosswind capability is 15 knots — that is the limit for normal operations.
The POH states a demonstrated crosswind component of 15 knots. This is not a suggestion or a soft limit; it is the maximum demonstrated capability. Gusts to 16–17 knots exceed this limit. At KSPG on this afternoon, the steady wind is 12 knots with gusts to 18 — the gust component alone exceeds the demonstrated limit. Recognize this before you commit to the approach. The decision to divert or request a different runway is the correct one, not a sign of weakness.
Crosswind control authority is reduced with gear down and flaps extended.
The Piper Arrow's landing gear and flaps increase drag and reduce maneuverability. On short final with gear down and flaps at 25°, your control authority is at its minimum. A gust that would be manageable at cruise altitude becomes critical at 300 ft AGL on short final. Recognize the vulnerability and plan accordingly: if the crosswind is marginal, brief yourself on the slip technique or plan a go-around threshold.
A forward slip on short final is a valid recovery tool for crosswind loss of control.
The forward slip — lower the upwind wing, apply opposite rudder — increases descent rate and reduces drift. On short final, a slip can recover control authority when the crosswind gust is pushing you off the centerline. The slip is not a sign of poor technique; it is a deliberate, controlled maneuver to regain alignment. Practice it in calm conditions so you can execute it smoothly under pressure.
If the approach is unstable on short final, go around — do not fight the airplane to the runway.
An unstable approach — oscillating pitch and roll, steep bank, loss of control authority — is a go-around trigger. At 100 ft AGL, you still have altitude and energy to go around safely. Advancing the throttle, retracting flaps, and climbing back to 1,000 ft is the correct decision. The NTSB regional precedents (GAA17CA105, ERA17CA149) show that pilots who fight an unstable approach to the runway often end up in a worse situation — a hard landing, a bounce, or a loss of control on rollout.
Post-maintenance brake failures are real — hydraulic leaks can occur during brake service.
The NTSB WPR25LA178 pilot experienced brake failure immediately after annual inspection, when the brake system had been serviced. A hydraulic leak from the post-maintenance service resulted in loss of braking authority on rollout. If brakes are soft or unresponsive on rollout, do not assume they will improve — they will not. Accept the runway excursion and steer toward the least-damaging area. Do not fight the airplane on the pavement.
Off Runway 25 at KSPG, the off-field environment is dense development — a runway excursion is a collision.
The USGS NLCD ground cover off Runway 25 is dense development, medium development, and low-density development — buildings, streets, parking lots. A runway excursion off Runway 25 is not a soft-field landing; it is a collision with urban terrain. This is the geographic reality of KSPG. If you lose braking or directional control on rollout, steer toward the least-damaging area — the grass off the left side of the runway, not toward the buildings on the right.
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 / takeoff roll), and regional crosswind-loss-of-control precedents GAA17CA105, ERA17CA149, GAA16CA149, CHI02TA149. Anonymized and localized to KSPG.
NTSB reports: WPR25LA178 · CEN24LA288 · CEN23LA417 · CEN21LA269 · GAA17CA105 · ERA17CA149 · GAA16CA149 · CHI02TA149
ACS tasks: PA.I.F — Weather Information · PA.I.G — Cross-Country Flight Planning · PA.II.E — Takeoff and Departure · PA.III.A — Approaches and Landings · 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 KSPG