Gusts on Short Final
Crosswind landing in a Piper Archer — recognizing when conditions exceed your limits and the cost of a delayed go-around decision
The scenario
Arriving Albert Whitted Airport (KSPG), St. Petersburg, FL — Runway 25 in use. Elevation 7 ft MSL. You are a Private pilot with 180 hours total, 45 hours in the Piper Archer. This is a local flight; you are familiar with KSPG.
Weather: VFR, scattered clouds at 3,500 ft, visibility 10 SM. Wind is reported from 280° at 12 knots, gusting to 18 knots. Runway 25 is aligned 242° (true). The crosswind component is roughly 10–12 knots steady, gusting to 16–18 knots. The Piper Archer's demonstrated crosswind capability is 12 knots. You are at the limit, and the gusts are exceeding it.
You are on a 5-mile final approach to Runway 25, descending through 800 ft AGL, airspeed 90 KIAS (slightly fast for approach). The tower has cleared you to land. You are hand-flying the approach; no autopilot. The wind is noticeably gusty — you are correcting with aileron and rudder, but the airplane is drifting. You have not yet committed to a go-around decision.
Aircraft: Piper PA-28-181 Archer, solo, within limits. Fixed gear, fixed-pitch prop, carbureted Lycoming O-360, 180 hp. Vref (approach speed) is 66 KIAS; best glide is 76 KIAS. The Archer is heavier and faster than a Warrior — it carries more energy into the landing, and a fast or high approach will float and consume runway.
Off-field environment: Off Runway 25's climb-out end (heading 242°) is dense development, medium development, and low-density development — buildings, roads, and scattered open space. An engine failure on the Runway 25 departure would be a forced landing in a built-up area. Off Runway 07's climb-out end (heading 062°) is open water — Tampa Bay. There is no alternate landing surface off Runway 07.
- {'label': 'Field', 'value': 'KSPG · Albert Whitted'}
- {'label': 'Runways', 'value': '7/25 · 18/36'}
- {'label': 'Elevation', 'value': '7 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 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 landed hard, bounced, and veered off the runway.
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 probable cause was 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 probable cause was the student pilot's misjudged landing flare and failure to maintain directional control during the landing rollout.
NTSB ERA10FA020 (2009, FATAL): A Piper PA-28-181 on a personal local flight landed fast and hard on a wet turf runway, 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.
NTSB GAA17CA105 (2016, regional precedent): 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 pilot continued to struggle with the approach rather than committing to a go-around early.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Albert Whitted Airport. KSPG has its own accident history (see field dominant patterns: LOSS_OF_CONTROL_INFLIGHT 20%, FORCED_LANDING 16.4%, LOSS_OF_CONTROL_GROUND 14.5%, DITCHING 12.7%, STALL_SPIN 12.7%), but these specific events happened elsewhere. The scenario is localized to KSPG to make the runway choice and off-field environment real and consequential for you as a student here.
The consistent thread across all these events: crosswind landings in the Piper Archer demand early decision-making. The Archer's demonstrated crosswind capability is 12 knots — that is the limit. Gusts exceeding that are a red flag. The Archer is heavier and faster than a Warrior; it carries more energy into the landing. A fast or high approach floats and consumes runway. The decision to go around should be made early — on base or early final — not on short final when energy is high and options are limited. If an approach becomes unstable (drifting, loss of directional control), the correct response is immediate go-around, not aggressive rudder input to 'save' the landing. A bounce at low altitude is not a second chance to land — it is a signal to go around.
Key lesson — In the Piper Archer, crosswind landings demand respect. The demonstrated crosswind capability is 12 knots; gusts exceeding that are beyond the airplane's tested limits. Recognize when conditions exceed your limits and commit to a go-around early — on base or early final — rather than fighting an unstable approach on short final. If you land hard and bounce, go around immediately; do not try to land again. The Archer is heavier and faster than a Warrior — it carries more energy into the landing. Vref is 66 KIAS; flying faster than Vref increases float and runway demand. At KSPG, Runway 25 (aligned 242°) is less favorable in a 280° wind than Runway 07 (aligned 062°). Know your runway options and request the favorable one early.
Debrief — teaching points
The Piper Archer's demonstrated crosswind capability is 12 knots — that is the limit.
The Archer's POH specifies a demonstrated crosswind component of 12 knots. This is the maximum the manufacturer has tested and certified. Gusts exceeding 12 knots are beyond the airplane's tested limits. At KSPG, a wind of 280° at 12G18 knots on Runway 25 (aligned 242°) produces a crosswind component of roughly 10–12 knots steady, gusting to 16–18 knots. The gusts exceed the demonstrated limit. This is a red flag. Recognize it early and make a conservative decision — request a more favorable runway or divert.
The Archer is heavier and faster than a Warrior — it carries more energy into the landing.
The Archer weighs 2,550 lbs gross; a Warrior weighs 2,450 lbs. More importantly, the Archer is faster. Vref (approach speed) is 66 KIAS; best glide is 76 KIAS. Flying faster than Vref on approach increases float and runway demand. A fast landing in the Archer will consume significant runway. At KSPG, Runway 25 is 3,676 ft long; Runway 07 is also 3,676 ft long. A fast landing that consumes 1,800 ft leaves only 1,876 ft for rollout. With aggressive braking, you can stop; without it, you risk overrun. Know your airplane's energy and plan accordingly.
The go-around decision should be made early — on base or early final — not on short final.
A go-around on base or early final (at 800 ft AGL or higher) is a simple maneuver: full power, flaps to 0°, climb. A go-around on short final (at 300 ft AGL or lower) is marginal — you have less altitude to work with and less time to recover. An unstable approach (drifting, loss of directional control, excessive airspeed) is a signal to go around early. Do not wait until you are committed to the landing. The NTSB LAX08CA199 case shows the cost: a student pilot who delayed the go-around decision and tried to recover from a bounced landing by landing again. The nose gear collapsed.
If you land hard and bounce, go around immediately — do not try to land again.
A bounce at low altitude (50 ft AGL or lower) is not a second chance to land — it is a signal that the approach was unstable and the landing was hard. The correct response is immediate go-around: full power, flaps to 0°, climb. Trying to land again after a bounce risks a second hard landing that can damage the nose gear, collapse the gear, or cause a loss of control. The NTSB LAX08CA199 case (2008 PA-28-181) and ERA10FA020 case (2009 PA-28-181, fatal) both show this sequence: hard landing, bounce, second hard landing, nose gear collapse or loss of control. Go around immediately.
Crosswind correction technique: land in a crab (nose into wind, fuselage drifting) and straighten just before touchdown.
The correct technique for a crosswind landing is to maintain a crab angle on approach — nose pointed into the wind, fuselage drifting across the runway. Just before touchdown (at 50 ft AGL or lower), lower the upwind wing and apply opposite rudder to align the fuselage with the runway. This results in a wings-level, straight landing. Do not try to align the fuselage with the runway on approach — that requires aggressive rudder input and can lead to loss of directional control. Accept the crab and straighten just before touchdown.
At KSPG, Runway 07 is more favorable than Runway 25 in a 280° wind.
KSPG has two runways: Runway 07/25 (aligned 062°/242°) and Runway 18/36 (aligned 180°/360°). In a 280° wind, Runway 07 (aligned 062°) is more favorable than Runway 25 (aligned 242°). The crosswind component for Runway 07 is roughly 4–5 knots; for Runway 25, it is roughly 10–12 knots. Request Runway 07 early if the wind is from the northwest. Off Runway 25 is dense development; off Runway 07 is open water. Know your runway options and request the favorable one.
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/runway excursion), CHI05CA208 (2005 PA-28-181 overrun/obstacles), LAX04CA289 (2004 PA-28-181 hard landing/loss of directional control), ERA10FA020 (2009 PA-28-181 wet runway loss of control, fatal), CEN23LA345 (2023 PA-28 fuel exhaustion/overrun), and regional crosswind-loss-of-control precedents GAA17CA105, ERA17CA149, GAA16CA149, CHI02TA149. Localized to KSPG.
NTSB reports: ERA10CA473 · LAX08CA199 · CHI05CA208 · LAX04CA289 · ERA10FA020 · CEN23LA345 · GAA17CA105 · ERA17CA149 · GAA16CA149 · CHI02TA149
ACS tasks: PA.I.F — Weather Information · PA.V.A — Preflight Inspection · PA.VII.A — Normal Approach and Landing · PA.VII.B — Forward Slip to a Landing · PA.VII.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 KSPG