The Go/No-Go Decision: A Working Framework

A go/no-go decision is the judgment a pilot makes about whether a specific flight can be flown safely in the conditions that actually exist, weighing four inputs: the pilot, the aircraft, the environment, and any outside pressure to go. The honest version of that judgment is not a single yes at the hangar door. It is a chain of smaller decisions that starts the first time you look at the forecast and keeps running until the engine is shut down and the airplane is tied down.

The framework below turns that judgment into something repeatable: a structured self-assessment you run the same way every time, backed by hard numbers you set in advance, when nobody is waiting on you. Those pre-set numbers are your personal minimums, and they are the most useful decision-making tool a GA pilot owns, because they move the hard call off the ramp, where pressure lives, and back to the kitchen table, where it doesn’t.

Go/no-go is a chain, not a verdict

Most of us were taught go/no-go as a gate: you brief, you decide, and once you’ve decided to go, the deciding is over. That model fails in the exact situation it’s meant to cover. Weather changes. The airplane develops a squawk on the ground. A passenger shows up two hours late and now you’re landing at an unfamiliar field after dark. A single yes at the start has no answer for any of that.

A better model treats the go decision as provisional and time-limited. You make it, then you keep testing it against what the flight actually shows you. There are natural checkpoints where the decision comes up for renewal: at planning, at the airplane, before takeoff, at top of climb, at each fuel or weather decision point en route, and on approach to any airport you intend to use. At every one of those, the airplane is still on the ground or still has the fuel and altitude to change the plan. The decision keeps its teeth right up until it doesn’t.

This is also where the regulation lives. 14 CFR 91.103, Preflight action, opens with the line every checkride hangs on: “Each pilot in command shall, before beginning a flight, become familiar with all available information concerning that flight.” For flights under IFR or not in the vicinity of an airport, that explicitly includes weather reports and forecasts, fuel requirements, and the alternatives available if the flight can’t be completed as planned. The rule is describing the same chain: it isn’t asking whether you glanced at the weather, it’s asking whether you know enough to keep making good calls once the wheels are up. Gathering that information well is its own discipline, and our guide to briefing aviation weather before every flight covers the sequence. This post is about what you do with it.

A framework you can run: PAVE plus numbers set in advance

The FAA’s structured tool for this is the PAVE checklist, from the Risk Management Handbook (FAA-H-8083-2A, 2022). It splits every source of risk on a flight into four buckets so none gets overlooked, and the letters are worth reading literally:

• P — Pilot. Are you fit to fly this trip today? Experience, currency, and recency in type and in the conditions expected, plus your physical and mental state. The IMSAFE checklist (Illness, Medication, Stress, Alcohol, Fatigue, Emotion/Eating) is the sub-tool here. Fatigue and self-imposed stress are the two that pilots consistently rate too generously.
• A — Aircraft. What does the airplane let you do today? Airworthiness and open squawks, equipment for the conditions (an airplane with an inoperative attitude indicator has no business near marginal weather), fuel capacity, and honest performance numbers for the field elevation, weight, and temperature you’ll actually see.
• V — enVironment. Weather, terrain, airspace, runway lengths and surfaces, lighting, and time of day. This is the bucket most people mean when they say “the weather looks fine,” and it’s the one with the most moving parts.
• E — External pressures. Why is this flight happening, how badly does someone need it to, and is that need starting to answer the other three buckets for you? This is the bucket that gets people killed, and it gets its own section below.

PAVE is a sorting tool. It makes sure you looked at everything. What it doesn’t do by itself is tell you where “acceptable” ends, and that’s the half most pilots skip. A checklist that runs on judgment alone will quietly bend toward whatever you already want to do. The fix is to pair the four buckets with hard numbers you decided on in advance: a ceiling you won’t launch below, a crosswind you won’t take, a fuel reserve you won’t shave, a personal duty-day limit. When the environment bucket says “800-foot ceiling” and your number says “1,500 for this route,” you don’t have to adjudicate anything in the moment. You already did.

The FAA frames the in-the-moment loop as the 3P model: Perceive the hazards, Process their effect on the flight, Perform by mitigating or deciding. PAVE is how you perceive. Your numbers are how you process without arguing with yourself. Understanding what those weather inputs actually do to a light airplane, from density altitude to airframe icing, is its own subject, covered in our overview of the weather that hurts GA pilots.

Personal minimums are decisions you already made

Personal minimums are the numbers half of the framework: the limits you set for yourself, above the legal and aircraft minimums, that define the flights you’ll accept. The regulations give you a floor that assumes a current, proficient pilot on a good day. Personal minimums are you admitting you are not always that pilot, and pre-committing to margins that hold on your average day, not your best one.

The power of a personal minimum is entirely in the timing. A ceiling limit written at your desk on a Tuesday, with no trip on the line, is a clean decision. The same limit “reconsidered” on Saturday morning with the family loaded and the destination clear is not a decision, it’s a negotiation you’re going to lose. Writing them down converts a Saturday argument into a Tuesday policy. Build them by category (ceiling and visibility for day and night, surface wind and crosswind, personal minimum runway length, currency thresholds), start conservative, and tighten or relax them only in writing, only when you’re not about to fly. The full method, including a table you can fill in and a schedule for reviewing it, is in our guide to setting personal minimums you’ll actually keep.

Two categories deserve tighter numbers than pilots usually give them. Crosswind is the first: the number in the POH is a demonstrated value from a test pilot on a dry runway, not a limit and not a promise about you. Your personal crosswind limit should reflect your recent landings, not the flight manual, and we work through the difference in demonstrated crosswind versus your limit. Night is the second: the same 1,000-foot ceiling that’s comfortable at noon hides rising terrain and a lost horizon after dark, and margins that work in daylight don’t transfer. Night flying weather margins makes the case for a separate, higher set of night numbers.

The trap: continuation bias and outside pressure

Every framework in this post exists to counter one predictable failure. Once we’ve committed to a plan, we resist changing it, and we resist harder the more we’ve invested and the closer we get to the goal. Psychologists call it plan continuation bias; pilots call it get-there-itis; the FAA’s Risk Management Handbook names it directly as a pattern that turns up again and again in accident files. The bias is not a character flaw you can willpower your way out of. It’s how the mind is built, and it runs strongest at exactly the moment good judgment matters most, on the last leg, near the destination, with weather going down.

The numbers are blunt about where this leads. The AOPA Air Safety Institute’s Joseph T. Nall Report has for years shown weather-related accidents making up a small share of all GA accidents but a much larger share of the fatal ones, and continued VFR flight into instrument conditions sits at the top of that list, with more than 75 percent of those accidents fatal. These are rarely pilots who couldn’t fly the airplane. They’re pilots who kept saying yes to a decision that had quietly expired, often within sight of home. How the last few minutes actually unfold, and the specific outs that break the chain, are the subject of VFR into IMC: how it happens, how it doesn’t.

External pressure is the accelerant, and it’s usually self-supplied. A paid-for hotel, a Monday meeting, passengers who took the day off, the quiet fear of looking timid. None of it changes the weather, but all of it changes how you read the weather. The countermeasures are structural, not motivational:

• Decide the abort conditions before you launch, out loud or in writing. “If the ceiling at the ridge is below 2,000 or I’m not on the ground by 45 minutes past sunset, I turn around.” A pre-set trigger doesn’t care how much you want to continue.
• Name the pressure to make it visible. Saying “the only reason I’m still considering this is the hotel deposit” often ends the argument on its own.
• Kill the false economy of the sunk cost. Fuel and time already spent are gone whether you continue or divert. The only question that matters is the one about the air in front of you.
• Give yourself a graceful out in advance. Tell passengers before you start that you may divert, delay, or drive, and that the decision is final when you make it. Removing the audience removes half the pressure.

Build outs before you need them

A defensible go decision is one that still has options after it goes wrong, and those options have to exist before you launch, because they cannot be created in the air. Building outs is the unglamorous part of the framework that does the most work.

Alternates you’d actually use. An alternate isn’t a box on the flight plan, it’s an airport you have briefed, that you can reach with reserves intact, whose weather is genuinely better than your destination’s and forecast to stay that way. Two alternates in different directions is not overcautious on a marginal day. It’s the difference between a divert and a scramble.

Fuel as a decision, not a leftover. Legal reserves are a floor written for a good day. A personal reserve, an hour in the tanks rather than the regulation’s 30 or 45 minutes, buys you the one thing continuation bias steals: time to think and room to change your mind. Fuel is the resource that converts directly into options, and running it down to the legal line converts options into a single mandatory landing.

Time buffers. Most weather is worse later in a summer afternoon and after dark. A departure that leaves you racing sunset or the day’s convection has spent its margin before takeoff. Building in slack, so that a 30-minute delay doesn’t cascade into a night arrival at an unlit strip, is a go/no-go decision you make with the calendar, days ahead.

The pre-briefed divert. The best divert is one you already flew in your head on the ground: which airport, which frequency, which approach or pattern, what the fuel looks like when you get there. A divert you’ve rehearsed is a calm turn. A divert you’re inventing at 1,500 feet in deteriorating visibility is an emergency wearing a friendlier name.

A marginal VFR flight, decided

Say it’s a summer Saturday and you’re planning a two-hour VFR cross-country from a field near sea level to a mountain airport at 5,900 feet elevation, wheels-up around 1600Z, home again before dark. Nothing about the plan is reckless. Everything about it is marginal in a way the framework is built to catch. (Hypothetical, but the shape of it will be familiar.)

Pilot. You’re current and proficient, but you flew a long day yesterday and slept badly. Run IMSAFE honestly and Fatigue is a soft yes. Not disqualifying on its own, but it’s a debit you carry into every other bucket, and it argues for wider margins today, not narrower.

Aircraft. A normally aspirated single, well maintained, full fuel. The catch is performance, and it belongs to the destination, not the departure. At 5,900 feet field elevation with an afternoon temperature near 30°C, the density altitude works out close to 9,000 feet. Run your actual numbers through the density altitude calculator, then open the POH, and the takeoff and landing distances you memorized at sea level are fiction. Climb performance out of that field, on a hot afternoon, at gross weight, is the real limiting factor of the whole trip.

enVironment. The departure TAF is clean all day. The destination is forecast VFR in the morning with a line that says gusty southwest winds and thunderstorms in the vicinity after 2000Z. The single runway favors a wind that, in the afternoon gusts, would put a crosswind component near the edge of what you’d accept. Before you launch, run the forecast wind through the crosswind calculator against the runway heading, and check it against your personal crosswind limit, not the demonstrated number in the book. This is a mountain field, in the afternoon, in summer convective season. Every part of that sentence is a known hazard stacking on the others.

External pressures. You told friends you’d be there for dinner. That’s the whole pressure, and naming it is most of the work.

Now process it against numbers set in advance. Your personal minimum for an unfamiliar mountain field says arrive no later than two hours before the convective forecast goes bad, which means a hard turnaround well before 2000Z, not a hopeful one. Your fuel policy says land with an hour aboard, which on this route means the return leg has to launch on schedule or not at all. Your fatigue debit says widen, not shave.

The defensible call is not a simple no. It’s a go with pre-set outs: launch early, treat 1800Z as the go/no-go for the return rather than a target, brief a lower-elevation alternate in the flatlands that stays VFR all day, and commit out loud that if the destination winds or the convective timeline move earlier, you divert to the alternate and drive the last hour. That is a defensible decision because it survives being wrong. The version that gets people hurt is the same flight with none of the outs, launched at noon, arriving as the first cells build, low on fuel and options, with dinner as the only thing still voting yes.

The go decision expires

The single most useful habit in this entire framework is to treat the go decision as perishable. It was made with the information you had at the time, and that information starts aging the moment you turn away from the computer. A briefing from three hours ago describes a different atmosphere. A go decision made before a passenger showed up late no longer fits the flight you’re actually about to make.

So re-decide, on a schedule, at the checkpoints where you still have the power to act: at the airplane with the latest observation, before takeoff, at top of climb with the picture ahead, at each planned fuel and weather point, and on every approach. At each one, ask the small version of the same question: does the flight in front of me still fit the numbers I set, and do I still have the outs I built? When the answer changes, the plan changes with it, and it changes while you’re still on the ground or still have the fuel and altitude to make changing easy. The pilots the Nall Report counts are, overwhelmingly, the ones who made one go decision and then stopped asking. Keep asking. The go decision is a lease, not a deed, and the ground is a far better place to discover it expired than the air.

FAQ

What is the go/no-go decision in aviation?

It’s the pilot-in-command’s judgment about whether a specific flight can be flown safely in the conditions that exist, based on the pilot’s fitness, the aircraft, the environment, and any external pressure to go. It isn’t a one-time gate at the start. A good go/no-go is a chain of decisions that keeps running from planning through shutdown, renewed at every point where you still have the ability to change the plan.

What are personal minimums?

Personal minimums are self-imposed limits, set above the legal and aircraft minimums, that define which flights you’ll accept: ceiling and visibility, surface wind and crosswind, runway length, currency, and duty day. Their value comes from being decided in advance, with no trip on the line, so the hard call is already made before pressure arrives. Our personal minimums worksheet walks through building a set you’ll keep.

How is a go/no-go decision different from PAVE?

PAVE (Pilot, Aircraft, enVironment, External pressures) is the FAA’s checklist for finding every source of risk on a flight, so nothing gets overlooked. The go/no-go is the decision you make after sorting those risks. PAVE tells you what to look at; your personal minimums and pre-set abort triggers tell you where acceptable ends. You need both: the checklist without hard numbers bends toward whatever you already want to do.

Common questions

What does PAVE stand for?

PAVE is the FAA risk checklist from the Risk Management Handbook: Pilot, Aircraft, enVironment, and External pressures. It sorts every hazard on a flight into four buckets so nothing gets overlooked: your fitness and currency, the airplane and its equipment, weather and terrain and time of day, and the reasons pushing you to go. It finds risk; it does not tell you where acceptable ends.

When should I re-check a go decision once the flight has started?

At every point where you can still act on the answer: at the airplane with the latest observation, before takeoff, at top of climb with the picture ahead, at each planned fuel or weather decision point, and on approach to any airport you intend to use. Each check asks the same small question: does this flight still fit the numbers I set, and do I still have my outs?

What does 14 CFR 91.103 actually require before a flight?

It requires the pilot in command to become familiar with all available information concerning that flight before beginning it. For flights under IFR or not in the vicinity of an airport, that explicitly includes weather reports and forecasts, fuel requirements, and the alternatives available if the flight cannot be completed as planned. The standard is knowing enough to keep making good calls once you are airborne.