Electronic Fishing Logbook: The Regulation That Makes Connectivity Mandatory

The paper logbook had one advantage: it did not depend on the internet. The disadvantage was that data reached authorities days after the trip, with transcription errors, illegibility and no possibility of real-time verification.

The European Commission decided to eliminate that disadvantage. The result is the ERS (Electronic Recording and Reporting System) — the electronic catch recording system that turns on-board connectivity from a luxury into an operational requirement.

What ERS is and its legal basis

ERS is regulated by EC Regulation 1224/2009 (the Fisheries Control Regulation) and its implementing regulations, particularly EC Regulation 404/2011 (detailed rules of application). Member states have implemented these through national legislation.

In essence, ERS requires that:

• Catches are recorded electronically during the fishing operation.
• Data is transmitted to the flag state in real time or within strict deadlines.
• Landing declarations and prior port entry notifications are submitted electronically.

Who is required to comply and from when

Vessel length	ERS obligation	Application date
Over 24 metres	ERS mandatory	Since 2010
15–24 metres	ERS mandatory	Since 2012
12–15 metres	ERS mandatory	Since 2016
Under 12 metres	Simplified ERS or temporary exemption	Varies by member state

The regulatory trend is progressive extension to increasingly smaller vessels. Vessel owners with vessels under 12 metres should check their current national obligations.

What ERS requires in practice

1. Catch recording during the fishing operation

Each species caught must be recorded with:

• FAO species code.
• Quantity in kilograms live weight.
• Catch zone (ICES statistical rectangle or FAO zone).
• Fishing gear used.
• Date and position of catch.

Recording must be done as soon as possible after the catch, and no later than 24 hours after.

2. Transmission to the Fisheries Monitoring Centre

Electronic logbook data must be transmitted to the Fisheries Monitoring Centre (FMC) of the flag state before landing.

This is the point where connectivity becomes critical. Without reliable internet, transmission accumulates until the vessel has mobile phone coverage close to shore. With Starlink, transmission can happen from any position.

3. Prior port entry notification

Before entering port, the skipper must send an electronic notification including:

• Intended landing port.
• Estimated time of arrival.
• Quantities of catch on board by species.

This notification must be sent at least 4 hours in advance for vessels on longer trips. With limited connectivity, sending this from offshore was a recurring problem. With Starlink, it can be sent from any position.

4. Landing declaration

After discharge, the final landing declaration is sent, which must match the logbook data and the prior notification. Discrepancies are investigated by inspectors.

Consequences of ERS non-compliance

Sanctions for ERS non-compliance in EU member states:

Infringement	Type	Indicative penalty
Non-transmission of ERS data	Serious	€3,001–60,000
Serious errors in the logbook	Serious	€3,001–60,000
Manipulation of ERS data	Very serious	€60,001–600,000
Repeat infringements	Very serious	Up to vessel detention

Beyond financial penalties, a history of non-compliance affects licence and quota applications — which in many fisheries are the most critical business assets.

How Starlink solves the ERS connectivity problem

The solution is not to change your ERS software. The solution is to ensure that the ERS software you already use always has a reliable connection.

With Starlink:

• Automatic logbook transmissions are sent in real time from any position.
• Prior port entry notifications can be sent with the required notice, without needing to be close to shore.
• VMS position reports travel in the same connectivity package.
• The skipper can receive real-time acknowledgement from authorities.

Syntelix configures the network so that ERS and VMS traffic has absolute priority over any other traffic.

---

Which ERS software is compatible with Starlink?

Any ERS software that transmits via IP protocol (internet) is compatible with Starlink, which provides the internet connection. The main systems used in EU fishing fleets (national authority systems, eCatch, SFA and others) work without modification. If you have questions about your specific software, we verify this during the initial analysis.

Does Starlink have sufficient speed for simultaneous ERS and VMS transmission?

Completely. ERS and VMS data are low-volume transmissions (kilobytes, not megabytes). With speeds of 50–250 Mbps, Starlink has ample capacity for simultaneous regulatory transmissions alongside any other network use. Traffic prioritisation ensures these transmissions are never affected by crew welfare consumption.

Can I accumulate transmissions and send everything before entering port?

Technically possible for some data, but EC Regulation 404/2011 requires daily logbook data transmission for vessels at sea for more than 24 hours. The 4-hour prior notification requires active connectivity when the vessel is still offshore. Accumulating transmissions is an unnecessary risk that Starlink eliminates.

What happens if Starlink fails at sea and I cannot transmit ERS?

In the event of a demonstrable technical failure, regulations provide for contingency procedures (notification to authorities of the technical failure and subsequent transmission). However, to avoid this risk, for vessels where ERS compliance is critical we recommend keeping an alternative satellite data channel (even basic Iridium) as a backup specifically for regulatory transmissions.

---

Does your vessel have an ERS obligation and is connectivity a recurring problem?

Request the free analysis — we analyse your current situation and propose the most appropriate solution for your fleet’s regulatory compliance.