Float and Overshoot at Tampa North
Excess approach energy, a short runway, and the decision to go around — runway excursion risk in the C172R
The scenario
Departing Tampa North Aero Park Airport (X39), Tampa, FL — Runway 14, a 3,541 ft asphalt runway. Elevation 68 ft MSL. This is a non-towered field (CTAF 122.8); you are in Class G airspace below 3,000 ft MSL. Above 3,000 ft, you enter the Tampa Class B airspace (floor 3,000 MSL, ceiling 10,000 MSL).
It is a clear, calm afternoon: OAT 26°C, altimeter 29.98, visibility 10 SM. Light wind from 160°, roughly 4 knots — nearly calm. The runway is dry. Off Runway 14's departure end (heading 141°), the off-field environment is medium development, low-density development, and wooded wetland — not ideal for a forced landing, but not water. Off Runway 32 (heading 321°), similar: medium development, wooded areas.
You are on a solo cross-country flight, approaching X39 for a full-stop landing. You have been flying for 1.8 hours; fuel is good. This is your second visit to X39; you flew here once before with your CFI. The runway is shorter than your home field (3,541 ft vs. 5,000 ft), and you are aware of that.
Aircraft: Cessna 172R, solo (1,450 lb), within limits. Fuel-injected Lycoming IO-360-L2A (160 hp), fixed-pitch prop, fixed gear, steam panel (vacuum-driven attitude indicator, heading indicator, turn coordinator). Best glide 65 KIAS. Approach speed (short final, full flaps) is 62 KIAS.
Pilot: you — a Private pilot, current, roughly 280 hours total. You have about 40 hours in the C172R. You are familiar with the airplane's handling and performance, but you have not practiced short-field landings recently. You are not fatigued, but you are focused on getting the landing done cleanly.
- {'label': 'Field', 'value': 'X39 · Tampa North Aero Park'}
- {'label': 'Runways', 'value': '14/32'}
- {'label': 'Elevation', 'value': '68 ft'}
- {'label': 'Aircraft', 'value': 'C172R'}
- {'label': 'Dominant phase', 'value': 'Takeoff / Landing'}
The decision
Before we get into the decision tree — what do you already know about landing the C172R on a short runway? (Pick all that apply; this records your baseline.)
What the record shows
What the NTSB files show
NTSB CEN24LA263 (2024): A Cessna 172R performing a power-off 180° maneuver landed too high on the runway and was unable to stop within the remaining distance. 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 — a classic runway excursion scenario.
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 — a loss of control on the ground.
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.
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.
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.
The common thread across all these accidents: the landing was unstable, the approach was too fast or too high, the flare was improper, or directional control was lost. In every case, a go-around before the landing became unstable would have prevented the accident. Tampa North Aero Park Airport (X39) has a runway of 3,541 ft — shorter than many training fields. The off-field environment is medium development and wooded areas — not ideal for a forced landing, but not water. The real accidents cited above occurred at other airports and in other circumstances — NOT at X39. But the lessons are directly applicable to any short-runway landing in the C172R.
The dominant accident pattern at X39 itself is LOSS_OF_CONTROL_INFLIGHT (27.3%), followed by LOSS_OF_CONTROL_GROUND (18.2%), OBSTACLE_ON_TAKEOFF_LANDING (9.1%), HARD_LANDING (9.1%), and STALL_SPIN (9.1%). Loss of control on the ground — runway excursions, directional control failures, and hard landings — accounts for a significant portion of X39's accident history. This scenario is grounded in that local pattern.
Key lesson — A short runway demands precision. The C172R's approach speed is 62 KIAS (short final, full flaps). If you arrive at the runway threshold too high, too fast, or unstable, go around. A go-around is not a failure — it is the correct decision. If the approach is unstable, a runway excursion is not a matter of if, but when. Land in the first 1,000 ft of the runway, maintain directional control, execute a smooth flare, and apply brakes. If you cannot do all of that, go around and try again.
Debrief — teaching points
Approach speed in the C172R is 62 KIAS (short final, full flaps).
This is the reference speed for a stabilized short-field approach. If you are faster than 62 KIAS on short final, you will float. If you are slower, you risk a stall. The C172R's stall speed in landing configuration (Vs0) is 33 KIAS, but the stall warning sounds near 40 KIAS. Maintain 62 KIAS on short final by managing power — reduce power as you descend to keep the airspeed stable. Do not accept 72 KIAS and plan to 'slow down later'; you will float and land long.
A short runway requires landing in the first 1,000 ft.
At X39, the runway is 3,541 ft. Landing distance from 50 ft AGL in a C172R is roughly 1,500–1,800 ft depending on weight, density altitude, and technique. If you land at 1,500 ft down the runway, you have 2,041 ft remaining to stop. If you land at 2,000 ft, you have 1,541 ft remaining. A landing at 2,500 ft leaves only 1,041 ft to stop — marginal. Plan to land in the first 1,000 ft. If you are not going to make that, go around.
A go-around is not a failure — it is the correct decision.
If the approach is unstable, too fast, too high, or if you are not confident in the landing, go around. Advance power to climb power, retract flaps to 10°, and climb out. Circle around and set up a second approach. A go-around costs time and fuel, but a runway excursion costs the airplane and possibly your life. The NTSB data shows that pilots who go around when the approach is unstable do not have accidents; pilots who try to salvage an unstable approach do.
The flare is critical — improper flare causes porpoising and loss of control.
A proper flare reduces the descent rate to near zero at touchdown. An improper flare — too high, too hard, or too shallow — can cause a porpoise (bouncing) or a hard landing. At 50 ft AGL, begin a gentle pitch-up to reduce the descent rate. At 20 ft AGL, the descent rate should be near zero. At 10 ft AGL, you should be floating just above the runway, ready to touch down. If you pitch up too aggressively, you will float and land long. If you do not pitch up enough, you will land hard and bounce. Practice the flare on every landing.
Directional control during landing is active — use ailerons and rudder.
Even in light crosswinds, you must actively manage the ailerons and rudder during landing. Use aileron into the wind to keep the wings level and prevent drifting. Use rudder to keep the nose aligned with the runway. Do not relax these inputs after touchdown — maintain directional control all the way to a stop. The NTSB data shows that loss of directional control on the ground is a significant accident cause at X39. Stay ahead of the airplane.
Built from the real accident record
Scenario built from NTSB CEN24LA263 (2024 C172R power-off 180° landing overshoot), CEN24LA233 (2024 C172R directional control loss on landing), ERA22LA280 (2022 C172 porpoising landing / runway excursion), ERA21LA249 (2021 C172R directional control loss / excursion), and ERA21LA119 (2021 C172R crosswind loss of control). Localized to Tampa North Aero Park Airport (X39).
NTSB reports: CEN24LA263 · CEN24LA233 · ERA22LA280 · ERA21LA249 · ERA21LA119
ACS tasks: PA.II.J — Approach and Landing · PA.II.K — 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.121
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 Cessna 172R scenarios · More scenarios at X39