Level Crossing Occurrence Sample Clauses

Level Crossing Occurrence. Any collision of a train or rolling stock with either a road vehicle, person, level crossing safety equipment or gate, or any other occurrence that compromises safety, at a level crossing. Includes: • Cases of road vehicles causing damage to gates, barriers or other equipment at level crossings; • Near miss incidents; • Any case of a train running onto a level crossing when not authorised to do so is reportable; • Any failure of equipment at a level crossing which could endanger users of the road or path crossing the railway. This includes ‘wrong-side’ failures of equipment (where equipment fails to a dangerous condition) whether or not any train or crossing user is involved at the time of failure; • Incidents which occur during periods of unusual operation are to be included, eg when an automatic crossing is operated manually. • Level crossing occurrences with Tramways where Trams operate over their exclusive right of way. Excludes: • Exclude suspected and attempted suicides from the count of level crossing fatalities and persons injured in level crossing occurrences. These are recorded as “suspected suicide”. • Excludes infrastructure irregularities such as broken rails, welds and bonds that result in the unnecessary operation of crossing protection equipment. (These are reported in infrastructure irregularities). • Roadways crossing tramways where tramways operate on roadways shared with road vehicles.
AutoNDA by SimpleDocs

Related to Level Crossing Occurrence

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

  • Reports of unusual occurrence The Contractor shall, during the Maintenance Period, prior to the close of each day, send to the Authority and the Authority’s Engineer, by facsimile or e- mail, a report stating accidents and unusual occurrences on the Project Highway relating to the safety and security of the Users and Project Highway. A monthly summary of such reports shall also be sent within 3 (three) business days of the closing of month. For the purposes of this Clause 15.4, accidents and unusual occurrences on the Project Highway shall include:

  • Developer Default Each of the following shall be an Event of Default by Developer:

  • Train Operator Events of Default The following are Train Operator Events of Default:

  • Excellent Above Average Satisfactory Needs Improvement Unsatisfactory 5 4 3 2 1 5. The instructor demonstrates knowledge of the subject matter.

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

  • Accidents and Dangerous Occurrences The Hirer must report all accidents involving injury to the public to a member of the Village Hall management committee as soon as possible and complete the relevant section in the Village Hall’s accident book. Any failure of equipment belonging to the Village Hall or brought in by the Hirer must also be reported as soon as possible. Certain types of accident or injury must be reported on a special form to the local authority. The Hall Secretary will give assistance in completing this form. This is in accordance with the Reporting of Injuries, Diseases and Dangerous Occurrences Regulations 1995 (RIDDOR).

  • OUTCOME IF GRANTEE CANNOT COMPLETE REQUIRED PERFORMANCE Unless otherwise specified in this Statement of Work, if Grantee cannot complete or otherwise comply with a requirement included in this Statement of Work, HHSC, at its sole discretion, may impose remedies or sanctions outlined under Contract Attachment C, Local Mental Health Authority Special Conditions, Section 7.09 (Remedies and Sanctions).

  • Supervisory Control and Data Acquisition (SCADA) Capability The wind plant shall provide SCADA capability to transmit data and receive instructions from the ISO and/or the Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected, as applicable, to protect system reliability. The Connecting Transmission Owner for the Transmission District to which the wind generating plant will be interconnected and the wind plant Developer shall determine what SCADA information is essential for the proposed wind plant, taking into account the size of the plant and its characteristics, location, and importance in maintaining generation resource adequacy and transmission system reliability in its area.

  • Termination for Concessionaire Default 37.1.1 Save as otherwise provided in this Agreement, in the event that any of the defaults specified below shall have occurred, and the Concessionaire fails to cure the default within the Cure Period set forth below, or where no Cure Period is specified, then within a Cure Period of 60 (sixty) days, the Concessionaire shall be deemed to be in default of this Agreement (the “Concessionaire Default”), unless the default has occurred solely as a result of any breach of this Agreement by the Authority or due to Force Majeure. The defaults referred to herein shall include:

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