Float and Overshoot at Tampa International

Departing Tampa International Airport (KTPA), Tampa, FL — Runway 19R, landing after a local VFR flight. Elevation 26 ft MSL; the runway is 11,002 ft long, the longest at KTPA. Runway 19R's heading is 182° true (southbound). You are approaching from the north.

It is a clear afternoon in early summer: OAT 31°C, dew point 18°C, altimeter 29.98. Light and variable winds, reported as 180° at 4 kt — nearly aligned with Runway 19R. Visibility 10 SM. A textbook VFR day. KTPA tower is active 24 hours; you are in Class B airspace (ceiling 10,000 ft MSL). The approach is stable and the weather is not a factor.

You are on a 3° glide slope, 500 ft AGL, descending at 500 fpm on a 182° heading toward Runway 19R. Airspeed is 70 KIAS — slightly above Vref (62 KIAS short-field, full flaps) — and you are not yet at full flaps. The runway is long and straight ahead. You have been flying the C172R for 180 hours total; this is your first landing at a major airport like KTPA. You are current and within your personal minimums, but KTPA's size and the Class B environment are new.

Aircraft: Cessna 172R, solo, within limits. Fuel-injected Lycoming IO-360-L2A, fixed-pitch prop, fixed gear, steam panel. Nothing was written up; the airplane is airworthy. You are configured for landing: 10° flaps, mixture rich, boost pump on, trim set for approach.

Pilot: you — a Private pilot, current, roughly 180 hours total. You have landed at smaller regional airports (Class D, uncontrolled) but never at a Class B major hub like KTPA. Your CFI is not on board; this is a solo cross-country. You have been cleared to land on Runway 19R by tower.

NTSB CEN24LA263 (2024): A Cessna 172R performed a power-off 180° maneuver and landed too high on the runway. The pilot was unable to stop within the remaining distance and the aircraft overran the runway end, breached the perimeter fence, and came to rest upright. The probable cause was the pilot's decision to continue the landing attempt with insufficient runway remaining. The runway was 5,000 ft long; the aircraft touched down at approximately 3,500 ft, leaving only 1,500 ft to stop. At 62 KIAS, the C172R requires approximately 1,200 ft to stop (POH landing distance, no headwind, sea level). The pilot had margin, but only barely — and the decision to continue instead of go around was the critical error.

NTSB CEN24LA233 (2024): A Cessna 172R on an instructional flight veered left of the runway centerline during landing. The pilot's correction attempts resulted in a right veer, causing the aircraft to exit the left side of the runway and strike a distance marker. The probable cause was the pilot's failure to maintain directional control during landing. The oscillating corrections — left veer, then right veer — are the classic signature of overcontrolling. A smooth, proportional correction is required; aggressive rudder inputs cause the airplane to overshoot centerline.

NTSB ERA22LA280 (2022): A Cessna 172 flown by a student pilot during touch-and-go landings experienced a porpoising landing after an improper flare. The student's attempt to recover by pulling back caused a skid, and subsequent overcompensation with rudder input resulted in a runway excursion and collision with a taxiway sign. The probable cause was the student pilot's improper flare, which resulted in a loss of control during landing. Porpoising — a bounce and skip pattern — is the result of a flare that is too aggressive or too late. The recovery attempt (pulling back harder) worsens the porpoise.

NTSB ERA21LA249 (2021): A Cessna 172R on a solo cross-country instructional flight experienced loss of directional control during landing when the nose gear contacted the runway. The accident resulted from the student pilot's failure to maintain directional control, resulting in a runway excursion and collision with an airport sign. The nose gear is the last to touch; if directional control is lost at that moment, the airplane is already committed to the landing and recovery is difficult.

NTSB ERA21LA119 (2021): A Cessna 172R on a personal flight veered left off the runway during landing in gusting crosswind conditions and struck the ground with the propeller and left wing tip. The probable cause was the pilot's failure to maintain directional control during landing in a gusting crosswind. Crosswind control is a primary concern on landing; a gust can cause a veer if the pilot is not actively correcting with smooth rudder inputs.

All of these accidents occurred at other airports — NOT at KTPA. KTPA's own dominant accident pattern includes FORCED_LANDING (22.2%), LOSS_OF_CONTROL_INFLIGHT (11.1%), and LOSS_OF_CONTROL_GROUND (8.9%). The runway excursion and directional control loss are real hazards at any airport, but the specific events cited above happened elsewhere. The scenario is localized to KTPA to make the runway environment and airspace real for you as a student here.

The consistent thread across all these events: an unstable approach (too fast, too high, not fully configured) leads to a landing that is not stabilized. The pilot then makes aggressive corrections (hard flare, aggressive rudder) that result in a loss of control. The fix is simple: if you are not stabilized by 300 ft AGL, go around. Do not press on and hope to make it.