Common use of HAIL Clause in Contracts

HAIL. i) Transmission of all vessel hails must be either as an email via Vessel Monitoring System (VMS) or some other electronic method, as determined by the sector. In all instances hail notification must be provided by either the sector manager (SM) or DSM vendor to NOAA Fisheries Office for Law Enforcement (OLE); the mechanism for hail notification must be detailed in the sector’s operations plan. ii) Prior to leaving port on a sector trip for which catch will count against sector annual catch entitlements (ACE), each sector vessel must hail trip start, meaning notify the SM and DSM vendor that the vessel is departing on a sector trip. The trip start hail must include vessel permit number, the trip ID# (which is the VTR number on the first VTR page used for that trip), and estimated trip duration. The DSM vendor must immediately send a confirmation to the vessel that the trip start hail was received; if the vessel does not receive confirmation within 10 minutes, the captain must contact the vendor to confirm the trip start hail via an independent backup system (e.g., a phone number) that must be set up by the DSM vendor. iii) At the appropriate time before landing (detailed below), the sector vessel must hail trip end to the DSM vendor. For all trips greater than 6 hours in length, and occurring more than 6 hours from port, vessels must hail trip end at least 6 hours in advance of landing. For trips less than 6 hours in length, or occurring within 6 hours of port, trip end hail notification time must be defined in the sector’s operations plan, after being agreed upon by the sector, the monitoring provider, and OLE. The trip end hail must include the following: A) Permit number; B) Trip ID#; C) Specific offloading location(s): Dock/dealer, port/harbor, and state (for all dealers or facilities where the vessel intends to offload); D) Estimated landing time; E) Estimated offloading time; and F) Estimated weight of each species of fish being landed. iv) The DSM vendor must immediately send a confirmation to the vessel that the trip end hail was received. If the vessel does not receive confirmation prior to landing, the captain must use the backup system to contact the DSM vendor prior to landing. The DSM vendor must inform the vessel in the trip end hail confirmation (and no earlier) that: A) The vessel will have a dockside monitor (DM) or roving monitor (RM) present; or B) The vessel is issued a DSM waiver for the trip (meaning no DM or RM will be present to witness the offload). v) If the DM has an emergency and cannot meet the vessel as scheduled, the DSM vendor must notify the vessel, the sector manager, and OLE as soon as possible to resolve the pending DSM event. vi) If the vessel retains a portion of the landings from a trip to be offloaded during a future landing event, the VTR for the trip on which the landings were caught must include those landings with the code for fish retained for future sale. The VTR for the subsequent trip, after which the retained landings are finally sold, must include the previously retained landings in addition to the current landings from trip. The previously retained landings must be identified by a unique code on the VTR. Landings will only count against ACE once.

HAIL. i) Transmission of all vessel hails must be either as an email via Vessel Monitoring System (VMS) or some other electronic method, as determined by the sector. In all instances hail notification must be immediately upon receipt from the vessel provided by either the sector manager (SM) or DSM vendor to NOAA Fisheries Office for Law Enforcement (OLE); the mechanism for hail notification must be detailed in the sector’s operations plan. ii) Prior to leaving port on a sector trip for which catch will count against sector annual catch entitlements (ACE), each sector vessel must hail trip start, meaning notify the SM and DSM vendor that the vessel is departing on a sector trip. The trip start hail must include vessel permit number, the trip ID# (which is the VTR number on the first VTR page used for that trip), and estimated trip duration. The DSM vendor must immediately send a confirmation to the vessel that the trip start hail was received; if the vessel does not receive confirmation within 10 minutes, the captain must contact the vendor to confirm the trip start hail via an independent backup system (e.g., a phone number) that must be set up by the DSM vendor. iii) At the appropriate time before landing (detailed below), the sector vessel must hail trip end to the DSM vendor. For all trips greater than 6 hours in length, and occurring more than 6 hours from port, vessels must hail trip end at least 6 hours in advance of landing. For trips less than 6 hours in length, length or occurring within 6 hours of port, the estimated time of arrival to port and time of offload will be provided in the trip start hail. The trip end hail notification time must will be defined in sent upon completion of the sector’s operations plan, after being agreed upon by the sector, the monitoring provider, and OLE. last tow/haul with required updated information The trip end hail must include the following: A) Permit number; B) Trip ID#; C) Specific offloading location(s): Dock/dealer, port/harbor, and state (for all dealers or facilities where the vessel intends to offload); D) Estimated landing time; E) Estimated offloading time; and F) Estimated weight of each species of fish being landed. iv) The DSM vendor must immediately send a confirmation to the vessel that the trip end hail was received. If the vessel does not receive confirmation prior to landing, the captain must use the backup system to contact the DSM vendor prior to landing. The DSM vendor must inform the vessel in the trip end hail confirmation (and no earlier) that: A) The vessel will have a dockside monitor (DM) or roving monitor (RM) present; or B) The vessel is issued a DSM waiver for the trip (meaning no DM or RM will be present to witness the offload). v) If the DM has an emergency and cannot meet the vessel as scheduled, the DSM vendor must notify the vessel, the sector manager, and OLE as soon as possible to resolve the pending DSM event. vi) If the vessel retains a portion of the landings from a trip to be offloaded during a future landing event, the VTR for the trip on which the landings were caught must include those landings with the code for fish retained for future sale. The VTR for the subsequent trip, after which the retained landings are finally sold, must include the previously retained landings in addition to the current landings from trip. The previously retained landings must be identified by a unique code on the VTR. Landings will only count against ACE once.