Rotation Equity: Settling the Fair-Share Dispute That Splits Pilots Associations

Ask any executive director what keeps the partnership up at night and they will not say groundings. They will say the rotation. The single most corrosive dispute inside a US licensed pilots association is not about safety, training, or the tariff — it is the quiet, persistent suspicion that the order isn't fair. That somebody is getting more turns. That somebody else keeps drawing the big inbound tankers while you get the light-displacement coastwise jobs. Left unmeasured, that suspicion metastasizes into a partnership fight that no amount of goodwill resolves, because goodwill can't settle an argument about numbers when nobody has the numbers.

This is a solvable problem. Not a political one — a measurement one. Below is how associations think about fair share, where the math gets subtle, and why putting the rotation on a transparent, data-backed board does more to keep a partnership together than any retreat or handshake ever has.

Two different things are being shared, and people conflate them

When a pilot says "the rotation isn't fair," they usually mean one of two distinct things, and the association can't fix either until it separates them.

Turns. The count of jobs assigned. The classic equity model: a single rotating queue where the pilot at the top takes the next vessel, then drops to the bottom. Over a year, everyone should land within a few turns of everyone else. Easy to state, surprisingly hard to honor once leave, sick days, training rotations, restricted-tonnage endorsements, and night/weekend coverage start carving exceptions into the line.

Job value. Not every turn is worth the same. Under a per-GT tariff, a 150,000-GT inbound tanker with a long transit, a docking, and a night differential can be worth several times what a short coastwise shift on a 6,000-GT vessel pays the pool. If the rotation equalizes turns but the high-value jobs cluster — by tonnage class, by berth, by daypart, by who happens to be near the top when the big ships call — then turn-equity is a fiction. Two pilots can have an identical turn count and a meaningfully different draw from the pool.

Most internal disputes are really the second thing wearing the costume of the first. Someone counts turns, finds them roughly even, and declares the matter closed — while the colleague who keeps drawing the light jobs knows something is off but can't prove it. The argument never resolves because the two sides are measuring different quantities.

The fair-share baseline: define "even" before you can prove "uneven"

You cannot adjudicate fairness without a baseline. The fair-share baseline is the simplest idea in the whole exercise and the one most associations never write down: over a defined period, each available pilot's expected share equals their availability divided by the pool's total availability.

If a pilot was on the board 92% of the period and the rest of the pool averaged 95%, that pilot's fair share is slightly below an equal split — and any honest equity measure has to credit them for the leave, the training rotation, the medical absence. Equity is not "everyone gets exactly 1/N." Equity is "everyone gets their share of what they were actually available to work." Get this wrong and you punish the pilot who took approved leave, which is exactly how a fairness system loses the room's trust in its first month.

Once the baseline is defined, you measure two deltas against it:

• Turn delta — actual turns minus fair-share turns.
• Value delta — actual pool-dollars (or GT-weighted units, if you don't want to expose individual earnings) minus fair-share value.

A pilot can be positive on one and negative on the other. That is not a contradiction; it is the whole insight. The pilot up three turns but down on value has been taking the small jobs. The pilot dead even on turns but well up on value has been catching the heavies. Neither pattern is anyone's fault — usually just the geometry of when ships call and who was near the top. But you can't correct a pattern you refuse to name.

The owed-next ranking: turning measurement into a decision

A scorecard that says "you're down 4.2 turns" is interesting. It does not dispatch a ship. The operational payoff of all this measurement is a single ordered list: the owed-next ranking — who, right now, is most owed the next job, and the next high-value job specifically.

A defensible ranking blends both deltas. The pilot most negative on the value-weighted measure floats toward the top of the next-heavy-vessel queue; the pilot most negative on raw turns floats toward the top of the next-available-job queue. You can weight the blend to your association's culture — some pools care almost entirely about turns and treat value variance as noise that evens out over years; others, especially where tonnage classes are bimodal and the big-ship windows are tide-gated and rare, weight value heavily because the variance doesn't wash out on its own.

The point is that the ranking is derived, visible, and the same for everyone. When the dispatcher assigns the next inbound VLCC, the board can show every partner that the pilot who got it was the one the owed-next math put at the top, given availability, the duty clock, and the value owed. The assignment stops being a judgment call one person made in a back office and becomes the output of a rule the partnership agreed to.

Why transparency, not policy, is the actual fix

Here is the part that surprises people who think this is a software problem. The dispute is rarely caused by a bad rotation policy. It's caused by an invisible one. When the order lives in a dispatcher's head, a spreadsheet only the dispatcher edits, or a whiteboard erased every shift, every pilot is free to construct a private theory of the injustice being done to them, with no shared artifact to check it against. Suspicion fills the vacuum that data should occupy.

Make the same numbers visible to everyone and the fight changes character. It stops being pilot versus pilot and becomes pilots versus a number on the board that they can all see, question, and audit. People will still disagree about the weighting — turns versus value, the lookback window, how to treat a half-job or a scrubbed assignment — but those are governance arguments the partnership can settle in a meeting and encode in the rule. They are not the festering, personal, who's-screwing-whom argument that splits associations.

I won't pretend the politics vanish. A pilot who has quietly benefited from an opaque rotation is not always thrilled to see it lit up, and "we've always done it this way" is a real force. But the loudest early skeptics tend to become the loudest defenders within a quarter — because the same transparency that exposes an unearned surplus also, finally, vindicates the pilot who was genuinely getting shorted and could never prove it. Transparency cuts both ways, and most partners would rather be measured fairly than flattered vaguely.

Where the value math meets the water

The reason value variance doesn't always wash out is operational, not statistical. In many districts the high-value jobs are the ones the environment rations. A deep-draft tanker can only transit on the right water, so the big jobs cluster into tide windows — and whoever is near the top of the rotation when that window opens catches the heavy ship. If your district is tide-gated, the fair-share question is entangled with sailing-window math: you can't reason about value equity without reasoning about under-keel clearance and the tide windows that gate the deep-draft moves in the first place. Two pilots with identical availability can draw very different value purely because of when their turns came up relative to the tide. That's not unfairness anyone intended — but it is real variance the owed-next ranking should be allowed to correct.

It also explains why the disputes run hotter in some districts than others. A high-volume harbor with a steady mix of tonnage tends to self-equalize; turns and value track each other because the law of large numbers does its work. A district with a bimodal fleet — a stream of small coastwise traffic plus a handful of tide-gated heavies a month — is where value variance bites hardest. It's a live tension in places like Cook Inlet, where extreme tides ration the big jobs into narrow windows and the rotation has to be defensible against partners watching every heavy assignment.

What this asks of a dispatch board

Equity tracking is not a bolt-on report you run at the annual meeting. To be trusted it has to be a byproduct of normal dispatching — computed from the same transit records the desk already keeps, so the numbers are never in question. That means the board has to:

• Track every assignment as a complete record — assigned, aboard, underway, complete — so turns are counted from reality, not from memory.
• Carry the GT and the relevant tariff inputs on each job, so value is computed from the per-GT tariff the same way every time, not estimated after the fact.
• Account for availability honestly — leave, sick, training, restricted endorsements — so the fair-share baseline credits absence instead of punishing it.
• Respect the duty clock and rest rules first, so the owed-next ranking never proposes a pilot who isn't rested and legal under the association's fatigue policy. Equity never overrides safety; it operates inside it.
• Show the math to every partner, not just the dispatcher.

Binnacle Passage is built around exactly that loop. The same transit record that drives the live board and the billing also feeds the rotation engine, so turn counts, value-weighted deltas against the fair-share baseline, and the owed-next ranking come straight out of operations — not a separate spreadsheet someone has to maintain and the rest of the pool has to trust on faith. The dispatcher sees who's owed next; the partnership sees why.

The bottom line

The fair-share dispute splits associations because it is fought in the dark. Separate the two things being shared — turns and job value. Define the fair-share baseline from real availability. Express the result as an owed-next ranking the dispatcher actually uses and every partner can audit. Do that, and the argument doesn't disappear, but it transforms: from a personal grievance with no resolution into a shared number the partnership governs together. That is the difference between a pool that fractures over the rotation and one that keeps its peace because the rotation has nothing left to hide.

If the rotation is a sore subject in your association, the fastest way to defuse it is to make it visible. See how Binnacle Passage tracks turns, job value, and the owed-next ranking off your live operations — and see a live pilot board to watch the fair-share math run on real transits before you change a thing about how your desk works.