The Go/No-Go Decision Framework

Home › Pilot Guides › Go/No-Go Decision Framework

A sound go/no-go decision is a structured comparison of today's conditions against pre-set personal minimums — across pilot, aircraft, environment, and external pressures (PAVE). You decide the criteria on the ground, where thinking is cheap, so that at the airport the question is not "do I feel okay about this?" but "do the numbers clear the bar I already set?"

Why does gut-feel fail on go/no-go decisions?

Because by the time you're standing at the airplane, you are no longer a neutral judge. You've filed, packed, driven out, told someone you're coming. Every one of those steps makes "go" feel more reasonable than it is. Three biases do most of the damage:

• Continuation bias (get-there-itis). Once a plan is in motion, new information gets read in the plan's favor. A 1,800-foot ceiling becomes "probably lifting." A TAF you'd have canceled over yesterday becomes "workable if we leave now."
• Sunk cost. The hour you spent preflighting and the fuel you already bought feel like reasons to launch. They aren't — they're spent either way. The only question that matters is whether the flight in front of you clears your minimums.
• Social pressure. Passengers watching you check the weather a fourth time. A spouse expecting you home. A rental slot that expires. None of these change the weather; all of them change how you read it.

Plan continuation shows up again and again in AOPA Air Safety Institute accident analyses of fatal GA weather accidents — pilots who pressed on into deteriorating conditions rather than diverting, most lethally in VFR flight continued into IMC. The pattern is rarely a pilot who never saw the weather. It's a pilot who saw it and kept negotiating with it.

The fix is not more willpower. It's moving the decision to a time and place where the biases are weak: at home, the night before or the morning of, against criteria you wrote down when nobody was waiting on you.

How do you use the PAVE checklist for a real flight?

PAVE — from the FAA's Risk Management Handbook — splits the decision into four categories so nothing gets waved through as "fine, probably." Work through it concretely, not ceremonially.

P — Pilot

Start with IMSAFE: Illness, Medication, Stress, Alcohol, Fatigue, Emotion. Answer honestly — "a little tired" after five hours of sleep is a fatigue hit, not a footnote. Then recency, which is where most personal risk actually hides:

• When did you last fly this airplane (or type)?
• When did you last land in wind like today's? At night? On a runway this short?
• Are you legally current — and, separately, actually proficient — for what this flight demands?

Legal currency (three takeoffs and landings in 90 days for passengers) is a floor. If your last real crosswind landing was in March and it's July, your crosswind number today is not your crosswind number from March.

A — Aircraft

• Squawks. Read the squawk sheet before you commit, not at the hold-short line. An inop attitude indicator is a different flight in marginal VFR than on a clear day.
• Fuel. Plan to land with a real reserve — many careful pilots use one hour, well above the 30-minute day-VFR legal minimum. Fuel exhaustion remains a steady, entirely preventable slice of GA accidents.
• Performance for today. Not book numbers at sea level standard — today's density altitude, today's weight, this runway. Run the takeoff and landing distances and compare against the actual pavement with margin (a common rule: runway at least 1.5× the POH distance). A hot afternoon can quietly turn a comfortable runway into a marginal one — check it with a density altitude calculator.

V — enVironment

This is the category pilots think of as "the weather," but it's wider:

• Ceilings and visibility vs. your minimums. Not legal minimums — yours. Look at the trend, not just the current METAR: is the TAF improving or decaying through your departure window? (See how to read a TAF.)
• Winds vs. your crosswind max. Compute the component at the gust value, at departure and destination — the crosswind calculator does this in seconds. Forecast winds at your ETA matter more than winds now.
• NOTAMs and TFRs. Closed runways, unlit obstacles, out-of-service approaches, and pop-up TFRs are all go/no-go inputs. Know which NOTAMs actually matter and check them the same day.
• Night and terrain. Night converts a marginal ceiling into an invisible one, and rising terrain converts a scud run into a trap. If any leg is dark or mountainous, your numbers for that leg should already be tighter.

E — External pressures

Name them out loud, because unnamed pressure does its work invisibly:

• Who is waiting at the other end, and what did you promise them?
• What happens if you don't go — concretely? Usually the honest answer is "we drive," "we leave tomorrow," or "I make a phone call." Almost never is it anything that justifies added risk.
• Do you have a plan B already arranged? A pilot with a refundable hotel room and a rebookable meeting cancels easily. A pilot with neither negotiates with the weather.

What numbers actually decide the flight?

PAVE organizes the questions; personal minimums supply the answers. The comparison must be against your own numbers, not the legal ones — legal VFR minimums in some airspace permit conditions that most pilots cannot safely handle. If you haven't set personal minimums, that's the prerequisite step: written figures for ceiling, visibility, crosswind, gusts, runway length, and fuel reserve, set on a calm day.

With those in hand, the go/no-go check becomes almost mechanical: ceiling forecast 2,500 broken against a 3,000 minimum is a no-go — not a discussion. Winds 14 gusting 22, 60° off the runway, against a 10-knot crosswind max is a no-go. That's the whole point. The hard thinking happened weeks ago; today is just arithmetic.

What does a marginal "caution" call require?

Not every flight is a clean go or a clean no-go. Conditions that clear your minimums with little to spare — or clear them now but trend the wrong way — are a legitimate middle ground, but flying into it carries requirements, not just acceptance:

• An out. A specific alternate with better weather, reachable at any point along the route — not "I'll figure something out."
• A hard divert trigger. A pre-stated condition that ends the attempt: "if I can't hold 3,000 AGL over the ridge, I turn around at the checkpoint." Decided on the ground, so that en route you're executing a plan rather than making a new decision under stress.
• Extra fuel. The marginal flight is the one where you'll need the option to divert, hold, or backtrack. Top the tanks; land with more than your normal reserve.

If you can't supply all three, the marginal flight isn't a caution — it's a no-go wearing a costume.

Why re-run the decision close to departure?

Because forecasts age. A go decision made at 7 a.m. on a 6 a.m. TAF is stale by a noon departure — TAFs are routinely amended, and the atmosphere doesn't consult the forecast. Re-check the latest METARs, the current TAF, and any new NOTAMs or TFRs shortly before you launch, and run the same comparison again. A "go" that survives a fresh look is a go. A "go" you're reluctant to re-examine is your gut telling you something your checklist should hear.

And the decision never fully closes: the same minimums that grounded you at home are your divert triggers in the air. Go/no-go is not one decision at the hangar — it's a standing comparison you keep running until the airplane is tied down.

Common Questions

Related guides and tools

Educational content for flight-planning practice. It is advisory only and not a substitute for an official weather briefing, your POH, or your own judgment as pilot in command (14 CFR 91.3). Sources: FAA Risk Management Handbook (FAA-H-8083-2A); FAA Pilot's Handbook of Aeronautical Knowledge, Ch. 2 (Aeronautical Decision-Making); AOPA Air Safety Institute accident analyses. Last reviewed: July 17, 2026.