Gusts on Short Final
Crosswind landing in a Piper Archer — recognizing when conditions exceed aircraft limits and committing to the go-around
The scenario
Departing Tampa Executive Airport (KVDF), Tampa, FL — Runway 23, landing in gusty crosswind conditions. Elevation 22 ft MSL. You are on approach to Runway 23 (heading 222°) after a local flight.
Weather: OAT 31°C, dew point 24°C, altimeter 29.91. Wind is reported from 280° at 14 knots, gusting to 22 knots. Runway 23 is aligned 222° (magnetic). The crosswind component is roughly 12–14 knots steady, with gusts pushing 18–20 knots. The Piper Archer's demonstrated crosswind capability is 12 knots. You are at the limit in the steady wind and exceeding it in the gusts.
You are 2 nm from the field on a 5° left base for Runway 23, 1,200 ft AGL, descending at 76 KIAS (best glide / approach speed). The runway is in sight. You have not yet requested landing clearance on CTAF (KVDF is non-towered). The off-field environment off Runway 23's departure end (heading 222°) is pasture/hay, open water, and medium development — not ideal for a forced landing, but not a pure ditching either.
Aircraft: Piper PA-28-181 Archer, solo, within limits. Carbureted Lycoming O-360-A, 180 hp, fixed-pitch prop, fixed gear, steam panel. Fuel selector on LEFT tank (full). Flaps are at 0°; you will add them on short final.
Pilot: you — a Private pilot, current, roughly 250 hours total. You have landed in crosswinds before, but not in gusts this strong. Your personal minimums are 10 knots demonstrated crosswind. You are aware the wind is pushing your limits.
- {'label': 'Field', 'value': 'KVDF · Tampa Executive'}
- {'label': 'Runways', 'value': '5/23 · 18/36'}
- {'label': 'Elevation', 'value': '22 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-181'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before the decision tree — what do you know about crosswind landings in the Piper Archer? (Pick all that apply.)
What the record shows
What the NTSB files show
NTSB ERA10CA473 (2010): A Piper PA-28-181 on approach to a destination airport encountered windshear and stalled during landing, resulting in a hard landing and runway excursion. The probable cause was inadequate compensation for crosswind conditions. The pilot did not recognize that the gust component exceeded the aircraft's demonstrated crosswind capability and did not go around.
NTSB LAX08CA199 (2008): A Piper PA-28-181 student pilot on solo flight was vectored to a runway and landed with excessive airspeed after delaying flap extension. The aircraft bounced on touchdown, veered left during recovery, departed the runway, and struck a ditch, collapsing the nose gear and damaging the firewall. The probable cause was inadequate recovery from the bounced landing and failure to maintain directional control.
NTSB ERA10FA020 (2009, FATAL): A Piper PA-28-181 on a personal local flight landed fast and hard on a wet turf runway at Oliver Springs Airport, lost directional control during rollout, and collided with trees. The probable cause was loss of directional control while landing on a wet runway. The pilot did not recognize the loss of control early enough to correct it.
NTSB CHI05CA208 (2005): A Piper PA-28-181 overran a grass runway and struck a utility pole during landing. The probable cause was delayed decision-making, excessive approach airspeed, and failure to execute a go-around. Contributing factors included high density altitude and obstacles near the runway. The pilot continued an unstable approach rather than going around.
NTSB LAX04CA289 (2004): A Piper PA-28-181 on a student instructional flight experienced a hard landing and runway excursion at Scottsdale Airport. The probable cause was a misjudged flare resulting in a stall and hard landing, and failure to maintain directional control during rollout. The pilot's improper recovery from a bounced landing contributed to the accident.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Tampa Executive Airport (KVDF). KVDF's dominant accident pattern is LOSS_OF_CONTROL_GROUND (18.4%), HARD_LANDING (18.4%), and FORCED_LANDING (15.8%) — the same categories that dominate the NTSB PA-28-181 crosswind landing corpus. The scenario is localized to KVDF to make the runway environment and crosswind challenge real for you as a student here.
The consistent thread across all these events: the Piper Archer is heavier and faster than a Warrior. It floats on landing, carries more energy, and requires more runway. In crosswind conditions, the demonstrated crosswind limit (12 knots) is not a suggestion — it is the limit for which the airplane was tested and approved. Gusts that exceed that limit can cause loss of directional control, even if the steady-state wind is within limits. The decision to go around or switch runways is not a failure — it is airmanship.
Key lesson — The Piper Archer's demonstrated crosswind capability is 12 knots. Know this number. Respect it. If the steady-state wind or gusts exceed it, go around or switch runways. Do not try to salvage an unstable approach. Recognize loss of directional control early and correct it with firm rudder and nosewheel steering — but if the airplane is veering off the runway at low speed, the better decision is to have gone around earlier. Off Runway 23 at KVDF, the environment is pasture/hay, open water, and medium development — a runway excursion is not survivable.
Debrief — teaching points
The Piper Archer's demonstrated crosswind limit is 12 knots — know it and respect it.
The Piper PA-28-181 was tested and approved for a maximum demonstrated crosswind component of 12 knots. This is not a guideline; it is the limit for which the airplane's handling and control authority were validated. If the steady-state crosswind is at or above 12 knots, or if gusts exceed 12 knots, you are operating outside the airplane's tested envelope. The decision to go around or switch runways is not a failure — it is the correct application of your limits and the airplane's limits.
Gusts that exceed the demonstrated crosswind limit can cause loss of directional control, even if the steady-state wind is within limits.
A gust of 18–20 knots from a 280° direction on a runway aligned 222° creates a crosswind component that exceeds the demonstrated limit. The airplane's control authority — rudder, nosewheel steering, and aileron — may not be sufficient to maintain directional control during landing or rollout. The NTSB regional precedents (GAA17CA105, ERA17CA149, GAA16CA149, CHI02TA149) all show loss of directional control in gusting crosswind conditions. Recognize the gust factor and make the decision to go around or switch runways before you are committed to the landing.
The Piper Archer floats on landing — it is heavier and faster than a Warrior.
The Archer's gross weight is 2,550 lbs and its cruise speed is 125 KIAS. It carries more energy than a Warrior (2,300 lbs, 110 KIAS). On landing, the Archer will float if you reduce power too slowly or if the approach is too fast. The landing distance is longer. In crosswind conditions, a floating landing means more time in the air, more exposure to gusts, and more runway consumed. Plan for a longer landing distance and be prepared to go around if the approach is not stable by 300 ft AGL.
Recognize an unstable approach early and go around — do not try to salvage a bad landing.
An unstable approach is one in which the airplane is not aligned with the runway, the descent rate is not controlled, the airspeed is not stable, or the wind is pushing the airplane around. If you feel the airplane is not tracking the runway centerline smoothly, or if you are fighting the controls, the approach is unstable. The correct response is to go around immediately. At 300 ft AGL, you have enough altitude to execute a safe go-around. At 200 ft AGL, the margin is thin. At 100 ft AGL, you are committed. Do not wait until you are committed to recognize the problem.
Use forward slip technique to maintain alignment and control descent in crosswind conditions.
A forward slip — lowering the wing into the wind and applying opposite rudder to maintain heading — is a powerful tool for crosswind landings. The slip increases drag, slows the descent, and keeps the airplane aligned with the runway. The Piper Archer's control authority is sufficient for a forward slip at approach speeds (66 KIAS Vref). Practice this technique in calm conditions so you are comfortable with it when the wind is gusty.
Maintain directional control during rollout with firm rudder and nosewheel steering — but recognize when to go around.
During rollout, if a gust pushes the nose off the runway centerline, apply firm rudder and nosewheel steering to correct. However, if the airplane is veering off the runway edge at low speed (30–40 KIAS), the better decision is to have gone around earlier. A nose-over or wingtip strike during rollout is the outcome of a landing that should not have been attempted. Recognize the loss of control early and correct it — but the best correction is to have gone around before the landing became unstable.
Built from the real accident record
Scenario built from NTSB ERA10CA473 (2010 PA-28-181 crosswind landing loss of control), LAX08CA199 (2008 PA-28-181 bounced landing / directional control), CHI05CA208 (2005 PA-28-181 runway overrun / high DA), LAX04CA289 (2004 PA-28-181 hard landing / flare misjudgment), ERA10FA020 (2009 PA-28-181 wet runway loss of control — fatal), CEN23LA345 (2023 PA-28 fuel exhaustion / approach), and regional crosswind precedents GAA17CA105, ERA17CA149, GAA16CA149, CHI02TA149. Real events occurred at other airports — NOT at Tampa Executive (KVDF).
NTSB reports: ERA10CA473 · LAX08CA199 · CHI05CA208 · LAX04CA289 · ERA10FA020 · CEN23LA345 · GAA17CA105 · ERA17CA149 · GAA16CA149 · CHI02TA149
ACS tasks: PA.II.C — Takeoff and Departure · PA.III.A — Approaches, Landings, and Go-Arounds · PA.III.B — Crosswind Landings · PA.I.F — Weather Information · 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 Archer scenarios · More scenarios at KVDF