NR/L3/OPS/045/3.35
National Operating Procedure (NOP) 3.35: Managing the Files and Investigation of Signals Passed at Danger (SPAD) Events
active, Most Current
Buy Now
| Organization: | NR |
| Publication Date: | 2 September 2017 |
| Status: | active |
| Page Count: | 6 |
scope:
This procedure applies to:
a) all Category A SPADs occurring on Network Rail Managed Infrastructure where Network Rail is the lead investigator for the organisation.
b) all Category A SPAD incidents where Network Rail is designated as the lead organisation and the incident is initially categorised as a Category A SPAD and to comply with the requirements of RIS-3119-TOM.
PURPOSE
This National Operating Procedure provides:
a) the framework to set out the minimum requirements for the maintenance of investigation files relating to Category A SPADs, as required by NR/L1/OPS/010;
b) a process for confirming the categorisation of a SPAD incident initially categorised as a Category A SPAD where Network Rail is designated as the lead organisation.
Document History
NR/L3/OPS/045/3.35
September 2, 2017
National Operating Procedure (NOP) 3.35: Managing the Files and Investigation of Signals Passed at Danger (SPAD) Events
This procedure applies to:
a) all Category A SPADs occurring on Network Rail Managed Infrastructure where Network Rail is the lead investigator for the organisation.
b) all Category A SPAD...