← Blogcolumbia-river
Columbia River Pilotage: Dispatch Across the Bar and the River
The Columbia pairs one of the world's most dangerous bar crossings with a hundred-mile river transit serving multiple ports — and two separate pilot groups who hand off at Astoria. Here's the dispatch challenge of the whole system and what coordinating it actually takes.
The Columbia River entrance has earned its nickname — the Graveyard of the Pacific — across two centuries of wrecks. But the bar is only the first act. A ship inbound to Portland, Vancouver, Longview, or Kalama crosses the bar, then transits roughly a hundred miles of river, under the hands of two different pilot groups who hand off near Astoria. Dispatching that system is a study in coordination across a long, multi-port district.
Two pilotages, one ship
The Columbia is served by two distinct organizations:
- The bar pilots take the ship across the Columbia River Bar — the violent, shoaling, current-swept entrance where the river meets the Pacific swell.
- The river pilots take her from the Astoria area up the river to the terminals at Longview, Kalama, Vancouver, and Portland, and back down.
The two hand off near Astoria. That handoff is itself a dispatch event: the river pilot has to be staged and ready as the bar pilot brings the ship in, and the whole sequence has to be timed against the bar conditions and the river's own currents and traffic.
What makes the river demanding to dispatch
Length and duration. A hundred-mile transit is a multi-hour commitment of a pilot and a vessel. A dispatcher is not timing a single boarding; they are managing a long passage with intermediate ports, meeting situations, and a pilot whose duty clock is running the entire time.
Multiple ports, one waterway. Longview, Kalama, Vancouver, and Portland all draw traffic up the same river. The dispatch picture is not one boarding ground; it is a corridor with several destinations, vessels at different points along it, and assignments that have to account for who is where.
The bar as a gate. The bar's conditions — swell, ebb against swell, the restriction windows — govern when ships can cross at all. A river that is otherwise ready still waits on the bar. The dispatch desk has to see both.
Currents and the tide. The lower river runs with the tide; a speed-over-ground ETA that ignores current misreads when a ship reaches the next point. Timing the handoff and the berth windows means timing the current.
The coverage angle
Like other less-populated districts, stretches of the Columbia have historically had thin commercial AIS coverage — the terrestrial aggregator networks are sparse outside the busiest reaches. For a dispatch board that needs a continuous picture of a hundred-mile corridor, gaps in the feed are gaps in awareness. The authoritative fill for US waters is the Coast Guard's NAIS, and the path to it runs through a data-sharing agreement (see NAIS vs. commercial AIS).
What a board for a river district has to do
Dispatching a corridor rather than a single boarding ground asks for:
- A multi-zone view. The bar approach, the handoff area, and the upriver ports are distinct zones along one waterway; the board should show per-zone traffic without losing the single-corridor picture.
- Current-aware ETAs for the handoff and the berth windows, folding NOAA current into speed over ground.
- A transit record that spans the passage — assigned, aboard, underway, complete — so the long river job is one continuous record from handoff to berth, feeding the duty clock and the billing.
- Awareness of the bar gate so the river side sees what the bar conditions allow.
How Binnacle Passage approaches it
Binnacle Passage models the district as one or more coverage zones along the waterway, tracks each transit across its full length, and folds NOAA current into the ETA so the handoff and berth timing are current-aware. For a corridor with coverage gaps, the architecture is built to run on NAIS once the agreement is in place — the same board, ETA logic, and transit record regardless of the underlying feed. The duty and rotation engine accounts for the long transit times the river imposes, so the next pilot proposed is one who is actually rested and legal.
The bottom line
The Columbia is two pilotages and a hundred miles of river serving several ports, gated by one of the world's hardest bar crossings. Dispatching it means coordinating a handoff, timing a long transit against the current, and keeping a continuous picture of a corridor that commercial AIS doesn't fully cover. It is exactly the kind of district a zone-first, current-aware, NAIS-capable board is built for.
This article is general information. Columbia River pilotage is governed by Oregon and Washington state law and the licensed pilot organizations serving the bar and the river.
You might also like
pilotage
Configuring an AIS Coverage Zone for Your Pilotage District (Any Bounding Box)
How to set up an AIS coverage zone for any pilotage district: bounding boxes, boarding points, transit times, and three worked examples.
Read →
tug-escort
Tug Escort and Bollard Pull: Planning Assist for Laden Tankers
For a laden tanker in confined water, the escort tug is the last line of defense if steering or propulsion fails. Here's how escort differs from assist, what bollard pull actually buys you, and why the tug plan belongs in the transit record.
Read →
tidal-windows
Tidal Windows and Slack Water: Timing the Transit
For a deep-draft ship in a shallow channel, the tide decides when she can move at all. Here's how tidal windows, slack water, and current set the dispatch clock — and why a board that's blind to the tide gives a dispatcher the wrong answer.
Read →
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.