← Blogtidal-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.
In a lot of pilotage districts the single most important input to dispatch is not the ship's speed or the pilot rotation — it is the tide. A deep-draft vessel in a tidally-constrained channel can only move during a window when there is enough water under her, and often only when the current cooperates. Getting that window right is the difference between a clean transit and a ship that sits, or worse. This guide covers how the tide sets the dispatch clock.
Two different things the tide controls
It helps to separate two effects that both go by "the tide":
- Height of tide → depth → the window. A channel's charted depth plus the height of tide gives the actual water available. For a deep-draft ship, only part of the tidal cycle provides enough depth — plus the required under-keel clearance and an allowance for squat — to transit safely. That stretch of the cycle is the tidal window.
- Current → timing and handling. The same tide drives a current that helps or hinders the ship and shifts her arrival time. Slack water — the brief period at the turn of the tide when the current is near zero — is often the preferred moment to make a berth or a tight maneuver, because the ship is not being set by a running current.
A dispatcher has to respect both: the ship must be in the window for depth, and ideally timed to favorable current or slack for the critical maneuver.
How the window sets the dispatch clock
Work it from the constraint backward:
- The tidal window at the controlling shoal or berth defines the band of clock time the transit can happen.
- The ship's transit time from the boarding ground to that point determines how early she has to board to arrive inside the window.
- The pilot-boat launch has to put the pilot aboard in time to make all of that work.
Miss the window and the next one may be hours away — a tide cycle later. That is why tidal districts run on a schedule the tide writes, and why a late pilot-boat launch is not a minor slip; it can cost a tide.
Why a tide-blind board gives the wrong answer
A dispatch tool that computes ETA from speed over ground alone is blind to current. In a place where the current runs at several knots, that blindness is not a rounding error — it can move the estimated arrival at the boarding point or the controlling shoal by a wide margin, in either direction depending on flood or ebb. A dispatcher launching a boat on a tide-blind ETA is making a timing decision on bad data at the exact moment timing matters most.
The fix is not exotic. NOAA publishes tide predictions and current predictions for thousands of stations through its CO-OPS API. A board that pulls the nearest station's data can:
- Show the tidal window for a given draft and controlling depth.
- Fold the along-track current into the ETA so it reflects the water the ship is actually moving through.
- Surface slack times at the boarding ground so the dispatcher can time the critical maneuver.
How Binnacle Passage handles it
Binnacle Passage computes a tide window for a transit from the nearest NOAA station given the ship's draft, the controlling depth, and the required clearance, and folds predicted current into the ETA to the boarding point so the estimate is current-aware rather than a flat speed-over-ground figure. The boarding-area conditions — nearest current station, flood/ebb, slack — sit on the board next to the vessel list. For the depth side of the window, the squat and UKC tool puts honest numbers on the clearance the tide is buying you.
It does not replace the pilot's judgment about when the ship moves; it makes the tide an explicit, computed input to the dispatch decision rather than a mental calculation done under pressure.
The bottom line
In a tidal district, the tide is the dispatch clock: it sets the window the ship can move in and the current that times the critical maneuver. A board that ignores current gives a confidently wrong ETA exactly when precision matters. Build the window from the constraint backward, time to slack where it counts, and let the dispatch tool carry the tide rather than the dispatcher's memory.
This article is general information and uses simplified concepts. Always apply the ship's UKC policy, official tide and current data, and professional judgment.
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 →
tampa-bay
Tampa Bay Pilotage: Dispatch Across a Long, Shallow, Bridge-Spanned Bay
Tampa Bay is a long transit through a narrow dredged cut in shallow water, under the Sunshine Skyway, to three ports. Shallow margins, a long passage, and a bridge with a hard history make timing and clearance the dispatch priorities. Here's the challenge.
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.