SESSION 7.1 Developments with Observer Data Collection Sixth Tuna Data Workshop (TDW-6) April 2013 SPC, Noumea, New Caledonia

9 th DCC 9 th Tuna Fishery Data Collection Form Committee process has started Starting with Observer Forms Over four days in Rarotonga Artisanal forms reviewed Logsheets and unloading and port sampling forms to follow

With respect to the new CMMs CMM – Mitigating Impacts of fishing on Sea Birds Mitigation devices already recorded. Capture the details of any weighted lines Record the weight of any attached weights to the branchline Record the distance this weight is from the hook

CMM on Oceanic White Shark and CMM 2011 on Sharks Prohibits vessels from retaining on board, transhipping, storing, or landing any OCS in whole or part. Requires vessels to release any OCS that is caught as soon as possible after the shark is brought alongside the vessel. Flag States to report – using observer data etc – the total number of releases and status on release. This is already done on the LL-4 form. Sharks will be recorded as a species of special interest on the PS-3 form. The codes DPA, DPD, DPU will be used along with DFR and RFR as secondary codes in the comments

CMM on Whale Sharks Similar to wording used in CMM ( ) on Cetaceans Prohibits PS vessels from setting their net on a school of tuna that is associated with a whale shark/cetacean. And if found after the set is made Ensure that all reasonable steps are taken to ensure its safe release Report the incident Follow the WCPFC guidelines for the release (to be provided) Observers will record if vessel followed WCPFC guidelines on their GEN-2 form Added to the GEN-3 form to note if an infringement has been made.

PNA MSC Chain of Custody Observer Programme The DCC said... The work of the observer should be limited to the catcher vessel and that observers cannot be in two places at one time and should not be asked to move to the carrier vessel. The observer scheme should not go ahead until the transhippment observer programme is in place Many of the data items required by the PNA MSC forms are already part of the DCC observer forms and it is a burden to maintain two sets of forms. Data Management protocols should be specified – how to identify a MSC trip and clarification on the transfer of completed data to the programme provider (multiple?) The reason that the first three MSC trials failed be identified and shared with the PIFRO programme. Placing transhippment observer on carrier vessels is a positive development and it could be seen as an opportunity for improved port sampling

Form changes of interest Add unique vessel identifier (FAO UVI), remove the WCPFC – WIN number Use ISO 8601 standard for date and time (year/month/day) Placement form After WCPFC Audit. Create a vessel safety check form based on the WCPFC standard and integrate it into the placement form. Data kept in OPM database. Electronics – pre print vessel electronics form from the OPM database. The observer will check if there are any updates. Other trip id codes captured - MSC or other COC cross- endorsed trips.

GEN-3 expanded to allow more written reporting on the form. Difficult to access reports, journals. GEN-5 form – has the FAD been lifted from the water when reporting on any entangled species. GEN-6 form – retired. Request for information on invasive species to be explored.

DCC also looked at Scanning observer data (Corey) – Ideas to improve – Calibration strips, arrows to orientate page, page identifier, fineness of the lines etc For data management, DCC requested a review of – Procedures to attach observer documents – net plans – Photo storage – The format of the observer journal especially with respect to data management