← Blogpuget-sound

Puget Sound Pilotage: Dispatch in a Busy, Multi-Port District

Puget Sound is the opposite problem from a remote inlet: not too little traffic to see, but a great deal of it, spread across many ports, threaded with ferries and a traffic separation scheme. Here's the dispatch challenge of a dense district and what helps.

Capt J7 min read

If Cook Inlet's dispatch problem is too little — too little tide forgiveness, too little AIS coverage — Puget Sound's is too much. The Sound is one of the busiest pilotage districts in the country: container terminals at Seattle and Tacoma, refineries at the north end, grain and breakbulk, cruise in season, the constant cross-traffic of one of the largest ferry systems in the world, and a US/Canada border running through it. The pilots who serve it are managing density, not scarcity, and the dispatch desk's job is shaped by that.

What makes a dense district hard

Volume. Many vessels inbound and outbound, to many destinations, at once. Where a remote district might see a handful of transits a day, a busy Sound sees a steady stream — and the dispatcher is assigning pilots and boats against a board that is never empty.

Many ports, one waterway system. Seattle, Tacoma, Everett, Olympia, Anacortes, the Cherry Point and March Point refineries — each draws traffic through shared waters. An inbound assignment has to account for where the ship is going, not just that it is inbound.

Cross-traffic. The ferries are constant and high-priority, the recreational and fishing traffic is real, and the commercial stream runs through a traffic separation scheme managed by a vessel traffic service. Close-quarters situations develop continuously, and the ones that matter have to be picked out of a crowded picture.

The boarding ground and the transit. Many transits stage from the Port Angeles area, then run east and south into the Sound — a substantial passage with meeting situations the whole way.

The dispatch picture in dense water

In a crowded district, the value of a dispatch board is less about finding the traffic — there is plenty of AIS coverage here — and more about making sense of it:

  • Sorting the board to what matters. With a full vessel list, the home screen has to surface the ships with an open transit or the soonest ETA, not bury them among dozens of contacts.
  • Automatic close-quarters awareness. In dense traffic, no dispatcher can eyeball every developing CPA. A board that runs CPA/TCPA across all contacts and flags the genuinely close ones turns a crowded picture into a short list of things to actually watch.
  • The unpiloted-vessel check. In a district with compulsory pilotage, a large vessel transiting without an open assignment is worth surfacing automatically — easy to miss in a busy picture, easy for a board to flag.
  • Per-port zones. A multi-port district benefits from seeing per-zone counts — the north-end refineries vs. the south Sound — without losing the single picture.

Where the data is the easy part

Puget Sound is well served by commercial AIS — the receiver geography that fails Cook Inlet is abundant here. That flips the problem: the feed is not the constraint, the interpretation is. The same zone-first model that surfaces every vessel in a remote district has to, in a busy one, also help the dispatcher not drown in contacts. (For the contrast, see Cook Inlet pilotage and NAIS vs. commercial AIS.)

How Binnacle Passage approaches it

Binnacle Passage ingests the district's live AIS, sorts the board so open transits and soonest ETAs rise to the top, runs CPA/TCPA across all contacts with a red alert under half a mile within thirty minutes, and flags a compulsory-pilotage-size vessel transiting with no open assignment. A multi-zone view gives per-area counts across the Sound's ports, and the rotation engine keeps "next up" on a rested, legal pilot even when the board is busy. The dense district is where automatic awareness earns its keep — there are simply too many contacts to watch by hand.

The bottom line

Puget Sound's challenge is density: a great deal of traffic, many ports, constant ferries, and a traffic separation scheme. The dispatch board's job there is not to find the vessels but to make a crowded picture legible — surfacing what matters, flagging the close-quarters situations and the unpiloted gaps automatically, and keeping the rotation honest. In busy water, that automation is the difference between a board you read and a board you fight.

This article is general information. Puget Sound pilotage is governed by Washington state law and the licensed pilots serving the district.

You might also like

Free tool

Try the free 46 CFR compliance calculator

No login. 8 inputs, 2 minutes. Real CFR citations — same checks a USCG inspector runs through.

Open the calculator →

Binnacle AI is not affiliated with, endorsed by, or sponsored by the U.S. Coast Guard. CFR citations refer to the current Code of Federal Regulations as of publication; confirm against eCFR before filing or inspection. This article is informational and is not legal advice — consult a qualified maritime attorney for specific regulatory questions.

Built for evaluation-grade trust