FlightEdge
Sample scenario-based training
SAMPLE SBTApproach / Landing

Long and High on Final

Excess approach energy, a go-around decision, and the margin between a safe abort and a runway excursion — the C172S demands precision pitch control

Cessna 172S · Brooksville–Tampa Bay Regional Airport (KBKV) · Private · Approach / Landing

The scenario

Departing Brooksville–Tampa Bay Regional Airport (KBKV), Brooksville, FL — Runway 09, a 7,001-foot concrete runway. Elevation 76 ft MSL. You are on a personal flight, solo, full fuel, within limits.

It is mid-afternoon, VFR. Wind is reported 120° at 12 knots, gusting to 18 — a crosswind on Runway 09 (true heading 090°). Visibility 10 SM, scattered clouds at 3,500 ft. The approach is stable until about 500 ft AGL, when the wind becomes gusty and variable. You are high and long on final.

Aircraft: Cessna 172S, glass panel (G1000), fuel-injected Lycoming IO-360-L2A. Fixed gear, fixed-pitch prop, fuel selector BOTH. All systems normal at departure. You are current and proficient; roughly 400 hours total time, 80 hours in type.

Pilot: you — a Private pilot, current, IFR-rated. You have landed at KBKV twice before. You are familiar with the runway length (7,001 ft is generous) and the off-field environment (open pasture and developed areas to the north and south). You are not rushed, but you are committed to landing on this approach.

The decision point is now: you are 400 ft AGL on a 3° glide slope, 1.5 nm from the runway threshold. The wind is gusting. You are noticeably high and long — the touchdown point is drifting toward the middle of the runway, not the first third. Your airspeed is 75 KIAS, slightly above Vref (65 KIAS). Flaps are at 20°. The runway is clearly visible and well within reach, but the approach energy is higher than ideal.

The decision

Before we get into the decision tree — what do you know about go-arounds in the C172S? (Pick all that apply; this records your baseline.)

What the record shows

What the NTSB files show

NTSB CEN23LA159 (2023): A Cessna 172S on a personal flight experienced a tailwind on final approach. The pilot attempted a go-around when landing appeared long. The aircraft porpoised during the go-around, the nose landing gear collapsed, and the aircraft departed the runway. The probable cause was the pilot's failure to maintain airplane control during the attempted go-around, resulting in abnormal contact with the runway pavement and a runway excursion. The pilot was not injured, but the aircraft was substantially damaged.

NTSB ERA21LA202 (2021): A Cessna 172S on short final in gusting crosswind conditions (120° at 12G18 — identical to this scenario's wind) was high and slow. The pilot initiated a go-around but improper pitch control resulted in a tail strike and runway excursion to the left into grass. The probable cause was the pilot's improper pitch control during a go-around in gusting crosswind conditions. The aircraft was substantially damaged; the pilot was not injured.

NTSB ERA11LA421 (2011): A Cessna 172S experienced total electrical failure shortly after takeoff from Lincoln Park Airport, rendering the flaps inoperable. The pilot landed long on the runway with high airspeed and inadequate braking performance, resulting in a runway overrun and collision with a guardrail. The probable cause was the pilot's improper touchdown point, resulting in a runway overrun. The aircraft was substantially damaged.

The common thread across all three accidents: approach energy management and go-around technique. CEN23LA159 shows that an aggressive go-around pitch in a C172S can result in a porpoise and nose-gear collapse. ERA21LA202 shows that improper pitch control during a go-around in gusting wind is a tail-strike risk. ERA11LA421 shows that a long landing after electrical failure can result in a runway overrun if the runway is not long enough.

At KBKV, Runway 09 is 7,001 feet — long enough to absorb landing-distance penalties and provide margin for error. However, the off-field environment off Runway 09 (heading 090°) is open developed areas, pasture, and medium development — not a runway. A runway excursion off the side of Runway 09 would result in a ground accident in developed or pasture terrain, not a water landing. The consequences are real.

The real accidents cited above occurred at other airports and in other circumstances — NOT at KBKV. This scenario is localized to KBKV to make the runway length and off-field environment real and consequential for you as a student here. The decision tree focuses on the C172S-specific go-around technique and approach energy management that the NTSB accidents reveal as critical.

Key lesson — In the C172S, a high, long approach on final is a decision point, not a problem to be solved by aggressive maneuvering. A forward slip loses altitude without increasing airspeed — it is the correct tool. A go-around in gusting crosswind conditions requires smooth, controlled pitch and staged flap retraction — not aggressive pitch that can cause a tail strike or porpoise. Approach at Vref (65 KIAS), not faster. If you are high and long, slip or go around. Do not try to salvage a bad approach with aggressive control inputs. The C172S's fixed landing gear and fixed-pitch prop mean that once you are committed to the landing, the only tools you have are pitch, power, and flaps. Use them smoothly.

Debrief — teaching points

A high, long approach is a decision point, not a problem to be solved by aggressive maneuvering.

If you are high and long on final approach, you have two tools: a forward slip (to lose altitude without increasing airspeed) or a go-around (to abort and set up again). A forward slip at 400 ft AGL in the C172S is safe and effective — it increases descent rate without increasing airspeed or requiring a hard descent. A go-around is also safe if executed smoothly. What is NOT safe is trying to salvage a bad approach by aggressive power reduction, hard descent, or aggressive pitch changes. The NTSB CEN23LA159 pilot who attempted an aggressive go-around porpoised and collapsed the nose gear. Recognize the marginal approach early and act decisively.

Go-around technique in the C172S requires smooth pitch and staged flap retraction.

A go-around in the C172S is not a maximum-performance maneuver. It is a controlled climb-out. Pitch up smoothly to climb attitude — not aggressively. Retract flaps in stages: 20° to 10° first, then to 0° as you climb through 800 ft AGL. Sudden flap retraction can cause a pitch change or loss of lift. In gusting crosswind conditions (like the 120° at 12G18 in this scenario), the wind shear and control authority are both factors. A smooth, staged go-around is the correct technique. The NTSB ERA21LA202 pilot's improper pitch control during a go-around in gusting wind resulted in a tail strike. Smooth is safe.

Vref (65 KIAS) is the published approach speed for the C172S — fly it.

The C172S POH specifies Vref as 65 KIAS for approach and landing. Landing at higher airspeed (e.g., 75 KIAS) increases float distance and touchdown energy. In gusting crosswind conditions, the published speed is not a luxury — it is a requirement. The extra airspeed reduces control authority and increases landing distance. At KBKV, the runway is long enough to absorb the penalty, but at a shorter runway, landing fast can result in a runway overrun. Know your V-speeds and fly them.

A forward slip is the correct tool for losing altitude without increasing airspeed.

In the C172S, a forward slip (cross-controlled: ailerons into the slip, opposite rudder) increases descent rate without increasing airspeed. It is safe and effective at 400 ft AGL on final approach. The slip increases drag and descent rate; the airspeed remains stable. At 400 ft AGL, 75 KIAS, a forward slip will lose 200–300 feet of altitude in 30–45 seconds without increasing airspeed. This is the correct technique for a high approach. The alternative — reducing power and increasing descent rate — can result in a hard landing or a steep descent that is difficult to recover from.

Electrical failure in the C172S renders flaps inoperable — plan for a longer landing distance.

The C172S flap system is electrically driven. A total electrical failure (like the one in NTSB ERA11LA421) renders flaps inoperable. If you experience electrical failure on final approach, you will land with flaps at whatever position they were in when power was lost. If flaps are at 20° (not full 30°), landing distance increases. The NTSB ERA11LA421 pilot landed long after electrical failure and collided with a guardrail. At KBKV, the runway is 7,001 feet — long enough to absorb the penalty. At a shorter runway, the outcome could be different. Know your runway length before you commit to the approach.

Off Runway 09 at KBKV, the off-field environment is open developed areas and pasture — not water.

The USGS NLCD ground cover off Runway 09 (heading 090°) at KBKV is open developed areas (parks, large lots), pasture/hay, and medium development. A runway excursion off the side of Runway 09 would result in a ground accident in developed or pasture terrain. This is not a water landing scenario. However, the consequences are still real — a runway excursion into developed terrain or a collision with a structure is a serious accident. Stay on the runway.

Built from the real accident record

Scenario built from NTSB CEN23LA159 (2023 C172S go-around porpoise / nose gear collapse), ERA21LA202 (2021 C172S go-around tail strike in gusting crosswind), and ERA11LA421 (2011 C172S electrical failure / long landing / runway overrun). Anonymized and localized to KBKV.

NTSB reports: CEN23LA159 · ERA21LA202 · ERA11LA421

ACS tasks: PA.II.C — Takeoff and Climb · PA.III.A — Approaches and Landings · PA.III.B — Go-Around / Rejected Landing · PA.I.H — Human Factors · PA.IX.C — Emergency Approach and Landing

Relevant FARs: §91.3 · §91.13 · §91.103

Run this scenario yourself

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 172S scenarios · More scenarios at KBKV