There is a moment in every captain upgrade that no simulator can prepare you for. It is not the first single-pilot emergency, or the first time you take a crew into weather that demands every resource you have. It is quieter than that. It is the first time a first officer looks at you — not for information, but for a lead.
Rank is conferred in a ceremony. Leadership is earned in that moment, and in every moment that follows. The distinction matters enormously — and in aviation training, we have not always been honest about it.
The Rank Assumption
Command upgrade programmes have traditionally focused on technical currency, procedural mastery and regulatory knowledge. These are necessary. They are not sufficient. What they produce, at best, is a technically competent pilot with the authority to make decisions. What they do not automatically produce is a leader — someone who can shape the performance environment around them.
The ICAO and EASA Core Competency frameworks recognise this. Leadership and Teamwork — is not a single behaviour. It is a cluster of nine observable behaviours that together describe what genuine flight deck leadership looks like in practice. They include cooperating as a team, taking initiative, preparing and briefing effectively, managing and demonstrating leadership skills, showing empathy, clarifying roles, building trust, acknowledging errors and influencing assertively.
"The stripes tell the crew who has final authority. The behaviours tell them whether that authority is worth following."
What is striking about this list is how many of the behaviours are relational rather than technical. They are about how a captain engages with their crew — not just what they know or how precisely they fly.
What the Research Actually Shows
The aviation safety record has improved dramatically over the past four decades. Much of that improvement is attributable to better systems, better procedures, and better training. But a significant portion traces directly to the maturing understanding of crew dynamics — what happens between the people in the flight deck, not just what happens with the aircraft.
The Tenerife disaster. Air France 447. Numerous approach-and-landing accidents where a technically capable crew failed to function as a unit under pressure. The common thread in these events is not a failure of individual skill. It is a failure of the leadership environment — specifically, the failure to create conditions where all available information could reach the person who needed it.
A crew that does not feel psychologically safe to challenge will not challenge. A crew that has not had roles clearly established will improvise under pressure. A crew that has not been led with genuine empathy will disengage at precisely the moment engagement matters most.
Takes initiative and gives direction when required
Give clear, calm direction during high workload phases. Assign tasks explicitly and confirm execution.
Adapt your leadership style to the crew and situation. Be directive when required, consultative when time allows.
Create conditions where the crew can perform at their best. Manage the environment as much as the task.
The Three Shifts of Command
Pilots who make the transition from first officer to captain successfully tend to navigate three distinct shifts — shifts in how they think about their role, their crew, and their responsibility.
From Individual to Environmental
As a first officer, your primary performance domain is your own. You manage your scan, your calls, your workload. As a captain, your primary domain expands. You are responsible not just for your own performance, but for the performance environment you create. A captain who is technically excellent but creates an environment of tension, uncertainty or fear is not a high-performing captain — regardless of what the flight data recorder shows.
From Reactive to Anticipatory
Leadership under pressure is too late. The most effective captains are not distinguished by how they handle the crisis — they are distinguished by the fact that their crews rarely reach crisis, because the environment they created meant threats were identified, communicated and managed earlier. Briefings that surface contingencies. Role clarity that prevents task confusion. Psychological safety that means the first officer speaks up at the first deviation, not the fourth.
From Knowing to Modelling
A captain who lectures their crew about assertive communication but never demonstrates it themselves has not led — they have instructed. The behaviours that define high performance on the flight deck are caught more than they are taught. Your crew will calibrate their standard against yours, not against the SOP manual.
"The behaviours that define high performance are caught more than they are taught. Your crew will calibrate their standard against yours."
What Observable Behaviour Actually Looks Like
One of the most useful contributions of the Core Competency framework is that it makes leadership observable. It moves the assessment of a captain from the vague — "good command presence," "strong CRM" — to the specific.
Consider the briefing. Most captains brief. Fewer brief interactively — inviting input, confirming understanding, adapting to the specific flight. Fewer still brief in a way that builds a shared mental model and surfaces latent threats before they affect the flight. The first is procedural compliance. The third is leadership.
Or consider trust. Trust is not built by being technically excellent. It is built by doing what you say you will do — consistently, transparently, and honestly. A captain who acknowledges an error to their first officer without defensiveness builds more trust in that moment than a year of smooth flying.
The Nine Leadership & Teamwork Behaviours
Implications for Command Development
If we accept that captaincy is more than rank — that it requires a specific, learnable, observable set of behaviours — then command development programmes need to do more than test technical currency and procedural knowledge.
They need to create structured opportunities for captain candidates to practise the relational behaviours of leadership: debriefing errors honestly, adapting communication style to crew and situation, building trust through consistent follow-through, influencing assertively without becoming aggressive. These behaviours cannot be assessed on a type rating checkride. They need to be developed over time, through practice, reflection and feedback.
This is precisely what self-directed development tools like High Performance Pilot are designed to support — not as a replacement for formal training, but as the daily practice layer that reinforces and deepens the behaviours that formal training introduces.
The four stripes are the beginning of the journey, not the destination. The behaviours that follow them are what captaincy actually is.
That Define Captaincy
HPP gives you structured daily practice across all nine Core Competencies, with How-To guides at three levels and a progress report you can take to your next appraisal. Free to start.
Try Free →