Great Western Coffee Shop

Journey by Journey => London to Reading => Topic started by: SandTEngineer on August 10, 2018, 10:51:33



Title: 1Y35 0827 Heathrow T5 to Paddington 10/08/2018
Post by: SandTEngineer on August 10, 2018, 10:51:33
Today 10/08/2018. 1Y35 (0827 Heathrow T5 to Paddington) sat down on the Up Main just west of Southall at 0838. Still there at 1040. At least they can run around it via the Down Main. Hope they don't leave it too long before they consider a controlled evacuation...


Title: Re: 1Y35 0827 Heathrow T5 to Paddington 10/08/2018
Post by: martyjon on August 10, 2018, 11:13:09
Today 10/08/2018. 1Y35 (0827 Heathrow T5 to Paddington) sat down on the Up Main just west of Southall at 0838. Still there at 1040. At least they can run around it via the Down Main. Hope they don't leave it too long before they consider a controlled evacuation...

On up relief at Ealing Broadway @ 11:12


Title: Re: 1Y35 0827 Heathrow T5 to Paddington 10/08/2018
Post by: SandTEngineer on August 10, 2018, 11:34:10
Today 10/08/2018. 1Y35 (0827 Heathrow T5 to Paddington) sat down on the Up Main just west of Southall at 0838. Still there at 1040. At least they can run around it via the Down Main. Hope they don't leave it too long before they consider a controlled evacuation...

On up relief at Ealing Broadway @ 11:12

Now stalled there at 1133 with a line of seven trains behind it.... :P


Title: Re: 1Y35 0827 Heathrow T5 to Paddington 10/08/2018
Post by: martyjon on August 10, 2018, 11:55:48
Today 10/08/2018. 1Y35 (0827 Heathrow T5 to Paddington) sat down on the Up Main just west of Southall at 0838. Still there at 1040. At least they can run around it via the Down Main. Hope they don't leave it too long before they consider a controlled evacuation...

On up relief at Ealing Broadway @ 11:12

Still there @ 11:42 with 5G29 - 2P31 - 2Y22 - 2P32 - 9P23 all lined up behind it on the relief line with approaching trains being switched to up main line at Southall West.


Title: Re: 1Y35 0827 Heathrow T5 to Paddington 10/08/2018
Post by: martyjon on August 10, 2018, 12:03:37
Today 10/08/2018. 1Y35 (0827 Heathrow T5 to Paddington) sat down on the Up Main just west of Southall at 0838. Still there at 1040. At least they can run around it via the Down Main. Hope they don't leave it too long before they consider a controlled evacuation...

On up relief at Ealing Broadway @ 11:12

Still there @ 11:42 with 5G29 - 2P31 - 2Y22 - 2P32 - 9P23 all lined up behind it on the relief line with approaching trains being switched to up main line at Southall West.

Off up relief into HEX Depot @ 12:00.


Title: Re: 1Y35 0827 Heathrow T5 to Paddington 10/08/2018
Post by: SandTEngineer on August 10, 2018, 12:59:41
I'd like to see the delay minutes for that lot (at the end of the day of course) :P


Title: Re: 1Y35 0827 Heathrow T5 to Paddington 10/08/2018
Post by: Gordon the Blue Engine on August 10, 2018, 17:00:58
Assuming that there was no mechanical reason why this train could not be moved (eg damage to running gear), it is pathetic that Network Rail, as the infrastructure manager, was unable to get this train moved for over 2 hours.

It was sitting on the Up Main approaching Paddington in the morning rush hour causing huge disruption.  It was within a few miles of its depot.  Potential rescue trains (ie another emu or a loco) were available.

We’ve had this before, eg there was an HST just outside Paddington a few months ago.  It is inevitable that trains sometimes fail, but the railway seems to lack the ability to clear them off the main line within a reasonable time. 

Whether this is a consequence of modern signalling systems, or a lack of knowledge of how to get a rescue train up to a failed train, or risk-averse managers I don’t know.  But NR and the TOCs need to get a plan together to ensure that failed trains are rescued in much less than 2 hours.


Title: Re: 1Y35 0827 Heathrow T5 to Paddington 10/08/2018
Post by: CJB666 on August 10, 2018, 22:59:47
And what about all the intending airline pax. on Pad. to T5 HEX's who missed their flights with consequent missed connection, hotels, events, cruises, etc.?

And if the Central to / from T5 Shuttles failed to turn up what arrangements did Heathrow make to get pax. between Terminals? Likely nothing.

GWR / HEX / TfL seem collectively incapable of handling such frequent disruptions.   


Title: Re: 1Y35 0827 Heathrow T5 to Paddington 10/08/2018
Post by: JayMac on August 10, 2018, 23:54:34
And what about all the intending airline pax. on Pad. to T5 HEX's who missed their flights with consequent missed connection, hotels, events, cruises, etc.?

And if the Central to / from T5 Shuttles failed to turn up what arrangements did Heathrow make to get pax. between Terminals? Likely nothing.

GWR / HEX / TfL seem collectively incapable of handling such frequent disruptions.   

Services to Heathrow were relatively unaffected. A handful of cancellations reducing the service to half hourly at worst. I very much doubt anyone missed a flight because HEx was briefly half hourly mid morning.


Title: Re: 1Y35 0827 Heathrow T5 to Paddington 10/08/2018
Post by: Adelante_CCT on August 11, 2018, 07:54:43
Bnm is correct, the gap between arrivals at T5 did not exceed 33 minutes. Those on XR wishing to catch the 11:54 from Hayes would have been delayed by 1 hour. Anyone arriving 2-3 hours before flight would not have been affected.


Title: Re: 1Y35 0827 Heathrow T5 to Paddington 10/08/2018
Post by: SandTEngineer on August 11, 2018, 11:20:06

Whether this is a consequence of modern signalling systems, or a lack of knowledge of how to get a rescue train up to a failed train, or risk-averse managers I don’t know.  But NR and the TOCs need to get a plan together to ensure that failed trains are rescued in much less than 2 hours.

We don't know what caused the problem so cannot speculate.  I'll ask in the WNXX Forum if anybody knows (quite a few insiders on there).


Title: Re: 1Y35 0827 Heathrow T5 to Paddington 10/08/2018
Post by: stuving on August 11, 2018, 11:33:04

Whether this is a consequence of modern signalling systems, or a lack of knowledge of how to get a rescue train up to a failed train, or risk-averse managers I don’t know.  But NR and the TOCs need to get a plan together to ensure that failed trains are rescued in much less than 2 hours.

We don't know what caused the problem so cannot speculate.  I'll ask in the WNXX Forum if anybody knows (quite a few insiders on there).

The knock-on cancellations due to this were tagged in RTT with "This service was cancelled throughout due to a problem with the brakes (MN).". So that was, presumably, what was recorded when 1Y35 called in sick.



This page is printed from the "Coffee Shop" forum at http://gwr.passenger.chat which is provided by a customer of Great Western Railway. Views expressed are those of the individual posters concerned. Visit www.gwr.com for the official Great Western Railway website. Please contact the administrators of this site if you feel that content provided contravenes our posting rules ( see http://railcustomer.info/1761 ). The forum is hosted by Well House Consultants - http://www.wellho.net