The Briefing That
Never Gets Done Properly

Ask any line pilot what a crew briefing is for and they'll give you the right answer. Establish crew roles. Identify threats. Agree how we'll operate together. The theory is well understood. It is taught at every type rating, rehearsed at every sim check, and largely ignored at every turn.

That isn't cynicism. It's an observation that most experienced pilots will recognise. The briefing has become a procedural checkbox — something to complete before the real work begins, rather than a genuine tool for crew performance. And that misunderstanding has consequences that play out quietly on flight decks every day.

Why Briefings Fail

The most common failure isn't a bad briefing. It's a briefing that looks correct but communicates nothing. Both pilots nod at the right moments. The SOP boxes are ticked. And then they climb out with entirely different mental models of how the flight will go.

This happens for a predictable set of reasons. The first is familiarity. Once you've flown a sector a hundred times, the briefing starts to feel redundant. You know the procedure. Your colleague knows the procedure. The tendency is to compress, to reference rather than articulate, to assume shared understanding rather than confirm it. The briefing becomes a formality rather than a function.

The second reason is rank. In many crews, the Captain briefs and the First Officer listens. The expectation of a two-way discussion — where the FO challenges an assumption, raises a concern, or adds information the Captain hasn't considered — is never really established. The briefing runs in one direction, and the crew dynamic that follows reflects that.

The third reason is the absence of specific threat content. Generic briefings — the ones that could apply to any flight on any day — offer almost no value. They confirm that the crew knows the procedures, which is already assumed. What they fail to do is address the actual conditions of today's operation: the weather system building to the south, the unfamiliar airport, the fatigued colleague who's just come off a night sector, the NOTAMs that change the approach.

What the Briefing Is Actually For

A briefing has three distinct functions, and only one of them is commonly understood. The obvious function is information transfer — ensuring both crew members have the same operational picture. But the two less visible functions matter just as much.

The second function is role clarity. Not just who flies and who monitors, but who owns which decisions in which scenarios, how the crew will divide tasks during high workload phases, and what the trigger points are for handing control or escalating a concern. Crews that brief role clarity operate with less friction when it matters. Those that don't discover the gap at the worst possible moment.

The third function is environment-setting. The tone of a briefing establishes the crew dynamic for the rest of the duty. A briefing where the Captain genuinely invites challenge — where the FO's input is not just tolerated but expected — creates a crew that communicates more freely throughout the flight. A briefing where information flows in one direction creates a crew where it continues to flow in one direction, even when it shouldn't.

What an Outstanding Briefing Looks Like

Outstanding briefings share four characteristics, regardless of the operation or aircraft type.

They are specific to today. The crew has looked at the actual conditions — weather, NOTAMs, aircraft status, operational constraints — and the briefing addresses them directly. The threats are named, not implied. The contingencies are discussed, not left unspoken. If the weather at destination is marginal, that's on the table: what does deterioration look like, at what point do we reassess, who calls it?

They establish genuine two-way communication. The Captain creates the conditions for the FO to contribute. Not a performative "any questions?" at the end, but genuine open questions earlier in the process: what have you seen on the weather? Have you flown this approach before? Is there anything from your preparation that we haven't covered? The FO's contribution is integrated, not acknowledged and set aside.

They confirm understanding, not just transmission. There is a significant difference between having said something and having been understood. Outstanding briefers build in confirmation — a paraphrase from the FO, a verbal confirmation of the key contingency plan, an explicit check that the role split is clear. The briefing ends when both crew members demonstrably have the same mental model, not when the Captain has finished speaking.

They are proportionate. A complex operation into a challenging airfield in deteriorating weather demands a thorough briefing. A routine sector to a familiar destination in benign conditions does not require the same depth — but it still requires specificity. The skill is calibrating depth to the operation, not defaulting to either a full SOP recitation or a two-sentence summary.

For First Officers

The quality of a briefing isn't only the Captain's responsibility. An FO who engages actively — who contributes their own preparation, asks specific questions, and confirms their understanding of the plan — will consistently receive better briefings than one who waits passively for information to arrive.

If the briefing you receive is generic, make it specific. Ask about today's threats. Confirm the role split for the non-normal you've just looked at. Share what you found in your own preparation. You are not obligated to accept a low-quality briefing; you are entitled — professionally obligated — to ensure you and your Captain have a shared mental model before you close the door.

This matters especially for those working towards command. The habits you build as an FO become the standard you set as a Captain. First Officers who actively shape the quality of crew communication tend to brief well as Captains — not because they were taught to, but because they've been practising it for years.

The Practical Test

At the end of your next briefing, ask yourself two questions. First: could this briefing have applied to any flight, or was it specific to today? Second: do I know, with certainty, what my colleague will do in the two most likely non-normal scenarios for this operation?

If the answer to either question is unsatisfactory, the briefing wasn't done properly. Not improperly — just not properly. There's a gap between adequate and outstanding, and that gap is where most briefings live. Closing it doesn't require more time. It requires more intent.