The Questions That
Build a Crew

CRM training tells pilots to speak up, challenge constructively, and ensure shared understanding. What it rarely provides is the actual language to do any of those things. The competency is described. The mechanism is named. The words are left as an exercise for the pilot.

This matters more than it might seem. Knowing that you should ask open questions and actually having a set of open questions that feel natural under pressure are different things. The pilot who understands the principle but has never practised the language will, under workload, default to silence or to closed questions that close the conversation rather than open it.

This article is about the language. Specifically, about questions — how they work, when to use them, and what they sound like in the context of the real flight deck. It is aimed at both crew members, because effective questioning is not just an FO skill. It is the mechanism by which a Captain draws on the crew's collective capacity, and by which any crew member confirms that what they said has actually been understood.

Open and Closed — Why It Matters

A closed question has a binary answer. "Are you happy with that?" invites yes or no, and in the context of crew dynamics — where the Captain has just explained something and is implicitly expecting agreement — it almost always gets a yes, regardless of whether the First Officer is genuinely happy with it or not. The question feels like an invitation to confirm, not to contribute.

An open question has no predetermined answer. "What's your read on the weather at the alternate?" requires the other person to actually think, form a view, and express it. The answer cannot be yes. It might surprise you. It might contain information you did not have. That is precisely the point.

The distinction is not about politeness or CRM technique. It is about cognitive resource management. Every open question is an invitation for the other person's situational awareness, knowledge, and judgement to enter the shared mental model. Every closed question is a small act of exclusion — it confirms that the person asking already has the answer and simply wants ratification.

On a two-crew flight deck, a Captain who asks only closed questions is flying with one brain. A Captain who asks open questions is flying with two.

The Experience Gradient Problem

The experience gradient is one of the least discussed challenges in crew operation, and one of the most common. A newly promoted Captain flying with a highly experienced First Officer. A line check where the examiner in the right seat has more hours, more type experience, or deeper knowledge of the company's operations than the Captain being assessed. A fractional operator where senior Captains routinely fly as First Officers — and where the person in the left seat may be significantly less experienced than the person in the right.

The authority sits with the Captain. The knowledge may not. And that gap creates a specific leadership challenge that neither CRM training nor standard operating procedures address directly: how do you lead someone who knows more than you do?

The answer is not to pretend the gradient does not exist. Experienced crew members are aware of it immediately, and a Captain who performs certainty they do not have will lose credibility faster than one who acknowledges the situation honestly. The answer is to use the gradient deliberately — to ask questions that make the First Officer's experience available to the crew without abdicating command in the process.

The experienced First Officer in this dynamic has their own challenge. The temptation — usually well-intentioned — is to fill the space. To offer information the Captain has not asked for, to suggest decisions before they have been invited, to manage the flight deck in the way they would if they were Captain. That is not teamwork. It is a quiet takeover, and it leaves the Captain less able to exercise command, not more.

The experienced FO's role is to make their knowledge available without imposing it. Open questions work in both directions — the FO who asks "what would you like me to monitor on the approach?" is contributing actively while keeping the Captain in command. The FO who simply starts monitoring without a word has made a unilateral decision about task allocation that the Captain may not even be aware of.

Confirming Understanding — Closing the Loop

One of the most common communication failures on the flight deck is not the absence of information — it is the absence of confirmed understanding. Something is said. The other person nods, or says "roger", or says nothing. The speaker assumes it has landed. It has not, or not completely, or not in the way it was intended.

Confirmed understanding is not the same as acknowledged transmission. The readback that confirms a clearance has been received is not the same as a conversation that confirms a plan has been genuinely shared. The first is procedural. The second requires a question.

The questions that confirm understanding are deliberately simple. They are not tests. They are invitations for the other person to demonstrate — to themselves as much as to you — what they have taken from what was said. A paraphrase is more valuable than a repeat. If someone can say back what they understood in their own words, the shared mental model is real. If they can only repeat what was said verbatim, you do not yet know whether understanding exists.

The Question Framework

What follows is not a script. It is a set of questions, mapped to specific flight deck moments, that have been found useful across different crew dynamics and experience gradients. They are starting points — the actual language will develop with practice and will need to fit the crew relationship and the situation.

Each question is tagged by who it is most naturally used by, though most can be adapted for either crew member.

Using These Questions Well

A few observations from using open questioning in crew environments — both as a line training captain and in MCC training where the habits are being built for the first time.

Timing matters as much as content. A good question asked at the wrong moment — during a critical phase of flight, when the other person is task-saturated, when the crew is already under pressure — will either go unanswered or generate a truncated response that is no more useful than silence. The questions in the framework above are most valuable when asked early, in the space before the demanding phase arrives. The brief is not just for sharing plans. It is for building the questioning relationship that makes the questions safe to ask later.

The question has to be genuine. A Captain who asks "what's your view?" and then ignores the answer — or visibly considers it for half a second before proceeding with the original plan — is not asking an open question. They are performing one. Experienced crew members notice immediately, and the next question will get a shorter, more cautious answer. Open questioning only works when the person asking is genuinely prepared to be influenced by the response.

Practice reduces the activation energy. The first time a pilot asks a colleague "what would you be doing differently if you were in the left seat today?" it will feel uncomfortable. The tenth time, it will not. The questions in this framework are not natural language for most pilots trained in the command-and-comply tradition. They become natural through repetition, and that repetition needs to start somewhere — ideally in normal operations, before the moment arrives when it genuinely matters.

Silence is also an answer. When you ask an open question and the response is slow, hesitant, or conspicuously thin, that is information. The First Officer who says "no, I think we're fine" to "is there anything about this situation we haven't talked about yet?" may genuinely mean it. Or they may be telling you that the crew environment does not yet feel safe enough for the real answer. Either way, the question has done its job by revealing where the shared understanding actually is.