Gusts Over Tampa Bay

Departing Peter O Knight Airport (KTPF), Tampa, FL — Runway 22, a 3,583 ft asphalt runway oriented 217° magnetic. Elevation 8 ft MSL. You are on a local VFR flight, solo, 2.5 hours of fuel. The field is non-towered (CTAF); you self-announce on 122.95.

It is a warm, humid afternoon in late spring. OAT 29°C, dew point 24°C, altimeter 29.94. Scattered clouds at 2,500 ft, visibility 10 SM. The wind is from 260° at 12 knots, gusting to 18 knots — a crosswind for Runway 22 (heading 217°). The crosswind component is roughly 10–12 knots steady, with gusts adding 4–6 knots of additional crosswind energy. The demonstrated crosswind capability for the PA-28-180 is 12 knots. You are at the edge of the envelope, and the gusts are pushing into the red.

You have been flying for 2.5 hours. The flight was smooth; you are not fatigued. You have 200 hours total time, 80 hours in the PA-28-180. You are current and proficient. This is a routine local flight — nothing unusual planned. You are planning to land on Runway 22 and return to the field for dinner.

Aircraft: Piper PA-28-180, solo, 2,400 lbs gross weight, within limits. Lycoming O-360-A carbureted engine, fixed-pitch prop, fixed gear, left/right fuel selector (currently on LEFT tank, which has 45 minutes of fuel remaining). Steam panel with vacuum-driven attitude indicator and turn coordinator. Nothing was written up; the airplane is airworthy.

Pilot: you — a Private pilot, current, 200 hours total, 80 hours in type. You have landed in crosswinds before, but not often in gusts this strong. You are not uncomfortable, but you are not experienced in this exact condition either. You have not briefed the crosswind limits or the go-around criteria for this flight.

NTSB CEN09CA208 (2008): A Piper PA-28-180 made a hard landing after ballooning and becoming airborne again. The pilot's improper flare during landing resulted in a bounced landing. The nose landing gear collapsed and the wing main spar was damaged. The probable cause was the pilot's improper flare technique — pulling back too aggressively in response to a gust or approach instability, causing the airplane to balloon.

NTSB LAX08CA035 (2007): A Piper PA-28-180 encountered a downdraft on approach and landed hard and short of the runway. The pilot misjudged distance and altitude, leading to an undershoot and hard landing. On the return flight to the home base airport, the left wheel and strut were damaged. The probable cause was the pilot's misjudged distance and altitude.

NTSB DFW07CA213 (2007): A Piper PA-28 experienced thermal lift upon crossing the runway threshold and drifted off-center due to crosswind, resulting in a hard landing on the nose gear and a nose-over. The probable cause was the pilot's failure to compensate for existing wind conditions during landing. A contributing factor was the crosswind itself.

NTSB NYC04CA091 (2004): A Piper PA-28-180 flown by a student pilot on her first unsupervised solo flight made a high approach and hard landing. The aircraft bounced, porpoised, and the propeller struck the runway, causing nose gear collapse. The probable cause was the student pilot's failure to recover from the bounced landing, with a contributing factor being lack of solo flight experience.

NTSB ERA11CA212 (2011): A Mooney M20J on a personal flight landed in a crosswind, veered 90 degrees, 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. This is the exact scenario — loss of directional control during landing rollout in crosswind conditions — that the scenario models.

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 did not recognize the exceedance early enough and attempted to recover during rollout instead of going around. The lesson: recognize when crosswind conditions exceed aircraft capability and commit to go-around early.

NTSB CHI02TA149 (2002): A Cessna A185F operated by the Wisconsin Department of Natural Resources veered off the runway during landing rollout when a wind gust forced the aircraft into an uncontrollable turn. The probable cause was directional control not being maintained, with gusting winds as a contributing factor. The lesson: understand how a sudden gust can overwhelm directional control during rollout.

The real accidents cited above occurred at other airports and in other aircraft — NOT at Peter O Knight Airport (KTPF). 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%), 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. Off Runway 22's departure end, the off-field environment is open water — Tampa Bay. A loss of directional control during landing rollout could result in a veer into the water, exactly as documented in ERA11CA212.

The consistent thread across all these events: crosswind gusts can exceed the demonstrated crosswind capability of the aircraft, overwhelming directional control during landing rollout. The pilot's failure to recognize the exceedance early and commit to a go-around is the critical error. The recovery — once directional control is lost — requires immediate, aggressive opposite rudder and aileron. But the better decision is to go around before the approach becomes unstable.