What does DECIDE stand for?

DECIDE is an FAA acronym for Detect, Estimate, Choose, Identify, Do, and Evaluate - a six-step loop for making decisions in flight when conditions change.

What is plan continuation bias?

It's the human tendency to keep pushing toward a plan you've already committed to, even as evidence mounts that the plan has gone bad. The more time, fuel, and emotional investment you've put in, the harder it becomes to turn around.

How is the DECIDE model different from the PAVE checklist?

PAVE is a pre-flight risk assessment you run on the ground to identify hazards and pressures, while DECIDE is an in-flight loop you run repeatedly whenever a fact about your flight changes.

Why do examiners want me to talk through my decisions on a checkride?

Because risk management is written into the ACS, and verbalizing your reasoning shows you're actively running a decision loop. Silence looks like a pilot who isn't managing risk at all.

What's the single best habit for avoiding weather accidents?

Set a personal trigger in advance - a specific, observable condition, like the ceiling dropping below a set number, that commits you to running the DECIDE loop regardless of how you feel in the moment.

The DECIDE Model, the Six-Step Loop You Run When the Weather Turns, and How to Break Plan Continuation Before It Breaks You

The DECIDE model is the FAA’s six-step decision-making loop - Detect, Estimate, Choose, Identify, Do, Evaluate - that pilots run whenever conditions change in flight. Its real purpose is to break plan continuation bias, the human tendency to keep pushing toward a goal even as evidence mounts that the plan has gone bad. Run correctly, it turns a potential accident into a boring, uneventful landing at a different airport.

What Is the DECIDE Model?

The DECIDE model is a structured, six-step process for making decisions in the cockpit when a situation shifts. Each letter is a step you run deliberately, out loud, before your emotions get a vote:

D - Detect. Notice that a fact on the ground is different from the fact you planned around. This is the step most pilots skip, because detecting a change means admitting your plan just developed a crack.
E - Estimate. Weigh the significance of that change. The ceiling dropped - does that matter, and how much?
C - Choose. Pick the outcome you actually want. It may not be your original goal. The good result might be getting on the ground safely tonight, not getting home tonight.
I - Identify. List the actions that could get you there - more than one. A pilot with only one option isn’t deciding; they’re just falling.
D - Do. Commit and act.
E - Evaluate. Assess the effect of what you did, then loop back to the top.

The critical thing to understand is that DECIDE is not a one-time checklist - it’s a wheel. You run it again and again as the situation keeps changing.

Why Do Perfectly Good Pilots Fly Into Bad Weather?

The single most common way general aviation pilots are killed is not a spin or an engine failure. It is a perfectly good airplane, flown by a perfectly capable pilot, into weather they should have turned away from.

The reason they don’t turn is plan continuation bias - the deep human tendency to stick with a plan you’ve already committed to, even as the evidence piles up that it’s going bad. The more you’ve invested (time, fuel, a family lunch, a promise to have the airplane back), the harder it becomes to abandon the plan. Your brain quietly reframes every new piece of bad news to fit the outcome you already want.

The overcast drops a little - you tell yourself it’s just local. The visibility gets hazy - you tell yourself you can still see the ground. You pass a good airport with a long runway and fuel - you press on, because stopping feels like failure and home is only forty more miles away.

Each reframe is reasonable on its own. Stacked together, they form what accident investigators call the error chain: not one catastrophic mistake, but a dozen small, forgivable ones, each of which felt fine in the moment.

How Do I Run the DECIDE Loop in a Real Scenario?

Picture a realistic Sunday. You’re a fresh private pilot, maybe 90 hours, not instrument rated. You flew 120 nautical miles to have lunch with family on a severe-clear fall morning. It’s now 4:00 PM, you have work in the morning, and the airplane is due back tonight for someone else’s lesson at 8:00 AM. Your standard weather briefing warned of a line of weather moving in from the west, ceilings dropping, marginal visual conditions expected along your route by early evening. The sky looks fine right now, so you go.

Thirty minutes in, cruising at 5,500 feet, you notice the high overcast is now much closer above you. Run the loop:

Detect. Say it out loud, even alone: “The ceiling is lower than it was twenty minutes ago.” You noticed, and you didn’t explain it away. That was the hardest step.
Estimate. You’re a visual-only pilot. Your entire safety margin depends on being able to see. A dropping ceiling isn’t a minor annoyance - it’s a direct threat to the one thing keeping you alive. Estimate: this is significant. This is the weather the briefer warned about, arriving early.
Choose. Be ruthless. The outcome you want is not to get home. It’s to be on the ground, safe, airplane intact, tonight. If that’s a field forty miles short, that is still a total success. Choosing the right outcome is where you disarm the bias - you consciously trade the goal your ego wants for the goal your survival needs.
Identify. Name at least three options: (1) turn around and return to the airport where you had lunch, where the weather is still good; (2) divert to the airport with the long runway coming up on your right in about ten minutes; (3) descend and press on toward home underneath the layer. Notice that option three is the one your gut likes best - and the one that leads into the accident report if the ceiling keeps squeezing you down into the trees and towers.
Do. Be honest and pick option two. Make the radio call, enter the pattern, land, taxi in.
Evaluate. You’re on the ground. You pull up the weather on your phone and watch your home field’s ceiling drop over the next hour to something no sane visual pilot would launch into.

Why Does a Good Decision Feel Like Nothing?

Here is what nobody tells you about running DECIDE correctly: when you do it right, nothing happens. There’s no near miss to tell at the hangar. You just landed at a different airport and had a boring evening.

The successful decision is invisible. Your brain gets no reward for it, which is exactly why it’s so hard to do. You have to reward yourself. You have to learn to feel proud of the boring landing.

How Does This Show Up on My Checkride?

Risk management is now baked into every area of operation in the Airman Certification Standards (ACS). It is not a separate section you can ignore.

When an examiner sets up a cross-country scenario and starts feeding you deteriorating weather, they are not testing whether you can hold altitude - they are testing exactly this decision loop. The examiner wants you to detect the change, verbalize it, weigh it, and choose a course of action with real alternatives in it. They want to hear your decision-making out loud. Silence is what fails you, because silence looks like a pilot who isn’t running any loop at all.

How Does the PAVE Checklist Fit With DECIDE?

The PAVE checklist lives right alongside DECIDE and front-loads your risk assessment before you even start the engine. PAVE stands for Pilot, Aircraft, enVironment, External pressures:

Pilot - Am I rested, current, healthy, and honest about my limits?
Aircraft - Is it fueled, airworthy, and equipped for this flight?
enVironment - What’s the weather, terrain, daylight, and what airports are along the way?
External pressures - What is pushing me to go when I shouldn’t?

Look back at that Sunday. Work in the morning. The airplane due back at 8:00 AM. Family watching you fly off like a real pilot. Every one of those is an external pressure, and none has anything to do with whether the sky is safe. Naming a pressure out loud strips most of its power away.

Put the two tools together: run PAVE on the ground before you launch to see the pressures clearly, and run DECIDE in the air every time a fact changes to keep the error chain from linking up.

The One Habit to Carry Into Your Next Flight

Pick a personal trigger. Decide right now - calm, on the ground, no pressure - on a specific, observable thing that will make you run the DECIDE loop no matter how you feel in the moment. The ceiling drops below a number you set. The visibility gets worse two checkpoints in a row. You catch yourself descending just to stay under a layer.

Name it now, because the calm version of you is far smarter and braver than the tired, pressured version at 5,500 feet who desperately wants to be home. Let the smart version make the rule. Let the pressured version just follow it.

The bravest thing you’ll ever do in an airplane is turn around when everything in you wants to keep going. It doesn’t look brave - it looks like a boring landing at the wrong airport. But it’s the whole game.

Key Takeaways

DECIDE stands for Detect, Estimate, Choose, Identify, Do, Evaluate - a repeating loop, not a one-time checklist, that you run each time conditions change.
Plan continuation bias - the urge to stick with a committed plan as evidence mounts against it - is the real killer, and it builds through an error chain of small, reasonable-seeming choices.
The hardest step is Detect, because noticing a change means admitting your plan is failing; the rest of the model is easy by comparison.
Use PAVE (Pilot, Aircraft, enVironment, External pressures) on the ground to name your pressures, and DECIDE in the air to act on changes.
A correct decision often feels like nothing - a boring landing at an alternate airport - so learn to take pride in the uneventful outcome.