DIGITAL MONITORING OF COMMERCIAL FISHING

Similar documents
Fisheries (Codes and Instructions) Circular. Fisheries (Codes and Information) Circular 2017

Digital monitoring of commercial fishing

Instructions: Section A: Vessel Owner, Operator and Manager. Complete for each application / vessel. Complete each question unless otherwise directed.

11th Meeting of the Science Working Group. Lima, Peru, October SWG-11-12a. New Zealand SPRFMO Observer Implementation Report for 2011

The Commission for the Conservation and Management of Highly Migratory Fish Stocks in the Western and Central Pacific Ocean

Recalculation of historical landings of porbeagle shark New Zealand Fisheries Assessment Report 2017/12

FIN 8/2015 8/07/2015. No, it is prohibited to target BFT during any fishing trip, including commercial, recreational and sports fisheries.

IOTC Agreement Article X. Report of Implementation for the year 2016

Intersessional Working Group Regional Observer Programme September 2007 WCPFC MINIMUM DATA STANDARDS FOR REGIONAL OBSERVER PROGRAMME (DRAFT)

1. Weigh entire catch (small, ~400 kg,) before or

Data Type Example Additional Explanation. ISO 3 alpha country code

SCIENTIFIC COMMITTEE TENTH REGULAR SESSION. Majuro, Republic of the Marshall Islands 6-14 August 2014

Conservation Services Programme Project MIT : Protected species bycatch media

018 COM Doc. No. COC-324A / 2018 November 18, 2018 (3:00 PM)

7 th Annual Meeting of the Commission January, The Hague, The Netherlands

Data Type Example Additional Explanation ISO 3-alpha country code Capitalised Free text AUS

82 ND MEETING RESOLUTION C RESOLUTION ON THE PROCESS FOR IMPROVED COMPLIANCE OF RESOLUTIONS ADOPTED BY THE COMMISSION

SCIENTIFIC COMMITTEE THIRTEENTH REGULAR SESSION. Rarotonga, Cook Islands 9 17 August 2017

SCIENTIFIC COMMITTEE TENTH REGULAR SESSION. Majuro, Republic of the Marshall Islands 6-14 August 2014

Blue cod 5 (BCO5) pot mesh size review

PORT PHILLIP BAY COMMERCIAL NETTING ADJUSTMENT PROGRAM. Information Booklet

Best Practice Guidance for Assessing the Financial Performance of Fishing Gear: Industry-led gear trials

IOTC-2017-CoC14-CR17 [E] IOTC Compliance Report for: Mauritius Report produced on: 15/04/2017

Changes to the Gas. (Safety and Measurement) Regulations. effective 1 July 2013

TECHNICAL AND COMPLIANCE COMMITTEE Sixth Regular Session 30 September - 5 October 2010 Pohnpei, Federated States of Micronesia

ANNEX ANNEX. Proposal for a Regulation of the European Parliament and of the Council

COMMISSION OF THE EUROPEAN COMMUNITIES. Proposal for a COUNCIL REGULATION

Report of Implementation for the year 2014

82 ND MEETING PROPOSAL IATTC-82-A-1 PRESENTED BY JAPAN DRAFT RESOLUTION ON IATTC CATCH DOCUMENTATION SCHEME

7. Catch Balancing. 7.1 Catch Balancing

7 th Annual Meeting of the Commission January, The Hague, The Netherlands

Recognising however that an interim management measure for deep pelagic redfish in 2018 in the Irminger Sea and adjacent waters is required;

High seas: conservation and management measures to prevent significant adverse impacts on vulnerable marine ecosystems

2018 COM Doc. No. COC-303_Appendix 1 / oct.-18 (11:37 )

AD HOC WORKING GROUP ON GROUNDFISH MANAGEMENT, MAY 5 and 6 Overview of ADF&G skate fishery management and data collection, 2003

This document is meant purely as a documentation tool and the institutions do not assume any liability for its contents

BLACK SEA BASS NORTH OF CAPE HATTERAS DEALER PERMIT ISSUE PAPER. June 12, 2008 (REVISED) (NOTE: proposed rule under construction, eff.

Agenda Item H.4.b Excerpt of the Alaska Streamer Line Regulations NMFS Report Gear Limitations

Updated abundance indicators for New Zealand blue, porbeagle and shortfin mako sharks

SHARK CHECK SHEETS RECEIVED IN ACCORDANCE WITH REC (As of 16 October 2017, Madrid time)

For the purposes of any clarification and legal interpretation the original byelaw should referred to.

IOTC-2018-CoC15-CR10 [E] IOTC Compliance Report for: Japan Report produced on: 12/04/2018

Fisheries data collection of Thai oversea fishing fleet

CONSERVATION AND MANAGEMENT MEASURE TO MITIGATE THE IMPACT OF FISHING FOR HIGHLY MIGRATORY FISH STOCKS ON SEABIRDS

Draft Addendum V For Board Review. Coastal Sharks Management Board August 8, 2018

Unit C Operational Coordination

Requested Changes for the Bluefin Tuna Catch and Release Fishery

New Zealand s Fisheries Quota Management System

Sampling Priorities. Trawl Catch Composition Sampling. Effects on sampling. Objectives 1/19/2012. List 4 things that can impact catch composition

ALBACORE TUNA (ALB) INITIAL POSITION PAPER

Proposal for a REGULATION OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL

LICENSING SERVICES DIVISION QUICK GUIDE

Fisheries Management (Fish Processors)

(Legislative acts) REGULATIONS

Official Journal of the European Union. (Legislative acts) REGULATIONS

L 340/8 Official Journal of the European Union

REGULATIONS RELATING TO MESH SIZES, BYCATCHES AND MINIMUM SIZES, ETC., DURING FISHING OPERATIONS IN THE FISHERIES PROTECTION ZONE AROUND SVALBARD

SCIENTIFIC COMMITTEE ELEVENTH REGULAR SESSION. Pohnpei, Federated States of Micronesia 5-13 August 2015

Unit C Operational Coordination

Guidelines for fishing for sharks posing an imminent threat to public safety

Regional Logbook Best Practices Guidelines: Module 4, 5 and 6: Daily Catch Reporting, Biological Data, Socio-economic Data

Coastal zones for public fishing

PROPOSAL IATTC-92 B-4 REVISED SUBMITTED BY BELIZE, GUATEMALA, NICARAGUA, COSTA RICA AND PANAMA

NZ s Fishery Management Framework The Fisheries Act 1996 & Spatial Management Tools

BLUE SHARK (BWS) (Prionace glauca)

Unit C Operational Coordination

Conservation and Management Measures

COMMISSION OF THE EUROPEAN COMMUNITIES. Proposal for a COUNCIL REGULATION

NZ Sport Fishing Council submission on the proposal for an inseason increase to the total allowable catch for southern bluefin tuna

Economic review. of the seafood industry THE ECONOMY IN THIS EDITION. Edition 8 June 2014

NFR 17. New Zealand Tuna Fisheries in 2002 and SCTB17 Working Paper. Terese Kendrick 1, Talbot Murray 2 and Susan Jane Baird 3

IOTC-2018-CoC15-CR09 Rev1 [E] IOTC Compliance Report for: Iran Report produced on: 12/04/2018

Marine Protected Species Interactions with Commercial Fisheries

1. TAC and quota allocation between Contracting Parties for the deep pelagic fishery

Fisheries and Other Legislation Amendment Regulation (No. 1) 2006

FISHERIES MANAGEMENT ACT 1998 AND FISHERIES (TORRES STRAIT PROTECTED ZONE) ACT 1984, CHAPTER 411.

Options for Differential Management and Monitoring of Seabird Bycatch

INSPECTION, TESTING AND CERTIFICATION OF GASFITTING WORK DONE UNDER SUPERVISION

COMMISSION OF THE EUROPEAN COMMUNITIES. Proposal for a COUNCIL REGULATION

MANDATORY REPORTING GUIDELINES

REPUBLIC OF THE MARSHALL ISLANDS. FISHING LICENSE (THIRD IMPLEMENTATION ARRANGEMENT) REGULATIONS OF 2009 (Title 51 MIRC ) ARRANGEMENT OF REGULATION

Sustainable Recreational Fishing Student Activity Workbook 6.2. Sustainable Recreational Fishing

2017 CONSERVATION HARVESTING PLAN Atlantic Halibut (4RST) Prince Edward Island fixed gear fleet Less than meters

Using Electronic Monitoring to Document Snapper Discards and Validate Catch effort Data New Zealand Fisheries Assessment Report 2016/57

Undulate ray (Raja undulata) in divisions 8.a b (northern and central Bay of Biscay)

Atlantic States Marine Fisheries Commission

Independent Observers

Pacific States Marine Fisheries Commission Annual Meeting August 21, 2017

Unit 1 Operations. Joint Deployment Plan PELAGIC FISHERIES IN WESTERN WATERS 2017 Joint Campaign

REC.CM-GFCM/40/2016/4

NATIONAL MARINE FISHERIES SERVICE REPORT ON DEEP-SET BUOY GEAR AMENDMENT SCOPING

National Oceanic and Atmospheric Administration. Pacific Island Pelagic Fisheries; 2016 U.S. Territorial

Brussels, COM(2017) 128 final. ANNEXES 1 to 13 ANNEXES

Introduction. Page 1 of 28

Trials of a Net Grid for the UK Nephrops trawl fisheries

A8-0377/

3/ Sprat ISprattus sprattus L.I. 3. Anadromous and catodromous species may be fished only in exceptional

AK EM Marching orders for PSMFC

4. BOAT TEAMS. All boats shall consist of a minimum of 2 anglers with a maximum limit to the number of anglers as per NSW Maritime Vessel Capacity.

16-05 SWO RECOMMENDATION BY ICCAT REPLACING THE RECOMMENDATION [13-04] AND ESTABLISHING A MULTI-ANNUAL RECOVERY PLAN FOR MEDITERRANEAN SWORDFISH

Transcription:

DIGITAL MONITORING OF COMMERCIAL FISHING User Guide >28 metre trawl vessels Geospatial Position Reporting and E-logbook Reporting FUTURE OF OUR FISHERIES www.mpi.govt.nz

Digital Monitoring of Commercial Fishing CONTENTS Introduction 3 What s changing 3 Geospatial Position Reporting 4 System failure process 4 Registering people to report 4 Updating your e-logbook 4 Completing records and reports overview 5 Trip Start Record 6 Fish Catch Report trawling 7 General information 7 Report content 7 Non-fish Species or Protected Species Catch Report 9 General information 9 Report content 9 Processing Report 11 General information 11 Report content 11 Disposal Report 13 General information 13 Report content 13 Trip End Record 15 Landing Report 16 General information 16 Report content 16 Page 2

FUTURE OF OUR FISHERIES INTRODUCTION The Ministry for Primary Industries is making changes to the way commercial fishing activity is monitored and reported. For all trips starting on or after 1 October 2017, trawl vessels longer than 28m in overall length will be required to have a Geospatial Position Reporting device, and to use an e-logbook for completing and transmitting their fishing catch and effort reports. There are also changes to what needs to be reported, and when information needs to be transmitted. This guidebook will help you understand the new reporting requirements. Similar guidebooks will be provided at a later date for other methods of commercial fishing. This is not a legal document For the exact requirements please refer to the: Fisheries (Reporting) Regulations 2017, and the Fisheries (Geospatial Position Reporting) Regulations 2017 (available at legislation.govt.nz) the four circulars on the MPI webpage mpi. govt.nz/fisheries-digital-monitoring and the exemptions Exemption to the fisheries (Geospatial Position Reporting) regulations 2017 Exemption to the fisheries (reporting) regulations 2017 Limited exemption to the fisheries (reporting) regulations 2017 Together, these set out the legal and technical requirements for the e-logbooks and GPR. The circulars also describe in more detail exactly what information must be provided. What s changing Some of the key changes between the old paper-based system and the new electronic (e-logbook) reporting system are: A different structure the new electronic system is based around the five types of event: fish catch non-fish and protected species catch processing disposal landing. Two new records are required a Trip Start Record and a Trip End Record. Some new fields for information have been added to Fish Catch Reports, and some have been removed. For example, you no longer need to note your position at midday, or the water temperature when the net is shot, but you do need to record the use of mitigation devices. The estimated catch now applies to eight species: the top five QMS species and the top three non- QMS species. All fish caught now needs to be reported. This includes some fish that have not required reporting before, such as fish below the minimum legal size. All position information must be given as coordinates that are accurate to four decimal places if the system is entering them automatically, or three decimal places if you are entering them manually. While the co-ordinates have to be given as decimals, it is expected that e-logbooks will be able to record positions in other formats and will decimalise them automatically if necessary. Disposal Reports need to record all catch that is not on vessel at the end of the trip. Landing Reports will only need to record fish that are on a vessel at the end of the trip. Page 3

Digital Monitoring of Commercial Fishing Geospatial Position Reporting The new Geospatial Position Reporting (GPR) requirements will be met by your existing VMS system. You are not required to make any changes in order to comply with the new GPR requirements, as your existing VMS systems will be automatically re-registered as a GPR system. Your only responsibility is to ensure that the GPR system is operational at all times, by working with your GPR provider. System failure process Geospatial Position Reporting (GPR) device failure If you become aware that the GPR device has failed, you need to notify the Fisheries Communication Centre (FCC) by emailing FCC@mpi.govt.nz as soon as practicably possible. The FCC will: verify that the signal is not being received and will attempt to remedy the situation, or seek alternative methods of providing positioning data for the remainder of the fishing trip. If the FCC becomes aware that a GPR device is not transmitting they will contact the skipper directly in order to resolve the situation. e-logbook failure If you become aware that your e-logbook has failed and you are unable to record event data; or unable to transmit event data you must: notify MPI of the nature of the failure by emailing fisheries@mpi.govt.nz. If you are unable to record event data: use an alternative method of recording all the required event data and required trip-related data. If you are unable to transmit event reports: continue recording the event data. Upon returning to port: in both cases supply the appropriate event reports and trip-related data to FishServe via an authorised electronic device. Registering people to report Permit holders need to register the skippers who will complete and provide the reports, and notify them to FishServe. Updating your e-logbook It is your responsibility to ensure that your vessel has up-to-date software. Catch Effort EDT (Cedric) users need to make sure they have updated to the new version before any trip starting on or after 1 October 2017. All types of e-logbook will notify users when an update is available and this update should be completed the next time the vessel is in port. There is no need to use satellite data to carry out the update while you are at sea. Page 4

FUTURE OF OUR FISHERIES COMPLETING RECORDS AND REPORTS OVERVIEW Table 1 gives an overview of when you need to complete the various records and reports. Detailed information about each record and report type is provided in the later sections of this guidebook. Information on current exemptions relating to reporting timeframes can be found on the MPI website at mpi.govt.nz/fisheries-digital-monitoring Table 1. Reporting timeframes Record or report type (in the order that they must be completed)* Completion within an e-logbook Information type Completion timeframe Provision timeframe Trip Start Record All general trip start details Before a Fish Catch Report is started By the end of day Fish Catch Report Record type of fish the permit holder intends to take Date and time of when and location of where fishing starts Date and time of when and location of where fishing ends Immediately after fishing starts Immediately after fishing starts Immediately after fishing ends All catch information as specified in a circular Within 8 hours after fishing ends By the end of day on which event is completed NFPS Catch Report Information about the NFPS caught and the catch event. Before the close of the day on which the permit holder becomes aware of the catch Before the close of the day on which the permit holder becomes aware of the catch Processing Report Disposal Report Daily summary of catch put into the freezer and whole fish to meal If you provide processing reports, give a summary of all disposals for the day. Otherwise summarise all disposals for a tow. The processing can be completed and provided before the close of the day following the day covered by the report. If processing starts on one day and ends on another day, the report can be completed and provided before the close of the day following the day on which the processing ends The Disposal Report be completed and provided before the close of the day following the day covered by the report. Trip End Record End location date/time and other required information When the vessel arrives in port (unless it is an end-of-year Landing Report or relates to transhipping) No later than the date that the Landing Report is provided Landing Report Types of fish or fish product landed and their quantities Any time between the end of fishing and the end of landing At latest immediately after the landing is finished Date when landing finishes Destination type code All other information as specified in a circular e.g., greenweights As soon as is practicable after actual weights are received from LFR As soon as is practicable after actual weights are received from LFR *Note: not all reports may need to be completed and submitted if, for example, there is no NFPS catch or no processing carried out. Page 5

Digital Monitoring of Commercial Fishing TRIP START RECORD The Trip Start Record must be completed before the first Fish Catch Report for the trip is started. Note that some fields in the Trip Start Record will be filled in automatically by the system when you begin a record: Event ID, authorised user and completed date/time. There are five fields that must be filled in manually: Trip ID this can be generated by the e-logbook, or you can enter a combination of letters and numbers yourself. An example might be your vessel name and the number of trips this season e.g., MidnightExpress05. This ID will show on every report that relates to this trip. Each trip must have a unique ID. Client number this is the client number given by FishServe to the permit holder in whose name fish are taken. Is vessel used? for trawling, this will always be yes. Vessel number enter the number shown on the vessel s certificate of registration. Person in charge this means the name of the person who is in charge of fishing operations for the trip. Start details enter the date and time of the start of the trip and the co-ordinates for where the vessel is at the trip start. This should ideally happen before you leave port to check that the system is operating correctly. Amendment reason only needs to be filled in if you need to change a report (for example to correct any information) after it has already been submitted. If there is any extra information that you want to add you can type it in the Notes field, but you can leave this field blank. Page 6

FUTURE OF OUR FISHERIES FISH CATCH REPORT TRAWLING General information This report provides the data that you previously reported on at the top part of a Trawl Catch, Effort and Processing Return (TCEPR). The e-logbooks are designed so that it is not possible to start a Fish Catch Report unless a Trip Start Record has been completed. You must complete a separate Fish Catch Report for each tow. Report content The first five fields of the catch report are general information about the fishing trip and will be automatically carried across from the trip start record: Trip ID Client number Is vessel used? Vessel number All the codes that you need to complete the next three fields are listed in Schedule 2 of the Fisheries (E-Logbook Users Instructions and Codes) Circular 2017. The fishing method and target species codes have not changed from the old system. Fishing code method choose one of the six possible codes for trawling Target species code this is the code for the main species you are trying to catch (although it may not be the one you actually catch the most of) Mitigation device codes enter the codes for devices required by the regulations as well as any used on a non-regulatory basis. In the next set of fields you will need to provide more details about the tow itself, but depending on the type of tow you are doing some of these fields might be left blank: Number of nets this will be at least one. Vessel pair number if you work in a pair, add the registration number of the second vessel. Wingspread this should be the wingspread (in whole metres) as the net was originally designed, or as it is at present if you have modified it. If you use more than one net, enter the total combined wingspread of all nets in metres. If you have a spread sensor installed give the average wingspread during the entire tow. Headline height this should be the average distance from the groundrope to the headline as measured by a net monitor, if you have one, or the headline height that the net is currently designed to operate at. For bottom trawl nets that have a headline height of less than 10 m MPI encourages you to record this information to one decimal place (e.g., 5.2 m) if this information is available. Otherwise, please record this information to the nearest metre. Codend mesh size this should be the minimum mesh size (in millimetres) of the codend(s), or 0 if you are using PSH gear. Groundrope depth this should be the distance (in whole metres) from the sea surface to the groundrope at the point when the net reaches the target depth. Bottom depth this should be the water depth at the groundrope (in whole metres) from the sea surface to sea bottom when the net reaches the target depth. Page 7

Digital Monitoring of Commercial Fishing Speed this should be the average speed (in knots) of the entire tow. Is net lost? if the answer here is yes, give as many extra details as possible in the Notes field. Start position enter the date/time of when the net reaches its intended depth and position e.g., when the brakes are applied, and the position of the vessel at that time. Finish position enter the date/time of when the net leaves its intended depth and position e.g., when the brakes come off, and the position of the vessel at that time. Total estimated catch enter a value in kilograms. Catch Records you will need to fill in the species code and estimated greenweight (in kilograms) for the five QMS and top three non-qms that you catch. The codes are listed in Schedule 2 of the Fisheries (E-Logbook Users Instructions and Codes) Circular 2017, and have not changed from the old system. The method you use to estimate the weight of each species is up to you. For example, you could: multiply the number of bins of a species by an average bin weight; or make a visual estimate of the weight of a species; or divide the initial estimate of bag weight by the relative proportion of species caught. Instructions on what to do if you catch non-fish or protected species are in the next section. Page 8

FUTURE OF OUR FISHERIES NON-FISH SPECIES OR PROTECTED SPECIES CATCH REPORT General information You will have to complete this report if you make an Non-fish/Protected Species (NFPS) catch at any time during a trip whether it was made during a tow or while you were not fishing (for example if there was a deck strike while you were steaming). This report is largely the same as the Non-fish / Protected species catch return required under the previous regulations. Report content Most fields in the general information section of the NFPS Catch Report will be filled in automatically by the system, but some details will need to be changed if the catch was made during a tow: NFPS Trip ID this will be filled in automatically by the system. Client number this will be filled in automatically by the system. Is vessel used? this will be filled in automatically by the system. Vessel number this will be filled in automatically by the system. Fish catch event ID unless you are reporting a deck strike or are unsure which fishing event a capture resulted from, enter the event ID of the corresponding Fish Catch Report for the tow where the capture occurred. Event date/time enter the details for where and when the catch occurred, whether it was as part of a tow or during non-fishing activity. If you catch a seabird, marine mammal, reptile, or protected fish species, the NFPS Catch Report must give the number of animals caught and the life status uninjured, injured, or dead each one was in when it was released or returned to sea. If you catch corals, sponges or bryozoans, you must record the weight of each species. The next section, NFPS catches, gives the specific details of the catch: Species code enter the exact species code if possible. Otherwise, enter the other species code. For example, if you catch a seabird and you think it is a petrel but can t identify the individual species, enter the code XXP, which is the code for unidentified petrels, prions and shearwaters. For each species code, you must then indicate whether it was uninjured, injured or dead, using the definitions below. Number uninjured enter the number of a particular seabird, marine mammal, reptile or protected fish species released that was alive and uninjured. Number injured enter the number of a particular seabird, marine mammal, reptile or protected species that was released alive and injured, according to the definitions in the section above. Number dead enter the number of a particular seabird, marine mammal, reptile or protected species that were dead. For example, if you caught one fairy prion that sustained a broken wing and one New Zealand fur seal that was dead you would need to enter the following: Species code XFP Number uninjured 0 Number injured 1 Number dead 0 and Species code FUR Number uninjured 0 Number injured 0 Number dead 1 Page 9

Digital Monitoring of Commercial Fishing Definitions of injured: For seabirds, it is one or more of the following: broken or drooping wing (i.e., the seabird cannot fold the wing up) broken beak or leg open wound hook in bird (whether removed or not). For a marine mammal or reptile, it is one or more of the following: open wound hook in the animal (whether removed or not) broken flipper, fin, or tail broken shell (turtle). For a protected species, it is one or more of the following: open wound a hook in the animal (whether removed or not) removed from the water. The last five fields of an NFPS Catch Report may or may not need to be filled in: Estimated weight if applicable, enter your estimate of the weight of each species of coral, sponge or bryozoan caught rounded down to the nearest kilogram (or enter 1 if less than a kilogram was caught). Seabird capture code this is only relevant if you catch a seabird during trawling activities. You should enter the code for whether you think the bird was caught on the net, on the warps, or other. If you re not sure, enter other and add any other information in the Notes field. Tag if it is possible to safely obtain any identifier (such as a band on a seabird s leg or a tag on a marine mammal), record the numbers on each identifier. Corals, sponges, and bryozoans, are able to be recorded under a single code: (CSB) Amendment reason only needs to be filled in if you need to change a report after it has already been submitted. If there is any extra information that you want to add you can type it in the Notes field, but you can leave this field blank. Page 10

FUTURE OF OUR FISHERIES PROCESSING REPORT General information This report only needs to be completed for vessels that have the appropriate MPI registrations, including i.e.. Limited Processing Fishing Vessels, or Registered Risk Management Programme. If you are required to complete a Processing Reports, one is required for every 24 hours that you process catch. Each report must cover a time period of no more than 24 hours. This report is largely equivalent to the daily processing summary of a TCEPR. The main difference is that fish that is not processed/packed (e.g. returned to the sea or eaten) is reported on a Disposal Report rather than the Processing Report. You do not need to provide details about fish oil on the Processing Report, but the amount of fish oil landed will need to be reported in a Landing Report. Report content The first four fields of the processing report are general information about the fishing trip and will be automatically carried across from the Trip Start Record: Trip ID Client number Is vessel used? Vessel number For processing date time you should record the end of the time period that the processing report applies to. If there is any extra information that you want to add, you can type it in the Notes field, but you can leave this field blank. Amendment reason only needs to be filled in if you need to change a report after it has already been submitted. Note that some fields in the processing report will be filled in automatically by the system: Event ID, authorised user and completed date/time. Event version is filled in if you are changing a report, (for example for the first, second or third time in which case it will be 1, 2 or 3). To complete the product records section, you will need codes that are listed in Schedule 2 of the Fisheries (E-Logbook Users Instructions and Codes) Circular 2017 for the first two fields: Product state code you should choose the code that best describes the state of the fish after processing. If the fish is in more than two states, you should give the code for the state that has the greatest weight after processing as the principal product state and list the other code under additional product state. Container type code you should choose the code that best describes the container the fish was packed in. The next three fields should be filled in for each different type of container: Estimated container weight you should record the average weight of fish in a container (i.e., excluding the weight of the container and any packaging and other non-fish components). Container count do not include any containers that are in blast freezers. Conversion factor this means the appropriate conversion factor for the species and product state you have entered, unless the product state code is LIV, MEA or GRE. You can also leave this blank if you are giving the information for an additional product state. There may be more than one species record in a Processing Report, and for each one you must give the: Species code choose from the codes in Schedule 2 of the Fisheries (E-Logbook Users Instructions and Codes) Circular 2017. Greenweight this will be a weight in kilograms that, if necessary, uses the appropriate conversion factor. Table 3 shows what information is needed if you are filling in a Processing Report for fish meal and shark livers. Page 11

Digital Monitoring of Commercial Fishing Table 3. Specific requirements for MEA, LIV and LIB product states. Product state Specific requirements for completing a Processing Report MEA (whole fish to meal) The information for container type, estimated container weight and container count only needs to be entered once on a processing report for each container type / container weight combination. For example if fish meal is packed into 30 kg sacks, you only need to enter the following information once: Container type = SAC Estimated container weight (kg) = 30 Container count = total number of sacks of fish meal produced during the 24 hr period. This includes all fish meal, whether it was produced from whole fish or offal. For each species of fish mealed during the 24 hr period (principal product state) you must also enter the species code and greenweight (kg). LIV (livers, principal product state); and LIB - (livers, additional product state) Note that this only applies to shark livers If livers from multiple species of shark are packed in the same container, information on container type, estimated container weight and container count only needs to be entered once on a processing report for each container type / container weight combination. For example, if livers from several species of shark are packed in 20 kg cartons, you only need to enter the following information once: Container type = CAR Estimated container weight (kg) = 20 Container count = total number of containers of livers produced during the 24 hr period. This includes all livers, whether they were produced as a principal or additional product state. For each species of shark from which livers are packed (principal product state) you must also enter the species code and greenweight (kg). Page 12

FUTURE OF OUR FISHERIES DISPOSAL REPORT General information Situations where a Disposal Report needs to be provided include instances where fish are caught but are: eaten on board the vessel; or are below minimum legal size and must be returned to the water; or are returned to the water for any other reason. If you have to complete a Processing Report, you need to complete the Disposal Report in the same time period as your Processing Report. For other vessels, you must submit a Disposal Report for each tow. Catch that is reported on a Disposal Report does not also need to be reported on a Landing Report. Note, this is a change from the old system. Report content The first four fields of the Disposal Report are general information about the fishing trip and will be automatically carried across from the trip start record: Trip ID Client number Is vessel used? Vessel number For disposal date time you should record the date and time when all the fish caught in that fishing event that are going to be disposed of have actually been disposed of. For trawl vessels completing a Processing Report this will be the same information that is recorded as processing date time. In any other situation this will be the time when the disposal is complete. Fish Catch Event ID unless you are on a processing vessel, enter the event ID of the corresponding Fish Catch Report for the tow where the fish were caught. This field does not need to be completed for processing vessels. Amendment reason only needs to be filled in if you need to change a report after it has already been submitted. If there is any extra information that you want to add you can type it in the Notes field, but you can leave this field blank. To complete the stock disposal records section you will need codes that are listed in Schedule 2 of the Fisheries (E-Logbook Users Instructions and Codes) Circular 2017 for the fishstock code, and in Table 4 below for disposal code. Enter the estimated greenweight in kilograms for each species. Page 13

Digital Monitoring of Commercial Fishing Table 4. Disposal codes Disposal type Disposal code Required to be reported on Monthly Harvest Return? Fish or fish product used for human consumption on board a vessel E Yes Fish or fish product of a species or classes of fish managed under the QMS that are returned to the sea, abandoned in the sea, or accidentally lost at sea, except for fish or fish product to which another disposal code applies A Yes Loss of fish or fish product from a holding container in the water (e.g. through mortality, escape, or damage to fish product) H Yes Fish or fish product taken or used for bait during the period of a trip U Yes Spiny dogfish that are returned to the water M Yes Blue shark (Prionace glauca), mako shark (Isurus oxyrinchus) or porbeagle shark (Lamna nasus) that are returned to the water dead or near-dead in accordance with the requirements set out for those species in Schedule 6 of the Fisheries Act 1996 Z Yes Fish or fish products of a species or classes of fish subject to the QMS that are returned to, or abandoned in, the sea in accordance with the requirements set out in section 72(5)(c)(i) to (iii) of the Fisheries Act 1996 J Yes Fish or fish product of the species or classes of fish not managed under the QMS that are returned to the sea, abandoned in the sea, or accidentally lost at sea D No Fish or fish product placed in a holding receptacle in New Zealand fisheries waters P No Fish of the species or classes subject to the QMS that are (a) listed in Schedule 6 of the Act; and (b) not spiny dogfish; and (c) not blue shark, mako shark or porbeagle shark that are returned to the water dead or near-dead; and (d) not rock lobster that must be returned to the sea; and (e) returned to the water in accordance with the requirements set out for the relevant species or class of fish in Schedule 6 of the Act X No Fish below a minimum legal size, width or weight Y No Page 14

FUTURE OF OUR FISHERIES TRIP END RECORD This should be completed and provided no later than the date on which any Landing Report is provided (unless it is an end of year Landing Report or relates to transhipping). The first five fields will be automatically carried across from the Trip Start Record: Trip ID Client number Is vessel used? Vessel number Person in charge The end details will show when the vessel ties up at a place where landing takes place. Amendment reason only needs to be filled in if you change a Trip End Record (for example, correcting or updating information) after it has already been submitted. If there is any extra information that you want to add, you can type it in the Notes field, but you can leave this field blank. If you come in to port to carry out a partial unload, you will need to complete a Trip End Record and a Landing Report. When you restart fishing you will need to complete a new Trip Start Record as well as all the other required reports. The electronic monitoring system will count your entire fishing trip as two trips if a partial unload takes place at some point. Page 15

Digital Monitoring of Commercial Fishing LANDING REPORT General information This report provides the data that you previously reported in a Catch Landing Return (CLR). The process for completing Landing Reports is similar to the process for completing CLRs where you had to complete all details except greenweight as soon as you finish landing. Under electronic reporting however, the Landing Report needs to be transmitted as soon as landing is finished and then updated with greenweight details when that information becomes available. These updates will be entered either from your logbook, or online via Kupe. All fish that is landed must be included in a Landing Report and all fish that has been caught but not landed must be included in a Disposal Report. In most cases, a Landing Report will be required because fish have been removed or discharged from a vessel and the report should then be completed at some point between when fishing finishes and when landing ends. There are some situations when a Landing Report must be completed and transmitted within different timeframes, as shown in Table 5. Table 5. Requirement to complete a Landing Report. Scenario that a Landing Report must be completed and provided Latest time by which Landing Report must be provided When fish has been removed or discharged from a vessel. This can be all fish or some fish if the intention is for some fish to be retained on board the vessel. Immediately after all fish has been removed or discharged (at the latest). Can be provided before the process of removing or discharging fish from a vessel starts if the information is available. When a vessel containing fish has been granted approval under section 110 of the Fisheries Act 1996 to leave New Zealand fisheries waters. Immediately after the vessel leaves the New Zealand EEZ (at the latest). Can be provided before the vessel leaves New Zealand fisheries waters if the information is available. At the close of a fishing year. This applies only if fish are held on board a vessel that, at the close of the fishing year, is operated by or on behalf of a person who, during that fishing year, has held 100 tonnes or more of annual catch entitlement under the Fisheries Act 1996. Immediately after the close of the fishing year in question (at the latest). When a vessel containing fish ceases to be registered or is re-registered under the Fisheries Act 1996. Immediately after the vessel containing fish ceases to be registered or is re-registered under the Fisheries Act 1996. Report content The first four fields of the Landing Report are general information about the fishing trip and will be automatically carried across from the Trip Start Record: Trip ID Client number Is vessel used? Vessel number Landing date time if you are completing a Landing Report for fish held on board at the end of the year, enter the date of the end of the year. Otherwise, enter the date as required by Table 5 above. Page 16

FUTURE OF OUR FISHERIES Table 6. Greenweight: who and when? Landing code Will a Landing Report using this code normally need to be amended or involve a second Landing Report? Who determines greenweight (and how)? B No Fisher estimate CS No Fisher estimate EOY Yes. Greenweight is optional until the actual weight has been provided by the LFR. Actual from LFR F No Fisher estimate H No Fisher estimate L Yes. Greenweight is optional until the actual weight has been provided by the LFR. Actual from LFR LR Yes. Greenweight is optional until the actual weight has been provided by the LFR. Actual from LFR O No Fisher (in consultation with observers and compliance) Q Yes. Greenweight is optional until the actual weight has been provided by the LFR. Actual from LFR R Yes. Fish must be reported on separate Landing Report when removed or discharged from the vessel. Fisher estimate S No Actual fish weighed under MPI supervision T Yes. Greenweight is optional until the actual weight has been provided by the LFR. Actual from LFR TT Yes. The vessel that receives the fish must also report it on a Landing Report. Fisher estimate V No Information provided to fisher by observer W No Actual weighed by fisher Amendment reason only needs to be filled in if you need to change a report after it has already been submitted. If there is any extra information that you want to add you can type it in the Notes field, but you can leave this field blank. A landing record must be filled out for each distinct combination of landing code, LFR client number (if applicable), and tranship vessel number (if applicable): Landing code enter the code from the list in Schedule 2 of the Fisheries (E-Logbook Users Instructions and Codes) Circular 2017 that best describes what has happened to the landed fish. LFR details received date/time enter the date the greenweight details are received from the LFR. This field only applies to those landing codes where fish is sold or conveyed to an LFR. LFR client number you only need to fill this in if the fish goes to a licensed fish receiver. Tranship vessel number if this applies give the registration number of the vessel that the fish was transferred to. Page 17

Digital Monitoring of Commercial Fishing The following three fields may or may not need to be filled in: Customary fishing document reference only applies if the landing code is CS. In this case, fill in the identifier of the customary fishing authorisation that the fish was landed under. Litres of fish oil landed Offal has been mealed (this is a Y/N field) To complete the landing-product record section, you will need codes that are listed in Schedule 2 of the Fisheries (E-Logbook Users Instructions and Codes) Circular 2017 for the first two fields: Product state code you should choose the code that best describes the state of the fish when it was landed, but if the fish is in more than two states, you should give the code for the state that has the greatest weight after processing as the principal product state and list the other code under additional product state. Container type code you should choose the code that best describes the container the landed fish was in. Estimated container weight you should record the average weight of fish in a container (i.e., excluding the weight of the container and any packaging and other non-fish components). Container count enter the number of containers of a particular type and content weight. Purchase order number if applicable, enter the number of the purchase tax invoice (or similar document) from the LFR that provides you with the greenweight of the fish that you supplied them with. For the stock record, you must give the: Fishstock code choose from the codes in Schedule 2 of the Fisheries (E-Logbook Users Instructions and Codes) Circular 2017. Greenweight this will be a weight in kilograms that, if necessary, uses the appropriate conversion factor. Shark fins enter the actual weight of shark fins, if applicable. There will only be one stock record for each landing-product record unless the product state code is MEA, LIV or LIB. For those three codes, follow the instructions in Table 7 below. Table 7. Special requirements for Landing Reports with codes MEA, LIV, or LIB. Code Instructions MEA (whole fish to meal) Information on container type, estimated container weight and container count only needs to be entered once on a Landing Report for each container type / container weight combination. For example if fish meal is packed in 30 kg sacks, you only need to enter the following information once: Container type = SAC Estimated container weight (kg) = 30 Container count = total number of sacks of fish meal produced during a trip. This includes all fish meal regardless of whether it was produced from whole fish or offal. For each species of fish mealed during the trip (prinicipal product state) you must also enter the fishstock code and greenweight (kg). LIV (livers, principal product state); and LIB (livers, additional product state) Only applies to shark livers If livers from multiple species of shark are packed in the same container on a vessel, information on container type, estimated container weight and container count only need to be entered once on a Landing Report for each container type / container weight combination. For example, if livers from several species of shark are packed in 20 kg cartons, you only need to enter the following information once: Container type = CAR Estimated container weight (kg) = 20 Container count = total number of containers of livers produced during a trip. This includes all livers regardless of whether they were produced as a principal or additional product state. For each species of shark from which livers are packed (principal product state) you must also enter the fishstock code and greenweight (kg). Page 18

FUTURE OF OUR FISHERIES www.mpi.govt.nz