Final Deviation Check Sample Clauses

Final Deviation Check. In i. A deviating pilot shall check in with VIPS, or CRS if VIPS is not accessible, and indicate that he is positioned within 100 nautical miles, or at a distance as approved by his ACP, of the airport from which the first revenue flight will depart. This check in must occur as follows: (a) no later than 8 hours prior to showtime of a revenue flight that operates entirely within North America (i.e., Alaska, Canada, Mexico, 48-States, Caribbean and Puerto Rico); or (b) no later than 12 hours prior to showtime of a revenue flight that either takes off from, or lands in, a city outside North America. ii. For purposes of Section 8.C.1.d. (this paragraph) the showtime of a revenue flight shall be one hour prior to the scheduled departure of that flight. iii. The final deviation check-in may occur at the same time as the initial deviation check-in if the pilot is already in position for the scheduled revenue departure when he makes the initial deviation check-in. iv. If a final deviation check-in has not occurred as required, then prior to replacing the deviating pilot, CRS shall place three calls based on the following hierarchy. However, if time does not permit, CRS shall not be required to make these calls. (a) VIPS primary contact number.
AutoNDA by SimpleDocs
Final Deviation Check. In i. A deviating pilot shall check in with VIPS, or CRS if VIPS is not accessible, and indicate that the pilot is positioned within 100 nautical miles, or at a distance as approved by the pilot’s Fleet Captain (or designee), of the airport from which the first revenue flight will depart or at which the pilot’s standby period begins. This check in must occur: (a) no later than 8 hours prior to showtime of a revenue flight that operates entirely within North America (i.e., Alaska, Canada, Mexico, the contiguous 48 United States, Caribbean and Puerto Rico); (b) no later than 12 hours prior to showtime of a revenue flight that either takes off from, or lands in, a city outside North America or a standby period that did not require an intercontinental deadhead from the pilot’s base; or (c) for a revenue flight or standby period that required an intercontinental deadhead from the pilot’s base, no later than: (1) 18 hours prior to showtime of a revenue flight or commencement of the standby period; or (2) The scheduled arrival time of the Company scheduled deadhead at the location of the revenue flight or standby period (if less than 18 hours prior to the scheduled departure of the revenue flight or commencement of the standby period).

Related to Final Deviation Check

  • Agreement Deviation/Compliance Does the vendor agree with the language in the Vendor Agreement?

  • Solicitation Deviation/Compliance Does the vendor agree with the General Conditions Standard Terms and Conditions or Item Specifications listed in this proposal invitation? Yes

  • Exhibit D - Debarment Certification By signing and submitting this Contract, the Contractor is agreeing to abide by the debarment requirements as set out below.

  • Project Completion Report At the completion of construction and once a Project is placed in service, the Subrecipient must submit a Project Completion Report that includes the total number of units built and leased, affordable units built and leased, DR-MHP units built and leased, an accomplishment narrative, and the tenants names, demographics and income for each DR-MHP unit.

  • Escrow Format Specification Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Conformity Assessment Procedures 1. Each Party shall give positive consideration to accepting the results of conformity assessment procedures of other Parties, even where those procedures differ from its own, provided it is satisfied that those procedures offer an assurance of conformity with applicable technical regulations or standards equivalent to its own procedures. 2. Each Party shall seek to enhance the acceptance of the results of conformity assessment procedures conducted in the territories of other Parties with a view to increasing efficiency, avoiding duplication and ensuring cost effectiveness of the conformity assessments. In this regard, each Party may choose, depending on the situation of the Party and the specific sectors involved, a broad range of approaches. These may include but are not limited to: (a) recognition by a Party of the results of conformity assessments performed in the territory of another Party; (b) recognition of co-operative arrangements between accreditation bodies in the territories of the Parties; (c) mutual recognition of conformity assessment procedures conducted by bodies located in the territory of each Party; (d) accreditation of conformity assessment bodies in the territory of another Party; (e) use of existing regional and international multilateral recognition agreements and arrangements; (f) designating conformity assessment bodies located in the territory of another Party to perform conformity assessment; and (g) suppliers’ declaration of conformity. 3. Each Party shall exchange information with other Parties on its experience in the development and application of the approaches in Paragraph 2(a) to (g) and other appropriate approaches with a view to facilitating the acceptance of the results of conformity assessment procedures. 4. A Party shall, upon request of another Party, explain its reasons for not accepting the results of any conformity assessment procedure performed in the territory of that other Party.

  • Inspection Checklist (Check one)

  • 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.

  • Certificate of Analysis Seller shall provide a certificate of analysis and other documents as defined in the Quality Agreement for any Product to be released hereunder, in a form in accordance with the cGMPs and all other applicable Regulatory Requirements and Product Specifications and as shall be agreed upon by the parties. For any batch that initially failed to meet any Product Specification, the certificate of analysis shall document the exception. Products that do not meet dissolution specifications at USP Stage I and II testing shall not be accepted by Buyer (and such requirement shall be included in the Product Specifications/Quality Manual).

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!