Cotswold Line - 2018 cancellation and amendments log

[whole diary]

[charles_uk]

The pattern that I'm seeing over the past month or so is of fewere cancellations, but a lot of late running, especially with down trains in the evening peak.

I'd like to propose the 17:22 Paddington - Hereford as being the least reliable train on the whole of GWR^▸ (Great Western Railway):

Mon Jun 25 : 40 late
Tue Jun 26 : 51 late
Wed Jun 27 : 27 late
Thu Jun 28 : 23 late
Fri Jun 29 : 23 late
Mon Jul 2 : 12 late
Tue Jul 3 : 68 late
Wed Jul 4 : 25 late
Thu Jul 5 : Operated non-stop between Oxford and Evesham - but still 19 late
Fri Jul 6 : Sorry - I don't have a record for this date
Mon Jul 9 - Fri Jul 20 : did not operate on account of the Oxford blockade
Mon Jul 23 : 71 late
Tue Jul 24 : 23 late
Wed Jul 25 : Cancelled Oxford - Hereford
Thu Jul 26 : 37 late
Fri Jul 27 : 47 late
Mon Jul 30 : 24 late
Tue Jul 31 : diverted via Stroud on account of a bridge bash near Evesham. 41 late
Wed Aug 1 : 20 late
Thu Aug 2 : 32 late
Fri Aug 3 : 39 late

Mon Aug 6 : 25 late
And for Tue Aug 7 : drumroll please,,,, just 12 late

8 Aug - 39 late
9 Aug - 37 late

[charles_uk]

15:22 London Paddington to Great Malvern due 17:58 will be terminated at Oxford.
It will no longer call at Hanborough, Charlbury, Kingham, Moreton-in-Marsh, Honeybourne, Evesham, Pershore, Worcester Shrub Hill, Worcester Foregate Street, Malvern Link and Great Malvern.
This is due to a shortage of train crew.
Last Updated:13/08/2018 16:00

and return 18:29 GMV:PAD^» (Paddington (London) - next trains) similarly affected.

Hopefully GWR^▸ (Great Western Railway) will managed to get the 15:50 Paddington to Moreton-in-Marsh beyond Oxford today...

[later]

I get to Oxford station just after 16:30 and there's an HST^▸ (High Speed Train) on platform 3. Presumably the 15:22 having decanted its passengers. No, it's the 15:22 ready to go through to Great Malvern after all. Fortunately, slightly late so I'm able to catch it.

[charles_uk]

Big problems at Worcester:

Delays to services between Worcester Shrub Hill and Oxford

Due to a fault with the signalling system at Worcester Shrub Hill all lines are blocked. Disruption is expected until 13:30 14/08.

Train services between Worcester Shrub Hill and Oxford may be delayed.


Delays to services between Worcester Shrub Hill and Hereford

Due to a fault with the signalling system at Worcester Shrub Hill all lines are blocked. Disruption is expected until 13:30 14/08.

Train services between Worcester Shrub Hill and Hereford may be delayed.

Last Updated:14/08/2018 13:11

I suspect knock-on disruption will run long into the afternoon which is now expected until "until 14:30".

[Witham Bobby]

12:00 Worcester Foregate Street to London Paddington due 14:27 has been delayed previously and is now 98 minutes late from Moreton-in-Marsh.
This is due to a fault with the signalling system earlier today.
Last Updated:14/08/2018 14:26[/i]

17:52 London Paddington to Worcester Shrub Hill due 20:06
17:52 London Paddington to Worcester Shrub Hill due 20:06 will be cancelled.
This is due to a shortage of train crew.
Last Updated:14/08/2018 13:56[/i]

Plenty disruption today

Noticed a couple of turbo units at Littleton and Badsey LC^▸ (Level Crossing) on both up and down services around the middle of the day today

[charles_uk]

A nice big hole in this morning's peak service:

05:28 Hereford to London Paddington due 08:28 will be diverted between Worcester Shrub Hill and Reading.
It will no longer call at Pershore, Evesham, Honeybourne, Moreton-in-Marsh, Charlbury, Hanborough and Oxford.
It is being delayed at Hereford.
This is due to a fault on this train.

07:10 Moreton-in-Marsh to London Paddington due 08:51 will be reinstated.
It will be started from Oxford.
It will no longer call at Moreton-in-Marsh, Kingham, Charlbury and Hanborough.
This is due to a fault on this train.

It'll be cosy on the following two coach Turbo which "will be started from Worcester Shrub Hill. It will no longer call at Worcester Foregate Street."

[Worcester_Passenger]

A nice big hole in this morning's peak service:

05:28 Hereford to London Paddington due 08:28 will be diverted between Worcester Shrub Hill and Reading.
It will no longer call at Pershore, Evesham, Honeybourne, Moreton-in-Marsh, Charlbury, Hanborough and Oxford.
It is being delayed at Hereford.
This is due to a fault on this train.

If there's a fault on the train, how does a diversion via Stroud help?

[fladpass]

I was wondering that. I saw that the service was 35 minutes late leaving Hereford - could the diversion have been to avoid fouling up other services on the single-track sections of the line?

[Worcester_Passenger]

Meanwhile, we have problems with signals:

09:54 Great Malvern to London Paddington due 12:28 has been delayed previously and is now 80 minutes late from Charlbury.
This is due to a fault with the signalling system.
Last Updated:16/08/2018 12:46

10:22 London Paddington to Hereford due 13:47 will be terminated at Worcester Shrub Hill.
This is due to a fault with the signalling system.
Last Updated:16/08/2018 12:24

11:20 London Paddington to Worcester Foregate Street due 13:44 will be terminated at Reading.
This is due to a fault with the signalling system.
Last Updated:16/08/2018 11:51

12:09 Hereford to London Paddington due 15:27 was terminated at Worcester Shrub Hill.
This is due to a fault with the signalling system.
Last Updated:16/08/2018 13:01

13:55 Worcester Foregate Street to London Paddington due 16:31 will be started from Reading.
This is due to a fault with the signalling system.
Last Updated:16/08/2018 11:51

An additional train service has been planned to operate as shown 13:59 Worcester Shrub Hill to London Paddington due 16:31.
Last Updated:16/08/2018 13:20

15:14 Hereford to London Paddington due 18:28 will be started from Worcester Shrub Hill.
This is due to a fault with the signalling system.
Last Updated:16/08/2018 12:24

According to RTT^» (Real Time Trains - website), the problems with the 09:54 Great Malvern - Paddington seem to have been at Charlbury, while the 10:22 Paddington - Hereford seems to have been at Didcot (was it held there in case it needed to go via Stroud?).

The 09:54 Great Malvern - Paddington has just given up at Reading, 103 late.

[charles_uk]

Not on JourneyCheck as at 16:00 but National Rail Enquiries has the 16:22 Paddington to Great Malvern showing as cancelled. @GWRHelp on Twitter says it's "not running because of a fault on board".

So that's another faulty IET^▸ (Intercity Express Train) cancellation on the Cotswold Line today.

[fladpass]

Not on JourneyCheck as at 16:00 but National Rail Enquiries has the 16:22 Paddington to Great Malvern showing as cancelled. @GWRHelp on Twitter says it's "not running because of a fault on board".

So that's another faulty IET^▸ (Intercity Express Train) cancellation on the Cotswold Line today.

RTT^» (Real Time Trains - website) lists as "This service was cancelled throughout due to a mishap (MY)." Note sure what qualifies as 'a mishap' ...

[IndustryInsider]

Welcome to the forum, Fladpass

TyrellCheck has it down to 'no set'.  Whether that's down to a 'mishap' or just general IET^▸ (Intercity Express Train) train unavailability I don't know, though the latter is more likely.  This train has been much more reliable of late than in the first few months of the year when it was often cancelled a couple of times a week.

[fladpass]

Thanks! Yes, it's been my twice-weekly ride home for the last six months or so (though through choice not today, as luck would have it) and it's generally been spot on

[Worcester_Passenger]

Friday Aug 17:

18:22 London Paddington to Hereford due 21:32 will be terminated at Worcester Shrub Hill.
This is due to a shortage of train crew.
Last Updated:17/08/2018 15:26

[Worcester_Passenger]

And the truncated 18:22 has now disappeared from JourneyCheck.

A case of "now you don't see it, now you do"?

[bobm]

That is because the 18:22 has been re-instated in its entirety.   

It’s something Journeycheck should be better at showing rather than just deleting the cancellation or alteration.