Thames Valley infrastructure problems causing disruption elsewhere - 2018

[whole diary]

[JayMac]

Meanwhile...

From what I can gather from GWR^▸ (Great Western Railway)'s Twitter feed, for the past 30 minutes the IET^▸ (Intercity Express Train) on 1C27 1900 PAD^» (Paddington (London) - next trains)-BRI^» (Bristol Temple Meads - next trains) has been blocking the DM at TWY^▸ (Twyford station) (having made an extra stop there due to other cancellations) because of an apparent loss of power. RTT^» (Real Time Trains - website) and OTT^▸ (Open Train Times website) both appear to confirm that it's currently going nowhere.

Brakes stuck on and losing air.

Sounds familiar...

[JayMac]

On the move again at 2012 after a Train Management System reset*.



*Driver must have called the IET^▸ (Intercity Express Train) Crowd:

[paul7575]

I wonder if the references to the speed of “105 mph” are just based on the typical speed reached at that particular location if accelerating away from the buffers at Paddington?

Paul

[martyjon]

Meanwhile...

From what I can gather from GWR^▸ (Great Western Railway)'s Twitter feed, for the past 30 minutes the IET^▸ (Intercity Express Train) on 1C27 1900 PAD^» (Paddington (London) - next trains)-BRI^» (Bristol Temple Meads - next trains) has been blocking the DM at TWY^▸ (Twyford station) (having made an extra stop there due to other cancellations) because of an apparent loss of power. RTT^» (Real Time Trains - website) and OTT^▸ (Open Train Times website) both appear to confirm that it's currently going nowhere.

Computer says you should not have stopped 'ere.

[JayMac]

Something very wrong with the software if a Special Stop Order causes the train to dump its air.

[stuving]

Some speculation across rail related forums and social media that the pantograph was tied down at the head end and it was the elbow that raised. Either commanded or uncommanded. Speculated to have been left tied down after transit from the factory in Italy.

However, there is YouTube footage of 802016 running with pan up at Reading on 3rd October. 802016 has been in the UK^▸ (United Kingdom) since 28th August. Hard to believe the pantograph would still be in delivery tied down status.

More to the point, that video shows 802016 on its own. Most of the 802s I've seen on test have been paired, and it was just possible a pantograph on an inner end might have been left retained. But the likelihood of it doing only one move A-B on the 3rd and otherwise always being paired when using 25kV is so low it can be deleted from the list.

There's an "after" picture of the pantograph on RailUKForums, showing the head end badly mangled, but I can't see the arm in that. That would have been the front end at the time of the incident, so unless it left Paddington on diesel (why?) it would have been raised already (at least normally, I'm sure the rear one can be raised if you want to). None of which really fits the explanations currently offered.

[Incider]

[quote author=bignosemac link=topic=14689.msg249138#msg249138 date=1539888667

There's also some contention over the speed the train was running at. Could an 802 have reached 105mph on diesel by the time it was at the incident location? [/quote]

Whether it could or not, it hadn’t reached 105mph.

Edit - there appears to have been some quoting slip of the fingers - hope I have corrected who said what now - Grahame

[IndustryInsider]

But it was going at way more than 20mph which would be the maximum speed to pan up at that location.

[Incider]

But it was going at way more than 20mph which would be the maximum speed to pan up at that location.

It was, but not the widely publicised 105mph. Closer to half that.

[Electric train]

There's also some contention over the speed the train was running at. Could an 802 have reached 105mph on diesel by the time it was at the incident location?

Whether it could or not, it hadn’t reached 105mph.

I've been miss quoted!!!!!

Edit - looks like there have indeed been some quoting errors - which I have tried to fix - Grahame
(Goodness only knows if I have got them right now - but at least I have planted a flag of caution for future readers!

Thanks Graham 

[TaplowGreen]

Here we go again.......

Cancellations to services between London Paddington and Slough
Due to damage to the overhead electric wires between London Paddington and Slough all lines are blocked.
Impact:
Train services running to and from these stations may be cancelled, delayed by up to 60 minutes or revised. Disruption is expected until 18:00 28/10.
Customer Advice:
Due to damage to the overhead electric wires between London Paddington and Reading all lines are closed.
Train services running to and from these stations may be cancelled, delayed or revised. Disruption is expected until the end of the day.
Customer Advice
Since around 11:30am Sunday morning,virtually no train service has been able to operate between London Paddington and Reading in either direction owing to the damage to the overhead wires. This has led to widespread disruption with trains initially stranded in various.

The position this afternoon is that all lines remain closed between London Paddington and Slough

[bobm]

Reports of some passengers taking it upon themselves to operate emergency door releases and spilling out onto the track near Ladbroke Grove.

[Timmer]

Not going to help the situation that one option for those travelling to the SW today isn’t easily available in that Waterloo to Exeter services are starting/terminating at Basingstoke due to engineering work in the Woking area.

My wife was due to travel home from London this afternoon but we’ve decided she is better off staying put and travel tomorrow. Someone reporting on uk Rail Forums that Waterloo is already busy with those arriving from Paddington.

[Timmer]

GWR^▸ (Great Western Railway) now reporting signalling problems at Bristol Parkway now. For those who have to travel this afternoon I wish you all the best, it’s not looking good.

[Worcester_Passenger]

Not going to help the situation that one option for those travelling to the SW today isn’t easily available in that Waterloo to Exeter services are starting/terminating at Basingstoke due to engineering work in the Woking area.

Someone needs to tell GWR^▸ (Great Western Railway)'s Journeycheck team. It's currently saying

Customers travelling to destinations in Devon and Cornwall are advised to travel via London Waterloo either to Reading or via Salisbury to interchange with West Country services at Exeter St Davids.
An update will follow within the next 2 hours.
Last Updated:28/10/2018 13:41