Upcoming Games

(UTC times)


Full list
Add a game

Upcoming Events

No events to display

Jubilee Neasden SCC

You are here: Home > Forum > Miscellaneous > The real thing (signalling) > Jubilee Neasden SCC

Page 1 of 1

Jubilee Neasden SCC 30/10/2015 at 08:48 #77343
HeadController
Avatar
33 posts
I am hoping someone can help re the Jubilee line. When Neasden SCC opened it controlled the extension from Green Park? to Stratford I have been told that it also controlled the rest of the line before TBTC all be it via an overlay control system or is this not the case, if so did it take on the existing line when it went TBTC in stages?
Log in to reply
Jubilee Neasden SCC 30/10/2015 at 11:20 #77345
Harsig
Avatar
16 posts
When Neasden SCC opened it controlled the signalling only on the extension, Green Park (exclusive) to Stratford. The Jubilee Line controllers moved from Baker Street to Neasden immediately but signalling control of the Charing Cross to Stanmore section remained at Baker St.
The new junction at Green Park was signalled in a similar fashion to the extension (a Westrace interlocking) and control of this was given to Baker St SCC. All the Westrace interlockings had a backup control system and these were all located at Neasden (including the one for Green Park) Thus it was possible for control of the signalling at Green Park only to be transferred back and forth between Neasden and Baker St. In later years, at the request of Tubelines Green Park spent most of its life controlled from Neasden, where they simply left the signals set in automatic operation for the extension.
Under TBTC Neasden finally gained control of the signalling for the whole Jubilee. The final transfer was done in two stages: Charing Cross to Dollis Hill and later Dollis Hill to Stanmore.

Log in to reply
The following users said thank you: UKTrainMan, Guts, GeoffM
Jubilee Neasden SCC 30/10/2015 at 12:42 #77346
HeadController
Avatar
33 posts
Harsig
Thanks for the detailed reply I think it was the moving of the line control facilities that caused the confusion together with the back up for the extension.

Log in to reply