Landing Port Exceptions Sample Clauses

Landing Port Exceptions. Participating Vessels may land at ports not listed in Exhibit FAnnual Catch Entitlement Monitoring Plan, on a temporary, case-by-case basis, subject to prior approval of Sector Manager, as provided by Exhibit EDockside Monitoring Plan.
AutoNDA by SimpleDocs
Landing Port Exceptions. Landings in ports other than those listed in Section 5.05 are permitted on a temporary, case-by-case basis, subject to prior approval of the Manager; provided, that the Manager determines that the excepted landing will not impair effective enforcement and monitoring of the Sector and this Agreement. Such exceptions may be granted in the sole discretion of the Manager. The Manager shall notify the Dockside Monitoring Vendor (“DMV”) of landing port exceptions in a manner and timeframe agreed upon by the DMV and Manager, and such agreement shall ensure compliance with the Sector’s Dockside Monitoring requirements. The Manager shall report to NMFS any landing port exceptions that are of a significant or prolonged nature. For the purposes of this paragraph, landing port exceptions that are of a significant or prolonged nature, would include, but not be limited to, more than two exceptions per month for a vessel, or if the timeframe for any such exception is greater than two days.
Landing Port Exceptions. 30 Landings in ports, remote or otherwise, other than those listed in Section 5.05 hereof are 31 permitted on a temporary, case-by-case basis, for the purpose of promoting safety at sea and 32 protecting vessel and crew. Should a Member need to enter port somewhere other than a 33 designated landing port, the Member shall contact the Manager through email or phone as soon 34 as it is safe to do so. The Manager shall notify NOAA fisheries via email of all landing port 35 exceptions, which would include but would not be limited to the number of landing port 36 exemptions granted to a vessel more than one time per month and the anticipated timeframe 37 for which landing port exemptions are to be granted if that timeframe is greater than two days, 38 including until further notice.
Landing Port Exceptions. Landings in ports other than those listed in Section 5.04 hereof are permitted on a temporary, case-by-case basis, subject to prior approval of the Manager; provided, that the Manager determines that the excepted landing will not impair effective enforcement and monitoring of the Sector and this Agreement. Such exceptions may be granted in the sole discretion of the Manager. The Manager shall report to NMFS any landing port exceptions within 24 hours of such exception being granted.
Landing Port Exceptions. Landings in ports other than those listed in 4 Section 5.06 are permitted on a temporary, case-by-case basis, subject to prior approval 5 of the Manager; provided, that the Manager determines that the excepted landing will not 6 impair effective enforcement and monitoring of the Sector and this Agreement. Such 7 exceptions may be granted at the discretion of the Manager with NMFS OLE approval of 8 the issue prompting the exemption request. Exemptions may be granted due to weather, 9 safety concerns, equipment malfunction, or family emergency. For the purposes of this 10 paragraph, landing port exceptions that are of a significant or prolonged nature, would 11 include, but not be limited to, more than two exceptions per month for a vessel, or if the 12 timeframe for any such exception is greater than two days.
Landing Port Exceptions. To promote safety at sea and ensure the safety of vessel and crew, certain circumstances beyond a vessel operators control may occasionally occur which require participating vessels to enter port somewhere other than the designated landing ports listed above. If a Tri State Sector participating vessel is required to enter port somewhere other than a designated landing port, then the vessel operator will notify the Sector Manager and the Dockside Monitoring Company by appropriate means as soon as it is safe to do so. Such circumstances include but are not limited to severe weather, mechanical failures, compromised hull integrity, instances of pump failures and danger of sinking, crew injury or life threatening illness and any other emergency situations that may arise. In the event of bad weather or other emergency that results in a participating vessel entering port without being able to give six hour notice prior to landing, the vessel will notify the sector manager and the Dockside monitoring company as soon as it is safe to do so. Such notification will include all required trip end hail information. Upon receiving such notification, the Dockside Monitoring Company will send the required confirmation and inform the vessel if it will have a dockside monitor or receive a waiver for the trip, and will also notify NMFS of the unexpected arrival in port. If assigned a Dockside monitor, then all participating vessels agree to not unload fish unless a Dockside Monitor is present. Further, the vessel owner will pay any additional costs for the required DM as may accrue as a result of invoking the landing port exception.
Landing Port Exceptions. Landings in ports other than those listed in Section 26 5.06 are permitted on a temporary, case-by-case basis, subject to prior approval of the Manager; 27 provided, that the Manager determines that the excepted landing will not impair effective 28 enforcement and monitoring of the Sector and this Agreement. Such exceptions may be granted 29 at the discretion of the Manager with NMFS OLE approval of the issue prompting the exemption 31 family emergency. For the purposes of this paragraph, landing port exceptions that are of a 32 significant or prolonged nature, would include, but not be limited to, more than two exceptions 33 per month for a vessel, or if the timeframe for any such exception is greater than two days.
AutoNDA by SimpleDocs

Related to Landing Port Exceptions

  • Agreement Exceptions/Deviations Explanation If the proposing Vendor desires to deviate form the Vendor Agreement language, all such deviations must be listed on this attribute, with complete and detailed conditions and information included. TIPS will consider any deviations in its proposal award decisions, and TIPS reserves the right to accept or reject any proposal based upon any deviations indicated below. In the absence of any deviation entry on this attribute, the proposer assures TIPS of their full compliance with the Vendor Agreement. No response

  • General Exceptions 1. For purposes of Chapter 2 (National Treatment and Market Access for Goods), Chapter 3 (Rules of Origin and Operational Procedures Related to Origin), Chapter 4 (Customs Procedures and Trade Facilitation), Chapter 5 (Trade Remedies), Chapter 6 (Sanitary and Phytosanitary Measures), Chapter 7 (Technical Barriers to Trade), Article XX of the GATT 1994 and its interpretative notes are incorporated into and made part of this Agreement, mutatis mutandis. The Parties understand that the measures referred to in Article XX(b) of the GATT 1994, as incorporated into this Agreement, can include any measure necessary to protect human, animal, or plant life or health, and that Article XX(g) of the GATT 1994 applies to measures relating to the conservation of any exhaustible natural resource. 2. For purposes of Chapter 8 (Trade in Services), Article XIV of the GATS (including its footnotes) is incorporated into and made part of this Agreement, mutatis mutandis. The Parties understand that the measures referred to in Article XIV(b) of the GATS, as incorporated into this Agreement, can include any measure necessary to protect human, animal, or plant life or health.

  • ADDITIONAL SPECIAL CONTRACT CONDITIONS A. Special Contract Conditions revisions: the corresponding subsections of the Special Contract Conditions referenced below are replaced in their entirety with the following:

  • Seller’s Conditions The obligations of Seller at the Closing are subject, at the option of Seller, to the satisfaction or waiver at or prior to the Closing of the following conditions precedent:

  • Exceptions Any other provision herein to the contrary notwithstanding, the Company shall not be obligated pursuant to the terms of this Agreement:

  • Training Conditions 3.1 The Trainee shall attend an approved training course or training program prescribed in the Training Agreement or as notified to the trainee by the relevant State or Territory Training Authority in accredited and relevant Traineeship Schemes.

  • Technical Objections No grievance shall be defeated merely because of a technical error, other than time limitations in the processing of the grievance through the grievance procedure. To this end, an arbitrator shall have the power to waive formal procedural irregularities in the processing of the grievance in order to determine the real matter in dispute.

  • Title Passage All right, title, and interest in and to any Included Timber shall remain in Forest Ser- vice until it has been cut, Scaled, removed from Sale Area or other authorized cutting area, and paid for, at which time title shall vest in Purchaser. For purposes of this Subsection, timber cut under cash deposit or pay- ment guarantee under B4.3 shall be considered to have been paid for. Title to any Included Timber that has been cut, Scaled, and paid for, but not removed from Sale Area or other authorized cutting area by Purchaser on or prior to Termination Date, shall remain in Forest Service.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • Solicitation Exceptions/Deviations Explanation If the bidder intends to deviate from the General Conditions Standard Terms and Conditions or Item Specifications listed in this proposal invitation, all such deviations must be listed on this attribute, with complete and detailed conditions and information included or attached. TIPS will consider any deviations in its proposal award decisions, and TIPS reserves the right to accept or reject any bid based upon any deviations indicated below or in any attachments or inclusions. In the absence of any deviation entry on this attribute, the proposer assures TIPS of their full compliance with the Standard Terms and Conditions, Item Specifications, and all other information contained in this Solicitation.

Time is Money Join Law Insider Premium to draft better contracts faster.