Gusts on Short Final
Crosswind landing in deteriorating conditions — the Archer is fast, the runway is narrow, and the wind is turning ugly
The scenario
Departing St. Petersburg Clearwater International Airport (KPIE), Pinellas Park, FL — Runway 18, a 9,730 ft concrete runway. Elevation 11 ft MSL. You are on approach to land after a local flight; the wind has picked up and is now gusting.
Current conditions: VFR, visibility 10 SM, scattered clouds at 2,500 ft. Wind is reported by tower as 180° at 12 knots, gusting to 18 knots. Runway 18 is aligned 171° true. The crosswind component is roughly 10–12 knots steady, with gusts pushing 15–17 knots. The Archer's demonstrated crosswind capability is 12 knots. You are at the limit, and the gusts are pushing beyond it.
You are on a 3-mile final approach to Runway 18, descending through 800 ft AGL at 76 KIAS (best glide speed / approach speed). The runway is in sight. The tower has cleared you to land. You have flaps at 20°. The wind is noticeably pushing the airplane; you are maintaining a crab angle of roughly 8–10° to track the runway centerline. The approach feels stable but requires active correction.
Aircraft: Piper PA-28-181 Archer, solo, full fuel, within limits. Fixed gear, fixed-pitch prop, carbureted Lycoming O-360, 180 hp. Steam panel, vacuum-driven instruments. Fuel selector on LEFT tank (you switched from RIGHT at the start of descent). Nothing was written up; the airplane is airworthy.
Pilot: you — a Private pilot, current, roughly 250 hours total. You have landed at KPIE several times. You are familiar with the runway and the local wind patterns. You did not brief a go-around decision; you are committed to landing. The wind is at the edge of your comfort zone, but you have landed in similar conditions before.
- {'label': 'Field', 'value': 'KPIE · St. Petersburg Clearwater'}
- {'label': 'Runways', 'value': '4/22 · 18/36'}
- {'label': 'Elevation', 'value': '11 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 already know about crosswind landings in the 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 was damaged but the pilot survived.
NTSB LAX08CA199 (2008): A Piper PA-28-181 student pilot on solo flight was vectored to Runway 22R 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. The nose gear collapsed and the firewall was damaged. 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 his failure to maintain directional control during the landing rollout. The 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. The pilot was fatally injured.
NTSB GAA17CA105 (2016): 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's loss of directional control during the aborted landing in gusting crosswind conditions was the probable cause. The key lesson: recognize when crosswind conditions exceed aircraft limits and commit to go-around early rather than fighting deteriorating control during rollout.
NTSB ERA17CA149 (2017): A North American T-6G landed hard during a go-around attempt in gusting crosswind conditions; the right wingtip contacted the runway, the aircraft pivoted right, and nosed over. The probable cause was the pilot's failure to maintain directional control during the landing roll and go-around in gusting wind conditions. The lesson: maintain crosswind correction technique through rollout and recognize when to commit to go-around; understand that go-around itself can be unstable in gusts if airspeed is marginal.
The real accidents cited above occurred at other airports and in other aircraft types — NOT at St. Petersburg Clearwater International Airport (KPIE). KPIE has its own accident history (see field dominant patterns: LOSS_OF_CONTROL_INFLIGHT 21.2%, LOSS_OF_CONTROL_GROUND 15.2%, STALL_SPIN 12.1%, GEAR_UP_LANDING 9.1%, OBSTACLE_ON_TAKEOFF_LANDING 9.1%), but these specific crosswind/loss-of-control events happened elsewhere. The scenario is localized to KPIE to make the runway geometry and off-field environment real and consequential for you as a student here.
The consistent thread across all these events: the Archer is a heavier, faster airplane than a Warrior. A fast or high approach floats and eats runway. In crosswind conditions, a crab angle on short final must be removed — either by a forward slip or by a go-around. A misjudged flare, a hard landing, or a bounced landing in a crosswind can result in loss of directional control and a runway excursion. The decision to go-around early — before the flare — is always the safer choice when conditions are deteriorating or control feels marginal.
Key lesson — The Archer's demonstrated crosswind capability is 12 knots. Gusts beyond that are outside the airplane's tested envelope. On approach in gusty crosswind conditions, make a go-around decision early — not in the flare. If you continue the approach, use a forward slip to remove the crab angle and align the fuselage with the runway before the flare. A misjudged flare or a hard landing in a crosswind can result in loss of directional control and a runway excursion. Know your limits and respect them.
Debrief — teaching points
The Archer's demonstrated crosswind capability is 12 knots — gusts beyond that are outside the tested envelope.
The Archer's POH specifies a demonstrated crosswind capability of 12 knots. This is the maximum crosswind component the airplane has been tested and proven to handle safely. Wind gusts that push the crosswind component beyond 12 knots are outside the airplane's tested envelope. When tower reports wind 180° at 12 knots gusting to 18 knots, and Runway 18 is aligned 171°, the steady crosswind is roughly 10–12 knots, but the gusts are pushing 15–17 knots. You are at the limit on average and beyond it in the gusts. This is not a comfortable margin.
Make a go-around decision early — not in the flare.
If crosswind conditions are deteriorating or control feels marginal on approach, the go-around decision should be made early — ideally by 500 ft AGL on short final. Once you are in the flare (below 50 ft AGL), a go-around becomes unstable and risky: you are low on altitude, the airplane is slow, and the wind gusts are most disruptive near the ground. The safest go-around is the one you execute before you are committed to landing. If you are uncomfortable with the wind on final approach, go around. The runway will still be there for another attempt.
Use a forward slip to remove the crab angle and align the fuselage with the runway.
In a crosswind landing, a crab angle (nose pointed into the wind) must be removed before touchdown. The correct technique is a forward slip: lower the wing into the wind and apply opposite rudder to align the fuselage with the runway. The slip should be established by 300 ft AGL on short final, giving you time to stabilize the approach and verify the fuselage is aligned before the flare. A forward slip is not a comfortable landing attitude, but it is the correct technique. Do not attempt to remove the crab angle in the flare — that is too late and too unstable.
A misjudged flare or hard landing in a crosswind can result in loss of directional control and a runway excursion.
The Archer is heavier and faster than a Warrior. A fast or high approach floats and eats runway. If the approach is fast and the flare is misjudged, the airplane can stall and drop hard onto the runway. A hard landing in a crosswind can cause the nose gear to come down while the fuselage is still crabbed, resulting in loss of directional control and a veer off the runway. The real-world precedent (NTSB LAX08CA199, 2008) involved a bounced landing and loss of directional control; the nose gear collapsed and the firewall was damaged.
Respect the demonstrated crosswind limit — it is not a suggestion.
The demonstrated crosswind capability is the result of flight testing by the manufacturer. It is not a suggestion or a guideline; it is the limit of the airplane's tested performance. When conditions exceed that limit, the airplane's behavior becomes unpredictable. The real-world precedent (NTSB GAA16CA149, 2016) involved a pilot who exceeded the aircraft's maximum demonstrated crosswind component of 13 knots during both takeoff and landing, resulting in loss of directional control and a noseover. Know your airplane's limits and respect them.
Density altitude erodes the Archer's climb performance — a go-around in high density altitude may be marginal.
The Archer is heavier and faster than a Warrior, but it is not a high-performance airplane. In high density altitude conditions (warm temperature, high elevation, high humidity), the Archer's climb performance is significantly reduced. A go-around in high density altitude may be marginal — the airplane may not climb at a safe rate. This is another reason to make the go-around decision early, while you still have altitude and airspeed. If you are uncomfortable with the approach, go around while you still have a comfortable margin.
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 turf), CEN23LA345 (2023 PA-28 fuel exhaustion / landing overrun), and regional crosswind precedents GAA17CA105, ERA17CA149, GAA16CA149, CHI02TA149. Localized to KPIE.
NTSB reports: ERA10CA473 · LAX08CA199 · CHI05CA208 · LAX04CA289 · ERA10FA020 · CEN23LA345 · GAA17CA105 · ERA17CA149 · GAA16CA149 · CHI02TA149
ACS tasks: PA.I.F — Weather Information · PA.III.A — Preflight Inspection · PA.III.B — Cockpit Management and Automation · PA.IV.A — Normal Takeoff and Climb · PA.IV.C — Forward Slip to a Landing · PA.V.A — Approach and Landing · PA.V.B — 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 KPIE