Great Western Coffee Shop

As reported on Journey Check earlier today............


1C76 0822 London Paddington to Penzance (http://www.realtimetrains.co.uk/train/C46149/2018/08/12/advanced) didn't appear to fare too badly on just one (rear) engine. However, I thought that full-length HSTs running on one engine only were "not permitted to stop at Totnes" because of the likelihood of failing on the South Devon banks? Not only has this service stopped at Totnes, it appears to be travelling well into Cornwall.

One almost wonders if a travelling fitter has managed to coax some life out of 43022 and it hasn’t been reported.

Journeycheck probably wrong again.  This has remained unnoticed and uncorrected by GWR for over 2 years:

Planned engineering work will take place.
Between Twyford and Reading
From 00:01, Sunday 12 June 2016 to 08:10, Friday 12 June 2020.
Additional Information
Sunday until 0810 Buses will be replacing trains between Twyford and Reading.
Last Updated:25/04/2016 11:28

And only lost a further one minute on its schedule. I was on a full length HST which lost an engine, front power car, at Exminster and even with a non stop run through Newton Abbot only just struggled up Dainton but succumbed on Rattery even though we had a clear run through Totnes. We ran back to Totnes, wrong line, where an on board fitter managed to rig up a temporary wire fix whilst laying in the four foot under the front power car and hey presto when he extracted himself and instructed the driver to give it a go the power car leaped into action and when we got the road that service romped up Rattery like a racehorse that had stowed away as we passed Newton Abbot Racecourse. The fitter was from Maintrain Maintenance and I have seen him on a YouTube video connected to the group hoping to preserve an HST, the group that operates the prototype HST powercar. Well done that man on that occasion.

I have picked up from another Forum that this should not have appeared in the public domain, only within the industry.

It looked like it shouldn’t have been there. This has happened a couple of times on journeycheck.