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/CS/OPS/010 ISSUE 9

Signals Passed at Danger and Signal Reversions

inactive
Organization: NR
Publication Date: 1 August 2005
Status: inactive
Page Count: 29
scope:

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 where a signal passed at danger on another party's infrastructure could lead to an unauthorised movement entering onto Network Rail's Controlled Infrastructure.

Purpose

The purpose of this procedure is, in accordance with the requirements applicable to an Infrastructure Controller in Railway Group Standard GO/RT3252, to provide a consistent and structured process for the immediate actions required in dealing with a Category A, B, C or D SPAD, gathering evidence following a SPAD incident, and subsequent management of SPAD issues within Network Rail and in conjunction with Train Operators. Signal reversions, not resulting in Category B SPADs, are also covered. This standard is supplemented by detailed procedures contained within the Control Manual, Investigators Manual, and Operations Manual.

Document History

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...
NR/CS/OPS/010 ISSUE 9
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