Cotswold Line - 2019 cancellation and amendments log

[whole diary]

[SandTEngineer]

Apparently the train was completely disabled after it hit the animal.  It was later assisted by one of the following services making the longest IET^▸ (Intercity Express Train) service so far, over 468m long (18 x 26m coaches)

[jamestheredengine]

Interesting that the 0954 Malvern to Paddington still got there on time, despite the diversion.

[grahame]

Interesting that the 0954 Malvern to Paddington still got there on time, despite the diversion.

When you think it skipped 8 stops on what was an HST^▸ (High Speed Train) schedule, with long station dwells, it becomes more understandable; on time (or not) in such a circumstance probably depends on the luck of pathing / what it gets stuck behind. 

[charles_uk]

A few bits and pieces from the last few days for the record:

1P23 1031 Oxford to London Paddington
Great Western Railway service departing on 19th April 2019
This service was cancelled between Moreton-in-Marsh and Oxford due to a problem with the traction equipment (MD).

1W47 1537 London Paddington to Oxford
Great Western Railway service departing on 21st April 2019
This service was cancelled between Oxford and Worcester Foregate Street due to a problem with the traction equipment (MD).

1P77 1826 Worcester Foregate Street to London Paddington
Great Western Railway service departing on 21st April 2019
This service was cancelled throughout due to late arrival of an inbound service (YI).

1W23 1122 London Paddington to Oxford
Great Western Railway service departing on 22nd April 2019
This service was cancelled between Oxford and Worcester Foregate Street due to a problem with the train (M8)

1P33 1557 Reading to London Paddington
Great Western Railway service departing on 22nd April 2019
This service was cancelled between Worcester Foregate Street and Reading due to late arrival of an inbound service (YI).

and today:

1W00 0821 London Paddington to Reading
Great Western Railway service
This service was cancelled between Reading and Hereford due to a problem with the train (M8).

1P31 1209 Hereford to London Paddington
Great Western Railway service
This service was cancelled throughout due to late arrival of an inbound service (YI).

[charles_uk]

A long time since we've seen this one:

15:50 London Paddington to Moreton-In-Marsh due 17:26 will be terminated at Oxford.
It will no longer call at Hanborough, Charlbury, Kingham and Moreton-in-Marsh.
This is due to passengers causing a disturbance on a train.

Last Updated:29/04/2019 16:18

with the return run similarly truncated.

[charles_uk]

1P07 0447 Hereford to London Paddington
Great Western Railway service
This service was cancelled throughout due to a problem with the train (M8).

[charles_uk]

The equivalent thread for 2018 was up to page 32 by this time last year. It just goes to show how much better 2019 has been.

But for the record:

05:47 London Paddington to Worcester Foregate Street due 08:17 will be terminated at Oxford.
It will no longer call at Slough, Didcot Parkway, Hanborough, Charlbury, Kingham, Moreton-in-Marsh, Honeybourne, Evesham, Pershore, Worcester Shrub Hill and Worcester Foregate Street.
It has been delayed at London Paddington and is now 34 minutes late.
This is due to a fault on this train.

08:25 Worcester Foregate Street to London Paddington due 10:57 will be started from Oxford.
It will no longer call at Worcester Foregate Street, Worcester Shrub Hill, Pershore, Evesham, Honeybourne, Moreton-in-Marsh, Kingham, Charlbury and Hanborough.
This is due to a fault on this train.

Last Updated:22/05/2019 06:30

[charles_uk]

And same again today:

05:47 London Paddington to Worcester Foregate Street due 08:17 will be terminated at Oxford.
It will no longer call at Slough, Hanborough, Charlbury, Kingham, Moreton-in-Marsh, Honeybourne, Evesham, Pershore, Worcester Shrub Hill and Worcester Foregate Street.
It has been delayed at London Paddington and is now 24 minutes late.
This is due to train crew being delayed.

08:25 Worcester Foregate Street to London Paddington due 10:57 will be started from Oxford.
It will no longer call at Worcester Foregate Street, Worcester Shrub Hill, Pershore, Evesham, Honeybourne, Moreton-in-Marsh, Kingham, Charlbury and Hanborough.
This is due to train crew being delayed.

Last Updated:23/05/2019 06:18

[grahame]

The equivalent thread for 2018 was up to page 32 by this time last year. It just goes to show how much better 2019 has been.

Follow up at http://www.firstgreatwestern.info/coffeeshop/index.php?topic=21645.0 - as this is (as far as I can see) a wider experience across the GWR^▸ (Great Western Railway) area.

THANK YOU for the Cotswold log, and please carry on - although things are much better, the build up of evidence and the continued view of what we hope is the tail of the abnormal service disruption is very useful.

[Worcester_Passenger]

And same again today:

05:47 London Paddington to Worcester Foregate Street due 08:17 will be terminated at Oxford.
It will no longer call at Slough, Hanborough, Charlbury, Kingham, Moreton-in-Marsh, Honeybourne, Evesham, Pershore, Worcester Shrub Hill and Worcester Foregate Street.
It has been delayed at London Paddington and is now 24 minutes late.
This is due to train crew being delayed.

08:25 Worcester Foregate Street to London Paddington due 10:57 will be started from Oxford.
It will no longer call at Worcester Foregate Street, Worcester Shrub Hill, Pershore, Evesham, Honeybourne, Moreton-in-Marsh, Kingham, Charlbury and Hanborough.
This is due to train crew being delayed.

Last Updated:23/05/2019 06:18

I was at Foregate Street at 08:30. A number of passengers were milling about outside. They'd been told that taxis would be arriving for them.

If that cancellation was posted at 06:18, but there were no taxis at 08:30, then GWR^▸ (Great Western Railway) needs to get its customer service act together.

[philipbourton]

Yesterday (22nd) the 1752 Paddington to Worcester Shrub Hill was 5 carriages instead of 9 - but no explanation given at all.   

Also, and apologies if the wrong place to post this - is anyone else having problems with the "free wifi" - as I tend to find on the 1822 Paddington to Hereford - the free wifi doesn't work at all; yet works fine on the 1752 or even the 0623 from Kingham to Paddington in the mornings.  Just wondered if it was me or others having the issues - as it used to work most of the time on the old HSTs^▸ (High Speed Train).

[Worcester_Passenger]

04:47 Hereford to London Paddington due 07:52
04:47 Hereford to London Paddington due 07:52 will be cancelled.
This is due to a fault on this train.
Last Updated:24/05/2019 03:09

[Worcester_Passenger]

Also, and apologies if the wrong place to post this - is anyone else having problems with the "free wifi" - as I tend to find on the 1822 Paddington to Hereford - the free wifi doesn't work at all; yet works fine on the 1752 or even the 0623 from Kingham to Paddington in the mornings.  Just wondered if it was me or others having the issues - as it used to work most of the time on the old HSTs^▸ (High Speed Train).

I too can rarely get the wifi to work, but I've never noticed whether it's down to specific departures. But perhaps this should be in a new topic.

[Richard Fairhurst]

It works probably 90% of the time for me. But I tend not to travel on the peakiest of peak trains.

[charles_uk]

Start of a bank holiday weekend and an old problem rears its depressingly familiar head...

16:22 London Paddington to Great Malvern due 19:24 will be terminated at Oxford.
It will no longer call at Hanborough, Combe, Finstock, Charlbury, Ascott-under-Wychwood, Shipton, 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:24/05/2019 16:28

but also

19:07 Worcester Shrub Hill to Great Malvern due 19:24
An additional train service has been planned to operate as shown 19:07 Worcester Shrub Hill to Great Malvern due 19:24.