Search results

The affected train was the FCC service which the alarm was pulled on too. It also terminated at Three Bridges. Assume the brakes applied during the alarm activation couldnt be turned off. The affected train is now running ECS to Three Bridges, last reported 71 minutes late from its normal...

http://www.bbc.co.uk/news/uk-england-wiltshire-28871327 6 injured - one carriage overturned.

http://www.realtimetrains.co.uk/train/H37917/2014/08/20/advanced - The service which has caused all these issues, looking at its timings - looks as if it failed a couple of times after getting going again. Now on the move again though, 4 hours down approaching Basingstoke.

Service involved is 1M30 0911 Reading to Manchester Piccadilly, which was 20 down at Lea Hall when the incident happened. Thoughts to those involved.

Correct, most cases of Code Red and in all cases of Code Black where possible. Tonight was Code Yellow, minor delays but services could run. The GatEx has made extra stops during a Yellow in the past, all depends on the time of disruption and what services are running. The incident at Clapham...

Exactly what i was thinking. Also, are Potters Bar and Kings Cross usually staffed at 3AM in the morning ?

Well, they could find out in a civilised way whilst actually caring for a member of staff which had been assaulted, but then some people dont actually care these days and want their train to run regardless. Remember, in this day and age, when a person gets hit by a train, you will always...

And thats a bad thing ? The important thing is that the person would have been freed.

Easy reason why this is the case - the 2-car DMU would be overwhelmed and would almost certainly leave people behind at Bedford and Bletchley and due to the services leaving Full and Standing, pax at stations along the route would be unable to board. Lengthening services wouldnt be possible...

They evacuated some and attempted to move it of course, it isnt as if they simply havent bothered. Pretty much everything that went wrong, happened.

UF-DF-US-DS A layout like the above would be preferable, whilst one set of lines can be closed for works, a service can still operate on the other lines.

Probably, yes. Would have thought it could be a panto fault on the 390. Expect this to be in the media tomorrow.....of course blaming the TOC for everything even if it wasnt actually their fault. Also expect the passengers who decided to trespass on the tracks to be portrayed as saints too....

NRE are saying it is an overhead wire problem as well.......

Reports that passengers have opened the train doors in order to get air, causing police to be called and rescue attempts halted in case passengers decide to go walkabout. Also seen one report on Twitter a loco used to try and rescue the unit was unable to do so.

Thinking about the layout of the station, it was probably used to send goods down to the concourse/ticket office level as at Haywards Heath, the platforms are on top of the subway and ticket office - so putting 2 and 2 together, id say it was for that.

I assume you have thought about the customers of the next trains which are due, which cant come in as you are holding a train. Also the customers at the next stations which will be delayed waiting and then finding out they cant actually get on board and having to wait even longer. Also, if you...

With Code Black disruption being declared, can you really expect NRE to be 100% accurate in situations like this ? I guess you havent learnt from the past posts you have made about NRE in disruption then which is to simply not bother with it and follow station/staff advice or check what TOCs are...

But dont let that get in the way of a rant :roll:

Well, 2 other finish times have been missed - so who knows !! Should have been completed last October and then last April. Pretty sure no new date has been set yet, which is probably for the best due to the delay.

A 377/7 has failed this afternoon working 2O51 1513 Milton Keynes Central to East Croydon (http://www.realtimetrains.co.uk/train/W61941/2014/07/21/advanced). It was rescued by another 377, which had to be terminated at Tring.