UNLIMITED FREE
ACCESS
TO THE WORLD'S BEST IDEAS

SUBMIT
Already a GlobalSpec user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your GlobalSpec Experience

Finish!
Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

NR/L1/OPS/010

Signals Passed at Danger (SPAD) and Signal Reversions Affecting Trains

active, Most Current
Buy Now
Organization: NR
Publication Date: 7 September 2019
Status: active
Page Count: 22
scope:

This policy contains the requirements for Network Rail as an Infrastructure Manager for managing movements:

a) resulting in a SPAD or signal reversion on Network Rail Managed Infrastructure; and

b) on another party's infrastructure which leads or may lead to a SPAD when entering onto Network Rail's Managed Infrastructure.

The policy details the:

a) actions required when dealing with

    • Signals or End of Authority Passed at Danger (SPAD); and

    • Signal Reversions.

b) subsequent management of such unauthorised movements and signal reversion incidents within Network Rail and in conjunction with Railway Undertakings.

This standard is supplemented by functional procedures, which detail the requirements and responsibilities for the reporting of event data and subsequent actions.

Purpose

The purpose of this standard is, in accordance with the requirements applicable to an Infrastructure Manager, to provide a consistent and structured process for the immediate actions required in dealing with SPADs or Movement Authority's passed without authority, gathering evidence following a SPAD incident and subsequent management of SPAD issues within Network Rail and in conjunction with Railway Undertakings.

This standard is supplemented by functional procedures, which detail the requirements and responsibilities for the reporting of event data and subsequent actions.

Document History

NR/L1/OPS/010
September 7, 2019
Signals Passed at Danger (SPAD) and Signal Reversions Affecting Trains
This policy contains the requirements for Network Rail as an Infrastructure Manager for managing movements: a) resulting in a SPAD or signal reversion on Network Rail Managed Infrastructure; and b)...
March 6, 2010
Signals Passed at Danger and Signal Reversions
This standard contains the mandatory requirements as an Infrastructure Manager for managing SPAD and signal reversion events on Network Rail Managed Infrastructure, or where a signal passed at danger...
August 26, 2008
Signals Passed at Danger and Signal Reversions
This standard contains the mandatory requirements as an Infrastructure Manager for managing SPAD and signal reversion events on Network Rail Managed Infrastructure, or where a signal passed at danger...
June 1, 2006
Signals Passed at Danger and Signal Reversions
This Company Standard contains the mandatory requirements as an Infrastructure Controller for managing SPAD and signal reversion events on Network Rail Controlled Infrastructure, or where a signal...
August 1, 2005
Signals Passed at Danger and Signal Reversions
This standard contains the mandatory requirements as an Infrastructure Controller for managing signal passed at danger (SPAD) and signal reversion events on Network Rail Controlled Infrastructure, or...
October 1, 2004
Signals Passed at Danger and Signal Reversions
This standard contains the mandatory requirements as an Infrastructure Controller for managing signal passed at danger (SPAD) and signal reversion events on Network Rail Controlled Infrastructure, or...
April 1, 2004
Category A Signals Passed at Danger
This procedure shall apply when a signal has been passed at danger without authority (Category A) on Network Rail Controlled Infrastructure, or where a signal passed at danger could lead to an...
December 6, 2003
Category a Signals Passed at Danger
This procedure shall apply when a signal has been passed at danger without authority (Category A) on Network Rail Controlled Infrastructure, or where a signal passed at danger could lead to an...
September 1, 2002
Signals Passed at Danger
This procedure shall apply when a signal has been passed at danger without authority (Category A) on Railtrack Controlled Infrastructure, or where a signal passed at danger could lead to an...
February 1, 2001
Signals Passed at Danger
This procedure shall apply when a signal has been passed at danger without authority (Category A), on Railtrack controlled infrastructure, or where a signal passed at danger could lead to an...
December 1, 2000
Signals Passed at Danger
This procedure shall apply when a signal has been passed at danger without authority (Category A), on Railtrack controlled infrastructure, or where a signal passed at danger could lead to an...
November 1, 1999
Signals Passed at Danger
This procedure shall apply when a signal has been passed at danger without authority (Category A), on Railtrack controlled infrastructure, or where a signal passed at danger could lead to an...
July 1, 1996
Signals Passed at Danger
This procedure shall apply in all instances of a signal being passed at danger without authority (category A), on Railtrack controlled infrastructure or where a signal passed at danger could lead to...

References

Advertisement