← Blogcook-inlet
Cook Inlet Pilotage: Dispatching Some of Alaska's Hardest Water
Cook Inlet pairs some of the largest tides in North America with effectively no commercial AIS coverage — a brutal combination for a dispatch desk. Here's what makes the district so demanding and what a purpose-built board does about the tide and the data gap.
If you wanted to design a worst-case environment for pilot dispatch, you would build something close to Cook Inlet. Enormous tides, fast currents, ice in winter, shoaling that moves, and — the part that surprises people — almost no commercial AIS coverage to see the traffic with. The pilots who serve it do extraordinary work; the dispatch side deserves tooling that respects how hard the water is.
What makes the district so demanding
The tide. Upper Cook Inlet has one of the largest tidal ranges in North America — in places exceeding thirty feet — and the currents that drive it run hard, well past six knots in the constrictions. That single fact reorders everything about timing a transit. A speed-over-ground ETA that ignores current can be off by a wide margin, and the difference between a flooding and an ebbing tide moves a vessel's arrival at the boarding area by a meaningful amount.
Shoaling and ice. The inlet shoals and the channels shift; winter brings ice that complicates both the transit and the pilot-boat work. Under-keel clearance and timing are not academic here — they are the job.
Remoteness. Anchorage, Nikiski, and the inlet's terminals sit a long way from anywhere, served by a small number of pilots who turn out at all hours for inbound tanker and cargo traffic.
The data problem nobody expects
Here is the operational gut-punch: commercial AIS aggregators have effectively no coverage of Cook Inlet. The volunteer-and-commercial terrestrial receiver networks that blanket a busy harbor simply are not there. Point a generic vessel-tracking tool at the upper inlet and you get an empty map at the exact moment you need to know what is inbound.
That is not a software bug; it is a receiver-geography fact. The traffic is broadcasting AIS — there is just nothing ashore in range to hear it and feed a commercial aggregator. (We cover the wider issue in NAIS vs. commercial AIS.)
For Cook Inlet, the only source with authoritative coverage is the US Coast Guard's Nationwide AIS (NAIS), District 17. Getting access is a process — it runs through a data-sharing agreement and typically expects a government or state-licensed party as the end-user — but for this district it is the path to a live board. A state-licensed Alaska pilots association is exactly the kind of co-applicant that path is built for.
What a dispatch board has to do about the tide
Seeing the traffic is half the job; timing it against the current is the other half. A board built for water like this should:
- Fold predicted current into the ETA. NOAA publishes current predictions for the inlet through its CO-OPS API. A board that overlays the along-track current component onto speed-over-ground gives an ETA the dispatcher can actually launch a boat on, rather than a tide-blind estimate.
- Surface the boarding-area conditions. Nearest current station, flood/ebb state, and the slack windows belong on the same screen as the vessel list.
- Compute under-keel clearance honestly for deep-draft transits, where the tide is the difference between a clean passage and a grounding. (See squat and UKC.)
How Binnacle Passage approaches Cook Inlet
Binnacle Passage is built around a coverage zone rather than a registered vessel list, ingests AIS from whatever source covers the district, and overlays NOAA current so the ETA to the boarding point is current-aware rather than a flat SOG calculation. For a commercially-dark district like Cook Inlet, the architecture is designed to consume NAIS once the data-sharing agreement is in place — the board, ETA logic, and transit record are identical regardless of the feed underneath.
We help founding-partner Alaska associations assemble the NAIS application; the package is pre-built and files on a single yes.
The bottom line
Cook Inlet is hard in two compounding ways: the tide makes timing unforgiving, and the lack of commercial AIS makes the traffic hard to even see. A dispatch board for this district has to be current-aware and able to run on NAIS — the only feed that covers the water. The pilots already do the hard part on the water; the desk should have tooling that matches it.
This article is general information. Pilotage in Cook Inlet is governed by Alaska state law and the licensed pilots association serving the district.
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.