Line closed between Reading and Paddington 6 July 2022

[whole diary]

[IndustryInsider]

Always difficult to always make the best decision, or be able to advise people of the best decision.

Generally a fatality leads to the lines being shut for between 60-90 minutes afterwards.  Sometimes it’s a little quicker, and sometimes it takes a lot longer as on this occasion.  There were complications in this case that led to it taking so long which I won’t go in to.

Generally if it happens between Reading and Paddington, people will be advised to go via Waterloo or Marylebone.  That won’t always be the best advice, but as a general rule it’s better to stop crowds massing at Paddington/Reading waiting for the lines to reopen.  It was certainly the best advice on this particular sad occasion.

[bobm]

Quite a few West of England services were started from Reading using sets that had come up from the West but couldn’t continue to Paddington.

[Worcester_Passenger]

My other half was caught up in this on a journey across London and on to Worcester.

She reports that Paddington was not at its best. 

She rang me at 13:22 and I recommended going to Marylebone. She caught the 15:05 from there to Oxford. Oxford was just as disorganised. No trains up the Cotswold line (one had left 30 minutes earlier). She ended up coming home by way of Birmingham.

It would help if GWR^▸ (Great Western Railway) had a Plan that they worked to when this happens.  Turning things round at Reading makes sense, but that doesn't seem to have been happening on the Cotswold line. I do hope that someone is reviewing the response.

[bobm]

From the reports I’ve seen I think it took longer to rescue the stricken train than first envisaged.  If it had been the usual 90 minutes the existing plans would have worked.  Sadly in this case it needed extra assistance from others outside the railway which took a while to summon and then work at the scene. 

It’s the longest time I’ve seen it take to clear the line after an incident of this time I can remember.

[Worcester_Passenger]

Wednesday July 20
From JourneyCheck:

Cancellations to services at Slough
Due to a person hit by a train at Slough some lines are blocked.
Train services running through this station will be cancelled, delayed or suspended. Disruption is expected until the end of the day.

Further Information
An update will follow within the next 2 hours.
If you hold a valid single, return, or weekly ticket, you will be able to claim compensation for delays of 15 minutes or more. Please keep your ticket and visit GWR^▸ (Great Western Railway).com/DelayRepay
Last Updated:20/07/2022 22:38

Lots of cancellations on JourneyCheck.

[a-driver]

Wednesday July 20
From JourneyCheck:

Cancellations to services at Slough
Due to a person hit by a train at Slough some lines are blocked.
Train services running through this station will be cancelled, delayed or suspended. Disruption is expected until the end of the day.

Further Information
An update will follow within the next 2 hours.
If you hold a valid single, return, or weekly ticket, you will be able to claim compensation for delays of 15 minutes or more. Please keep your ticket and visit GWR^▸ (Great Western Railway).com/DelayRepay
Last Updated:20/07/2022 22:38

Lots of cancellations on JourneyCheck.

BTP^▸ (British Transport Police) declared the incident suspicious so relief lines took about 90 minutes to get open. I believe the main lines are still shut as of 01:00 with nothing stopping at Slough.