Gusts on Short Final at Peter O Knight
Crosswind landing in gusty conditions — the decision to go around comes down to airspeed, altitude, and the point of no return
The scenario
Departing Peter O Knight Airport (KTPF), Tampa, FL — Runway 22 in use, elevation 8 ft MSL. You are a Private pilot with 280 hours total time, 45 hours in the Piper Archer. You have completed a 1.5-hour local flight and are now on approach to land.
Current conditions: VFR, scattered clouds at 2,500 ft, visibility 10 SM. Wind is from 310° at 14 gusting to 22 knots. Runway 22 is aligned 217° true (roughly southwest). The crosswind component is approximately 12–18 knots, depending on the gust. The Piper Archer's demonstrated crosswind capability is 12 knots. You are at the edge of the envelope, and the gusts are pushing you over it.
You are on a 3-mile final for Runway 22, 1,200 ft AGL, airspeed 90 KIAS (slightly fast for approach), descent rate 400 fpm. You have requested and received a landing clearance on Runway 22 from the CTAF (KTPF is non-towered, Class G). The runway is 3,583 ft long — plenty of room. Off the Runway 22 departure end (heading 217°), the off-field environment is open water — Tampa Bay. Off the Runway 04 end (heading 037°), the off-field environment is dense development.
Aircraft: Piper PA-28-181 Archer, solo, within weight and balance limits, full fuel. Carbureted Lycoming O-360, 180 hp, fixed-pitch prop, fixed gear, steam panel. Flaps are at 20°. You are configured for landing.
Pilot: You — Private pilot, 280 hours total, 45 hours Archer. You are current and have landed in crosswinds before, but never in gusts this strong. You are tired from a long day of flying and are eager to get on the ground. You have not flown this approach in gusty conditions.
- {'label': 'Field', 'value': 'KTPF · Peter O Knight'}
- {'label': 'Runways', 'value': '4/22 · 18/36'}
- {'label': 'Elevation', 'value': '8 ft'}
- {'label': 'Aircraft', 'value': 'PA-28-181'}
- {'label': 'Dominant phase', 'value': 'Landing / Approach'}
The decision
Before we get into the decision tree — what do you already 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 was damaged but the pilot survived.
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 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 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 event was fatal.
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 probable cause was the pilot's loss of directional control during the aborted landing in gusting crosswind conditions. The teaching point: recognize when crosswind conditions exceed aircraft capability and commit to go-around early rather than attempting recovery during rollout.
NTSB ERA11CA212 (2011): A Mooney M20J on a personal flight landed on runway 18 in a crosswind, veered 90 degrees left, departed the runway, struck a seawall, and came to rest nose-down in salt water. The probable cause was the pilot's failure to maintain directional control during a crosswind landing.
The real accidents cited above occurred at other airports and in other aircraft — NOT at Peter O Knight Airport. KTPF has its own accident history (see field dominant patterns: FORCED_LANDING 19.4%, LOSS_OF_CONTROL_INFLIGHT 16.7%, LOSS_OF_CONTROL_GROUND 11.1%, DITCHING 11.1%, STALL_SPIN 8.3%), but these specific events happened elsewhere. The scenario is localized to KTPF to make the off-field environment real and consequential for you as a student here.
The consistent thread across all these events: loss of directional control during landing in crosswind conditions. The Piper Archer's demonstrated crosswind capability is 12 knots. Gusts that exceed that limit, or a delayed go-around decision below 500 ft AGL, are the common failure modes. The decision to go around early — while you have altitude and climb performance — is the entire lesson.
Key lesson — The Piper Archer's demonstrated crosswind capability is 12 knots. When gusts exceed that limit, the go-around decision must be made early — above 500 ft AGL, with full climb performance available. Below 500 ft AGL in a marginal crosswind, the go-around becomes risky and the landing (even an off-runway excursion) becomes the safer option. Off Runway 22 at KTPF, the off-field environment is open water — a loss of directional control during landing rollout could result in a water strike. Respect the demonstrated limits and commit to the go-around early.
Debrief — teaching points
The Piper Archer's demonstrated crosswind capability is 12 knots — respect that limit.
The POH for the Piper PA-28-181 specifies a demonstrated crosswind capability of 12 knots. This is not a suggestion; it is the limit beyond which the airplane may not be controllable. When the wind is 310° at 14 gusting 22 knots and the runway is aligned 217°, the crosswind component is 12–18 knots — at or exceeding the limit. Gusts that push the crosswind beyond 12 knots are a go-around trigger. Do not press your luck.
The go-around decision window closes at 500 ft AGL.
Below 500 ft AGL in a marginal crosswind, the go-around becomes risky. The airplane is slow, the climb performance is marginal, and the crosswind is still pushing. An attempted go-around from 300 ft AGL in a steep bank and a crosswind can result in a stall/spin. Above 500 ft AGL, you have altitude and climb performance. Make the go-around decision early, while you have options. Once you are below 500 ft AGL, the landing (or the excursion) is the safer outcome.
A bounced landing in a crosswind can lead to loss of directional control and runway excursion.
The NTSB LAX08CA199 and LAX04CA289 cases both involved bounced landings followed by loss of directional control. A bounced landing means the airplane is back in the air, slow, and vulnerable to a gust. The left wing lifts, the nose yaws, and the airplane veers off the runway. Maintain crosswind correction through the entire landing — flare, touchdown, rollout. Do not relax the controls until the airplane is fully on the ground and slowing.
Approach speed matters — landing fast means floating and using more runway.
Vref (approach speed) for the Piper Archer is 66 KIAS. Landing at 90 KIAS means the airplane will float, use more runway, and be harder to control in a crosswind. Slow to Vref on approach. The slower you are on touchdown, the less energy you have and the easier the crosswind is to manage.
Off Runway 22 at KTPF, the off-field environment is open water — a forced landing there is a ditching.
The off-field environment off Runway 22's departure end (heading 217°) is open water — Tampa Bay. A loss of directional control during landing rollout that sends the airplane off the runway in that direction could result in a water strike. This is not hypothetical; it is the NLCD ground cover off that runway end. Know the off-field environment before you line up on the runway.
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), LAX04CA289 (2004 PA-28-181 misjudged flare/runway excursion), ERA10FA020 (2009 PA-28-181 wet runway loss of control), and regional precedents GAA17CA105 (PA-46 crosswind loss of control), CHI02TA149 (A185F wind gust/directional control), and ERA11CA212 (M20J crosswind veer/seawall). Localized to KTPF.
NTSB reports: ERA10CA473 · LAX08CA199 · CHI05CA208 · LAX04CA289 · ERA10FA020 · CEN23LA345 · GAA17CA105 · CHI02TA149 · GAA17CA021 · ERA11CA212
ACS tasks: PA.II.E — Approach and Landing · PA.II.F — Go-Around / Rejected Landing · PA.I.F — Weather Information · PA.I.H — Human Factors · PA.IX.C — Emergency Approach and Landing
Relevant FARs: §91.3 · §91.13 · §91.209
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 KTPF