Individual skill stopped being enough for airline safety decades ago; what carries a modern flight is the crew — and a crew is built, not assumed. This lesson assembles it: the awareness each member owes the others, the multi-crew machinery of SOPs, checklists and briefings, and the group dynamics that decide whether two pilots add up to more than two or to less.
Safety awareness
The founding obligation is awareness of performance — your own and everyone else's, before and during the flight. A colleague's fatigue, distraction or degradation is operational information, and the cost of not gathering it is written into the accident record. The starkest case is the commuter flight whose first officer, junior and on probation under an irascible senior captain, completed the approach checks with no responses from the left seat and challenged nothing: the aircraft flew into the ground short of the runway. The captain had not been sulking; he had died during the approach, and the incapacitation lesson's two-communication rule exists precisely so that silence is read as an alarm rather than a mood.
The multi-crew concept
Multi-crew cooperation is the functioning of the flight crew as a team of co-operating members led by the pilot-in-command, and its objectives are the reasons a second pilot is worth a salary: workload shared through task sharing, mutual monitoring and cross-checking, redundancy against error and incapacitation, and synergy (a whole exceeding its parts). The elements that deliver those objectives: task sharing between handling and monitoring roles, communication, SOPs, checklists and briefings, and the two kinds of synchronisation that hold the pair together — cognitive synchronisation (a common image of the situation, maintained through briefings and checklists) and temporal synchronisation (actions triggered together or in planned sequence).
Communication is the glue in that machine, and its coordinating function has a hard edge: announcements of modes, altitudes and intentions are the only guarantee that all the crew share the same model of the situation. The rule that follows is worth memorising as written: never abandon dialogue with the other crew members to concentrate exclusively on dialogue with the machine.
SOPs, checklists and briefings
Standard operating procedures are decisions made in advance: published patterns of behaviour that become habitual, covering every situation that can be foreseen. Their advantages compound: they reduce the decision-making load in flight, they make each pilot's actions predictable enough for the other to monitor (which is what lets two strangers fly together safely — the reason civil aviation rejected the constituted-crew model), and in threat and error management terms they work at all three stages: they avoid threats by pre-deciding the response, reduce errors because standard calls catch drift early, and manage what still arrives through practised drills.
Their threats live mostly at the boundaries, and the syllabus points at company and type conversion: the old type's motor programmes keep firing in the new cockpit (the environmental capture of the error lesson, wearing a company uniform), company cultures differ in what they leave unwritten, developed habits and shortcuts get absorbed unnoticed into a crew's practice (the constituted crew whose thumbs-up meant landing flap — until a replacement co-pilot read it as a compliment), and imported hazardous attitudes ride along, a subject the personality lesson takes up properly.
The two instruments the syllabus wants described:
Checklists — the written backbone of normal and abnormal operation: read, do or confirm, respond. They exist because working memory is small and interruption-fragile, which is also the operating rule: an interrupted checklist is restarted, never resumed.
Briefings — the crew's cognitive synchronisation in advance, and effective when they are short (fewer than ten ideas, split into sections if the standard version runs long), individual (built for this flight, not recited from habit), and understood by all — a simple, well-understood plan supported by everyone beats a brilliant one that was misunderstood. The commander emphasises the areas that will need crew cooperation.
Groups: cooperation, coaction and synergy
A group is a set of people with shared characteristics, goals, values and interests that give a sense of belonging — and interdependence is what makes it more than a list of names: each member's behaviour and effectiveness is shaped by the others, for better (mutual monitoring, drawn strength) and worse (the pressures below). The syllabus wants a working distinction: coaction is working in parallel toward a common goal: same site, same objectives, but relatively independent actions, the everyday relationship of flight crew and cabin crew. Cooperation is tighter: different, complementary actions deliberately designed to develop synergy, with communication keeping one shared image of the situation. (The exceptional third case, redundant action, is strict duplication: both pilots on the controls to avoid an obstacle.)
Synergy is the prize: the state where group performance exceeds the sum of the individual performances (one plus one making more than two), and its absence makes the group worse than its parts. Teamwork's ledger reads accordingly. Advantages: shared workload, mutual monitoring, pooled knowledge and experience, synergy itself, and strength drawn from each other in difficulty. Disadvantages: conformity pressure, groupthink, the risky shift the decision-making lesson already met (with the diffusion of responsibility that drives it), and the quiet coasting in which a member lets a colleague 'who probably knows what he is doing' proceed down the wrong road.
The essential conditions for good teamwork are a checkable list, and the syllabus asks for them:
Objectives understood by all and committed to by all; mutual trust and mutual support both high.
Communications open and reliable rather than guarded and cautious; members listen, understand and are understood.
The team is self-controlling; conflicts are accepted and worked through rather than smoothed over; and every member's abilities, knowledge and experience are actually used.
Cohesion, groupthink and the group's pressures
Cohesion is the sum of the forces binding crew members together, built on mutual motivation toward the job and mutual appreciation, and it is a genuine asset in difficulty. But cohesion overdone curdles into groupthink: a group so bound by its 'we-ness' that members will not introduce or entertain unsettling information for fear of upsetting the room: the mechanism behind historic fiascos from appeasement to the Bay of Pigs, and behind cockpit silences that killed. The group's other pressures act on each member's behaviour, and the syllabus names four: conformity (the stooge experiment: a lone subject will deny the evidence of his own senses to agree with four confederates, though a single partner in dissent breaks the spell), compliance (requests granted step by step: agree to the small sign and the large one follows), obedience to status (the high-status voice carries disproportionate weight: when right it persuades far more of the room than a junior would, and the junior's correct answer persuades far fewer), and persuasion, which the flight deck should rarely need: if a disagreement cannot be resolved by airing the facts, the group is not working, and persuasion earns its place only when a fact has genuinely been overlooked.
Role, norm and status
A role is the function currently performed, and behaviour follows the social expectation of it: the committee member made chairman behaves differently by the next meeting, and the newly promoted commander often changes visibly in the left seat. Norms are the standards a group adopts around its roles, written and unwritten: the constituted crew's absorbed hand signals and shortcuts were unwritten norms in action, and unwritten norms are where bad habits hide. The role patterns of a group are recognisable on any flight deck: leader and follower, handling and monitoring pilot, and the darker cast the canon documents in its two failed cockpits — the laissez-faire cockpit's vacuum-filler who assumes command when a passive captain leaves it lying, and the autocratic cockpit's withdrawn member, who has decided to say nothing more, and its scapegoat, usually ATC or the cabin, onto whom suppressed aggression is displaced.
Status is different from role: status is rank (the rings on the uniform), while role is today's function, and the flight deck constantly mixes them. The mix has documented dangers: a dominant captain freely questions a junior first officer but the reverse barely happens: the junior must be absolutely sure before airing anxiety, a threshold the safety-awareness accident shows to be lethally high; two pilots of equal status (a training detail with two captains) are notoriously reluctant to take control from each other; and the senior commander flying the co-pilot role under a lower-status captain is an escalating-conflict risk unless both handle it professionally. Culture modulates all of it — in some cultures questioning a senior is close to unthinkable, and the monitoring half of the multi-crew concept dies exactly there.
Leadership, followership and the gradient
The syllabus distinguishes what the uniform cannot: authority is assigned; leadership is acquired, and suggests a voluntary following. Followership is the active counterpart, not the passive one: supporting, monitoring, contributing assertively — the follower who challenges when the picture disagrees is doing the multi-crew concept's core work, without usurping command. Between the seats runs the trans-cockpit authority gradient, and its three shapes are the exam's favourite trio.