The Stabilized Approach, the Five Hundred Foot Gate, and the Go-Around You Decide Before You Ever Need It

The stabilized approach is a set of conditions that must all be true on final approach - on path, on speed, configured, controlled descent, and stable power - or you go around. The discipline is to pick a gate altitude (500 feet above ground in visual conditions is a solid choice for a light single) and decide, before you ever fly, that if you are not stable at the gate, you go around. No negotiation at 200 feet. You make the decision on the ground with a clear head, and the airplane simply keeps the promise.

Why the Stabilized Approach Matters More Than Anything Else You’ll Learn

A large share of general aviation accidents happen in one tiny slice of the flight: the approach and landing. Not the cross-country. Not the cruise. The last 500 feet.

When investigators pull those accidents apart, the same pattern appears again and again. The approach was never stable in the first place - too fast, too high, not lined up, not configured - and instead of throwing it away and trying again, the pilot tried to save it.

The whole idea is to give yourself a set of conditions that have to be true. If they are all true, you land. If any single one is not true, you go around. You already made that decision, hours ago, over coffee. The airplane just executes it.

What Does a “Stable” Approach Actually Mean?

Stable is not a feeling. It’s a checklist. In a light training airplane, it looks like this:

1. You are on the correct final approach path - laterally and vertically. Lined up with the runway centerline, tracking the extended centerline, and descending on a normal glide path. Not diving at it, not dragging it in flat and low.

2. You are on speed. This is the big one. For most trainers you’re targeting roughly 1.3 times your stall speed in the landing configuration. Your airplane has a published number - know it cold. If the book says 65 knots over the fence, then 65 is the target, and plus or minus 5 knots is the acceptable window. Not 15 knots fast.

3. You are in the landing configuration. Full flaps if that’s your normal, gear down and confirmed down if you fly retractable, and trimmed so the airplane wants to hold your target speed without you arm-wrestling it.

4. Your descent rate is under control. A normal approach descent in a small airplane is around 500 to 700 feet per minute. If you glance down and see 1,000 feet per minute peeling off the vertical speed indicator on short final, that is a warning, not a stable approach.

5. Your power is set and stable. Small corrections are normal flying. But if you’re slamming the throttle from idle to full and back, chasing the airplane all the way down, you are behind it.

On path, on speed, configured, controlled descent, power set. Say it to yourself on downwind so it’s already in your head.

What Is the “Gate” and Where Should I Set Mine?

The gate turns a nice idea into an enforceable rule. The concept comes from the airline world, where every approach has a hard altitude at which the approach must be stable or the crew goes around - no exceptions, no discretion to salvage it. In big turbine airplanes the gate is often 1,000 feet above the ground in instrument conditions and 500 feet in visual conditions.

You’re not flying a jet into a 1,000-foot ceiling, so make it real for your airplane. In visual conditions in a light single, 500 feet above the ground on final is a good, honest gate. Some instructors prefer 300 feet in the pattern because the pattern is tight and you configure later. Talk to your own CFI about the right number for your airplane and airport - but pick one, write it down, and treat it like it’s bolted to the airframe.

Here’s how it plays out. As you descend on final, you pass through your gate altitude. At that moment, you ask the question: Am I stable? On path, on speed, configured, controlled, power set. If the answer is yes to all of it, you continue and land. If the answer is no to any single piece, you go around - right then. Not at 200 feet. Not in the flare. At the gate.

Isn’t Going Around a Sign of a Bad Pilot?

No - and believing otherwise gets people hurt. The go-around is not the emergency. The go-around is the thing that prevents the emergency.

A lot of pilots pick up the idea that going around is a failure, that a real pilot greases every landing. That’s simply wrong. The examiner is not looking for a pilot who never goes around. The examiner is looking for a pilot who recognizes an unstable approach and does something about it while there’s still sky underneath them.

Real Scenarios Where the Gate Saves You

Scenario one: high and floating. You turn final a little high, figure you’ll slip it off, and it mostly works - but now you’re fast, so you float. And float. The far numbers get closer and you’re making a decision at 15 feet with two-thirds of the pavement behind you. That’s the setup for a runway overrun. Rewind it: at 500 feet you were high and you knew it. Not stable. Go around. Cost: four minutes and a little gas.

Scenario two: the base-to-final overshoot. This is the one that scares me most. You overshoot the centerline - maybe a tailwind on base, maybe too much speed into the turn. The brain wants to fix it: steepen the bank, then shy away from the steep bank down low, then feed in bottom rudder to skid the nose toward the runway, then pull back to keep the nose from dropping. Steep, slow, skidding, and pulling is the recipe for a cross-control stall that breaks into a spin, and at 400 feet on base to final there is no altitude to recover. You do not fix an overshoot with rudder. You overshot - not stable, not lined up - so you go around.

Scenario three: the gusty crosswind. Everything looks fine. On centerline, on glide path, wings level. But the wind is howling and you’re making a big correction every few seconds just to hold it. Down at 100 feet a gust drops you, you add a fistful of power, it lets go, and now you’re fast and won’t settle. The tell is the power. If you’re sawing the throttle all the way down, the conditions are past your comfortable margin today. That might mean a go-around, a diversion to a better-aligned runway, or a hard look at whether the crosswind component is inside your personal limits and the airplane’s demonstrated crosswind component.

What Does the Checkride Require?

If you’re training toward a certificate, this is not optional. Open the Airman Certification Standards (ACS) for the private pilot and look at the normal approach and landing task - it asks you to maintain a stabilized approach and a recommended approach airspeed, within a specified tolerance. There’s also a separate task for the go-around/rejected landing, where the standard is a timely decision to go around, executed correctly. The FAA built the go-around into the test on purpose. Practice it like a graded maneuver, because it is one.

How Do I Fly the Go-Around Itself Without Trading One Problem for Another?

A botched go-around is its own hazard, so fly the sequence deliberately: power, then pitch, then flaps in stages, then airspeed, then clean up.

1. Full power, smoothly.
2. Pitch to your climb attitude.
3. Retract the big drag flap setting one notch so the airplane can climb - but don’t dump all the flaps at once down low, or you’ll sink.
4. Establish your climb speed.
5. Finish retracting the flaps as you climb away.

With all that power in at low speed, the airplane will yaw hard - your right foot has a job to do. Fly the airplane first; talk on the radio second. Practice the whole sequence up at altitude until your hands and feet know the dance and your brain is free to fly.

The Real Tip: Decide Before You Fly

Before you ever take the runway, brief yourself out loud: My gate is 500 feet. If I’m not stable at the gate, I’m going around. My personal crosswind limit today is this many knots. If it’s worse than that, I’m not landing here.

You are pre-loading the decision so the tired, task-saturated, get-home version of you at the bottom of the approach doesn’t have to make it under pressure. You already made it. All that pilot has to do is keep the promise.

The airplane doesn’t get you. It’s the little negotiation at 200 feet - it’s probably fine, I’ve got this, I don’t want to go around in front of everybody - that’s where it goes wrong. The stabilized approach and the gate exist to take that negotiation away at the worst possible moment.

A go-around is not a failed landing. A go-around is a pilot flying the airplane. The greaser you salvaged out of a bad approach taught you only that you can get away with it. The go-around you executed cleanly off an unstable approach is the one that makes you the pilot people want to fly with.

The stabilized approach criteria and gate concept draw directly from FAA guidance in the Airplane Flying Handbook and the Airman Certification Standards, plus the airline stabilized-approach philosophy the rest of us borrowed. Those pages are worth reading in full.

Key Takeaways

• A stabilized approach requires five things to all be true: on the correct path, on speed (about 1.3× stall speed, ±5 knots), in landing configuration, a controlled 500–700 fpm descent, and stable power.
• Set a gate altitude - 500 feet AGL in visual conditions is a good default for a light single - and go around if any single stability criterion fails at that point.
• The base-to-final overshoot is uniquely deadly: steep, slow, skidding, and pulling leads to a cross-control stall and spin. Go around instead of correcting with rudder.
• A sawing throttle hand is data - it signals conditions past your margin, especially in gusty crosswinds.
• Decide your go-around policy on the ground, before you fly, so the decision is already made when you’re tired and task-saturated on short final.