Some of the flights that look easiest before takeoff end up demanding more attention in the cockpit than you expected.

Think back to your last “easy VFR” flight. It probably had some mix of clear skies, good visibility, light winds, and a familiar route. The kind of day you go for a Sunday joy ride. On paper, it looks like the kind of day where everything should feel manageable. Most pilots have had flights like that. You may have even been tempted to skip your pre-flight planning requirements under 91.103 — or actually did.

Either way, you blast off thinking weather probably won’t be the thing that drives your decision-making today. Or traffic. Or emergencies.

That assumption is exactly where things start to go sideways.

Expectation Bias: Your Brain Has Already Decided

There’s a name for what happens in the cockpit on days like this: expectation bias. It’s not just a feeling — it’s a well-documented cognitive tendency to filter incoming information through what you already believe will be true. Once your brain has decided a flight will be uneventful, it quietly begins deprioritizing data that might suggest otherwise.

Picture this: you pull the ATIS and it’s slightly worse than what you saw on your weather app an hour ago. Ceilings are a little lower, visibility is a touch softer. Nothing alarming. But because you already decided this was going to be a nice day, your brain rounds it back to “fine.” You weren’t lying to yourself. You were pattern-matching in a direction that felt safe — and that’s exactly what makes expectation bias so hard to catch in the moment.

This is why structure matters more on easy days than hard ones. Checklists, thorough briefings, and explicit go/no-go criteria aren’t just tools for bad weather — they’re tools for overriding a brain that has already made up its mind. They force you to evaluate conditions on their own terms, not through the lens of what you expected to find.

Normalization of Deviance: The Drift You Don’t Notice

Expectation bias sets the stage. Normalization of deviance is what happens over time when nothing goes wrong.

The term comes from sociologist Diane Vaughan, who studied the culture at NASA leading up to the Challenger disaster. Her finding was striking: when a deviation from standard occurs and nothing bad happens, that deviation gradually gets accepted as the new normal. The threshold shifts. And it keeps shifting, quietly, until the gap between what the standard actually requires and what people actually do is enormous — and nobody quite remembers how they got there.

In a cockpit it sounds like this: you skip 91.103 on a route you’ve flown a hundred times. Nothing happens. You do it again. You start briefing the weather “quickly” because you already know what it’ll say. You stop resetting the next frequency until you actually need it. Each instance feels harmless. Each one probably is harmless. But the habit that’s forming isn’t harmless — and one day the conditions won’t be what you expected, and the shortcuts will compound at exactly the wrong moment.

I see this developing in real time with students. A student skips a checklist step once. Nothing happens, so the brain files it away as acceptable. They skip it again. By the third or fourth flight, it’s just how they do it — and they’re not even aware it happened. That’s normalization of deviance in its earliest form, and it’s far easier to prevent than to reverse.

The antidote isn’t stricter self-criticism. It’s periodic recalibration — not just maintaining standards, but actively revisiting why the standard exists. That’s the difference between training to the ACS and training beyond it. A student who understands the reason behind a checklist item will maintain it long after the checkride. A student who learned it as a box to check will drop it the first time it feels inconvenient.

Multitasking Is a Myth, and the Cockpit Proves It

Here’s something cognitive scientists have known for decades that most pilots haven’t fully internalized: multitasking isn’t real.

The brain doesn’t actually parallel-process complex tasks. What feels like multitasking is rapid attention-switching — the brain jumping between tasks in sequence, with a small but real cost every time it makes the switch. The more tasks competing for attention, the longer each switch takes and the more information gets dropped in the gaps. When the queue gets long enough, things fall off the end entirely.

On an easy VFR day, the queue fills up slowly. That’s what makes it so deceptive.

Traffic gets heavier than expected. Frequency changes come faster. You’re trying to spot a target approach just called out. A passenger asks a question right as you’re listening for your sequence. You start thinking about the arrival, notice you’re a little high, realize you haven’t reset the next frequency yet. Nothing unusual has happened — but now your attention is spread across six things at once, and each one is waiting its turn.

That’s task saturation. And it doesn’t announce itself. It just slowly becomes the reality of your flight while you’re still operating under the assumption that today was supposed to be easy.

The solution isn’t to think faster. It’s to manage the queue deliberately. Prioritize, sequence, and shed load where you can. That’s what “aviate, navigate, communicate” actually means as a framework — it’s not a motivational poster. It’s a triage protocol for a brain that can only truly do one thing at a time.

A Personal Experience

One of the better reminders I’ve had about this happened on a short VFR hop to the California Central Valley to buy cheaper fuel. The weather was good, the route was easy and direct and I was familiar with the area and airport. Nothing about the flight looked particularly demanding and because of that, I did a lighter preflight briefing than I normally would have.

Somewhere in that shortcut, I missed a NOTAM that the tower was closed on that Sunday. I was on flight following, and when NorCal handed me off, I switched over and started calling the tower. One call, no answer. I called again. Still nothing. Now I’m outside the Class D, orbiting, trying to figure out why nobody is responding. After a couple attempts, I went back to NorCal and told them I couldn’t raise the tower. Their response was immediate: “The tower is closed today by NOTAM. Didn’t you read them?”

Getting called out like that was eye-opening. My thoughts immediately went back to that light pre-flight brief. It wasn’t a difficult flight and that was the whole point. The conditions made it feel routine before I ever left the ground, and that mindset quietly changed the quality of my preparation.

How to Push Back

None of this means you should approach every blue-sky day with white-knuckle vigilance. The goal isn’t to make easy flights feel hard. It’s to stay honest about what “easy” actually costs in attention, preparation, and habit. A few things that help:

Brief every flight like the weather is marginal: The process should be identical regardless of conditions. What changes is the output, not the inputs. If your briefing on a nice day takes thirty seconds, you’re not briefing — you’re confirming what you already believe.

Use the 5Ps deliberately, especially when nothing seems wrong: It’s tempting to skip a structured review when there’s no obvious threat. That’s precisely when the check matters most, because the threats on easy days are the ones that accumulate quietly.

Name your expectation out loud before departure: Say it explicitly, even just to yourself: “I expect this to be routine.” Then ask: “What would change that?” It’s a simple forcing function that pulls the brain out of confirmation mode and into evaluation mode.

Build unfamiliarity into your flying: Normalization of deviance accelerates when you’re flying the same routes, the same airports, the same airspace week after week. Periodic exposure to new environments — a different destination, an unfamiliar airport, an IFR flight when you mostly fly VFR — resets the baseline and reminds you what deliberate evaluation actually feels like.

When workload spikes, slow your decision-making down: The instinct is to speed up. The right move is usually the opposite. Prioritize ruthlessly, let low-priority tasks wait, and resist the urge to race the queue.

The Debrief

The easy VFR day isn’t dangerous because something went wrong. It’s dangerous because nothing did — and the brain filed that away as confirmation that less preparation was fine.

Expectation bias narrows what you’re willing to see. Normalization of deviance raises the floor on what feels acceptable. And a brain that can’t actually multitask is trying to manage all of it while also flying the airplane.

Most of the time, it works out. The day really was easy. The shortcuts didn’t matter. That’s the problem.

Because the flight where they do matter looks exactly the same on the weather briefing.