How to Prepare for and Practice Airline Group Discussions

Most people walk into their first GD thinking it's a debate. Six or eight strangers, one topic, and a scoreboard nobody can see. So the instinct is to talk the most, sound the smartest, and out-argue everyone else in the room.

That instinct is wrong, and it's the single biggest reason capable people underperform in a GD.

Here's the thing nobody explains clearly enough: an airline isn't putting you in a room with strangers to see who wins the argument. They're watching how you behave inside a small group under time pressure. Because that's exactly what a flight deck is. Two or three people, a limited amount of time, and a problem that has to get solved together. Pilots even have a name for this: Crew Resource Management. It's the whole discipline built around the idea that a competent individual can still make a crew perform badly if they don't communicate, listen, or share the load properly. A GD is airlines getting an early look at whether you'd be that kind of teammate before they ever hand you a headset.

So the honest goal in the room isn't "sound impressive." It's "be someone this group would actually want on their crew." Those two goals produce completely different behaviour, and evaluators can tell the difference immediately.

The nerves get you before the topic does

Plenty of candidates who could talk about aviation for hours freeze the second they're sitting in a circle with five strangers and an evaluator taking notes. It's not a knowledge problem. It's that the room itself is unfamiliar, and unfamiliar rooms make people's brains go quiet.

The fix isn't confidence tricks. It's lowering the stakes in your own head. You're not being asked to perform. You're being asked to have a normal discussion with other people, the same way you would with classmates or colleagues. Nobody in a genuine conversation is grading every sentence. Try to actually believe that before you walk in, because your body language, pacing, and willingness to speak will all follow from it.

You also don't need to have an opinion loaded and ready for every conceivable topic. There are thousands of possible prompts. Memorising your way through all of them isn't realistic and isn't the point. What you're actually being tested on is whether you can think on your feet when the topic is unfamiliar, not whether you happen to already know it.

When the topic lands, give yourself a few seconds before you open your mouth. Quietly ask:

• What's actually being asked here?
• What's the obvious case on each side?
• What would change the answer?
• Do I have a real example, or am I about to invent one?

Then join in. A few seconds of thought beats a fast, empty sentence every time.

Figure out what kind of topic you've been given

Jumping straight into talking without figuring out what type of prompt you're dealing with is one of the most common mistakes in the room, and it's an easy one to fix.

An opinion topic. Something like "should airlines charge separately for carry-on bags?". Wants you to weigh genuine trade-offs, not pick a side and defend it to the death. Benefits, drawbacks, the conditions under which either answer changes, and a conclusion that acknowledges the tension rather than pretending it doesn't exist.

An abstract topic. A line like "a chain is only as strong as its weakest link". Isn't asking for a literal answer, so don't go hunting for one. Pull the concepts out of it first: individual responsibility, shared risk, where failure actually shows up in a system. Then, if it fits naturally, connect it to aviation. Forcing the connection is more obvious than people think.

A scenario topic. "a flight has been delayed six hours and passengers are furious, what does the airline do?". Is a problem, not an opinion. Define what's actually going wrong, weigh a few real options, and land somewhere sensible.

A ranking or activity topic. "you have ten items after an emergency landing, rank them by priority". Needs the most structure of all, because there's no room to talk in circles. You have to actually decide, and be ready to explain why.

Knowing which of these four you're in before you speak changes everything about how the next ten minutes go.

Your opening line doesn't need to be memorable

A lot of candidates put enormous pressure on their first sentence, like the entire discussion hinges on it landing perfectly. It doesn't. Your first contribution just needs to show that you're a real participant with a real thought. Nothing more dramatic than that.

A simple shape works every time: state a position, give one reason, back it with an example.

"I'd lean toward keeping a pilot in the loop rather than going fully autonomous, mainly because most safety incidents come from the unexpected, not the routine. Situations where judgment matters more than following a fixed procedure."

That's a complete, useful opening. You don't need a thesis statement. You need one honest thought, stated clearly.

Listening is the actual skill, not the pause before you talk

If there's one thing worth genuinely internalising, it's this: listening in a GD isn't sitting quietly until it's your turn again. It's taking in what someone just said and actually doing something with it.

Picture someone saying: "Cutting long-haul crew rest hours would save the airline money." A candidate who wasn't really listening waits for a gap and then delivers a point they'd already planned, completely unconnected to what was just said. A candidate who was listening says something like: "That's true on the cost side, but I'd push back a little. Fatigue is one of the more well-documented risk factors in aviation, so any saving there needs to be weighed against a safety cost that doesn't show up on a balance sheet."

The second response does something the first one can't: it proves you were actually present for the conversation, not just waiting for your turn in it. The pattern to aim for is listen, understand, respond, build. Not listen, wait, recite.

And you don't need to perform agreement to show you were listening. Saying "I completely agree" on repeat means nothing by itself. What lands is showing you understood the point well enough to add to it, push on it, or connect it to something else. The words matter far less than whether the group can tell you were paying attention.

Disagreeing without becoming the problem

Disagreement isn't the issue in a GD. How it's delivered is. "That's just wrong" shuts a person down and adds nothing. "I see where that's coming from, but I think there's an angle we haven't covered" keeps the discussion moving and still makes your point.

The distinction is simple: challenge the idea, never the person who said it. You can dismantle an argument completely while still treating the person who made it with basic respect. In fact, doing both at once is usually what evaluators are actually looking for.

If two people in the group start going back and forth and the temperature rises, resist the urge to pick a side and pile on. That's actually your best moment to step in as the calm one: "I think you're both onto something. One of you is focused on the upside here, the other's flagging the risk. Maybe the real question is what conditions would need to be true for the upside to actually hold." You've just defused a fight, credited both people, and moved the group forward. All in one sentence. That's worth far more than winning either side of the argument.

Leadership is quieter than people expect

The person talking the most in a GD is rarely the one evaluators mark as the leader. Real leadership in a ten-minute discussion looks like: getting things started when nobody else will, gently steering the group back on topic, connecting two people's points that clearly belong together, calming a disagreement, checking the time, or helping the group land on an actual conclusion instead of just running out of clock.

Notice that almost none of that is about your own opinion. It's about the group functioning. That's exactly why leadership and teamwork tend to show up as the same behaviour in a GD, even though candidates often treat them as opposites.

One caution here: don't turn into the self-appointed moderator. Constantly saying "let's hear from everyone" or "let's stay structured" without ever contributing an actual idea of your own isn't leadership. It's just narrating the meeting. If someone's been quiet for a while, a simple "we haven't heard your take on this yet" is genuinely useful. Doing it every ninety seconds is not. Use these moves when the group actually needs them, not as a script you're running through to look good.

Watch the clock and watch the topic

Two things quietly sink otherwise-good GDs: running out of time with no conclusion in sight, and drifting so far from the original prompt that nobody remembers what was asked.

You don't need a stopwatch in your head, but a rough sense of pacing helps a lot. Early on, the group should be surfacing different angles on the topic. By the middle, you should be testing and connecting those angles against each other. In the last stretch, the group needs to actually be converging toward something, not still generating fresh ideas. If you notice at the nine-minute mark that nobody has said anything resembling a conclusion, that's on everyone in the room. Including you.

Drift is just as common. A discussion about airline safety regulation can somehow end up being about a completely unrelated news story within a few minutes. When that happens, you don't need to shut it down rudely. A simple "that's an interesting point, but coming back to the original question…" brings things back without making anyone feel scolded.

It's fine to change your mind

If somebody makes a genuinely better point than the one you opened with, say so. "I was leaning against this earlier because of the safety concern raised, but the point about reduced fatigue actually shifts my thinking. I could see a supervised version of this working." That's not a loss. It's evidence you can actually update your thinking in real time, which is precisely what you'd want from someone in a cockpit when new information comes in. Defending a weak position out of pride is far more damaging than being seen to change course.

Say the plain thing

Don't reach for words you wouldn't normally use. Don't manufacture an accent or a "professional" register that isn't yours. "The main concern is safety" beats a much longer sentence stuffed with words like "ramifications" and "paradigm," every single time. Clarity reads as competence. Trying too hard to sound intelligent usually reads as exactly that. Trying too hard.

Your posture is part of the conversation too

Sit like you're actually in the discussion, not observing it from a distance. Look at whoever you're responding to. When you're addressing the whole group, let your eyes move around the group, not lock onto the evaluator the entire time. Don't stare at the table. Don't fold yourself away from the circle. None of this needs to be performed. It mostly sorts itself out once you're genuinely engaged rather than anxious.

If you genuinely know nothing about the topic

This happens to everyone eventually, and it's not fatal. Let the first couple of contributions from other people pass, and use them. You'll usually pick up what the core question actually is, where people disagree, and what assumptions are floating around, just from listening for a minute. Then contribute from reasoning rather than invented facts: "I don't know the technical side of this well, but from a safety standpoint, I'd think…" is a completely legitimate way in, and far better than confidently stating something you're not sure is true.

Your aviation knowledge is a tool, not the whole point

It's tempting, especially in an airline GD, to treat every topic as a chance to prove you know the industry. Resist that. If the topic touches automation, bring in workload, safety culture, training, and regulation where they genuinely help your point. Don't start reciting facts about flight-control systems nobody asked about. Knowledge should sharpen an argument, not replace one.

The one sentence worth remembering

You don't need to be the smartest person in that room. You need to show that you can think clearly, listen properly, disagree without damaging the discussion, and adjust when the evidence calls for it. With a group of strangers, under time pressure, the same way you'd be expected to on a flight deck.

That's really the whole test.

Frequently Asked Questions