The Stabilized Approach Gate, the Go-Around You Keep Putting Off, and the Decision Window That Closes Faster Than You Think on Final

The stretch of seconds between “I’m not quite where I want to be” and “I’m committed to landing” is where more accidents begin than almost anywhere else in general aviation. The stabilized approach gate - and the go-around decision that flows from it - is one of the most underrated skills in flight training. Understanding why pilots fail to execute go-arounds, and committing to a personal standard before leaving the ground, is one of the highest-value investments you can make in your flying right now.

Why Do Pilots Fail to Go Around?

In training, go-arounds happen on command. An instructor gives the word, you add power, pitch for climb, retract flaps on schedule, and climb away. Clean, rehearsed, controlled.

In the real world, there is no cue from the right seat. The go-around decision arrives when workload is already high - you are managing airspeed, managing power, the runway is close, and your brain is running the most compelling lie in aviation: that you can still make it work.

Psychologists call this plan continuation bias. Once committed to landing, the brain wants to complete that task. The further along you are in the approach, the harder it becomes to abandon the plan - even when the plan is actively going wrong.

The National Transportation Safety Board (NTSB) has documented this pattern repeatedly. Studies of approach-and-landing accidents consistently point to one common thread: the pilot recognized something was wrong but chose to continue rather than go around. In some cases, cockpit voice recorder data captured pilots commenting that the approach didn’t look right - and then continuing anyway.

This is not a skill gap. It is a decision gap.

What Is the Stabilized Approach Gate?

A stabilized approach means that by a defined checkpoint - typically 500 feet above the ground (AGL) in visual conditions - your approach must meet a specific set of criteria simultaneously, not just trending toward them.

Those criteria are:

• Aircraft configured for landing: gear down if applicable, flaps set, checklist complete
• Airspeed at or near target approach speed, within ±10 knots
• Rate of descent within normal parameters, typically 200–700 feet per minute in a light aircraft
• Power appropriate for a stabilized glide
• Aircraft on the correct flight path: aligned with centerline, tracking the glidepath

If every one of those criteria is met at 500 feet AGL, you have a stabilized approach. If any single criterion is not met, the Airman Certification Standards (ACS)-aligned decision is unambiguous: go around.

When Should You Go Around?

If your approach is not stabilized at 500 feet AGL, go around. Every time. Not sometimes. Not only when the deviation is severe. Every time.

The instinct most pilots have is to recall every time they salvaged a rough approach and made a perfectly acceptable landing. That experience is real - and it is exactly what makes plan continuation bias so dangerous. Every successful save reinforces the belief that the approach can always be recovered, which means the threshold for going around creeps later and later. Eventually the go-around comes too late, or never comes at all.

Scenario: High and Fast on Final - The Wrong Decision Chain

Picture a Cessna 172 on final with a light crosswind of approximately 8 knots from the left. A preceding aircraft stretched the downwind, leaving this approach high.

At 500 feet AGL: airspeed is 68 knots - 8 knots above the target of 60 knots. The aircraft is approximately 200 feet above the desired glidepath. Power is already at idle. That is the 500-foot gate. The approach is not stabilized. The correct call is to go around.

Instead, the typical internal decision chain looks like this: push the nose over to steepen the descent and bleed speed. At 300 feet, airspeed has climbed to 72 knots and the aircraft is still 60 feet above the visual glidepath. The rate of descent is now steepening. Pulling back to arrest the descent causes a momentary balloon. The runway numbers pass underneath.

The aircraft lands - maybe using a lot of runway, maybe requiring hard braking. Maybe everything is fine. But maybe the crosswind catches the nose in the flare. Or maybe 1,500 feet of a 3,000-foot runway disappear before touchdown, leaving only 1,500 feet remaining at 60 mph with wet pavement.

Each individual correction in that sequence looked reasonable in the moment. The aggregate was dangerous. That is plan continuation bias in action.

Scenario: High and Fast on Final - The Right Decision

Return to the same point: 500 feet AGL, 68 knots, high, not stabilized.

Go around.

Full power. Pitch for best rate of climb speed - in a Cessna 172, approximately 74 knots. Establish a positive rate of climb. Retract flaps to the first setting. Announce on the Common Traffic Advisory Frequency (CTAF) that you are going around. Climb to pattern altitude. Re-enter and fly a better approach.

The maneuver takes roughly 90 seconds. The second approach will be cleaner - the preceding traffic has moved further ahead, the distraction is gone, and the setup is fresh. A go-around is not a failure. It is a decision. Making that decision at 500 feet instead of 50 feet is the difference between sound airmanship and an accident report.

What Does the ACS Expect During a Checkride?

The ACS for the private pilot certificate is explicit. During the normal landing task, evaluators watch for proper use of the go-around procedure when an approach becomes unstabilized.

Continuing an approach that is clearly going wrong all the way to the runway is potential unsatisfactory performance - not because of how the aircraft touched down, but because it demonstrates willingness to press on when conditions indicate otherwise. Examiners are looking for pilots who identify the problem early, execute the go-around cleanly, and do not wait for the runway to force the issue.

What About Unexpected Runway Incursions?

Not every go-around decision involves geometry. On short final - perfectly stabilized, 50 feet above the numbers - a vehicle may pull onto the runway from a taxiway intersection ahead. The decision window is roughly three seconds.

There is no gate to work with here. The call is immediate. This is precisely why the habit matters. If the go-around has been practiced until it is automatic, the response - full power, pitch up, climb - happens before deliberate thought catches up. If go-arounds have only been performed on instructor command, the response will arrive a beat late. At 50 feet AGL at approach speed, that beat is not available.

Full power. Pitch up. Climb. Announce. Everything else follows once separation from the ground is established.

What If Conditions Compromise Your Visual Picture?

A third category of go-around involves neither geometry nor obstacles - it involves pilot confidence in the visual picture.

Turning final into direct sun, with the runway environment difficult to make out and depth perception compromised, is a legitimate go-around trigger even when all the numbers are right. If there is any genuine question about whether you can see what you need to see to land safely, reposition, get the sun out of your eyes, and try again from a sight picture you trust.

The standard here is genuine certainty - not optimism. If that certainty is absent, the approach is not stabilized regardless of what the instruments say.

How to Build the Go-Around Habit Before Your Checkride

The gate only works if you commit to it before the flight. The method is straightforward.

Before each flight, state this out loud during preflight: “If I am not stabilized at 500 feet above the ground, I am going around.” Then, during every approach, ask the question at 500 feet AGL: am I stabilized? If yes, land. If anything is off, go around.

What most pilots discover when they hold this standard honestly is that they go around more often than expected. That is not a problem - it means the habit is identifying approaches that would have required improvisation, and removing that improvisation from the equation. Over time, pattern work tightens up to meet the standard rather than the other way around.

After each flight, ask one question: was that approach stabilized at 500 feet? Not whether the landing was smooth - whether the approach met criteria when it needed to. If the answer is uncertain, the habit is not yet established. And the habit is the entire point.

The FAA Safety Team and NTSB accident data both identify the approach-and-landing phase as one of the highest-risk segments of every flight. Understanding why the go-around doesn’t get made - and deciding before you ever take the runway that you will make it when you need to - is one of the most valuable things you can do for your flying right now.

Key Takeaways

• Plan continuation bias is the primary psychological mechanism behind approach-and-landing accidents - the brain resists abandoning a task already in progress.
• The stabilized approach gate is 500 feet AGL in visual conditions. Configuration, airspeed, descent rate, power, and flight path must all be met simultaneously at that point.
• If any criterion is not met at 500 feet, the correct decision is to go around - every time, not just when the deviation is severe.
• A go-around is a decision, not a failure. Executing it at 500 feet rather than 50 feet is what separates disciplined airmanship from an accident scenario.
• Build the habit by committing to the gate out loud before every flight and evaluating the approach honestly after every landing.