5th Regional Observer Programme Intersessional Working Group

Within the CCFS, there are two types of SSI related cases that are based on ROP set-level data: 

• SHK: Shark Catch Alleged Infringements. These are Cases for alleged infringements related to retention of oceanic white tip or silky sharks, or shark fining activity identified in ROP observer data (obligations in CMM 2022-04).

  SHK cases are generated where a ROP observer has reported instances during a WCPFC ROP trip where 

  • fishing vessel has caught an oceanic white tip or silky shark as identified by a specific species code (SP_code) in combination with an observed fate code (FATE_code) indicating retention is whole or in part.
  • fishing vessel has caught shark as identified by a species code (SP_code) in combination with an observed fate code (FATE_code) indicating fining activity.

• CWS: Cetacean and Whale Shark Interactions.  Relevant WCPFC requirements prohibit purse seine vessels from setting if a whale shark or cetacean is sighted prior to the commencement of the set; required reporting of any incidents of unintentional encircling; and guidelines for safe release (obligations in CMM 2011-03 and CMM 2022-04). 

  CWS cases are generated where a ROP observer has reported instances during a WCPFC ROP trip where a cetacean or whale sharks as identified by a specific species code (SP_code) in combination with an observed fate code (FATE_code) indicates an interaction with the fishing vessel’s activity.

Some current issues identified include, but are not limited to:

• The Commission has acknowledged that the CWS cases in CCFS are an issue and TCC17 (2021) agreed this data would be excluded from consideration of the current trial process of reviewing the Aggregated Tables in the Compliance Monitoring Scheme (CMS).
• The CCFS CWS instances currently reflect a recording by the observer of interactions between the vessel and marine mammals or with whale sharks (an observer on a purse seine vessel has reported a cetacean or whale sharks, as identified by a specific species code (SP_code) in combination with an observed fate code (FATE_code)).  Currently the ROP data fields do not permit the observer to categorise the data fields that are inputs to the CCFS to distinguish between interactions where there is no alleged infringement and that are of scientific interest, with those interactions or actions by the crew that could indicate a potential infringement has occurred.
• As is noted in  Working Paper 02 Annex A, there are a number of other SSI obligations in CMMs (seabirds (CMM 2018-03), sea turtles (CMM 2018-04), mobulids (CMM 2019-05)) and potentially refinements for sharks (CMM 2024-05) and cetaceans (CMM 2024-07), which would facilitate the creation of additional types of observer-initiated cases in the CCFS, but the ROP data fields need to be reviewed to support more clear identification of potential violations of SSI related obligations.  
• In 2024, some suggestions were made as part of ROP-IWG discussions of data fields that will support the review of implementation of seabird mitigation measures under CMM 2018-03, these are provided in Working Paper 02 Annex A and Annex B.

Participants in the virtual meeting will be invited to share views, proposals and comments.  The Chair will lead a discussion on the next steps.