Float and Overshoot at Peter O Knight
Excess approach energy, a short runway, and the decision to go around — or press on
The scenario
Departing Peter O Knight Airport (KTPF), Tampa, FL — Runway 22, landing on a warm, hazy afternoon. Elevation 8 ft MSL. Runway 22 is 3,583 ft long, true heading 217°. The off-field environment off Runway 22's landing end (heading 217°) is open water — Hillsborough Bay. Off the departure end (heading 037°) is dense development.
It is 1430 local, late spring. OAT 31°C, dew point 24°C, altimeter 29.91. Scattered clouds at 3,500 ft. Visibility 10 SM. Light and variable winds, gusting to 8 knots — essentially calm. KTPF is non-towered (CTAF 122.8); you are in Class G airspace below 1,200 ft MSL. Above 1,200 ft, you are in the overlying Tampa Class B (ceiling 10,000 MSL).
You are on a local training flight — a series of power-off 180° approaches to Runway 22 with your CFI. This is your fourth landing of the afternoon. The first three were acceptable; the CFI did not call for a go-around. On this approach, you are high and fast. You are at 500 ft AGL, 1 nm from the runway, descending at 300 ft/min, and your groundspeed is noticeably higher than on the previous approaches.
Aircraft: Cessna 172R, dual, full fuel, within limits. Fuel-injected Lycoming IO-360-L2A, fixed-pitch prop, steam panel. Nothing was written up; the airplane is airworthy.
Pilot: you — a Private pilot, current, roughly 180 hours total. You have 12 hours in the C172R. This is your second visit to KTPF; you are not deeply familiar with the field. Your CFI is in the right seat, monitoring. The power-off 180° is a standard training maneuver, but this one is not going as planned.
- {'label': 'Field', 'value': 'KTPF · Peter O Knight'}
- {'label': 'Runways', 'value': '4/22 · 18/36'}
- {'label': 'Elevation', 'value': '8 ft'}
- {'label': 'Aircraft', 'value': 'C172R'}
- {'label': 'Dominant phase', 'value': 'Landing / Approach'}
The decision
Before we get into the decision tree — what do you know about power-off 180° approaches and the risks of being high and fast on final? (Pick all that apply.)
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. The pilot was performing a training maneuver and did not go around despite being high and fast on final.
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 consequence of an unstable approach and loss of control during the landing phase.
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. The pilot was attempting to salvage an unstable approach.
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, which resulted in a loss of control and runway excursion.
The consistent thread: all these accidents involved a pilot pressing on with an unstable or marginal approach instead of going around. In the C172R, a high, fast approach at low altitude is not a situation to salvage — it is a situation to reset. The go-around is the correct call. At KTPF, Runway 22's landing end is open water (Hillsborough Bay); an overshoot into the bay is a ditching, not a ground excursion. The stakes are high.
These real accidents occurred at various airports and in various conditions — NOT all at KTPF. The scenario is localized to KTPF to make the runway length, the off-field environment, and the decision window real and consequential for you as a student here.
Key lesson — In the C172R, a high, fast approach at low altitude is not a situation to salvage with a slip, an extended flare, or a hope that you have enough runway. It is a situation to go around. Vref (short-field approach speed) is 62 KIAS full flaps — that is the target speed for a stabilized approach. If you are high and fast at 500 ft AGL 1 nm out, a go-around is the correct call. At KTPF Runway 22, the landing end is open water — an overshoot is a ditching. The runway is 3,583 ft long; that is not unlimited distance. Pressing on is a gamble with your life and the airplane.
Debrief — teaching points
A high, fast approach at low altitude is unstable and dangerous.
When you are high and fast on final approach at low altitude, you have limited options. A slip can help, but it adds workload and requires practice. An extended flare can bleed off energy, but it consumes runway distance. At 500 ft AGL 1 nm from the runway, you are already marginal. The correct response is a go-around. A go-around is not a failure; it is airmanship. An unstable approach is a situation to reset, not to salvage.
Vref is the target approach speed — know it and fly it.
Vref (short-field approach speed) for the C172R is 62 KIAS full flaps. This is the speed at which the airplane will touch down with the slowest possible touchdown speed and the shortest possible landing distance. If you are faster than Vref on final, you will float. If you are high and fast, you will float farther. Know Vref, plan your descent to arrive at Vref, and if you are not on speed and altitude, go around.
Best glide speed (65 KIAS) is your descent target during a power-off approach.
During a power-off 180° approach, your target descent speed is best glide (65 KIAS). This gives you the best glide ratio and the most time to manage the descent. If you are faster than best glide during the descent, you will arrive at the runway high and fast. If you are slower, you will not make the runway. Manage your descent to arrive at 500 ft AGL 1 nm out at 65 KIAS; then transition to Vref (62 KIAS) on short final.
At KTPF Runway 22, the landing end is open water — an overshoot is a ditching.
The off-field environment off Runway 22's landing end (heading 217°) is open water — Hillsborough Bay. If you overshoot the runway, you are ditching in the bay, not landing in a field. This is not a worst-case scenario; it is the geographic reality. Know this before you line up on Runway 22. If you are high and fast, a go-around is the correct call — not a gamble with a ditching.
Forward slip technique requires practice — do not attempt it on an unstable approach at low altitude.
A forward slip (cross-control: right aileron, left rudder) can increase drag and steepen the descent. It is a useful tool, but it requires practice and adds workload. On an unstable approach at low altitude, a slip can make things worse — it can result in a hard landing, a loss of directional control, or a runway excursion. If you are going to slip, do it deliberately from a stable altitude and exit early with a smooth flare. Better yet, go around.
Directional control during landing is critical — loss of control is a runway excursion.
The NTSB accidents ERA21LA249 and ERA21LA119 both involved loss of directional control during landing — the pilot veered left or right, attempted a correction, and the correction overcorrected, resulting in a runway excursion. Directional control is maintained with rudder input and crosswind correction. If you feel the airplane drifting left or right, correct with rudder — not aileron. Aileron input during landing can result in a wing strike or a loss of control.
The go-around is the correct call — practice it and own it.
A go-around is not a failure; it is a decision. The NTSB data shows that pilots who go around when the approach is unstable survive; pilots who press on do not. In the C172R, a go-around is simple: apply full power, retract flaps to 10°, climb out on a safe heading. Practice go-arounds until they are automatic. When you are high and fast at low altitude, the go-around is the correct call — not a last resort, but the first option.
Built from the real accident record
Scenario built from NTSB CEN24LA263 (2024 C172R power-off 180° landing overrun), CEN24LA233 (2024 C172R directional control loss during landing), ERA22LA280 (2022 C172 porpoising and runway excursion), ERA21LA249 (2021 C172R loss of directional control on landing), and ERA21LA119 (2021 C172R crosswind loss of control). Localized to Peter O Knight Airport (KTPF), Tampa, FL.
NTSB reports: CEN24LA263 · CEN24LA233 · ERA22LA280 · ERA21LA249 · ERA21LA119
ACS tasks: PA.II.J — Approach and Landing · PA.II.K — Go-Around / Rejected Landing · PA.I.H — Human Factors · PA.IX.C — Emergency Approach and Landing
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 KTPF