Pilot Dispatch Software: What Modern Pilots Associations Actually Need

A licensed pilots association does something subtly different from a vessel operator: it does not track its own fleet, it coordinates other people's vessels through a defined body of water. The dispatcher's job is to know which ships are inbound, when each will reach the boarding area, and which pilot and pilot boat to assign — often under tidal and weather pressure, frequently in the middle of the night.

Most associations still run that job on a VHF radio, a phone, and a paper board. It works until two vessels arrive at once, the tide is running hard, and the duty pilot needs an extra twenty minutes. This guide covers what dedicated pilot dispatch software does to close that gap, and the specific capabilities to look for when evaluating a system.

Fleet tracking is the wrong model

The first thing to understand is why generic vessel-tracking and fleet-management software does not fit a pilots association. Fleet software is built around a list of vessels you own — you register their MMSI numbers, and the system shows you where your boats are.

A pilots association has no fleet. It has a coverage zone and a stream of third-party vessels transiting it. The right data model is a geographic bounding box, not a vessel list: the system should surface every AIS-broadcasting vessel inside the zone automatically, whether or not anyone pre-registered it. That single architectural difference is why dispatch tools built for pilots associations look and behave differently from fleet trackers.

Capability 1: Area-wide AIS, not own-fleet AIS

The foundation of a dispatch board is a live picture of every vessel in the district. A purpose-built system subscribes to an AIS feed filtered by your bounding box and refreshes on a short interval. You should see, for each vessel:

• MMSI, name, and call sign
• AIS ship type (tanker, cargo, passenger, tug)
• Position, speed over ground (SOG), and course over ground (COG)
• How stale the last position report is

The vessel list should be the board's home screen, sorted so the ships that matter — those with an open transit, or the soonest ETA — rise to the top.

Capability 2: ETA to the boarding point

Raw position is not actionable; time is. The dispatcher needs to know when each inbound vessel will reach the boarding area so the pilot boat can be launched to arrive just ahead of it.

The basic calculation is straightforward: great-circle distance from the vessel's current position to the boarding point, divided by its speed over ground, gives an ETA in minutes that updates continuously as the vessel moves. A good system then subtracts your configured pilot-boat transit time — the minutes from the pilot station to the boarding area — and fires an alert when it is time to launch.

One caveat worth raising during any evaluation: SOG-based ETA is blind to current. In a place like Cook Inlet, where currents run past six knots, the difference between a flooding and ebbing tide materially shifts arrival time. The better systems overlay predicted current at the boarding point (NOAA publishes current predictions through its CO-OPS API) so the dispatcher can mentally adjust.

Capability 3: A transit log that feeds billing

Pilots associations bill per transit. Yet in many shops the transit record is reconstructed after the fact from a dispatcher's notes and re-typed into a spreadsheet — if it gets entered at all.

A dispatch board should let the dispatcher open a transit record from any inbound vessel with one click, assign a pilot by name, note the origin and destination port, and step the transit through its lifecycle — inbound, pilot requested, pilot assigned, pilot aboard, completed — with each status change automatically timestamped. At month end, that log should export to a clean CSV your billing office can invoice from, including hours aboard and pilotage fees. The log is also the audit trail you want after any incident or near-miss.

Capability 4: Collision-risk awareness

Because the board already knows the speed and course of every moving vessel in the zone, it can do something a paper board never could: calculate the closest point of approach (CPA) and time to closest point of approach (TCPA) for every pair of vessels, and warn the dispatcher when two of them will pass dangerously close. This is the same math that ARPA radar systems run, applied at the district level. We cover the underlying calculation in CPA and TCPA Explained. It does not replace the vessels' own watchkeeping or a Vessel Traffic Service — it gives the association-side dispatcher a heads-up.

Capability 5: Unpiloted-vessel detection

Under federal law, most large commercial vessels are required to take a licensed pilot in compulsory pilotage waters — see Compulsory Pilotage Under 46 USC 8501. A dispatch board that already classifies vessels by AIS ship type can flag any tanker, cargo ship, or passenger vessel transiting the zone under way with no pilot transit logged. That is exactly the kind of thing that is easy to miss at 0300 and embarrassing to explain later.

Capability 6: Off-screen alerting

A dispatcher is not staring at the board every minute of a quiet night watch. The departure-due alert, the collision-risk alert, and the unpiloted-vessel alert all need to reach someone who is not looking at the screen — by SMS, email, or a channel like Slack — with sensible cooldowns so a single situation does not generate a storm of duplicate messages.

What to ask a vendor

If you are evaluating dispatch software for your association, the questions that separate a real fit from a repurposed fleet tracker are:

1. Does it scan all vessels in a configurable zone, or does it require me to register vessels first?
2. Does ETA account for current, or only speed over ground?
3. Can I export a month of transits to the format my billing office uses?
4. Does it alert me when I'm not watching the screen?
5. Can it run for my specific district — my bounding box, my boarding point, my pilot-boat transit time?

How Binnacle Passage approaches it

Binnacle Passage is the pilots-association product in the Binnacle AI platform, built around exactly the area-zone model described here: a configurable coverage box, live AIS, ETA to the boarding point, CPA/TCPA collision alerts, unpiloted-vessel flags, a billing-ready transit log, and NOAA current overlay at the boarding area. It is priced as a flat district subscription rather than per vessel, because pilots associations coordinate vessels they do not own.

If your association still runs dispatch on VHF and a paper board, that is not a criticism — it is how the profession has always worked. But the tooling has caught up to the job. You can see how the dispatch board works, and request a founding-partner pilot, on the Binnacle Passage page.