Why Fleet-Tracking Software Doesn't Fit a Pilots Association

When a pilots association goes looking for software, the first tools it finds are fleet trackers and fleet-management platforms. They demo well, they show boats on a map, and they are completely the wrong shape for the job. Understanding why saves an association months of forcing a square peg into a round hole — and clarifies exactly what to evaluate instead.

The fleet model: a list of vessels you own

Fleet-management software is built around one assumption: you own a defined list of vessels. You register each boat's MMSI, the system subscribes to those specific targets, and it shows you where your assets are. Everything downstream — maintenance, crew, compliance, fuel — hangs off that vessel list.

For a tug company, a ferry operator, or an OSV fleet, that model is exactly right. The vessels are yours, the list is stable, and the questions you ask ("where is our boat, is it due for a survey") are vessel-centric.

The pilotage model: a zone full of strangers

A licensed pilots association owns no fleet. It holds a commission to pilot vessels through a defined body of water — a bar crossing, a harbor approach, a river, a sound. The vessels it serves belong to ship owners and charterers all over the world, arrive on their own schedules, and are never seen again after the transit.

The dispatcher's real question is not "where is my boat." It is: "What is inbound to my district right now, when will each ship reach the boarding area, and which pilot and pilot boat do I assign?" — often at 0300, often with the tide running.

That question is geographic, not asset-based. The correct data model is a bounding box over the coverage zone, not a registered vessel list. The system should surface every AIS-broadcasting vessel inside the zone automatically, whether or not anyone pre-registered it, because the association cannot know in advance which ship will need a pilot tomorrow.

This is the architectural fork in the road. A fleet tracker filtered to "your" MMSIs will show you an empty map, because none of the inbound ships are yours. A dispatch board filtered to your geography shows you the whole picture.

What the zone-first model has to get right

Once you accept that the unit of work is a coverage area rather than a vessel list, a specific set of capabilities follows:

• Area-wide AIS ingest. A live feed filtered by your bounding box, refreshed on a short interval, surfacing MMSI, name, call sign, AIS ship type, position, SOG, COG, and how stale each report is. The vessel list is the home screen, sorted so the ships that matter — open transits, soonest ETA — rise to the top.
• ETA to the boarding point. Raw position is not actionable; time is. Great-circle distance from each inbound vessel to the boarding area, divided by speed over ground, gives a continuously updating ETA. Subtract your configured pilot-boat transit time and the board can tell the dispatcher when to launch.
• A transit, not a vessel, as the record. The thing an association tracks across its lifecycle is a transit — assigned, pilot aboard, underway, complete — with the pilot, the times, the draft, and the fee attached. That record then feeds billing and the monthly ops report. A vessel-centric schema has nowhere natural to put it.
• Collision and unpiloted-vessel awareness. Because the board already sees the whole zone, it can run CPA/TCPA between contacts and flag a large vessel that is transiting without an open pilot assignment — a compulsory-pilotage gap worth a phone call.

"Can't we just use the fleet tool we already have?"

Associations often try, because the fleet platform is already paid for. It breaks down in predictable ways:

1. The map is empty until someone manually adds every inbound MMSI — which defeats the purpose, since the value is seeing ships before anyone knew to register them.
2. There is no boarding-point ETA, because fleet tools answer "where is the boat," not "when does it reach a fixed point I care about."
3. Billing doesn't fit, because pilotage invoices on gross tonnage, draft, and tariff — not on vessel-hours of an owned asset.
4. The alerts are wrong, because fleet alerts are about your boats (geofence breaches, idle time), not about third-party traffic risk in a district.

None of this is a knock on fleet software. It is simply built for a different problem.

The bottom line

If you own boats, buy fleet software. If you pilot other people's boats through a zone, you need dispatch software whose first-class object is the coverage area and the transit, not the vessel. That is the design principle behind Binnacle Passage: point it at your bounding box and boarding point, and it shows you every inbound vessel, the ETA to the boarding area, and a transit log that feeds your billing — without anyone pre-registering a single ship.

For a deeper walk through the capabilities to evaluate, see our guide to pilot dispatch software. For the regulatory backdrop on which vessels must take a pilot, see compulsory pilotage under 46 USC 8501.