Pilot Fatigue and Rest: Building a Rotation You Can Defend

A ship's watchkeeper works a predictable rotation under hours-of-rest rules. A marine pilot does not. Pilots are dispatched one transit at a time, around the clock, driven by ship arrivals and the tide — a 0200 inbound, a 0600 shift, a 1400 outbound, in any combination the traffic throws up. That irregularity is precisely what makes pilot fatigue insidious, and why a defensible rotation has to be built deliberately rather than left to whoever answers the phone.

Why pilotage fatigue is its own problem

Three features make it distinct from crew fatigue:

• No fixed watch. Work arrives when ships arrive. A pilot can be called for a demanding transit at the bottom of their circadian low with little notice.
• High-acuity, short-duration work. A transit may be ninety minutes, but they are ninety minutes of continuous high-consequence decision-making — close-quarters, shallow water, traffic, tugs.
• Self-reported readiness. Whether a pilot is fit for the next job often comes down to the pilot's own judgment under pressure not to leave the association short.

Investigators repeatedly cite fatigue as a contributing factor in pilotage incidents. The mitigation is not heroics; it is a rotation that does not ask a tired pilot to take the next ship.

What a rest policy needs to express

An association's fatigue policy usually comes down to a few configurable limits:

• Minimum rest between the end of one duty period and the start of the next.
• Maximum work in a rolling window — for example, hours worked in any 24.
• Recognition of the time of day — a transit that runs through the early-morning circadian trough is more fatiguing than the same hours in daylight.

The numbers belong to the association and its local agreements. The system's job is to apply them consistently — which is where most manual rotations fall down, because the dispatcher coordinating ships at 0300 is not also reliably doing rolling-window arithmetic.

"Next up" should skip an unfit pilot

The single most useful automation is also the simplest: when the board proposes the next pilot in the rotation, it should compute each pilot's recent duty against the rest rules and skip anyone who would breach them — surfacing the next eligible pilot instead, with the reason the skipped pilot was held.

That turns the rest policy from a document nobody consults under pressure into a live constraint that shapes the assignment. It also protects the dispatcher: assigning a non-compliant pilot becomes a deliberate override with a record, not an accident of a busy night.

Why the rotation has to be auditable

Two reasons to keep the rotation as a record, not just a habit:

1. After an incident, the question will be whether the pilot was within rest limits. A computed duty history answers it; memory does not.
2. Equity. A rotation also has to be fair — turns and job value distributed evenly so no pilot is systematically handed the hard or the lucrative jobs. That, too, is arithmetic best done by the system. (We cover the fairness side in our note on rotation equity, built into the same board.)

How Binnacle Passage handles it

Binnacle Passage builds the fatigue check into the roster. Each pilot's work blocks are derived from their transits — aboard to off — and measured against the association's configured minimum rest and maximum-work-in-24 limits. The roster's "next up" logic skips a pilot who would breach those limits and explains why, so the dispatcher always sees an eligible pilot first. The same transit data drives a rotation-equity view, so fairness and fatigue are managed from one record rather than two spreadsheets.

It does not set your limits or override a pilot's own assessment of their fitness. It makes the limits you have chosen actually bind on the assignment, and it leaves a defensible trail.

The bottom line

Pilot fatigue is structural, not a matter of individual toughness: the work arrives at all hours, one job at a time. A defensible association does three things — writes down its rest limits, applies them automatically so "next up" never proposes an unfit pilot, and keeps the rotation as an auditable record. The technology is not exotic; the discipline is the point.

This article is informational and does not establish rest requirements. Follow your association's policies and any applicable local or state pilotage regulations.