Ordinance On The Transmission Of Data To The Traffic Agency On Accidents, Incidents And Safety Irregularities

Original Language Title: Bekendtgørelse om indberetning af data til Trafikstyrelsen vedrørende ulykker, hændelser og sikkerhedsmæssige uregelmæssigheder

Subscribe to a Global-Regulation Premium Membership Today!

Key Benefits:

Subscribe Now for only USD$20 per month, or Get a Day Pass for only USD$4.99.
Overview (Table of Contents)

Appendix 1

Appendix 2

Appendix 3

Appendix 4

Annunciation of data reporting to Traffic Management in relation to accidents, incidents and security irregularities

In accordance with section 21 h, section 21 l, paragraph 1.  6, section 21 p, paragraph.  3, and section 22 (3).  6, in the law of rail, cf. Law Order no. 567 of 9. June 2008, according to section 24 a :

Scope and Definitions

Section 1. Traffic Management driver and maintain a database relating to railway undertakings and railway infrastructure managers reports on accidents, incidents and safety irregularities in the railway area for the preventive use of the management ; rail safety work, etc.

Stk.  2. Railway undertakings and railway infrastructure managers have a duty to report the accidents, incidents and safety irregularities that the undertakings have been implicated in the railway sector to the accident referred to in paragraph 1.  1 mentioned database.

Stk.  3. Companies that do not operate commercial railway operations but carry out a limited passenger transport by rail and coach (vintage), has a duty to report the accidents, incidents and safety ; Irregularities have been implicated in the railway sector to the one referred to in paragraph 1.  1 mentioned database.

Stk.  4. People employed in railway undertakings and railway infrastructure managers may report security irregularities to Traffic Management.

Stk.  5. People who perform security-related functions in the railway area and not employed in railway undertakings and railway infrastructure managers may also report security irregularities to the Traffic Management Board.

§ 2. The database and the electronic reported information are not available to the public, cf. Section 5 (5).  2, in the disclosure law.

section 3. For Railway means any public or private company whose main activity is in the carriage of goods or Passenger carriage by rail and which is required to ensure the traction of the traction, including undertakings that only ensure the traction of the traction.

Stk.  2. For Rail Infrastructure Manager , any public or private enterprise whose main activity is the operation of railway infrastructure with related regulatory and security systems and the allocation of infrastructure capacity.

Stk.  3. When accident is understood an unwanted or unintended event or a specific chain of events that have harmful effects. This is also referred to in Annex 1

Stk.  4. The event means any other parenting other than an accident associated with Rail Operations,1) , and which affects safety ; for the railway operation. This is also referred to in Annex 1

Stk.  5. For security irregularities , an event in the railway area means that there has been no accident or incident but which could have been relevant to rail safety. The

Report

Section 4. Railway undertakings, railway infrastructure managers and veterans shall be referred to the latest by 1. March each year report accidents, incidents and safety irregularities to the Traffic Management Board for the preceding calendar year, cf. Section 1 (1).  2 and 3.

Stk.  2. The report shall be subdivided into the categories referred to in Annex 1 in the notice referred to in Annex 1.

section 5. The report of the data pursuant to section 4 shall be made electronically. The report shall be made by either completing an electronic copy of the security database of the Traffic Management Database or by transferring data from the company's own database in a format corresponding to the Traffic Management database.

Stk.  2. For the requirements for the information to be provided by companies for each accident, event or security irregularity, reference is made to Appendix 2.

Stk.  3. The company ' s reports must not in addition to the information listed in Appendix 2 may include personal information.

Stk.  4. The Traffic Management Board shall draw up a guide for the procedure for reporting, including information about the format of the database and so on

Stk.  5. Veteranlanes can also use the form in Appendix 4 that is found on the Trailer page.

§ 6. People, cf. Section 1 (1).  4 and 5 shall, when reporting of security irregularities to the Traffic Management Board, use the form in Annex 3. The form is found on the Traffic Management Home page and can be submitted to the Traffic Management Board either electronically or with common mail.

Strain and entry into force

section 7. Inherit of the provision in section 4 (4).  1 may be punished by fine.

Stk.  2. Companies can be imposed on them. (legal persons) punishable by the rules of Chapter 5 of the Penal Code

§ 8. The announcement shall enter into force on the first of the 1. July 2008. As far as the reporting is concerned, the 1. In March 2009, this will be based on the period from 1. July to the 31. December 2008.

Stk.  At the same time, paragraph 10, paragraph 10, is repealed.  3, in the notice. 1169 of 29. December 1999, so that the report for the calendar year 2008 shall be made by 1. March 2009 and be based on the rules in section 10 (1).  3, in the notice. 1169 of 29. December 1999 for the period from 1. January 2008 to the 30th. June 2008.

Stk.  Paragraph 10 (3).  1, in the notice. 1169 of 29. December 1999 shall be repealed on 31. December 2008. However, the provision still applies to railway infrastructure managers up to 31.

Traffic Management for Railway and Skill, 25th. June 2008

Carsten Falcon Hansen

/ Leif Funch


Attachments 1

Categories of Accident and Events and Security Irregularities that are reported to Traffic Management.

Accidents :
-
Collision,1) including collision with objects
-
Tracking
-
Accidents in rail overruns2)
-
Persons injury3) as a result of rolling stock in motion, (accident in rail runs and suicides are not included)
-
Suicide and attempted suicide
-
rolling stock fire (high-end vandalism)
-
Accidents with dangerous goods (reported in accordance with the definition in RID)
-
Other
Events :
-
Rail breach
-
Solkurver
-
Signal error that can be executed for technical conditions
-
Signal Exit
-
Rolling and axles on rolling stock
-
Incident with dangerous goods (reported in accordance with RID)
Security irregularity :
-
Risk of personal effects caused by rolling stock in movement (suicide attempt is not included)
-
Brake technical errors
-
Irregularity in Rail Execution
-
Deformation of the tracks
-
Error when signaling, not technical conditions
-
Profile relationship (excluding personal injury due to rolling stock in movement)
-
Hefwork
-
Other
Accidents must be registered under the main accident category, although the consequences of a secondary accident are more extensive, for example. a fire followed by a discovery.
All incidents and safety irregularities must be reported. This includes both those resulting in an accident, and those that do not result in an accident. An accident shall be registered under the said categories of incidents or security irregularities, and the alleged accident shall be recorded in the above categories of accidents.
1) Jf. Impact in Directive 2004 /49/EC of the European Parliament and of the Council of 29. April 2004 on EU rail safety and amending Council Directive 95 /18/EC on the granting of licences to railway undertakings and Directive 2001 /14/EC on the allocation of railway infrastructure capacity and the levying of charges for use by the Member States ; rail infrastructure, as well as safety certification carried out by executive order. 38 of 23. January 2006 (Rail Safety Directive).
2) Jf. Rail Security Directive
3) Jf. personal accidents in the Rail Security Directive

Appendix 2

Information on incidents and incidents and security irregularities reported to the Traffic Management Board must include the following :

1.
Name of involved railway undertakings or infrastructure managers
2.
The date of the accident, event, or security irregularity
3.
The time of the accident, event, or security irregularity
4.
Site, including relationship matters for the event
5.
Run (trainset or Rank)
6.
Traffic Type
7.
Involved trains, including train number and point (*
)
8.
Accident, event or security irregularity indicated by category (Appendix 1.)
9.
Event descript* * *
10.
Consequences of the accident, (damage to people, financial cost) ***
11.
Reasons for the accident or event
12.
The company's recommendation for improvement as a result of the accident or event
* The information is reported to the extent that it is relevant for the individual accident, event or security irregularity.
** The description may contain only the necessary information and no direct personal information for such as names, personal numbers. equal.
*** This information is reported only by accident

Appendix 3

BL75_1.jpg Size : (593 X 82) BL75_2.jpg Size: (593 X 761)BL75_3.jpg Size : (593 X 779)


Appendix 4

BL75_4.jpg Size : (593 X 819) BL75_5.jpg Size: (593 X 735)BL75_5.jpg Size: (593 X 735)BL75_6.jpg Size : (593 X 797) BL75_7.jpg Size: (593 X 696)BL75_8.jpg Size: (593 X 696)

Officially Notes

1) Jf, the train operation of Directive 2004 /49/EC of the European Parliament and of the Council of 29. April 2004 on EU rail safety and amending Council Directive 95 /18/EC on the granting of licences to railway undertakings and Directive 2001 /14/EC on the allocation of railway infrastructure capacity and the levying of charges for use by the Member States ; rail infrastructure, as well as safety certification carried out by executive order. 38 of 23. January 2006 (Rail Safety Directive).

Editorial Note
  • Publication no. 646 of 25. June 2008 on the reporting of data to the Third Board of Trial for accidents, incidents and safety irregularities shall be applicable until 31. In December 2010, despite the fact that it is marked as historically in court information .dk.