• Our new ticketing site is now live! Using either this or the original site (both powered by TrainSplit) helps support the running of the forum with every ticket purchase! Find out more and ask any questions/give us feedback in this thread!

Cambridge Problems - 26/02/11

Status
Not open for further replies.

suffolk_lp3

Member
Joined
22 Jan 2011
Messages
32
The bad luck strikes again...

When I got to Kings Cross at 20:30 last night (Saturday) I was greeted with a message that stated previous signalling problems in the Cambridge area had been resolved... or so I thought.

After waiting an additional 15 or so minutes, the platform for my 20:45 FCC London Kings Cross - Cambridge service was announced. Took another 6-8 minutes past original departure before we left...

Now everything seemed to be fine till we got to Royston. Must have been around 21:20 now. Where after a good 15 minutes in Platform 2 we were told that Cambridge signal box had said due to a fire, no more trains would be going northbound all night, and that this train was being terminated at Royston.

Cue a massive offloading to the station car park to look for buses. 2 buses turned up (that I saw) and for 45 minutes I kept going from the train to the car park as I was a group leader of 6 other agitated teens...

Then at around 22:15 we were told the issue had been resolved at we'd be terminated again at Cambridge (not the original destination of Kings Lynn).

My question is - where these 2 seperate issues (the cleared one I saw at Kings Cross + the new one I was caught up in at Royston) or where they linked?
 
Sponsor Post - registered members do not see these adverts; click here to register, or click here to log in
R

RailUK Forums

GB

Established Member
Joined
16 Nov 2008
Messages
6,553
Location
Somewhere
The signalling system at Cambridge totally failed at about 1750 and was mostly restored to normal by 1950.

It then failed again at 2110 and things did not starting coming back online untill about 2200.

So one incident at two different times.
 
Status
Not open for further replies.

Top