Gusts on Final to Runway 22
Crosswind landing in gusty conditions — when to commit to the approach, when to go around, and how the Archer's weight and momentum work against you
The scenario
Departing Venice Municipal Airport (KVNC), Venice, FL — Runway 22, on a local VFR flight. Elevation 18 ft MSL. You are a Private pilot with 180 hours total, 40 hours in the Piper Archer. You are current and comfortable in this airplane.
It is a Saturday afternoon in late spring. Surface wind is reported from 180° at 12 knots, gusting to 18 knots. Runway 22 has a true heading of 225°. The wind is roughly 45° off the runway heading — a crosswind component of approximately 9–13 knots, depending on the gust. The Archer's demonstrated crosswind capability is 12 knots. You are at the edge of limits, and the gusts are pushing you over.
You are on a 3-mile final to Runway 22, descending through 500 ft AGL, airspeed 76 KIAS (best glide / approach speed), flaps 20°. The runway is in sight. You are configured for landing. The wind is gusting noticeably — the wings are being pushed left (north) by each gust, and you are correcting with right aileron and right rudder to stay aligned with the runway.
Aircraft: Piper PA-28-181 Archer, solo, within weight and balance limits, fuel adequate. Fixed gear, fixed-pitch prop, carbureted Lycoming O-360-A, 180 hp. Flaps 20°, landing gear down and locked, mixture rich, fuel selector on RIGHT (the tank you've been using). Descent rate 400 fpm, stable approach.
Pilot: you — Private pilot, 180 hours, 40 hours Archer time. You have landed in crosswinds before, but not in gusts this strong. You have not established a personal crosswind limit. You are committed to this landing.
- {'label': 'Field', 'value': 'KVNC · Venice'}
- {'label': 'Runways', 'value': '4/22 · 13/31'}
- {'label': 'Elevation', 'value': '18 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-181'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before we get into the decision tree — what do you know about crosswind landings in the Archer and when to go around? (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 veered off the runway and struck the ground.
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 CHI05CA208 (2005): A Piper PA-28-181 on a personal flight overran a grass runway and struck a utility pole during landing. The accident resulted from the pilot's delayed decision-making, excessive approach airspeed, and failure to execute a go-around. Contributing factors included high density altitude and obstacles near the runway.
NTSB LAX04CA289 (2004): A Piper PA-28-181 on a student instructional flight experienced a hard landing and runway excursion at Scottsdale Airport. The accident resulted from the student pilot's misjudged landing flare and failure to maintain directional control during the landing rollout. 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 was a fatal accident.
NTSB CEN23LA345 (2023): A Piper PA-28-181 on a student solo cross-country flight experienced fuel exhaustion during approach to an alternate airport after the student pilot failed to visually verify fuel quantity before departure. The engine lost power during approach, resulting in a forced landing with runway overrun.
Regional crosswind precedents (GAA17CA105, ERA21LA119, GAA19CA170, ERA10CA448) show a consistent pattern: pilots attempt landings in crosswind conditions that exceed demonstrated capability, fail to recognize when the approach is unstable, and do not commit to a go-around early enough. The result is loss of directional control during landing, runway excursion, and often a nose-over or collision with obstacles.
The consistent thread: the Archer's demonstrated crosswind capability is 12 knots. Gusts that exceed that limit, or a mean wind near the limit with gusts above it, create a situation where control authority is marginal. The pilot's personal limits should be lower than demonstrated capability — perhaps 10 knots for a pilot with 40 hours in the airplane. When the approach is unstable (increasing drift, aggressive corrections, or a gust-induced wing lift that cannot be corrected), the correct decision is to go around — not to try to recover during the landing. A go-around at 300 ft AGL is safe and clean. A loss of directional control at 20 ft AGL is not.
The real accidents cited above occurred at other airports — NOT at KVNC. KVNC has its own accident history (see field dominant patterns: LOSS_OF_CONTROL_INFLIGHT 24.4%, FORCED_LANDING 12.2%, SPATIAL_DISORIENTATION 12.2%, HARD_LANDING 12.2%, LOSS_OF_CONTROL_GROUND 12.2%), but these specific NTSB cases happened elsewhere. The scenario is localized to KVNC to make the decision points real and consequential for you as a student here.
Key lesson — The Archer's demonstrated crosswind capability is 12 knots. Establish a personal crosswind limit lower than that — perhaps 10 knots — based on your experience and comfort level. When you are on approach and the wind is gusting, evaluate whether the crosswind component (accounting for gusts) exceeds your personal limit. If it does, or if the approach becomes unstable (increasing drift, aggressive corrections, or loss of alignment), commit to a go-around early — at 300–500 ft AGL, when you have altitude and energy. A go-around is not a failure; it is the correct decision. Do not attempt to recover from an unstable approach during the landing rollout. A bounced landing, a loss of directional control, or a nose-over are the outcomes of trying to land an unstable approach. The alternative — a go-around followed by another approach in improved conditions, or a diversion to an alternate airport — is always the safer choice.
Debrief — teaching points
Demonstrated crosswind capability is not a personal limit.
The Archer's demonstrated crosswind capability is 12 knots — that is the maximum the manufacturer tested. But demonstrated capability is not the same as personal minimums. Your skill, experience, airplane familiarity, and comfort level may require a lower personal limit. A Private pilot with 40 hours in the Archer might set a personal limit of 10 knots. A commercial pilot with 500 hours might be comfortable at 12 knots. Know your limit before you depart. If the forecast wind exceeds your personal limit, choose a different runway or divert to an alternate.
Gusts are sudden increases in wind speed — they exceed the mean wind.
When the surface wind is reported as '180° at 12 kt, gusting to 18 kt,' the mean wind is 12 knots and the gust is 18 knots. The crosswind component during the gust is higher than the crosswind component of the mean wind. If the mean wind gives you a 9 kt crosswind and the gust adds 6 knots, the crosswind component during the gust is 15 knots — exceeding demonstrated capability. Plan for the gust, not the mean wind.
An unstable approach is a go-around.
If you are on final approach and the wind is pushing you around, if your corrections are increasing rather than decreasing, if a gust causes loss of alignment that you cannot quickly correct, or if you are drifting left or right of the runway centerline — these are signs of an unstable approach. The correct response is to go around. A go-around at 300 ft AGL is safe and clean. A loss of directional control at 20 ft AGL is not. Commit to the go-around early, before you are committed to landing.
A bounced landing is not a second chance to land — it is a go-around.
If the airplane bounces on touchdown, do not attempt to land it again from the bounced state. The airplane is at 20–50 ft AGL, in a compromised state, and the wind is still present. The correct response is to go around: advance the throttle to full power, retract flaps to 0°, and climb out. A go-around from a bounce is tight, but the Archer has enough power to climb out from 20 ft AGL. The alternative — trying to land the airplane again from a bounced state — often results in a nose-over or runway excursion.
Flap reduction improves control authority in gusts.
In gusty crosswind conditions, reducing flaps from 20° to 10° reduces the wing's surface area and thus the gust-induced lift. The approach becomes more stable and the controls feel more responsive. However, flap reduction increases airspeed and landing distance. Use flap reduction as a tactical adjustment to improve control authority, but understand the trade-off: you will land farther down the runway. If the runway is short or obstacles are near the runway end, flap reduction may not be the right choice.
A fast approach means a long landing distance and more energy to dissipate.
The Archer's best glide speed is 76 KIAS. Landing at 85 KIAS or 90 KIAS gives you better control response in gusts, but you will land farther down the runway and have more energy to dissipate with brakes. At KVNC, Runway 22 is 5,000 ft long — plenty of runway for a fast landing. But at a shorter runway, a fast approach might consume too much runway. Plan your approach speed based on the runway length and your comfort level.
Directional control during rollout is critical — use differential braking and rudder.
After touchdown, the crosswind is still present. Use differential braking (more brake on the upwind wheel) and rudder input to maintain alignment with the runway centerline. The Archer's fixed gear and fixed-pitch prop mean you cannot reduce drag quickly — brakes are your primary deceleration tool. Apply brakes smoothly and use differential braking to manage the crosswind during rollout.
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/loss of directional control), CHI05CA208 (2005 PA-28-181 runway overrun/delayed go-around decision), LAX04CA289 (2004 PA-28-181 misjudged flare/hard landing), ERA10FA020 (2009 PA-28-181 loss of directional control on wet runway — fatal), CEN23LA345 (2023 PA-28-181 fuel exhaustion/landing overrun), and regional crosswind precedents GAA17CA105, ERA21LA119, GAA19CA170, ERA10CA448. Localized to KVNC.
NTSB reports: ERA10CA473 · LAX08CA199 · CHI05CA208 · LAX04CA289 · ERA10FA020 · CEN23LA345 · GAA17CA105 · ERA21LA119 · GAA19CA170 · ERA10CA448
ACS tasks: PA.I.F — Weather Information · PA.III.A — Preflight Preparation · PA.III.B — Preflight Procedures · PA.IV.A — Normal Takeoff and Climb · PA.IV.B — Normal Approach and Landing · PA.IV.C — Go-Around / Rejected 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 Archer scenarios · More scenarios at KVNC