Gusts on Final — Crosswind Limits and the Go-Around Decision
A Piper Archer in gusty crosswind conditions: recognize the limits, commit early, or lose directional control on rollout
The scenario
Departing Tampa North Aero Park Airport (X39), Tampa, FL — Runway 14, landing in gusty crosswind conditions. Elevation 68 ft MSL. The field is non-towered (CTAF 122.8); you are in Class G airspace below 3,000 ft MSL. Above 3,000 ft MSL, you are in the overlying Tampa Class B airspace (3,000–10,000 MSL).
It is a late-afternoon VFR flight on a breezy Florida day. Surface wind is reported 180° at 12 knots, gusting to 18 knots. Runway 14 is aligned 141° true. The crosswind component is roughly 10 knots steady, with gusts pushing it to 16 knots — near or exceeding the Piper Archer's demonstrated crosswind capability of 12 knots. Visibility 10 SM, scattered clouds at 2,500 ft, no precipitation. The air is smooth at altitude but turbulent in the surface layer.
You are on a 3-mile final to Runway 14, descending through 800 ft AGL at 76 KIAS (best glide / approach speed). The airplane is stable, flaps are at 25°, and the runway is made. As you descend through 500 ft AGL, the wind gusts noticeably. The left wing lifts slightly; you correct with right aileron and a touch of right rudder. The airplane settles. You are committed to the landing.
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 (you switched from RIGHT on downwind). Nothing was written up; the airplane is airworthy.
Pilot: you — a Private pilot, current, roughly 250 hours total. You have landed at X39 twice before in calm conditions. You have not practiced crosswind landings in conditions this gusty. Your personal crosswind limit is 10 knots; the conditions are at or above that limit.
- {'label': 'Field', 'value': 'X39 · Tampa North Aero Park'}
- {'label': 'Runways', 'value': '14/32'}
- {'label': 'Elevation', 'value': '68 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-181'}
- {'label': 'Dominant phase', 'value': 'Takeoff / Landing'}
The decision
Before we get into the decision tree — what do you know about crosswind landings in the Piper Archer? (Pick all that apply; this records your baseline.)
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 the pilot's inadequate compensation for crosswind conditions. The airplane sustained damage but the occupants were not seriously injured.
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 the student pilot's inadequate recovery from the bounced landing and failure to maintain directional control.
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 the student pilot's misjudged flare, resulting in a stall and hard landing, and failure to maintain directional control. The pilot's improper recovery from a bounced landing was a contributing factor.
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 the pilot's loss of directional control while landing on a wet runway, which resulted in a runway excursion and collision with a tree. This accident was fatal.
The consistent thread across all these PA-28-181 accidents: loss of directional control during landing, often in gusty or crosswind conditions, often after a bounced or firm landing, often because the pilot did not maintain crosswind correction throughout the rollout or did not recognize when the approach was unstable and commit to a go-around early.
At Tampa North Aero Park Airport (X39), the off-field environment off Runway 14 is medium development, low-density development, and wooded wetland — not a safe landing area if you veer off the runway. The runway is 3,541 ft long, which is adequate for a normal landing, but only if you stay on it. The real accidents cited above occurred at other airports — NOT at X39. But the scenario is localized to X39 to make the off-field environment real and consequential for you as a student here.
The lesson: recognize your personal crosswind limit (lower than the airplane's demonstrated limit), recognize when the approach is unstable or the crosswind is gusting above your limit, and commit to the go-around while you have altitude and control. Once you are on the ground in a crosswind, directional control is harder to recover. Once you are in a steep bank at low altitude, recovery is not possible.
Key lesson — The Piper Archer's demonstrated crosswind capability is 12 knots — that is the limit tested by the manufacturer. Your personal crosswind limit should be lower, based on your experience and the conditions. If the crosswind is gusting above the demonstrated limit, or if you are not comfortable with the conditions, execute a go-around on final approach while you have altitude and control. Once you are on the ground, directional control is harder to recover. Once you are in a steep bank at low altitude, recovery is not possible. Recognize the limits, commit early, or lose directional control on rollout.
Debrief — teaching points
The Piper Archer's demonstrated crosswind capability is 12 knots — that is a ceiling, not a target.
The Archer's POH states a demonstrated crosswind capability of 12 knots. This is the maximum crosswind the airplane was tested to handle during certification. It is not a recommendation; it is a limit. Your personal crosswind limit should be lower, based on your experience, the turbulence, the runway length, and the conditions. A 12-knot steady wind with gusts to 18 knots means the crosswind component is gusting above the demonstrated limit. That is a signal to go around or choose a different runway.
Recognize when the approach is unstable and commit to the go-around early.
An unstable approach is one in which the airplane is not in a stable descent, the airspeed is not stable, the descent rate is not stable, or the airplane is not aligned with the runway. In gusty crosswind conditions, an unstable approach is a warning sign. If you are correcting for wind gusts on final approach, or if the airplane is not tracking the runway centerline, or if the descent rate is changing, the approach is unstable. Commit to the go-around while you have altitude and control — before you are committed to landing. Once you are below 500 ft AGL in a crosswind, your options are limited.
Maintain crosswind correction throughout the landing rollout.
Crosswind correction in the Archer is done with aileron (to keep the upwind wing down) and rudder (to keep the nose aligned with the runway). This correction must be maintained throughout the landing rollout, not just during the approach and flare. As the airplane decelerates, the wind has less effect, but it does not disappear. Continue to hold aileron and rudder correction until the airplane is slow enough that the wind cannot push it around — typically below 20 KIAS. Do not relax the controls early.
If the landing bounces, a go-around is often the safest recovery.
A bounced landing in a crosswind is a dangerous situation. The airplane has excess airspeed and energy, and directional control is compromised. The instinct to 'land it again' on the second touchdown is often wrong. If the landing bounces in a crosswind, advance the throttle to full power, retract flaps to 0°, and climb out. Circle back and land again in better conditions or on a different runway. The real NTSB LAX08CA199 (2008 PA-28-181) pilot tried to recover from a bounced landing in a crosswind and lost directional control, collapsing the nose gear. A go-around would have been the safer choice.
Recognize that technique adjustments (reduced flaps, extra airspeed) have limits.
Some pilots try to handle crosswind conditions by reducing flaps or increasing approach airspeed. These techniques can help, but they have limits. Reducing flaps increases approach speed and can improve control authority, but it also increases landing distance. Increasing airspeed gives more control authority but also increases landing distance and energy. In gusty crosswind conditions that exceed your personal limit, these adjustments are not enough. The correct response is to go around or choose a different runway.
At X39, off-field environment off Runway 14 is not suitable for a forced landing.
The off-field environment off Runway 14's departure end (heading 141°) is medium development, low-density development, and wooded wetland. This is not a safe landing area if you veer off the runway or lose directional control. The runway is 3,541 ft long, which is adequate for a normal landing, but only if you stay on it. If you lose directional control during the rollout and veer off the runway, you may strike obstacles, trees, or ditches. The runway itself is your safety margin — stay on it.
Built from the real accident record
Scenario built from NTSB ERA10CA473 (2010 PA-28-181 crosswind stall/hard landing), LAX08CA199 (2008 PA-28-181 bounced landing / directional control loss), CHI05CA208 (2005 PA-28-181 runway overrun / excessive airspeed), 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, ERA21LA119, GAA19CA170, ERA10CA448. Localized to Tampa North Aero Park Airport (X39).
NTSB reports: ERA10CA473 · LAX08CA199 · CHI05CA208 · LAX04CA289 · ERA10FA020 · CEN23LA345 · GAA17CA105 · ERA21LA119 · GAA19CA170 · ERA10CA448
ACS tasks: PA.II.E — Approach and Landing · PA.II.F — Go-Around / Rejected Landing · PA.I.H — Human Factors · PA.IX.C — Emergency Approach and Landing
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 X39