Statutory guidance

Common errors found on Electronic Logbooks

Updated 5 August 2025

Analysis of electronic logbooks (e-logs) and landing declarations, submitted by over 12 metre fishing vessels, has identified several issues of incorrect information being declared. This guidance summarises the most common errors found and why it is important that information must be accurate. The most common issues for errors include:

• Species codes
• Species presentations
• Number of fishing operations
• Departure and/or return port

1. Why is it important to provide accurate data:

Accurate data in relation to species codes, presentation, fishing operations, departure and return to port, are key to ensure:

• quota uptake is calculated correctly. This enables regulators to accurately assess uptake of quota stocks, reducing the potential for specific fisheries being incorrectly closed or restricted.
• non-compliance with quota limits or restrictions are identifiable.
• accurate scientific assessments of stocks and quota allocations.
• a better understanding of changes to fisheries and to identify new fishing opportunities in response to changing climate and species availability (e.g., Bluefin Tuna)
• compliance with logbook data requirements. Avoiding enforcement action from regulators for failing to comply with requirements.

2. Species Codes:

It is a statutory requirement for masters of fishing vessels to identify and record the species caught and landed by their fishing vessel on the e-log and landing declaration under the correct Food and Agriculture Organisation (FAO) species code. Incorrect species codes in logbooks are often used accidentally or due to species misidentification.

A list of common species codes for UK fish species can be found here: List of common species codes for fish landed in the United Kingdom - GOV.UK

Species specific codes should be used where available e.g. Thornback ray (RJC) rather than ‘Skates and Rays.’ Generic or non-specific codes should only be used when a specific species code is not available for use.

For instance, where a mix of closely related species, such as gurnards or rays, are caught during a fishing operation, each species must be recorded separately on statutory returns, not captured under a single generic code.

Using gurnards as an example, this means separate recording for Red Gurnard (GUR), Grey Gurnard (GUG), Streaked Gurnard (CTZ) and Tub Gurnard (GUU), instead of recording total quantity under the generic code: Gurnards (GUX).

If non-specific or incorrect codes are recorded, the MMO may require amendments be made to the returns submitted.

Below are some common examples of where incorrect species codes have been detected:

• POR (Porbeagle) recorded instead of POL (Pollack).
• POK (Saithe) recorded instead of POL (Pollack).
• SKA (Skate) recorded instead of the correct skate or ray species code (e.g., RJC Thornback Ray).
• CPR (Common Prawn) recorded instead of NEP (Nephrops)

Some of the species commonly recorded incorrectly are dogfish species, and skate and ray species. The following sections provide more information on how to record these correctly.

2.1 Dog Fish

• Small-spotted catsharks are also known as lesser spotted dogfish. These should be recorded under the code: SYC
• Nursehounds, also known as greater spotted dogfish or bull huss, should be recorded under the code: SYT
• There are two species of smooth-hound commonly found in English waters. Each should be recorded under the correct code respectively:
  • Smooth-hound: SMD
  • Starry Smooth-hound: SDS
• Spurdog, also known as picked dogfish, should be recorded using the code: DGS
• DGH, DGX, SCL and SYX should not be used as they are generic codes.
• Refer to the Shark Trust ID guides for further help on identifying species:

https://www.sharktrust.org/Pages/FAQs/Category/shark-id-guides.

2.2 Skates and Rays

• All skates and rays should be recorded using the individual species codes on the logbook and landing declaration. e.g. Thornback ray should be recorded using RJC, Blonde ray should be recorded using RJH etc.
• The code SKA (for Skates and rays) is a generic code and should not be used on Catch records or logbooks. This code is only permitted for use by merchants to indicate sale of parts of a skate or ray other than the wings e.g., ray backs.
• Refer to the Shark Trust ID guides for further help on identifying species:

https://www.sharktrust.org/Pages/FAQs/Category/skate-ray-id-guides.

3. Presentation codes:

It is a statutory requirement for masters of fishing vessels to correctly record the presentation (e.g. whole, winged, gutted, etc.) of the species caught and landed on the vessels landing declaration.

In some instances, the presentation code has been found to be incorrect. Incorrect presentation codes can cause issues when calculating live weight e.g. to convert the weight of anglerfish tails to anglerfish whole weight, the tail weight is multiplied by 3, meaning 100 kg of anglerfish tails is the equivalent of 300 kg of anglerfish live weight.

Weights on the fishing activity reports (FARs) should be recorded in live (whole) weight, however, presentation errors can also occur on FARs. This can happen where an incorrect species/presentation combination has been set up within e-log favourites and may lead to incorrect presentations being auto-populated within the landing declaration.

A list of processing and presentation codes for fish can be found on our website here: Processing, presentation and marketing information for fish - GOV.UK

4. Number of Fishing Operations:

It is a statutory requirement for masters of fishing vessels to correctly record the number of fishing operations in the vessels fishing activity report (FAR). The information required depends on the gear in use and is detailed within Annex XI of the Control Regulation Detailed Rules (EU 404/2011).

• Trawls, Seines and Encircling nets – The total number of times gear is shot should be recorded.
• Gillnets and Trammel nets – The number times nets are shot each day should be recorded.
• Dredges – The total number of times dredges are shot should be recorded.
• Hook and Lines – The total number of Hooks/lines shot each the day should be recorded.
• Pots and Traps – There is currently no requirement to record the number of fishing operations in relation to pots and traps, however the number of pots shot each day must be recorded in the FAR under gear details.

For example:

1. A fishing vessel shoots, tows, and hauls a towed net. Each instance of shooting the gear counts as a single fishing operation. If the vessel were to carry out this process four times on the same day, it should record four fishing operations on its FAR for that day.

2. A fishing vessel sets a single gillnet and then sets two more gill nets at different locations on the same day. Each setting of a net counts as a single fishing operation, so the vessel should record three fishing operations on its FAR for that day.

3. A fishing vessel sets 4 strings of 20 pots and then retrieves 6 strings of 20 pots that were set during a previous fishing trip. The total number of pots retrieved on this trip (6 x 20 = 120) should be number recorded in its FAR gear details, not the number set, unless these were retrieved during the same fishing trip.

This information, when combined with other data:

• provides a greater understanding of the effectiveness and impacts of different gears and fishing patterns on fisheries.
• provides useable data in respect of fishing effort.
• allows better identification, design, and implementation of targeted fisheries management measures to ensure sustainable fishing opportunities and preservation of stocks.

5. Ports:

It is a statutory requirement for masters of fishing vessels to correctly record the vessel’s port of departure, return, and landing. Incorrect ports may be declared where vessels are nomadic or move to fish from or land into a new port and forget to adjust the e-log to reflect the new port.

If you are unsure which code to use, please contact the local MMO office for advice.

Correct port information is important as it allows regulators to:

• check that a vessel lands and complies with licence conditions applicable to the vessel and species it intends to land.
• ensure vessels complete any applicable notifications and returns before landing in a designated port.
• undertake landing inspections to check that species are being landed at required ports and locations in accordance with licence conditions.
• verify that vessels comply with applicable Compliance Visiting Condition requirements of their fishing licence.
• ensure that published data and statistics are attributed to the correct ports.
• verify information supplied in relation to grant applications.