Crew resource management¶

Crew resource management trains communication, leadership, situational awareness, and decision-making to control human-error risk in high-consequence teams.

Version: v1 · 2026-09-28 · History
Domain-specific #: 7608
Domain group: Applied Sciences & Engineering
Origin domain: Aviation & Aeronautics
Subdomain: Aviation Human Factors → Aviation & Aeronautics

Core Idea¶

Crew resource management (CRM) is training for the effective use of people, information, equipment, and procedures in high-consequence operations where human error can be catastrophic.^[1] Originating in aviation as cockpit resource management, it develops the cognitive and interpersonal skills by which a crew detects error, shares an accurate picture of the situation, makes decisions, and safely completes a mission.^[2]

CRM trains nontechnical coordination rather than the technical operation of an aircraft. Its recurring skills include clear two-way communication, situational awareness, decision making, assertiveness, leadership, teamwork, mission analysis, adaptability, and workload management.^[3] The command hierarchy remains, but lower-ranking crew members are expected to state hazards and question a decision until the evidence is addressed, while leaders actively solicit and integrate relevant information.^[4]

The mechanism is error management through distributed attention and challenge.^[5] Briefings establish roles and contingencies; standardized callouts make observations actionable; cross-checks expose discrepancies; simulations rehearse time-critical coordination; and debriefings turn performance into corrective learning.^[6] CRM treats human error as inevitable and seeks to prevent individual slips, fixation, authority gradients, or ambiguous responsibility from becoming system accidents.^[7]

The term now includes whole aircrews rather than only pilots and engineers, and related programs adapt the method to maintenance, maritime bridges and engine rooms, rail, firefighting, and surgery.^[8] Those adaptations retain the resource-coordination and human-error-control structure but require domain-specific procedures. CRM is not generic friendliness, technical proficiency, or a checklist alone: it requires trained interaction practices that change how a high-consequence team notices, communicates, decides, and recovers.^[9]

How would you explain it like I'm…

Team Catches Mistakes

On an airplane, the pilots and crew are a team. Crew resource management teaches them to talk clearly, watch out for each other's mistakes, and speak up if something looks wrong, even to the boss pilot. That way one little mistake doesn't turn into a big accident.

Teamwork That Catches Mistakes

Crew resource management, or CRM, is training for teams doing dangerous jobs where mistakes can be very bad, like flying planes. It isn't about how to fly the plane; it's about how the team works together. People learn to talk clearly, notice what's going on, make decisions, and speak up if something looks wrong, even if they are not the boss. The captain is still in charge but is expected to listen. Because everyone makes mistakes sometimes, CRM helps the team catch them before they cause harm.

Team Error Management Training

Crew resource management (CRM) is training in how to make the best use of people, information, equipment, and procedures in high-stakes work where human error can be catastrophic. It started in aviation as "cockpit resource management" and focuses on non-technical skills: communication, situational awareness, decision making, assertiveness, leadership, teamwork, and managing workload. It assumes human error is inevitable, so the goal is to catch and manage errors before they become accidents. The chain of command stays in place, but junior crew members are expected to challenge a decision until the evidence is addressed, and leaders are expected to ask for input. Tools include briefings, standard callouts, cross-checks, simulator practice, and debriefings. CRM is not just being friendly or having a checklist; it's trained ways of interacting that change how a team notices, talks, decides, and recovers.

Crew resource management (CRM) is training for the effective use of all available resources, meaning people, information, equipment, and procedures, in high-consequence operations where human error can be catastrophic. Originating in aviation as cockpit resource management, it builds the cognitive and interpersonal skills a crew uses to detect error, share an accurate situational picture, decide, and safely complete a mission. It targets nontechnical coordination rather than technical operation: two-way communication, situational awareness, decision making, assertiveness, leadership, teamwork, mission analysis, adaptability, and workload management. The mechanism is error management through distributed attention and challenge. Briefings set roles and contingencies, standardized callouts make observations actionable, cross-checks expose discrepancies, simulations rehearse time-critical coordination, and debriefings convert performance into corrective learning. The command hierarchy remains, but subordinates are expected to voice hazards and question decisions until addressed, while leaders actively solicit and integrate information, flattening harmful authority gradients. CRM treats error as inevitable and aims to keep individual slips, fixation, authority gradients, or unclear responsibility from becoming system accidents. The term now covers whole aircrews, and related programs adapt it to maintenance, maritime operations, rail, firefighting, and surgery with domain-specific procedures.

Structural Signature¶

Sig role-phrases:

the high-consequence crew — the interdependent operational team whose distributed actions and attention determine mission safety
the available resources — people, information, equipment, time, and procedures coordinated rather than left in isolated roles
the shared situational picture — the crew's maintained account of system state, hazards, priorities, and likely next events
the authority gradient — the command relation retained while observations and concerns are required to move upward and be answered
the communication-and-challenge protocol — briefings, callouts, acknowledgments, and closed-loop exchanges carry discrepancies into assertive questioning, evidential response, and plan revision or confirmation
the workload allocation — explicit distribution and reassignment of tasks as attention and operational demand change
the rehearsal–debrief cycle — scenario practice followed by performance review that converts coordination failures into trainable corrections
the error-management outcome — prevention, detection, trapping, or recovery before individual slips or fixation become system accidents
the adaptation branch — transfer to maintenance, maritime, rail, firefighting, or surgery only with the receiving domain's roles, hazards, and procedures restored
the training boundary — technical proficiency, cordial teamwork, a checklist, or course attendance alone does not establish CRM behavior under operational load

What It Is Not¶

Not technical flight training. CRM develops communication, situational awareness, decision making, leadership, assertiveness, and workload coordination; it does not teach the underlying aircraft-handling or systems knowledge.^[10]
Not cordial teamwork alone. Agreeable interaction is insufficient unless crew members share operational information, cross-check one another, challenge hazards, and close the communication loop under load.
Not the abolition of command authority. CRM retains role and command structure while requiring lower-ranking members to voice relevant concerns and leaders to receive and address them.^[11]
Not a checklist or briefing by itself. Those tools instantiate CRM only when they support a shared situation picture, explicit responsibilities, error detection, decision revision, and recovery behavior.
Not proof of safety from course attendance. A program label or completed class does not establish that trained coordination behaviors occur during consequential operations.^[12]
Not an accident-classification system. Human-factors taxonomies may diagnose contributing failures after an event, whereas CRM is a training and operational practice intended to manage error through crew coordination.

Scope of Application¶

Crew resource management applies to high-consequence operational teams trained to coordinate people, information, equipment, time, and procedures so that human error is prevented, detected, trapped, or recovered from. Aviation is the home domain; a receiving field counts literally only when it restores its own roles and hazards while retaining shared-situation, communication, challenge, workload, decision, rehearsal, and debrief practices.

Flight-deck operations — pilots use briefings, callouts, cross-checks, challenge-and-response, workload distribution, and contingency planning across routine and abnormal flight phases.
Whole-aircrew coordination — pilots, engineers, and cabin crew share safety-relevant observations across occupational and authority boundaries.
Airline CRM training — classroom instruction, simulator scenarios, line-oriented practice, and debriefings teach observable coordination skills rather than technical aircraft handling.
Military aviation — aircrews adapt the same error-management functions to mission-specific command structures, hazards, and procedures.
Air-traffic control — controllers coordinate shared traffic pictures, handoffs, workload, and time-critical decisions under domain-specific separation rules.
Aviation maintenance resource management — technicians, supervisors, and operators address latent maintenance errors through communication, procedural compliance, task coordination, and assertive reporting.^[13]
Maritime bridge resource management — deck officers coordinate navigation, watchkeeping, communication, and command on the ship's bridge.^[14]
Maritime engine-room resource management — engineering teams apply resource coordination to machinery monitoring, workload, faults, and shipboard response.
Rail resource management — train crews and rail organizations train situational awareness, communication, decision making, and error recovery under rail operating rules.^[15]
Wildland and structural firefighting — emergency teams adapt CRM to command, changing hazards, near-miss recognition, and coordinated response under severe time pressure.^[16]
Surgical and clinical teams — healthcare adaptations use huddles, handoffs, check-backs, debriefs, and protected challenge to manage patient-safety risk.
TeamSTEPPS programs — hospitals, long-term-care facilities, and primary-care clinics train CRM-derived teamwork practices within their own clinical roles and procedures.

Clarity¶

Crew resource management distinguishes safe coordination from both technical proficiency and agreeable teamwork. A crew can operate equipment expertly yet remain vulnerable to fixation, an unchallenged command error, lost situational information, or ambiguous responsibility. CRM retains command authority while requiring observations and concerns to cross the authority gradient, so assertive challenge and receptive leadership are complementary safety behaviors rather than insubordination and courtesy.

The label also keeps tools from being mistaken for the trained interaction they support. A checklist, briefing, callout, simulator, or debrief is useful only insofar as it helps the crew build shared situational awareness, distribute workload, make decisions, and detect or recover from error. The operational question is: how will this team notice a developing discrepancy, communicate it unambiguously, challenge the current plan, and confirm that the response restored a safe state?

Manages Complexity¶

High-consequence operations combine changing hazards, technical tasks, limited attention, time pressure, specialized roles, and a command hierarchy. CRM makes this coordination problem tractable by tracking a smaller set of nontechnical functions: situational awareness, communication, decision making, assertiveness, leadership, mission analysis, adaptability, teamwork, and workload distribution. Briefings establish roles and contingencies; callouts and cross-checks expose discrepancies; challenge-and-response makes authority-gradient failures visible; and debriefings convert episodes into trainable corrections.

For a crew, this vocabulary makes the error pathway readable. A practitioner can ask who held a critical observation, whether it entered the shared picture, who owned the decision, whether contrary evidence was challenged and acknowledged, and how workload or fixation narrowed attention. Training branches—classroom instruction, simulation, line-oriented practice, briefing, and debriefing—address different points in that pathway. Domain adaptations such as maintenance or maritime resource management retain the coordination functions while substituting their own roles and procedures.

The compression stops before the operation itself. CRM cannot replace aircraft knowledge, equipment design, staffing, procedures, regulation, or a technical safety analysis, and the presence of a checklist does not establish effective coordination. Program labels also do not measure behavior automatically: assessment still needs observable performance standards, scenario context, and evidence that the trained communication and decision practices were used under load.

Abstract Reasoning¶

CRM supports a discrepancy-to-action inference. From one crew member's observation that the shared operational picture may be wrong to an explicit callout, cross-check, challenge, acknowledgment, and revised decision, the method turns distributed attention into error control. If the observation remains private or a challenge is not received and resolved, the coordination chain has failed even when each individual is technically proficient.

The framework also permits backward diagnosis after an event. From an unsafe outcome or near miss to the sequence of perception, communication, authority, workload, and decision states, an investigator can ask where information ceased to be shared or acted upon. This distinguishes a technical equipment failure from fixation, ambiguous task ownership, a steep authority gradient, or an overloaded crewmember, while allowing more than one contributing breakdown.

Intervention reasoning follows the same chain. From a briefing that assigns roles and contingencies, standardized callouts that expose discrepancies, and simulations that rehearse challenge-and-response to observable team behaviors under load, trainers can test whether the intervention changes coordination rather than merely teaching vocabulary. Debriefing then moves from recorded performance to a specific adjustment in communication, workload distribution, or decision practice.

These moves stop before mission competence is complete. CRM cannot infer aircraft state without technical data, replace operating procedures or system design, or guarantee safety from attendance at a course. Domain adaptations must preserve the error-management functions while supplying their own roles, hazards, and procedures.

Knowledge Transfer¶

Within aviation, CRM transfers literally across flight decks, aircraft types, operators, and mission phases when training preserves communication, situational awareness, decision making, assertiveness, leadership, workload distribution, and error-control practices. The cargo that carries intact includes briefing, callout, cross-check, challenge-and-response, acknowledgment, and debrief diagnostics; interventions test whether information crosses roles and authority gradients before an unsafe state develops.

Beyond aviation, CRM has an honest (B) shared team-safety mechanism in surgery, maritime operations, and other high-consequence teams when those practices are adapted to their actual roles, hazards, and command structures. The home-bound cargo is cockpit procedure, aircraft systems, flight authority, and aviation regulation. A generic teamwork seminar that borrows the name without scenario practice, shared-picture checks, or error-management behaviors is only analogy (A). The stopping boundary is operational fidelity: technical competence or cordial communication alone does not instantiate CRM.

Examples¶

Canonical¶

United Airlines Flight 173 is an origin case in the development of crew resource management in the United States.^[17] While the crew troubleshot a landing-gear problem during an approach to Portland in 1978, the captain remained focused on that problem despite repeated indications from the first officer and flight engineer that fuel was dwindling.^[18] The fuel supply was exhausted and the aircraft crashed short of the runway.^[19] The accident helped prompt an NTSB recommendation that flight crews be trained in flight-deck resource management, with particular attention to participative command and assertiveness by other cockpit crewmembers.^[20] The case does not show an absence of technical aircraft knowledge; it shows how fixation, an incomplete shared picture, and ineffective upward communication can prevent a crew from coordinating its available resources before an error becomes an accident.

Mapped back: The flight-deck team was the high-consequence crew, and its fuel, time, attention, information, and personnel were the available resources. Landing-gear fixation prevented the fuel indications from becoming the shared situational picture. The captain's relation to the first officer and flight engineer formed the authority gradient, while repeated hints that did not alter the response marked a failure of the communication-and-challenge protocol. Sustained concentration on one problem exposed a breakdown in the workload allocation; fuel exhaustion followed by the crash shows that the error-management outcome was not achieved.

Applied / In Practice¶

In a healthcare adaptation, a clinical team uses a central-line safety checklist with an observer who may be lower-ranking than the person performing the procedure. If the observer notices that a required safety step has not been completed, the CRM-derived behavior is to state the discrepancy clearly, obtain acknowledgment, and pause until the team resolves it. The checklist alone is not the mechanism: the protective effect depends on the observer's permission to challenge, the leader's receptive response, closed-loop confirmation, and a shared understanding of the patient's current safety state. The clinical procedure and infection-control standard remain domain-specific rather than being supplied by aviation training.

Mapped back: The clinical team is an instance of the adaptation branch in which local roles and hazards are restored. The checklist and clinical information are part of the available resources, while the observed discrepancy updates the shared situational picture. Protected escalation and acknowledgment instantiate the authority gradient and the communication-and-challenge protocol. The fact that possession of a checklist does not prove coordinated behavior enforces the training boundary.

Structural Tensions¶

T1: Command authority versus assertive challenge. A clear hierarchy coordinates time-critical action, while an unchallenged leader can isolate crucial observations and sustain a failing plan. Flattening authority entirely can make responsibility ambiguous; suppressing challenge defeats distributed expertise. Diagnostic: Can a lower-ranking member state a hazard, receive acknowledgment, and persist until evidence is resolved while the designated leader retains decision responsibility?

T2: Shared situational picture versus distributed attention. Crew members monitor different instruments, tasks, and environments, giving the team broader coverage than one operator. Integrating every observation can overload communication, while filtering too aggressively leaves critical discrepancies private. Diagnostic: Which changes must enter the common picture now, who confirms them, and which details can remain role-local without degrading safety?

T3: Workload specialization versus cross-check resilience. Assigning tasks to defined roles reduces duplication and protects attention, yet strict compartmentalization can allow fixation or failure to pass unnoticed. More cross-checking adds resilience but can distract members from their primary duties. Diagnostic: Does the workload plan preserve independent monitoring of critical states without creating competing ownership or excessive communication?

T4: Standardized protocol versus adaptive judgment. Briefings, callouts, acknowledgments, and check-backs make communication predictable under pressure, while abnormal situations may not fit the rehearsed script. Improvisation can restore fit or dissolve the shared coordination structure. Diagnostic: Which protocol element remains safety-critical, and what explicit cue authorizes deviation while preserving role and acknowledgment clarity?

T5: Simulation learning versus operational transfer. Rehearsal and debriefing expose coordination failures without real-world consequences, yet course performance or vocabulary does not guarantee behavior under workload, uncertainty, and authority pressure. Realism increases learning value but cannot reproduce every mission condition. Diagnostic: Are the trained behaviors observed and assessed in representative operational contexts rather than inferred from attendance or checklist completion?

T6: Nontechnical coordination versus technical dependence. CRM addresses communication, awareness, decisions, leadership, and error recovery, but those behaviors operate on technical information and procedures they do not supply. A well-coordinated crew can still share an incorrect technical picture; technical experts can still fail as a team. Diagnostic: Is the problem a coordination breakdown, a technical-knowledge gap, or an interaction requiring remedies in both layers?

T7: Error tolerance versus accountability. Treating human error as inevitable encourages detection, trapping, and recovery rather than denial, while careless use of that premise can seem to excuse ignored procedures or repeated unsafe conduct. Pure blame discourages reporting and learning. Diagnostic: Does review separate ordinary error, system conditions, and accountable choices while identifying a concrete coordination defense against recurrence?

T8: Crew Resource Management autonomy versus reduction to Coordination (Coordination). The parent Prime carries the portable alignment of locally responsible participants through shared information and interaction mechanisms toward coherent collective output. Every Crew Resource Management practice is a strict kind of Coordination because crew members join distributed information through briefings, calls, acknowledgments, cross-checks, challenge, and workload allocation. Reduction loses the high-consequence crew, situational picture, authority gradient, rehearsal, debriefing, and error-management outcome; total autonomy hides the general alignment structure. Diagnostic: Does the account preserve the crew-specific protocols and hazards as differentia of this Coordination, rather than treating Evaluation as the genus?

Structural–Framed Character¶

Crew Resource Management is framed-leaning: it contains a clear alignment structure, but its identity is a deliberately taught practice for human teams operating under high-consequence risk. The independently responsible participants, distributed information, alignment mechanisms, and coherent collective output instantiate the smallest reviewed skeleton, Coordination. The cross-domain reach belongs to that Prime. CRM adds a shared situation picture, authority-sensitive challenge, workload allocation, rehearsal and debrief, and the explicit prevention, trapping, or recovery of human error.

Its evaluative_weight is high because CRM is organized around safer, more effective performance and treats preventable coordination failure as undesirable. Its human_practice_bound is high: communication, leadership, assertiveness, challenge, and debriefing are enacted and learned by people in roles. Its institutional_origin is high because aviation training, operating procedures, regulatory expectations, and later domain programs stabilize what counts as CRM. Its vocab_travels is medium: briefing, callout, cross-check, workload, and situational awareness move among high-consequence teams, while cockpit, aircrew, authority-gradient, and mission vocabulary retain the aviation accent. Its import_vs_recognize judgment is import-leaning because CRM does not merely name spontaneous alignment; it installs explicit protocols, permissions, rehearsal, and evaluation practices in a crew.

Its character: Coordination owns the portable distributed-autonomy and alignment skeleton, while CRM supplies a human-factors discipline for making hazards speakable, revisable, and recoverable across an authority gradient. Removing those training and safety commitments leaves generic coordination; removing the coordination skeleton leaves a course or checklist without the interaction chain that defines CRM in practice.

Structural Core vs. Domain Accent¶

Crew Resource Management is a domain-specific specialization of the Prime Coordination: independently responsible participants use explicit alignment mechanisms so their distributed actions produce a coherent collective outcome. CRM fixes that structure to trained human-error management in high-consequence crews.

What is skeletal (could lift toward a cross-domain prime). Coordination supplies multiple agents or components with local roles and partial autonomy, interdependence that makes isolated action insufficient, signals or rules that align timing and choice, and a collective output whose coherence depends on that alignment. This signature recurs in at least three unrelated domains—for example, musicians synchronize distinct parts in an ensemble, distributed software services coordinate updates to a shared state, and cells coordinate differentiated activity through signaling. CRM fills those roles with crew members, distributed observations, briefings and closed-loop exchanges, and safe mission performance.

What is domain-bound. The aviation and human-factors accent supplies a high-consequence crew, an authority gradient, a shared situational picture, workload allocation, standardized callouts, cross-checks, assertive challenge-and-response, and the rehearsal–debrief cycle. Its outcome is prevention, detection, trapping, or recovery before individual slips, fixation, or ambiguous responsibility become system accidents. Adaptations to maintenance, maritime, rail, firefighting, or surgery remain literal only when the receiving domain restores its own roles, hazards, and procedures. Remove these trained safety commitments and generic coordination remains, not CRM.

Why this does not clear the prime bar. Stripping cockpit, crew-training, and error-management vocabulary leaves Coordination's distributed-autonomy and alignment skeleton, which already operates across unrelated substrates and does not require a human authority gradient. Conversely, retain course materials, checklists, and safety aims but remove the real-time alignment of independently responsible participants, and one has technical training or cordial teamwork without CRM's defining interaction chain. The two removal directions establish strict subsumption: Coordination remains complete without aviation, while CRM is the practice-bound specialization that makes hazards speakable, decisions revisable, and crew error recoverable.

This entry is a kind of Coordination.

Instantiates — Coordination (Coordination). CRM aligns independently responsible crew members through shared situational awareness, role and workload assignment, briefings, standardized calls, acknowledgments, cross-checks, and challenge-and-response so their distributed actions produce a coherent safety outcome. Authority and local expertise remain distributed rather than collapsing into one actor. Removing aviation roles, hazards, and training forms leaves Coordination's distributed-autonomy, alignment-mechanism, collective-output signature.

Related to — Learning (Learning). Scenario rehearsal and debriefing are intended to produce durable changes in future crew behavior. That update cycle is a constitutive training mechanism, but CRM's operational identity also includes coordination practices used during a mission, so the whole is not simply Learning.

Related to — Evaluation (Evaluation). Instructors and crews evaluate scenario performance and debrief observations against coordination criteria. Evaluation is one technique inside the rehearsal–debrief cycle, not the defining genus of CRM.

Decline — Evaluation (Evaluation) as a subsumption parent. CRM does not inherently reduce a bounded target through criteria and observations to a verdict or score; it trains and enacts communication, challenge, workload allocation, and error recovery. A debrief can evaluate CRM performance without being CRM as a whole.

Relationships to Other Abstractions¶

Current abstraction Crew resource management Domain-specific

Parents (1) — more general patterns this builds on

Crew resource management is a kind of Coordination Prime

CRM aligns independently responsible crew members through shared situational awareness, role and workload assignment, briefings, standardized calls, acknowledgments, cross-checks, and challenge-and-response so their distributed actions produce a coherent safety outcome.

Hierarchy paths (5) — routes to 4 parentless roots

Crew resource management → Coordination → Concurrency

Show alternative paths (4)

Neighborhood in Abstraction Space¶

Crew resource management sits in a moderately populated region (48^th percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.

Family — Organizational & Operational Failure Modes (38 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-08

Not to Be Confused With¶

Technical proficiency training. Technical training teaches the knowledge and motor or systems skills needed to operate equipment, whereas CRM trains the interpersonal and cognitive coordination that makes distributed expertise usable under pressure. Tell: ask whether the exercise assesses equipment operation or communication, shared awareness, workload, challenge, and decision behavior.
Threat and error management. Threat and error management is an operational framework for anticipating threats and trapping errors, while CRM is the broader training system that develops the crew behaviors used to do so. Tell: ask whether the subject is the threat–error–undesired-state model or the trained coordination repertoire.
Line-oriented flight training. Line-oriented flight training is a scenario-based simulation format in which CRM behaviors can be practiced and assessed; it is not the complete CRM skill set. Tell: ask whether the term names the training environment or the coordination capabilities being trained.
A checklist. A checklist externalizes required items, whereas CRM requires the crew to communicate, cross-check, allocate work, challenge concerns, and close the loop around such tools. Tell: ask whether ticking items alone would satisfy the claimed safety mechanism.
A safety-management system. A safety-management system organizes policy, risk governance, reporting, and organizational assurance, whereas CRM works at the level of crew training and operational interaction. Tell: ask whether the mechanism governs the organization or changes how an interdependent crew coordinates in real time.
Accident investigation. Investigation reconstructs causes and contributing factors after an event; CRM is intended to prevent, detect, trap, or recover from error before it becomes an accident. Tell: ask whether the activity explains a past failure or trains future operational behavior.
Generic teamwork training. Teamwork instruction may promote cooperation without the high-consequence resource, authority-gradient, shared-situation, error-management, and rehearsal requirements of CRM. Tell: ask whether the program tests observable safety-critical coordination under realistic operational load.

References¶

[1] NASA, “The Evolution of Crew Resource Management Training in Commercial Aviation” (source). registry ↩

[2] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[3] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[4] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[5] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[6] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[7] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[8] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[9] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[10] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[11] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[12] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[13] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[14] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[15] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[16] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[17] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[18] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[19] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩

[20] Unverified encyclopedia synthesis; no authoritative source located for the claim as written. ↩