Collision or Upset Sample Clauses

Collision or Upset. We cover loss or damage only while the mobile home is being transported or towed by a vehicle operated in the business of a person licensed as a common carrier.
Sample 1Sample 2Sample 3
Collision or Upset. This Section covers loss of or damage to an automobile caused by accidental collision of the automobile with another object, or by upset, provided always that the deductible specified in the Schedule shall be deducted from the amount of each and every loss or damage to each automobile.
Sample 1Sample 2
Collision or Upset. If, while an Employee uses an automobile on an Employer assignment on which the use of the automobile was specifically authorized by the Employer, such automobile is damaged by collision or upset or other cause, the Employer will either: 18.2.4.1 if the automobile is not otherwise insured against such damage, reimburse the Employee to the extent of the actual cost of repairing such automobile or the actual cash value of the automobile, whichever is the lesser, or 18.2.4.2 if such automobile is otherwise insured against such damage, reimburse the Employee to the extent of the amount of any deductible imposed by the insurance carrier in the settlement of the claim.
Sample 1Sample 2
Collision or Upset. This Section covers loss of or damage to a Recreational Vehicle caused by accidental collision of the Recreational Vehicle with another object, or by upset, provided always that the deductible specified in the Schedule shall be deducted from the amount of each and every loss or damage to each Recreational Vehicle.
Sample 1

Related to Collision or Upset

  • Name Collision Occurrence Management 6.1. No-­‐Activation Period. Registry Operator shall not activate any names in the DNS zone for the Registry TLD (except for "NIC") until at least 120 calendar days after the effective date of this agreement. Registry Operator may allocate names (subject to subsection 6.2 below) during this period only if Registry Operator causes registrants to be clearly informed of the inability to activate names until the No-­‐Activation Period ends.

  • Name Collision Occurrence Assessment 6.2.1 Registry Operator shall not activate any names in the DNS zone for the Registry TLD except in compliance with a Name Collision Occurrence Assessment provided by ICANN regarding the Registry TLD. Registry Operator will either (A) implement the mitigation measures described in its Name Collision Occurrence Assessment before activating any second-­‐level domain name, or (B) block those second-­‐level domain names for which the mitigation measures as described in the Name Collision Occurrence Assessment have not been implemented and proceed with activating names that are not listed in the Assessment. 6.2.2 Notwithstanding subsection 6.2.1, Registry Operator may proceed with activation of names in the DNS zone without implementation of the measures set forth in Section 6.2.1 only if (A) ICANN determines that the Registry TLD is eligible for this alternative path to activation of names; and (B) Registry Operator blocks all second-­‐level domain names identified by ICANN and set forth at <xxxx://xxxxxxxx.xxxxx.xxx/en/announcements-­‐and-­‐ media/announcement-­‐2-­‐17nov13-­‐en> as such list may be modified by ICANN from time to time. Registry Operator may activate names pursuant to this subsection and later activate names pursuant to subsection 6.2.1. 6.2.3 The sets of names subject to mitigation or blocking pursuant to Sections 6.2.1 and 6.2.2 will be based on ICANN analysis of DNS information including "Day in the Life of the Internet" data maintained by the DNS Operations, Analysis, and Research Center (DNS-­‐OARC) <xxxxx://xxx.xxx-­‐xxxx.xxx/xxxx/xxxx/xxxx>. 6.2.4 Registry Operator may participate in the development by the ICANN community of a process for determining whether and how these blocked names may be released. 6.2.5 If ICANN determines that the TLD is ineligible for the alternative path to activation of names, ICANN may elect not to delegate the TLD pending completion of the final Name Collision Occurrence Assessment for the TLD, and Registry Operator’s completion of all required mitigation measures. Registry Operator understands that the mitigation measures required by ICANN as a condition to activation of names in the DNS zone for the TLD may include, without limitation, mitigation measures such as those described in Section 3.2 of the New gTLD Name Collision Occurrence Management Plan approved by the ICANN Board New gTLD Program Committee (NGPC) on 7 October 2013 as found at <xxxx://xxx.xxxxx.xxx/en/groups/board/documents/resolutions-­‐ new-­‐gtld-­‐annex-­‐1-­‐07oct13-­‐en.pdf>.

  • Name Collision Report Handling 6.3.1 During the first two years after delegation of the TLD, Registry Operator’s emergency operations department shall be available to receive reports, relayed by ICANN, alleging demonstrably severe harm from collisions with overlapping use of the names outside of the authoritative DNS. 6.3.2 Registry Operator shall develop an internal process for handling in an expedited manner reports received pursuant to subsection 6.3.1 under which Registry Operator may, to the extent necessary and appropriate, remove a recently activated name from the TLD zone for a period of up to two years in order to allow the affected party to make changes to its systems.

  • Outage Repair Standard In the event of an outage or trouble in any Service being provided by a Party hereunder, the Providing Party will follow Verizon’s standard procedures for isolating and clearing the outage or trouble.

  • Exclusion of Creditor Party liability No Creditor Party, and no receiver or manager appointed by the Security Trustee, shall have any liability to a Borrower or a Security Party: (a) for any loss caused by an exercise of rights under, or enforcement of a Security Interest created by, a Finance Document or by any failure or delay to exercise such a right or to enforce such a Security Interest; or (b) as mortgagee in possession or otherwise, for any income or principal amount which might have been produced by or realised from any asset comprised in such a Security Interest or for any reduction (however caused) in the value of such an asset, except that this does not exempt a Creditor Party or a receiver or manager from liability for losses shown to have been directly and mainly caused by the dishonesty or the wilful misconduct of such Creditor Party’s own officers and employees or (as the case may be) such receiver’s or manager’s own partners or employees.

  • Aircraft Liability (Additional requirement applicable for aerial photograph or contract involving any use of aircraft.)

  • Aircraft This peril includes self-propelled missiles and spacecraft.

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Freedom has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Freedom. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Freedom (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Freedom, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Freedom will then have the option of paying the one-time SC rates to place the Loop.

  • Engine A. Any internal repairs or replacement of internal components, or replacement of engine assembly.

  • Engines POSITION SERIAL NO. TOTAL HOURS TOTAL CYCLES HRS/CYCLES SINCE LAST SHOP VISIT Time Remaining to Next LIFE LIMITED PART REMOVAL PART NAME HOURS CYCLES MSN MSN