What is a port state measures agreement, and why it matters for a watch desk

A port call request lands on your desk. A foreign-flagged longliner wants to enter a designated port, land its catch, take on fuel, whatever the request says. Before you sign off, you're supposed to check whether that vessel has any business anywhere near IUU fishing. That check, and the authority behind it, comes from the port state measures agreement.

What the PSMA actually requires

The Agreement on Port State Measures to Prevent, Deter and Eliminate Illegal, Unreported and Unregulated Fishing, the full name nobody uses day to day, entered into force in 2016 under the FAO. It's the first binding international treaty aimed specifically at IUU fishing, and it works from the port side rather than the water side. The logic is simple enough: illegally caught fish usually has to cross a dock to reach a buyer, so controlling the dock controls a chokepoint that patrol boats and flag states can't always reach in time.

Under the PSMA, a party state:

• designates specific ports where foreign vessels can request entry
• requires advance notice before a vessel arrives, naming the vessel, its catch, and where that catch was taken
• can deny port entry, or deny landing and transshipment even after entry, if there's reasonable grounds to believe the vessel engaged in IUU fishing
• runs inspections against a minimum standard and shares the record with the flag state, the relevant RFMO, and other PSMA parties

That last point is the one that matters for a watch desk. A port entry denial isn't a local administrative call that stays local. It feeds a shared record. A vessel turned away at one PSMA port is now flagged for every other party state checking advance notices against the same name.

Where the watch desk's own blind spot sits

The agreement gives you the authority to deny entry. It doesn't give you the sighting. Advance-notice checks and PSMA inspections work against vessels that identify themselves and request a port call: the ones broadcasting AIS, the ones already in your system. A vessel that wants to avoid all of that just doesn't ask. It transships at sea, works into a non-designated port, or runs a stretch of water with its AIS off long enough that nobody at the desk ever opens a file on it.

That's the gap the PSMA can't close on its own. Enforcement at the dock only catches what shows up at the dock. The vessels worth the most scrutiny under a port entry denial regime are often the ones that never request entry, because they've already worked out how to move catch without leaving a paper trail.

A watch desk that wants the PSMA to actually bite needs a way to see the part of the fleet that isn't asking permission. That means knowing which vessels were on the water, in the area you're watching, on a given day, whether or not they were broadcasting. Correlating optical detections against the AIS record for the same day and the same water does that: it surfaces a vessel with no matching broadcast, a position, a size class, a time. That gap, repeated over weeks, is the signature a dark fleet leaves, and it's exactly the kind of history worth having on file before a vessel turns up at your designated port asking to land.

What this means for the day-to-day file

None of this replaces the inspection itself. A PSMA port entry denial still rests on an inspector's judgment at the dock, the catch documentation, the flag state's own record. But a watch desk that's already been tracking unmatched detections has a running list to check a vessel against the moment its advance notice comes in, instead of starting from a flag and an MMSI with no prior history attached.

If building that history right now means someone on the team manually trawling AIS gaps against satellite passes, Illegal Fishing Detection is built to take that correlation off the desk and hand back a daily list of what's on the water and off the record.

Start building that history before the next port call request lands.