Float and Fence
Excess approach energy on a short runway — the decision to go around or land long is made in seconds
The scenario
Departing Albert Whitted Airport (KSPG), St. Petersburg, FL — Runway 07, 3,676 ft long. Elevation 7 ft MSL. You are a Private pilot with 180 hours total, current, and this is your first solo cross-country to KSPG. You have never landed here before.
Conditions: VFR, scattered clouds at 3,000 ft, visibility 10 SM. Wind 080° at 8 kt, gusting to 14 kt — a light crosswind on Runway 07 (true heading 062°). Temperature 24°C, altimeter 29.95. The runway is dry. You are in Class D airspace; the tower is open and active (current time 1030 local).
You have been in the air for 1.2 hours. The flight was uneventful. You are on a 10-mile final for Runway 07, 800 ft AGL, descending at 500 fpm. The runway is ahead. You are configured: flaps 10°, power 1,200 RPM, trim set for descent, airspeed 75 KIAS. You are slightly high on the glide slope — not dangerously, but noticeably. The runway is short (3,676 ft) and you know it. You have not landed at KSPG before.
Aircraft: Cessna 172R, solo, 1,850 lb (well within limits). Fuel-injected Lycoming IO-360-L2A, fixed-pitch prop, fixed gear, steam panel. Nothing was written up; the airplane is airworthy.
Pilot: you — a Private pilot, current, 180 hours total. You have landed at similar-length runways (3,500–3,800 ft) at your home field and one other airport. You are not a frequent short-field operator. You are slightly anxious about the short runway and the crosswind, but you are committed to the landing.
- {'label': 'Field', 'value': 'KSPG · Albert Whitted'}
- {'label': 'Runways', 'value': '7/25 · 18/36'}
- {'label': 'Elevation', 'value': '7 ft'}
- {'label': 'Aircraft', 'value': 'C172R'}
- {'label': 'Dominant phase', 'value': 'Landing / Takeoff'}
The decision
Before we get into the decision tree — what do you know about short-field landing technique in the C172R? (Pick all that apply.)
What the record shows
What the NTSB files show
NTSB CEN24LA263 (2024): A Cessna 172R on an instructional flight performed a power-off 180° maneuver and landed too high on the runway. The pilot 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, which resulted in a runway overrun.
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.
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, which resulted in a loss of control and runway excursion.
The common thread across all these accidents: the pilot committed to a landing that was unstable, high, fast, or poorly controlled. In each case, a go-around earlier in the approach would have prevented the accident. The decision to go around is made at 500 ft AGL or higher — not at 50 ft AGL when options are gone.
At KSPG, Runway 07 is 3,676 ft long — short by general-aviation standards. The off-field environment off Runway 07's departure end (heading 062°) is open water — Tampa Bay. A runway overrun off that end is not a ground excursion; it is a ditching. The stakes are higher at KSPG than at a typical 5,000+ ft runway with open fields off the ends. This is why the approach must be stable, on speed, and on glide slope by 500 ft AGL. If it is not, go around.
Key lesson — A stable, on-speed, on-glide-slope approach by 500 ft AGL is non-negotiable at a short runway like KSPG's Runway 07. If you are high, fast, or unstable at that point, go around. The decision to continue a marginal approach and land long, float, or lose directional control is the decision that leads to a runway excursion. At KSPG, a runway overrun off Runway 07 is a ditching in open water. The go-around is always available; use it.
Debrief — teaching points
Vref is the target approach speed for short-field landings in the C172R.
Vref (short-field approach speed, full flaps) is 62 KIAS. This is the slowest safe approach speed and results in the shortest landing distance. At a runway like KSPG's Runway 07 (3,676 ft), Vref is not optional — it is the standard. Approach at 75 KIAS or higher and you will float, land long, and risk an overrun. Approach at 62 KIAS and you will touch down early and stop comfortably. The difference is 300+ feet of landing distance.
A stable approach by 500 ft AGL is the gate — if you are not stable by then, go around.
Stable means: on glide slope, on airspeed (or slightly below), configured for landing (flaps set), and tracking the runway centerline. If you are high, fast, unstable, or struggling with directional control at 500 ft AGL, a go-around is the correct decision. You have fuel, the runway will be there, and a second approach will be better. The accidents in the NTSB files all involved pilots who committed to unstable approaches and tried to salvage them at low altitude. That is when things go wrong.
A float on landing is caused by excess approach energy — too much speed, too much altitude, or both.
If you touch down 500 ft down the runway instead of 200 ft down, you have floated. The float is caused by carrying excess energy into the landing: airspeed above Vref, a shallow flare, or a delayed flare. The solution is to prevent the float by flying Vref on final and executing a proper, progressive flare. If you do float, apply full flaps and brakes immediately and stop within the remaining runway. At KSPG, a float that results in an overrun off Runway 07 is a ditching.
The flare is a gentle, progressive pitch-up — not a dramatic pull-back.
A proper flare begins at 100 ft AGL and is a smooth, progressive pitch-up to slow the descent rate. The descent rate should decrease from 500 fpm at 100 ft to 50 fpm at 20 ft to near-zero at touchdown. A flare that is too aggressive (a dramatic pull-back) can cause a stall or a porpoise (a bounce). A flare that is too shallow or delayed results in a hard landing and a float. Practice the flare on every landing — it is the most important skill in short-field operations.
Crosswind gusts during flare can cause a wing drop or directional control loss.
At KSPG, the wind was 080° at 8, gusting 14 kt — a light crosswind on Runway 07. During the flare, when the airplane is slow and the control authority is reduced, a gust can cause a wing drop or a directional control loss. Anticipate the gust and be ready with aileron (to level the wing) and rudder (to maintain heading). The NTSB ERA21LA119 pilot lost directional control in gusting crosswind conditions during landing. Be ready for it.
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 flare / runway excursion), ERA21LA249 (2021 C172R directional control loss / runway excursion), and ERA21LA119 (2021 C172R crosswind directional control loss). Localized to KSPG with real runway geometry and off-field environment.
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 KSPG