FlightEdge
Sample scenario-based training
SAMPLE SBTLanding / Approach

Crosswind Surprise on Short Final

A gusty approach to a narrow runway, directional control on the edge, and the decision to go around — or not

Piper Arrow · Albert Whitted Airport (KSPG) · Commercial · Landing / Approach

The scenario

Departing Albert Whitted Airport (KSPG), St. Petersburg, FL — Runway 07, a 3,676 ft asphalt strip at 7 ft MSL. You are a commercial pilot with roughly 350 hours total, 80 hours in the Piper Arrow. This is a local flight — a short hop to a nearby field and back. You are familiar with KSPG; you have landed here a dozen times.

It is a late-afternoon VFR flight in early summer. Surface wind is reported as 080° at 12 knots, gusting to 18. That is a direct crosswind to Runway 07 (true heading 062°). The gust is at the edge of your personal crosswind limit — you have trained to 15 knots steady, and gusts to 18 are beyond that. Visibility is 10 SM, scattered clouds at 3,500 ft. The tower is open and active (1400 local, within 0700–2100 operating hours).

You are on a 3-mile final approach to Runway 07, gear down (Vle 129 KIAS), flaps 20°, descending through 800 ft AGL at 90 KIAS. The runway is narrow — 3,676 ft long but only 75 ft wide. Off the left side of the runway (the upwind side in this crosswind) is dense development. Off the right side (downwind) is more development. Off the Runway 07 departure end (heading 062°) is open water — Tampa Bay. This is not a forgiving runway for a loss of directional control.

Aircraft: Piper PA-28R-200, solo, within weight and balance limits. Constant-speed prop, retractable gear, fuel-injected Lycoming IO-360. All systems normal. You have 4.5 hours of fuel on board.

Pilot: You — commercial pilot, current, 350 hours total, 80 hours Arrow time. Your crosswind training maxed out at 15 knots steady; you have not practiced in gusts above 15. You are current on landings but have not flown KSPG in the last two weeks. The gust forecast was not in your briefing — you did not check the latest ATIS before requesting the approach.

The decision

Before we get into the decision tree — what do you already know about crosswind landings in the Piper Arrow? (Pick all that apply; this records your baseline.)

What the record shows

What the NTSB files show

NTSB CEN12LA189 (2012): A Piper PA-28R-200 on an instructional flight drifted off the runway during landing flare in a crosswind gust and struck a ditch after an unsuccessful go-around attempt. The student pilot did not relinquish controls to the instructor, and the instructor's remedial action was delayed. The probable cause was the pilot's failure to maintain adequate crosswind correction during the landing flare and the instructor's delayed remedial action.

NTSB CEN10CA318 (2010): A Piper PA-28R-200 encountered a downdraft during final approach to a wet grass strip and drifted left during landing rollout; the left main landing gear struck concrete driveways and separated. The probable cause was the pilot's failure to maintain directional control during the landing roll.

NTSB CHI08LA137 (2008): A Piper PA-28R on a personal cross-country flight lost control during takeoff when a wind gust forced the nose up; the pilot's corrective input resulted in impact with bushes alongside the runway. The probable cause was the pilot's failure to maintain control during takeoff, with contributing factors including gusty wind conditions.

The local environment at KSPG makes this scenario particularly unforgiving: Runway 07 is only 75 ft wide. Off the left side (upwind in this crosswind) is dense development. Off the right side (downwind) is more development. Off the Runway 07 departure end (heading 062°) is open water — Tampa Bay. A loss of directional control during landing roll toward the departure end is a ditching, not a field landing. A loss of control toward the sides is a collision with development. There is no margin for error.

NTSB LAX89LA222 (1989, fatal): A Grumman AA-1C aborted an approach to Runway 07 and entered a low unstable pattern for Runway 36 in gusting crosswind conditions, stalled on final approach, and impacted the ocean short of the runway. The probable cause was the pilot's failure to maintain sufficient airspeed to prevent a stall at an altitude too low for recovery. The mechanism — low altitude, gusting winds, unstable approach, pilot trying to make the landing instead of going around — is the same trap that kills pilots in crosswind landings.

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), but these specific events happened elsewhere. The scenario is localized to KSPG to make the runway width, the off-field environment, and the crosswind challenge real and consequential for you as a student here.

The consistent thread across all these events: crosswind landings in gusty conditions are unforgiving. The first symptom of loss of control is a drift during the flare or landing roll — subtle at first, but escalating quickly. The fix is either (1) recognize the unstable approach and go around before the flare, or (2) maintain crosswind correction throughout the landing roll and catch any drift immediately. Waiting to see if you can handle it is waiting too long.

Key lesson — At KSPG Runway 07, a crosswind gust beyond your training envelope (12G18 knots when you trained to 15 steady) is a go-around condition. The runway is narrow (75 ft), the off-field environment is dense development on the sides and open water at the departure end, and a loss of directional control during the flare or landing roll is a serious accident. Recognize unstable approach conditions early and commit to a go-around. If you do land, maintain crosswind correction throughout the landing roll — do not relax until the airplane is stopped.

Debrief — teaching points

Gusty crosswinds beyond your training envelope are a go-around condition.

The Piper Arrow's demonstrated crosswind capability is typically 12–15 knots steady. Gusts beyond that are outside the tested envelope. At KSPG, a wind of 080° at 12G18 knots is a direct crosswind to Runway 07 with gusts at 18 knots — beyond your training limit of 15 steady. This is a go-around condition. Recognize it early, on short final or in the flare, and commit to a go-around. Trying to make the landing anyway is the failure mode of NTSB CEN12LA189 and LAX89LA222.

Crosswind correction must be maintained throughout the landing flare and roll.

In a crosswind landing, aileron and rudder correction must be held all the way to touchdown and throughout the landing roll. The flare is where most crosswind landing accidents happen — the pilot relaxes the correction as the airplane slows, and a gust during the flare causes a sudden drift. The landing roll is the second critical moment — directional control is maintained with rudder and nosewheel, and a loss of control during the roll can escalate into a swerve or groundloop. Do not relax until the airplane is stopped.

Vle (max gear-extended speed) is 129 KIAS — do not exceed it on approach.

The Piper Arrow's Vle is 129 KIAS. On approach with gear down, maintain airspeed below this limit. If you are approaching faster than 129 KIAS with gear down, you are risking gear damage or failure. Slow to 129 KIAS or below before lowering the gear, or lower the gear and reduce airspeed to below 129 KIAS before continuing the approach.

A go-around from short final requires immediate positive control and careful airspeed management.

A go-around from short final (below 500 ft AGL) is a critical maneuver. Advance the throttle to full power, pitch up to maintain airspeed (do not let the nose drop), and retract the gear once you are climbing at a safe rate. The airspeed must be maintained — Vs0 (stall, landing config) is 55 KIAS, and with gear and flaps down, you have limited margin. Focus on airspeed first, gear retraction second.

KSPG Runway 07 is narrow and surrounded by hazards.

Runway 07 at KSPG is 3,676 ft long but only 75 ft wide. Off the left side (upwind in a crosswind from 080°) is dense development. Off the right side (downwind) is more development. Off the departure end (heading 062°) is open water — Tampa Bay. A loss of directional control during the landing roll toward the sides is a collision with development. A loss of control toward the departure end is a ditching. There is no margin for error. Recognize this before you line up on Runway 07, and be ready to go around if the approach is unstable.

Built from the real accident record

Scenario built from NTSB CEN12LA189 (2012 PA-28R crosswind landing loss of control), CEN10CA318 (2010 PA-28R directional control failure on landing roll), CHI08LA137 (2008 PA-28R takeoff loss of control in gusty winds), and local-environment precedents LAX89LA222 (1989 AA-1C stall on final in gusting crosswind) and ERA10CA300 (2010 PA-18 stall on climbing turn). Anonymized and localized to KSPG.

NTSB reports: CEN12LA189 · WPR11CA107 · CEN10CA318 · CHI08LA137 · LAX89LA222 · ERA10CA300 · ATL92LA146

ACS tasks: PA.VII.A — Crosswind Approach and Landing · PA.VII.B — Slip to Land · PA.VII.C — Go-Around / Rejected Landing · PA.I.H — Human Factors · PA.II.A — Preflight Assessment

Relevant FARs: §91.3 · §91.13 · §91.209

Run this scenario yourself

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 Arrow scenarios · More scenarios at KSPG