Crew Management & Leadership · OUPV & Master Exam

Crew Management & Leadership

Bridge Resource Management, STCW fatigue rules, non-technical skills, human factors, safety culture, and emergency management. The human element behind safe vessel operations.

BRM & CRM origins
STCW rest-hour rules
Human error taxonomy
Just Culture & SMS

What's Covered

Bridge Resource Management (BRM)
STCW Fatigue Rules
Leadership Styles
Crew Briefings
Non-Technical Skills (NTS)
Situational Awareness
Communication Models
Decision Making Under Pressure
Human Error Taxonomy
Swiss Cheese Model
Safety Culture & Just Culture
Safety Management System (SMS)
Emergency Management & ICS
Conflict Resolution & Authority Gradient
Practice Problems with Solutions

Bridge Resource Management (BRM)

BRM is the systematic use of all available resources on the bridge — people, equipment, and information — to achieve safe, efficient vessel operation. It is now required by STCW and taught in approved maritime training programs worldwide.

Origins: From Aviation CRM to Maritime BRM

In the 1970s, NASA researchers studying aviation accidents found that most crashes resulted not from mechanical failures or pilot incompetence, but from failures in crew coordination, communication, and decision-making. The industry developed Crew Resource Management (CRM). After the Exxon Valdez grounding in 1989 — where bridge team breakdowns were central — the maritime industry adapted CRM into Bridge Resource Management. The ISM Code (1994) and subsequent STCW amendments embedded BRM principles into international maritime law.

Core BRM Principles

Leadership & Authority
The captain establishes command climate, sets the standard, and maintains ultimate authority while encouraging crew input
Shared Mental Model
All bridge team members understand the vessel's position, intention, and plan at all times — no one is surprised by a maneuver
Communication
Clear, closed-loop communication for all orders; assertive communication when safety is at risk regardless of rank
Situational Awareness
Continuous monitoring of vessel position, traffic, weather, equipment status, and crew condition
Workload Management
Tasks distributed appropriately; high-workload periods anticipated and prepared for in advance
Decision Making
Structured decision-making using all available resources; options generated and evaluated before committing
Task Management
Priority tasks identified; low-priority tasks deferred during high-workload periods
Automation Management
Understanding autopilot and electronic aids limitations; manual oversight maintained

STCW BRM Requirements

The 2010 Manila Amendments to STCW (effective 2012) made BRM training mandatory for all officers in charge of a navigational watch. The STCW Code Table A-II/1 specifies competence in "use of leadership and managerial skills" including application of task and workload management, effective resource management, and application of decision-making techniques. For Master-level certificates, Table A-II/2 adds requirement for leadership and management skills covering organizational structure, personnel management, and cultural awareness.

Crew Fatigue Management

Fatigue is one of the most significant human factors in maritime casualties. The USCG and STCW both recognize that an fatigued watch officer is as dangerous as an impaired one. Managing fatigue is a legal obligation, not just good practice.

STCW Minimum Rest Hour Requirements

RequirementSTCW Minimum
Minimum rest per 24 hours10 hours
Minimum rest per 7 days77 hours
Maximum rest periods per 24 hoursNo more than 2 periods
Minimum length of one rest periodAt least 6 hours
Maximum interval between rest periods14 hours
Log record requiredYes — hours of rest must be recorded and signed

Critical Numbers to Memorize

10
minimum rest hours per 24-hour period
77
minimum rest hours per 7-day period
6
minimum length of one rest period (hours)

Recognizing Fatigue

Physical Signs
Yawning repeatedly, heavy eyelids, slow reaction time, clumsiness, micro-sleeps
Cognitive Signs
Forgetting recent actions, difficulty concentrating, poor judgment, tunnel vision
Emotional Signs
Irritability, apathy, increased risk tolerance, reluctance to hand over watch
Communication Signs
Shortened responses, missed radio calls, failure to confirm orders, lapses in logging

Fatigue Mitigation Strategies

Schedule watches to protect circadian rhythm — avoid watch rotations that constantly shift sleep time
Strategic napping: 20–30 minutes improves alertness without causing sleep inertia
Limit caffeine to the first half of the watch period; avoid near sleep time
Brief all crew before high-workload events so preparation happens during alert periods
Adjust watch schedule proactively when crossing time zones or during extended passages
Captain must monitor crew condition and relieve any watch officer showing fatigue signs
Maintain rest-hour logs accurately — falsification is a serious violation
Port state control inspectors check rest-hour logs; non-compliance can result in vessel detention

Leadership Styles

Effective captains adapt their leadership style to the situation. Using the wrong style at the wrong time is a BRM failure. Knowing when to direct and when to consult is a core competency tested on the Master exam.

Authoritative (Directive)
When to use
Emergency, time-critical situations, crew is inexperienced, safety is immediately threatened
How it works
Captain gives direct orders, expects immediate compliance, does not consult
Risk if overused
If overused in non-emergency situations, suppresses crew input and creates high authority gradient
Consultative (Democratic)
When to use
Routine operations, passage planning, briefings, non-emergency problem-solving
How it works
Captain solicits input from crew, discusses options, makes final decision with full information
Risk if overused
If used in emergencies, wastes time and creates confusion about who is in command
Delegative
When to use
Experienced crew, routine tasks, captain trusts individual competence
How it works
Task assigned to crew member with authority to execute independently; captain monitors
Risk if overused
Requires competent crew; delegation without oversight creates accountability gaps
Coaching
When to use
Training situations, new crew integration, skill development underway
How it works
Captain explains reasoning, asks questions, allows crew to work through problems with guidance
Risk if overused
Time-consuming; inappropriate during high-workload operations

Command Climate

Command climate is the atmosphere created by the captain that determines how crew behave. A positive command climate: crew speak up about safety concerns without fear; errors are reported and learned from; briefings are thorough; debriefs are honest. A toxic command climate: crew stay silent to avoid the captain's anger; near misses go unreported; shortcuts are normalized; fatigue is hidden. The captain is personally responsible for the command climate aboard the vessel. Every interaction — how the captain responds to a concern, whether they conduct briefings, how they react to a mistake — sets the climate.

Crew Briefings

A thorough briefing creates a shared mental model — everyone on the crew knows what is planned, what is expected, and what to do if something goes wrong. Failure to brief is a BRM failure.

Departure Brief
Timing: Before getting underway
  • Route, waypoints, and planned track
  • Hazards and traffic expected en route
  • Weather forecast and contingency plans
  • Crew watch schedule and assignments
  • VHF monitoring plan and Port Control contacts
  • Emergency equipment locations and procedures
Anchor Brief
Timing: Before anchoring
  • Selected anchorage position and depth
  • Scope calculation and anchor type to use
  • Swing circle and proximity to hazards
  • Holding ground quality
  • Anchor watch duties and alarm thresholds
  • Emergency procedures if anchor drags
Docking Brief
Timing: Before entering port or marina
  • Berth assignment and approach heading
  • Current and wind effects on the approach
  • Line-handling assignments for each crew member
  • Fender placement plan
  • Communication between helm and deck crew
  • Abort plan if approach goes wrong
Heavy Weather Brief
Timing: When significant deterioration is forecast
  • Expected conditions: wind, sea state, duration
  • Course changes to reduce motion or seek shelter
  • Securing procedures for loose gear and hatches
  • Life jacket and harness requirements
  • Man-overboard procedure review
  • Medical plan for crew incapacitation

Briefing Best Practices

Conduct the brief before getting underway — not while maneuvering
Require acknowledgment from each crew member for their assigned role
Use the brief to invite questions — the goal is shared understanding, not a speech
Keep it concise but complete — a 5-minute brief beats no brief and a 30-minute brief that loses the crew
Update the brief when conditions change: new weather forecast, changed berth assignment
Debrief after the evolution — what went well, what to improve next time

Non-Technical Skills (NTS)

Non-technical skills are the cognitive and social skills that underpin safe and effective performance in complex environments. They complement technical knowledge and are now explicitly assessed in maritime education and STCW competency standards.

Situational Awareness

Perceiving, comprehending, and projecting the state of the environment — vessel, crew, traffic, weather

Common breakdown: Channelized attention, plan continuation bias, complacency, fixation on one task
Communication

Clear transmission and reception of information; assertive communication regardless of rank

Common breakdown: Ambiguous language, failure to close the loop, cultural barriers, authority gradient suppression
Decision Making

Generating options, evaluating consequences, selecting and executing the best available action

Common breakdown: Time pressure, cognitive overload, confirmation bias, reluctance to deviate from original plan
Leadership & Followership

Setting standards, maintaining morale, managing crew, and knowing when to defer to the captain

Common breakdown: Excessive authority gradient, failure to delegate, reluctance to speak up
Workload Management

Prioritizing tasks, distributing work, maintaining capacity for unexpected events

Common breakdown: Task saturation, trying to do everything personally, failure to prepare during low-workload periods
Stress Management

Performing effectively under pressure without allowing stress to degrade decision-making

Common breakdown: Freezing, tunnel vision, regression to habit under extreme stress

Situational Awareness

Situational awareness (SA) is the foundation of safe navigation. Mica Endsley's three-level model defines how operators perceive, understand, and project environmental states. Most maritime accidents involve an SA breakdown at Level 2 or 3.

Level 1
Perception
Detecting and observing elements in the environment
Example
Seeing a vessel appear on the radar at 6 miles, bearing 045
Failure mode
Distracted helmsman does not scan radar; contact is not seen
Level 2
Comprehension
Understanding what perceived information means for the current situation
Example
Recognizing that the contact has a constant bearing and closing range — risk of collision
Failure mode
Watch officer sees contact but does not plot it; does not recognize collision risk
Level 3
Projection
Predicting future states based on current understanding
Example
Calculating that without action, CPA will be 0.1 nm in 8 minutes
Failure mode
Officer understands risk but misjudges time available; delays action too long

SA Breakdown Modes to Know for the Exam

Channelized attention
Focusing on one task or contact to the exclusion of others; classic precursor to grounding or collision
Fixation / Expectation bias
Seeing what you expect to see rather than what is actually there; misidentifying a vessel type or position
Plan continuation bias
Continuing with the original plan despite new information indicating it is no longer safe
Complacency
Reduced vigilance during routine or low-stimulus operations; notorious during long overnight passages
Cognitive overload
Too much information; operator cannot process everything and SA degrades rapidly
Information loss
Key information not communicated during watch handover; new watch officer starts with incomplete picture

Communication

Communication failure is a contributing factor in the majority of maritime casualties. Effective bridge communication requires structure, clarity, and discipline — especially under pressure.

Closed-Loop Communication

Required for all helm orders and engine orders

1
Sender transmits
"Come right to 045"
2
Receiver acknowledges & repeats
"Coming right to 045"
3
Sender confirms
"That is correct" — or corrects if wrong

The loop is closed only when Step 3 is complete. An unconfirmed readback leaves open the possibility of a misunderstood order being executed. If the readback is wrong, the sender must immediately correct it before the helmsman acts.

The SBAR Model

SBAR (Situation-Background-Assessment-Recommendation) is a structured communication tool used when a crew member needs to report a concern to the captain or a higher authority. It prevents vague, incomplete reports that leave the captain without enough information to act.

S
Situation
What is happening right now?
"Captain, we have a vessel 2 miles off the port bow at constant bearing"
B
Background
Relevant context
"We are in reduced visibility, fog signal sounding, radar is on 6-mile range"
A
Assessment
What do you think is happening?
"I believe we have a collision risk and the situation is developing quickly"
R
Recommendation
What do you suggest?
"I recommend we alter course to starboard and reduce speed immediately"

Watch Handover / Takeover Brief

The watch handover is a critical communication moment. Information lost here breaks situational awareness for the incoming watch officer before the watch even begins.

Current position, course, and speed
Traffic in vicinity — contacts, their CPA, and any concerns
Weather and visibility conditions and any forecasted changes
Navigational hazards ahead on planned route
Equipment status — any alarms, malfunctions, limitations
Captain's standing orders and any specific instructions for this watch
Crew condition — any fatigue issues, injuries, or assignment changes
Upcoming waypoints, ports, or maneuvers within the watch period

Decision Making Under Pressure

Classical decision-making assumes time to generate and evaluate all options. Real maritime decisions often happen under time pressure, with incomplete information, in a dynamic environment.

Naturalistic Decision Making (NDM)

NDM describes how experienced decision-makers actually work in the field. Rather than generating and comparing multiple options, expert operators rapidly recognize the situation as a familiar type, mentally simulate the first option that comes to mind, and act if the simulation indicates it will work. This is fast and effective for experienced mariners but breaks down in truly novel situations outside their experience base.

Recognition-Primed Decision (RPD)

RPD is the most common decision strategy under time pressure. The operator matches the current situation to a prototype from memory, identifies the typical action, runs a mental simulation of the outcome, and acts. If the simulation fails, the operator modifies the action or tries the next option. The RPD model explains why experience is safety-critical — without a pattern library built from training and experience, the recognition step fails.

The FOR-DEC Model (structured decision tool)

FOR-DEC is a structured decision-making aid used in high-stakes environments to prevent premature closure on a plan before all options and consequences are considered. Use it when time permits — during passage planning, briefings, or non-emergency problem-solving.

F
Facts
What do we know for certain about the situation?
O
Options
What are the possible courses of action?
R
Risks & Benefits
What are the consequences of each option?
D
Decision
Select the best available option
E
Execution
Carry out the decision with full commitment
C
Check
Monitor results; is the plan working? Adjust if needed

Decision-Making Traps Under Pressure

Plan continuation bias
Continuing with the original plan despite clear evidence it is no longer safe; most common pre-accident pattern
Confirmation bias
Seeking information that confirms the existing plan while ignoring disconfirming evidence
Sunk cost fallacy
Committing to a dangerous course because so much time or effort has already been invested
Premature closure
Accepting the first plausible explanation without considering alternatives
Authority bias
Accepting the captain's assessment without question even when your own observation suggests otherwise
Time pressure distortion
Underestimating how quickly a situation is developing; acting too late to be effective

Human Factors and Error Types

James Reason's human error taxonomy is the foundation of modern safety thinking in maritime and aviation. Understanding error types determines the correct defensive strategy.

Error TypeDefinition
SlipUnintended action — the right plan executed incorrectly
LapseMemory failure — a step in a familiar procedure is forgotten
Mistake (Rule-based)Applying the wrong rule to a situation
Mistake (Knowledge-based)Reasoning from first principles with incomplete knowledge leads to a wrong plan
ViolationDeliberate deviation from rules or procedures

The Swiss Cheese Model

James Reason's Swiss Cheese Model depicts each layer of defense as a slice of Swiss cheese — each slice has holes (weaknesses), but normally the holes do not align. An accident occurs only when the holes in all layers align simultaneously, allowing a hazard to pass through every defense.

Procedures
Hole: Standing orders not updated after route change
Equipment
Hole: Radar alarm silenced; never re-enabled
Training
Hole: New officer not briefed on system limitations
Supervision
Hole: Captain not called despite standing orders

The Swiss Cheese Model shifts focus from individual blame to system improvement. The question is not "who made the error?" but "why did all our defenses fail to catch it?"

Safety Culture

Safety culture is the collection of attitudes, values, and behaviors that determine how an organization actually treats safety — not just what the safety manual says. Culture is defined by what happens when no one is watching.

Just Culture

  • Distinguishes honest error from recklessness or willful violation
  • Encourages near-miss reporting — no fear of punishment for honest mistakes
  • Focuses on system improvement rather than individual blame
  • Graduated consequences: error = learning; negligence = counseling; recklessness = discipline
  • Produces more safety data, better hazard identification, continuous improvement

Blame Culture

  • Punishes any error, regardless of intent or circumstances
  • Suppresses near-miss reporting — crew hide mistakes to avoid consequences
  • Hazards accumulate invisibly until catastrophic failure
  • Crew cover up problems rather than fixing them
  • Accidents appear "sudden" despite long pre-existing hazard accumulation

Safety Management System (SMS) — ISM Code

The International Safety Management (ISM) Code requires all SOLAS vessels (and many commercially operated vessels) to maintain a documented Safety Management System. The SMS is the organizational framework for safety.

Safety policy signed by senior management
Risk assessment procedures for shipboard operations
Procedures for reporting accidents, hazardous occurrences, and non-conformities
Emergency preparedness: drills, assignments, communication plans
Maintenance procedures for safety-critical equipment
Internal audits to verify compliance
Management review process to improve the system
Document control — procedures are controlled, current, and accessible to crew

Emergency Management

Effective emergency response requires pre-planning, clear assignments, practiced procedures, and a command structure that functions under stress. Improvisation during an emergency is a sign of failed preparation.

Incident Command System (ICS)

The standardized emergency management structure used by USCG and required under NIMS

ICS was developed by U.S. wildfire agencies in the 1970s after communication failures and unclear command authority contributed to firefighter deaths. It was adopted by DHS/FEMA as the basis for the National Incident Management System (NIMS) after 9/11. USCG uses ICS as the standard command framework for maritime incident response.

Incident Commander
Overall command authority; sets objectives; accountable for all decisions; interfaces with external agencies
Operations Section
Executes tactical response: firefighting, damage control, rescue, navigation
Planning Section
Tracks situation, resources, and develops the Incident Action Plan
Logistics Section
Provides resources: equipment, personnel, fuel, food
Finance/Admin
Tracks costs; handles procurement; documentation for liability and insurance
Safety Officer
Monitors safety conditions; authority to stop unsafe operations immediately

Crew Emergency Assignments

Every crew member must have a pre-assigned role for each emergency type before the vessel gets underway. Emergency assignments are briefed in the departure brief and posted in the crew areas.

Man Overboard
Helm: execute recovery maneuver; Spotter: eyes on person, arm pointing continuously; Rescue: deploy throwable, prepare recovery sling; Radio: DSC alert and VHF Ch 16 call; Captain: direct all action
Fire Afloat
Captain: direct response, Mayday if needed; Engineer: isolate fuel and electrical; Deck: deploy extinguisher, activate fixed system if needed; All: don life jackets, prepare to abandon
Flooding / Sinking
Engineer: locate and plug source, operate bilge pumps; Deck: prepare liferaft and EPIRB; Captain: issue Mayday, plot position, assess abandon-ship timeline
Medical Emergency
Captain: contact USCG or Coast Guard for MEDICO advice; Designated crew: provide first aid; Radio: relay patient condition to shore medical; Navigator: plot course to nearest medical facility

Crew Conflict Resolution

Unresolved conflict degrades the command climate, suppresses safety communication, and impairs bridge team performance. The captain is responsible for resolving conflict before it becomes a safety issue.

Authority Gradient — Too Steep

When crew perceive the authority gap between themselves and the captain as very large, they do not speak up even when they observe safety-critical information. The captain appears unapproachable or punishes disagreement.

Result: captain makes decisions without all available information; crew know the vessel is in danger but say nothing. Classic accident pattern in multiple NTSB and MAIB investigations.

Authority Gradient — Too Flat

When the captain establishes insufficient authority, crew may override decisions, create competing commands, or refuse to follow orders. Particularly dangerous during emergency response when every second counts.

Result: conflicting actions, unclear accountability, no one sure whose call it is during a developing emergency.

Speaking Up to the Captain — The Assertive Statement

Every crew member has not only the right but the obligation to speak up when they observe a safety concern — regardless of rank. The assertive statement is the accepted BRM technique for doing so respectfully but effectively.

1. Get attention
"Captain, I have a safety concern I need to raise"
2. State the problem
"We are approaching the shoal area at 10 knots in this visibility"
3. Recommend action
"I recommend we reduce speed and alter course to seaward"
4. Confirm understanding
"Are you aware of the shoal position on the plotter?"

If the captain does not respond to the concern: repeat more firmly. If still no action and collision or grounding is imminent, the officer has the authority and obligation to take independent action to prevent immediate danger to persons aboard — then immediately report the action taken.

De-escalation Techniques for Crew Conflict

Separate the parties immediately if conflict becomes heated — remove from the operational environment
Listen to each party privately before forming a judgment
Focus on behavior and impact, not personality: what happened, not who is wrong
Identify the underlying interest — what each party actually needs, not just what they are demanding
Reach a specific agreement on future behavior, not a vague promise to do better
Document significant conflicts in the log; serious incidents may require reporting
If a crew member is intoxicated or making threats, remove them from duty immediately — this is non-negotiable
Never allow conflict to persist into a watch where the parties must work together; resolve it or reassign watches

Practice Problems with Solutions

1Under STCW, an officer stands a 4-hour watch from 0000 to 0400. She then sleeps from 0430 to 1200 (7.5 hours). Is she in compliance with rest hour requirements?
Answer

Yes, she is in compliance. She has obtained 7.5 hours of rest in the 24-hour period from 0000 to 2400. However, she has not yet reached 10 hours of rest for the full 24-hour period. If she does not obtain at least 2.5 more hours of rest before the period ends at midnight, she will be out of compliance. Additionally, the 7.5-hour period alone meets the requirement that at least one rest period be 6 hours or longer. The interval between the end of her watch (0400) and the start of her rest (0430) — 30 minutes — does not count against her, but she should be aware that the 14-hour maximum interval between rest periods also applies.

2The captain assigns the first mate to conduct the departure brief for a 45-mile offshore passage. What four topic areas should the brief definitely cover, and why might the captain still be present even though the mate is conducting it?
Answer

The brief should cover: (1) Route and navigation — waypoints, hazards, restricted areas, VHF plan; (2) Weather — forecast, deterioration plan, diversion option; (3) Crew assignments — watch schedule, stations, any limitations; (4) Emergency procedures — nearest shelter, medical plan, EPIRB/liferaft locations. The captain should be present because the brief is ultimately the captain's responsibility under the standard of care. Even when delegated, the captain must ensure the brief was thorough, answer questions beyond the mate's authority, and set the command climate that reinforces briefing as standard operating procedure — not optional.

3You are the captain. Your first mate tells you he thinks the planned anchorage is too exposed for the forecast overnight. You disagree. What is the correct BRM response and why?
Answer

The correct BRM response is to take the mate's concern seriously and engage in a consultative process. Ask the mate to explain his reasoning — what specifically concerns him about the forecast, and what alternative he proposes. Review the weather forecast together. Look at the chart for alternative anchorages. The final decision remains the captain's, but dismissing crew input without engagement is a BRM failure that creates high authority gradient. Studies of maritime accidents consistently show that bridge team members often possessed the information needed to prevent the accident but did not speak up — or spoke up and were dismissed. The mate raising a concern is the safety system working correctly.

4A crew member makes an error during a docking approach that results in a minor collision with the pier. Under a Just Culture framework, what determines whether disciplinary action is appropriate?
Answer

Under a Just Culture, the key question is: was this an honest human error made while following procedures, or was it the result of negligence, recklessness, or a deliberate violation? If the crew member was following the captain's instructions, using proper technique, and made a skill-based slip under reasonable workload — no disciplinary action is appropriate. The correct response is to debrief the incident, identify what contributed to the error (inadequate briefing, unclear assignment, equipment issue), and improve the system. If the crew member was distracted by a phone, ignored a warning, or violated a known procedure, graduated consequences are appropriate. Punishing honest mistakes destroys the reporting culture that prevents future accidents.

5Describe the Swiss Cheese Model of accident causation and give a maritime example.
Answer

James Reason's Swiss Cheese Model depicts safety defenses as slices of Swiss cheese — each layer (procedures, equipment, training, supervision) stops most hazards, but each layer also has holes (gaps in the defense). An accident occurs when the holes in all layers align simultaneously, allowing a hazard to travel through every defense and cause harm. Maritime example: (1) Fatigued officer on watch (hole in rest-hour compliance); (2) Radar alarm was silenced by previous watch (hole in equipment defense); (3) No standing orders for calling the captain in reduced visibility (hole in procedures); (4) Captain not informed (hole in communication). The vessel grounds. Any single hole would not have caused the accident — all had to align. The model emphasizes system failure over individual blame.

6What is the Incident Command System (ICS) and how does it apply aboard a vessel during a man-overboard emergency?
Answer

ICS is a standardized emergency management system that establishes a clear command structure, common terminology, and defined roles for emergency response. It originated in U.S. wildfire management and was adopted as the basis for NIMS (National Incident Management System). Aboard a vessel during a man-overboard: the captain assumes the role of Incident Commander and directs all response activities. A designated crew member takes the helm and executes the recovery maneuver (Williamson turn, quick-stop, or racetrack as briefed). Another crew member maintains eyes on the person in the water and points continuously. A fourth crew member deploys the throwable and prepares the recovery equipment. Radio watch (DSC, VHF Ch 16) is maintained. All crew have pre-assigned roles established in the departure brief — ICS prevents everyone from doing the same job and no one doing the critical tasks.

7Your engineer approaches you during a passage and says she is concerned that a junior crew member is showing signs of fatigue — making small errors and seems irritable and slow. What do you do and what are the regulatory implications?
Answer

Immediately assess the crew member directly. Signs of fatigue — errors, irritability, slow responses — are valid grounds for removing someone from an operational role under your duty of care as captain. Have the crew member rest immediately, even if it requires adjusting the watch schedule. Document the rest hours in the STCW rest-hour log. If the total rest hours for the 7-day period are below 77 hours or the 24-hour minimum of 10 hours has not been met, you have a STCW violation regardless of operational necessity. Regulatory implication: STCW rest-hour logs must be maintained and signed; they are subject to port state control inspection. Operating a fatigued watch officer is not only a safety hazard but a potential regulatory violation that can result in vessel detention. The correct action is to rest the crew member, redistribute duties, and log the hours accurately.

8An authority gradient is described as either too steep or too flat. Explain both failure modes with examples.
Answer

Authority gradient describes the perceived power difference between the captain and the crew. Too steep (high gradient): crew are afraid to question or challenge the captain. They observe a developing danger — a shallow spot on the plotter, closing traffic — but remain silent because past experience has taught them that questioning the captain results in anger or humiliation. The captain proceeds without the information the crew possessed. This is the most common authority gradient failure in maritime accident reports. Too flat (low gradient): crew do not respect the captain's authority or feel free to override decisions. On a docking approach, two crew members simultaneously take conflicting actions because neither deferred to the captain's call. The correct command climate is a moderate authority gradient: crew are encouraged and expected to speak up with safety concerns, but the captain has clear final authority and crew comply with decisions once made.

Quick Reference — Numbers to Memorize

STCW rest per 24 hours
10 hrs min
Can be split into max 2 periods
STCW rest per 7 days
77 hrs min
Logged and signed; PSC-inspectable
Minimum single rest period
6 hrs
At least one period must be 6+ hours
Max interval between rest periods
14 hrs
Cannot exceed 14 hours between periods
SA levels (Endsley)
3
Perception, Comprehension, Projection
Closed-loop steps
3
Transmit, Readback, Confirm
SBAR elements
4
Situation, Background, Assessment, Recommendation
FOR-DEC steps
6
Facts, Options, Risks/Benefits, Decision, Execution, Check
Error types (Reason)
3
Slips, Lapses, Mistakes (plus Violations)
BRM core principles
8
Leadership, Shared model, Communication, SA, Workload, Decision, Task, Automation
Briefing types
4+
Departure, Anchor, Docking, Heavy Weather
ICS Incident Commander
1
Single command authority — no dual command in ICS

Ready to Test Your Knowledge?

Practice with exam-style questions on crew management, BRM, STCW rules, and human factors. Drill until you hit 90%+ — then tackle the real exam with confidence.

Start Practicing Free