Cotswold Line - 2019 cancellation and amendments log

[whole diary]

[IndustryInsider]

The short formations I was on - and there have been more recently -  led to passengers standing for long distances, and yet on some of those occasions there were two first class carriages with seats vacant. I notice that in a recent post Worcester_Passenger says that in similar circumstances the first class was 'declassified'. I wonder if any of the experts on here can tell me who takes that decision and in what circumstances?

The Train Manager, and whenever they feel it is appropriate.  Though in reality it’s just the equivalent of one carriage but in two halves.

[Worcester_Passenger]

According to JourneyCheck:

Facilities on the 04:47 Hereford to London Paddington due 07:52.
This is due to a fault on this train.
Will be formed of 5 coaches instead of 9.
Last Updated:04/07/2019 04:51

Declassifying the first won't be an option here...

There's also the two Worcester starts that go via Cheltenham.

[charles_uk]

A consequence of the earlier disruption in the Didcot area:

17:52 London Paddington to Worcester Shrub Hill due 20:10 has been cancelled.
This is due to a fault with the signalling system.

[Worcester_Passenger]

A consequence of the earlier disruption in the Didcot area:

17:52 London Paddington to Worcester Shrub Hill due 20:10 has been cancelled.
This is due to a fault with the signalling system.

Curiously, it's running empty, as train 5W36. Currently shown as 41 late, and following the on-time 18:22 Paddington - Hereford train.

[Richard Fairhurst]

Were there any rail replacement buses running?

I was cycling up the hill out of Charlbury at 8pm and almost got wiped out by an exceptionally close pass from a Weavaway bus - the worst I've had in 10 years. Weavaway are usually only seen round here as RRBs^▸ (Rail Replacement Bus).

[IndustryInsider]

A consequence of the earlier disruption in the Didcot area:

17:52 London Paddington to Worcester Shrub Hill due 20:10 has been cancelled.
This is due to a fault with the signalling system.

Curiously, it's running empty, as train 5W36. Currently shown as 41 late, and following the on-time 18:22 Paddington - Hereford train.

No TM^‡(resolve) available in time to run it from Oxford until after the following train had left so it ran empty behind the next train to avoid having to cancel the return journey.  The TM got stuck at Slough working the 17:18 PAD^» (Paddington (London) - next trains)-OXF^» (Oxford - next trains) which was cropped due to engine issues.

[Worcester_Passenger]

A consequence of the earlier disruption in the Didcot area:

17:52 London Paddington to Worcester Shrub Hill due 20:10 has been cancelled.
This is due to a fault with the signalling system.

Curiously, it's running empty, as train 5W36. Currently shown as 41 late, and following the on-time 18:22 Paddington - Hereford train.

No TM^‡(resolve) available in time to run it from Oxford until after the following train had left so it ran empty behind the next train to avoid having to cancel the return journey.  The TM got stuck at Slough working the 17:18 PAD^» (Paddington (London) - next trains)-OXF^» (Oxford - next trains) which was cropped due to engine issues.

That seems an odd piece of crew scheduling. The 17:18 from Paddington is a stopper, due into Oxford at 18:43. The 17:52 from Paddington is due out of Oxford at 18:50. Quick handovers during the peak don't seem like a good idea - there's no resilience.

[IndustryInsider]

It is indeed an odd bit of scheduling.  Brought about by the need to find a TM^‡(resolve) for the 17:18 from somewhere as originally it would have been expected to be operated as a DOO^▸ (Driver-Only Operation (that is, trains which operate without carrying a guard)) service. 

The 17:18 does have a fair bit of slack in its schedule as it still runs on Turbo timings as well as having 8 minutes at Didcot, but it’s not how you’d ideally do things, as last night proved.

[grahame]

12:13 Hereford to London Paddington due 15:28
12:13 Hereford to London Paddington due 15:28 will be started from Reading.
It will no longer call at Hereford, Ledbury, Colwall, Great Malvern, Malvern Link, Worcester Foregate Street, Worcester Shrub Hill, Pershore, Evesham, Honeybourne, Moreton-in-Marsh, Kingham, Shipton, Charlbury, Hanborough and Oxford.
This is due to a shortage of train crew.

"No sir, it's not cancelled. It's updated"

[Worcester_Passenger]

Later...

08:22 London Paddington to Hereford due 11:41 will be terminated at Worcester Shrub Hill.
It will no longer call at Worcester Foregate Street, Malvern Link, Great Malvern, Colwall, Ledbury and Hereford.
This is due to a shortage of train crew.
Last Updated:06/07/2019 07:56

12:13 Hereford to London Paddington due 15:28 will be started from Worcester Shrub Hill.
It will no longer call at Hereford, Ledbury, Colwall, Great Malvern, Malvern Link and Worcester Foregate Street.
This is due to a shortage of train crew.
Last Updated:06/07/2019 07:56

12:22 London Paddington to Moreton-in-Marsh due 14:00 will be cancelled.
This is due to a shortage of train crew.
Last Updated:06/07/2019 07:41

14:50 Moreton-in-Marsh to London Paddington due 16:26 will be cancelled.
This is due to a shortage of train crew.
Last Updated:06/07/2019 07:44

[Timmer]

Certainly an improvement for the 1213. Starting it at Reading was about as much use as a chocolate teapot that is unless your journey was starting at Reading.

[ellendune]

Certainly an improvement for the 1213. Starting it at Reading was about as much use as a chocolate teapot that is unless your journey was starting at Reading.

Are there not other trains from Paddington to Reading in time to catch that train today? 

[Timmer]

Certainly an improvement for the 1213. Starting it at Reading was about as much use as a chocolate teapot that is unless your journey was starting at Reading.

Are there not other trains from Paddington to Reading in time to catch that train today? 

It was the other way round -  Hereford to Paddington. Hence me saying not much use unless you were starting at Reading.

[charles_uk]

A couple of chunks taken out of this afternoon's service (from Realtime Trains)

1W29 1421 London Paddington to Oxford
Great Western Railway service
This service was cancelled between Oxford and Worcester Foregate Street due to a problem with the train (M8).

and that regular GWR^▸ (Great Western Railway) "fix":

1W32 1550 London Paddington to Oxford
Great Western Railway service
This service was cancelled between Oxford and Moreton-in-Marsh due to late running owing to waiting for access to a single line (YE).

[Worcester_Passenger]

05:47 Paddington - Foregate St cancelled after Oxford due to a problem with the train.

08:25 Worcester Foregate Street to London Paddington due 10:57 will be started from Oxford.
This is due to a fault on this train.
Further Information
Road transport will be available from stations Worcester Foregate Street to Honeybourne inclusive to convey customers forward to Moreton-in-Marsh station to connect with the departure from there for Oxford and London Paddington at 09:50.
Last Updated:15/07/2019 08:07

06:50 London Paddington to Great Malvern due 09:31 will be terminated at Worcester Foregate Street.
It has been previously delayed, is being further delayed between Oxford and Hanborough and is now expected to be 44 minutes late.
This is due to a fault on this train.
Last Updated:15/07/2019 08:54

09:54 Great Malvern to London Paddington due 12:28 will be started from Worcester Foregate Street.
This is due to a fault on this train.
Last Updated:15/07/2019 08:58