Float and Overshoot at Zephyrhills
Excess approach energy, a short runway, and the decision to go around — energy management in the C172R
The scenario
Departing Zephyrhills Municipal Airport (KZPH), Zephyrhills, FL — Runway 19, a 5,072 ft asphalt runway. Elevation 90 ft MSL. You are inbound from a local VFR flight, 45 minutes airborne, and planning to land and refuel before continuing.
Conditions: VFR, clear skies, visibility 10 SM. Wind is 170° at 8 kt — a light crosswind from the left on Runway 19. Temperature 26°C, altimeter 29.95. The field is non-towered (CTAF); you will self-announce on 122.8.
You are on a 3° glide slope to Runway 19, 2 nm out, descending through 800 ft AGL. You have been flying this approach at a comfortable pace — not rushed, but not particularly focused on energy management. The runway is long (5,072 ft), so there is room to work with. Or so you think.
Aircraft: Cessna 172R, solo, 1,800 lb gross weight, within limits. Fuel-injected Lycoming IO-360-L2A, 160 hp. Fixed gear, fixed-pitch prop, fuel selector BOTH. Steam panel (vacuum-driven attitude indicator, heading indicator, turn coordinator). You have 2 hours of fuel remaining.
Pilot: You — a Private pilot, current, roughly 250 hours total. You have landed at KZPH before. You are comfortable here. This is a routine landing.
- {'label': 'Field', 'value': 'KZPH · Zephyrhills'}
- {'label': 'Runways', 'value': '19/1 · 5/23'}
- {'label': 'Elevation', 'value': '90 ft'}
- {'label': 'Aircraft', 'value': 'C172R'}
- {'label': 'Dominant phase', 'value': 'Landing / Cruise'}
The decision
Before we get into the decision tree — what do you know about energy management and go-around decisions in the C172R? (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. The pilot did not recognize the excess energy or execute a go-around.
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 symptom of an unstable approach and improper flare technique.
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 and 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 probable cause was the pilot's failure to maintain directional control of the airplane during landing.
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: excess approach energy (too much speed, too high, too steep) combined with the pilot's failure to recognize an unstable approach and execute a go-around. The C172R is a forgiving airplane, but it cannot overcome the physics of excess energy. Landing distance increases with the square of touchdown speed — a 10 KIAS overspeed can add 500+ ft to landing distance. At KZPH, Runway 19 is 5,072 ft — plenty of room for a normal landing, but not for a landing with excess energy and poor technique.
Real accidents cited above occurred at various airports — NOT at KZPH. KZPH's own accident corpus shows FORCED_LANDING (29.2%), LOSS_OF_CONTROL_INFLIGHT (29.2%), and STALL_SPIN (16.7%) as the dominant patterns. Runway excursions are less common at KZPH, but they are a real risk — and the decision to go around when the approach is unstable is the primary prevention.
Key lesson — Excess approach energy is the leading cause of runway excursions in the C172R. A stable approach at 62 KIAS (Vref), full flaps, on glide slope, is the foundation of safe landings. If the approach is not stable by 500 ft AGL, execute a go-around. A go-around is not a failure — it is airmanship. The NTSB data on C172R runway excursion accidents shows that pilots who recognize unstable approaches early and execute go-arounds do not end up in accidents. Those who continue unstable approaches do.
Debrief — teaching points
Energy management begins before the approach.
Before you descend to pattern altitude, calculate your landing distance requirement. For the C172R at 1,800 lb gross weight in calm conditions, landing distance is roughly 1,200 ft. At KZPH Runway 19 (5,072 ft), you have plenty of margin — but only if you execute a normal landing at Vref (62 KIAS). Excess approach energy (speed, altitude, descent rate) will consume that margin quickly. Know your numbers before you begin the approach.
Vref is 62 KIAS with full flaps — this is not a suggestion.
The C172R POH specifies Vref at 62 KIAS for short-field approaches with full flaps (30°). This is the speed that minimizes landing distance. Landing at 70 KIAS instead of 62 KIAS increases landing distance by roughly 500 ft — a significant penalty. Commit to Vref before you begin the approach, and fly it precisely on short final.
A stable approach at 500 ft AGL is the decision gate.
By 500 ft AGL, the approach should be stable: on speed (Vref ±5 KIAS), on glide slope (3°), fully configured (full flaps), and descending at a steady rate. If the approach is not stable by 500 ft AGL, execute a go-around. This is not optional. The NTSB data on C172R runway excursion accidents shows that pilots who fail to recognize unstable approaches at 500 ft AGL and continue the landing end up in accidents.
Floating down the runway is a go-around trigger.
If the airplane is floating (not touching down) at 50% of runway remaining, execute a go-around. At KZPH Runway 19 (5,072 ft), 50% is 2,536 ft. If you are still airborne at the 2,500 ft mark, go around. Floating means excess energy — you are too fast, too high, or both. Continuing the landing in this situation risks a runway overshoot.
A go-around is airmanship, not a failure.
The C172R climbs at a steady rate. A go-around takes roughly 30 seconds to reach pattern altitude. You can plan a second approach, this time stable and on speed. The alternative — continuing an unstable approach and risking a runway excursion — is not acceptable. Pilots who execute go-arounds do not end up in runway excursion accidents. Those who continue unstable approaches do.
Crosswind control requires active rudder input throughout the landing.
The 8 kt crosswind on Runway 19 is light and well within limits for the C172R, but it requires active rudder input throughout the approach and landing. Maintain directional control with the rudder; use aileron to maintain wings level. The NTSB ERA21LA119 accident (a C172R that veered left off the runway in gusting crosswind) resulted from inadequate crosswind control technique. Practice crosswind landings regularly.
Built from the real accident record
Scenario built from NTSB CEN24LA263, CEN24LA233, ERA22LA280, ERA21LA249, and ERA21LA119 — all C172R runway excursion and loss-of-directional-control landing accidents. Real events occurred at various airports; localized to KZPH.
NTSB reports: CEN24LA263 · CEN24LA233 · ERA22LA280 · ERA21LA249 · ERA21LA119
ACS tasks: PA.II.E — Approach and Landing · PA.II.F — 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.103
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 KZPH