2023 Delays and Cancellations

[whole diary]

[Worcester_Passenger]

From JourneyCheck:

09:52 London Paddington to Hereford due 12:46 has been delayed at London Paddington and is now 16 minutes late.
This is due to a late departure while the train was cleaned specially.

Looks like it'll be terminated at Ledbury, and the return working 1P04 started from there

I wonder what proportion of the trains intended to reach Hereford from Paddington ever actually arrive there?

During the week commencing Monday June 2, there should have been 33 GW^▸ (Great Western) arrivals and 33 GW departures at Hereford. Four of each failed to make it, so the answer to the question is 12%.

Mon 5 scheduled arrivals + 5 departures - all OK
Tue  5+5 but lost 1+1
Wed same
Thu same
Fri 5+5 all OK
Sat 5 departures + 4 arrivals but lost 1+1
Sun 3 departures + 4 arrivals - all OK

[Worcester_Passenger]

From JourneyCheck:

14:53 London Paddington to Worcester Foregate Street due 17:04 will be cancelled.
This is due to a fault on this train.
Last Updated:04/07/2023 14:40

17:26 Worcester Foregate Street to London Paddington due 19:54 will be cancelled.
This is due to a fault on this train.
Last Updated:04/07/2023 15:11

[Worcester_Passenger]

From JourneyCheck:

05:23 Hereford to London Paddington due 08:24 will be cancelled.
This is due to a fault on this train.
Last Updated:05/07/2023 04:21

05:53 London Paddington to Great Malvern due 08:38 has been cancelled.
This is due to a fault on this train.
Last Updated:05/07/2023 06:14

08:56 Great Malvern to London Paddington due 11:24 will be cancelled.
This is due to a fault on this train.
Last Updated:05/07/2023 06:14

[charles_uk]

From JourneyCheck:

05:23 Hereford to London Paddington due 08:24 will be cancelled.
This is due to a fault on this train.
Last Updated:05/07/2023 04:21

05:53 London Paddington to Great Malvern due 08:38 has been cancelled.
This is due to a fault on this train.
Last Updated:05/07/2023 06:14

08:56 Great Malvern to London Paddington due 11:24 will be cancelled.
This is due to a fault on this train.
Last Updated:05/07/2023 06:14

And Realtime trains is showing that the 05:14 Worcester Shrub Hill to Paddington service was also cancelled meaning the short-formed and late running 06:43 Worcester Shrub Hill to Paddington was the first up service of the day.

[Worcester_Passenger]

The first train from Hereford is not having a good week:

05:23 Hereford to London Paddington due 08:24 will be reinstated.
It will be terminated at Worcester Shrub Hill.
It will no longer call at Worcestershire Parkway Hl, Pershore, Evesham, Honeybourne, Moreton-In-Marsh, Kingham, Charlbury, Hanborough, Oxford, Reading and London Paddington.
This is due to a shortage of train crew.
Last Updated:06/07/2023 00:46

Note that cancellations due to the overtime ban are reported as "This is due to industrial action".

[GBM]

The first train from Hereford is not having a good week:

05:23 Hereford to London Paddington due 08:24 will be reinstated.
It will be terminated at Worcester Shrub Hill.
It will no longer call at Worcestershire Parkway Hl, Pershore, Evesham, Honeybourne, Moreton-In-Marsh, Kingham, Charlbury, Hanborough, Oxford, Reading and London Paddington.
This is due to a shortage of train crew.
Last Updated:06/07/2023 00:46

Note that cancellations due to the overtime ban are reported as "This is due to industrial action".

Many cancellations today on Cornish branches due to shortage of train crew (rather than industrial action).
Interesting.

[charles_uk]

The first train from Hereford is not having a good week:

05:23 Hereford to London Paddington due 08:24 will be reinstated.
It will be terminated at Worcester Shrub Hill.
It will no longer call at Worcestershire Parkway Hl, Pershore, Evesham, Honeybourne, Moreton-In-Marsh, Kingham, Charlbury, Hanborough, Oxford, Reading and London Paddington.
This is due to a shortage of train crew.
Last Updated:06/07/2023 00:46

As yesterday, the following 06.43 Worcester Shrub Hill to Paddington only five coaches and running over half an hour late.

[Worcester_Passenger]

Not a good day. According to RTT^» (Real Time Trains - website):

1P11 05:14 Shrub Hill - Paddington ran to time
1P02 05:23 Hereford - Paddington cancelled after Shrub Hill
1P16 06:43 Shrub Hill - Paddington (5 cars) left Shrub Hill 29 late, arrived Paddington 36 late. (Late departure from Worcester sidings.)
2E80 07:01 Shrub Hill - Didcot (2 cars) left Shrub Hill 15 late, was held at Norton, arrived Oxford 24 late, cancelled after that
1P18 07:13 Great Malvern - Paddington (9 cars) left Malvern 15 late, held at Henwick and Charlbury, arrived Oxford 40 late

1W11 05:53 Paddington - Great Malvern (5 cars) ran on time to Evesham, where it has a scheduled wait of 12 minutes. Despite this, it left Evesham 14 late and arrived Malvern 7 late.

[Worcester_Passenger]

From JourneyCheck:

15:23 London Paddington to Worcester Foregate Street due 17:47 will be cancelled.
This is due to more trains than usual needing repairs at the same time.
Last Updated:07/07/2023 11:02

18:02 Worcester Foregate Street to London Paddington due 20:30 will be cancelled.
This is due to more trains than usual needing repairs at the same time.
Last Updated:07/07/2023 11:02

[Witham Bobby]

07/07/2023

1P30 1316 Worcester Shrub Hill to Paddington arrived on time at 1334 at Evesham, departed 15 minutes late, no real picking-up of time to Oxford, where it was terminated.  5 car 800018 "Problem with the train (M8)"

1W02 1152 Paddington to Hereford.  5 mins late Didcot, 15 late off Oxford, 23 late off Foregate St, got to Hereford 32 minutes late (1513).  Due to form the 1518 back to Paddington, 1P05  9 car 802106

[Worcester_Passenger]

Saturday July 8

1W11 05:52 Paddington - Foregate Street was cancelled between Worcester Foregate Street and Great Malvern due to a points failure (IB). On time at Langley but 25 late after Slough.

08:50 Great Malvern to London Paddington due 11:22 will be started from Worcester Foregate Street.
This is due to a points failure.
Last Updated:08/07/2023 07:46

08:52 London Paddington to Great Malvern due 11:24 will be terminated at Reading.
It will no longer call at Oxford, Hanborough, Charlbury, Kingham, Moreton-In-Marsh, Honeybourne, Evesham, Pershore, Worcestershire Parkway Hl, Worcester Shrub Hill, Worcester Foregate Street, Malvern Link and Great Malvern.
This is due to a fault on this train.
Last Updated:08/07/2023 09:41

11:55 Great Malvern to London Paddington due 14:22 will be cancelled.
This is due to a fault on this train.
Last Updated:08/07/2023 09:41

RTT^» (Real Time Trains - website) is reporting 1W17 08:52 Paddington - Great Malvern as

This service was cancelled between Reading and Great Malvern due to adverse weather conditions (MW).

Wrong code perhaps?

13:05 Worcester Foregate Street to London Paddington due 15:22 will be cancelled.
This is due to a fault on this train.
Last Updated:08/07/2023 11:11

[Worcester_Passenger]

17:00 Great Malvern to London Paddington due 19:24
Service full and standing from Oxford.
Last Updated:08/07/2023 18:41

RTT^» (Real Time Trains - website) reports this as being a 5-car.

[Worcester_Passenger]

Sunday July 9 : JourneyCheck reports

13:11 Worcester Foregate Street to London Paddington due 15:25 will be started from Oxford.
This is due to a shortage of train crew.
Last Updated:09/07/2023 02:13

[Worcester_Passenger]

Sunday July 9 had time-keeping issues. The worst cases:

1W15 07:36 Paddington - Great Malvern : held at Didcot due to overunning engineering work. Left 53 late. Arrived Foregate Street 59 late, cancelled thereafter.
1W35 08:53 Paddington - Great Malvern : held at Reading and at Wolvercote. 22 : late at Hanborough, arrived Malvern 20 late.
1W01 09:47 Paddington - Hereford : 13 late at Shrub Hill, but it has a scheduled 13 wait at Malvern, so on time at Hereford.
1W03 13:44 Paddington - Hereford : problems before Reading. Left Oxford 26 late, arrived Hereford 32 late.
1W47 14:44 Paddington - Great Malvern : delayed at Didcot. Left Oxford 17 late, arrived Malvern 24 late.
1W51 16:44 Paddington - Great Malvern : left Paddington 23 late. 30 late at Norton Junction, but arrived Shrub Hill 56 late, cancelled thereafter.
1W59 17:44 Paddington - Great Malvern : on time until after Evesham. 18 late at Norton Junction and 27 late at Malvern.
1W08 18:51 Paddington - Hereford : lost time after Charlbury. 18 late at Shrub Hill, arrived Hereford 19 late.

1P30 08:15 Foregate St - Paddington : held at Charlbury. Left there 48 late. Arrived Paddington 48 late.
1P37 08:58 Great Malvern - Paddington : held at Charlbury. Left there 21 late. Arrived Paddington 22 late.
1P45 11:05 Great Malvern - Paddington : started from Foregate St. On time into Paddington.
1P49 11:55 Great Malvern - Paddington : started 8 late. Arrived Paddington 14 late.
1P55 13:12 Foregate St - Paddington : cancelled throughout. RTT^» (Real Time Trains - website) does not record it as starting from Oxford as per JourneyCheck.
1P59 13:58 Great Malvern - Paddington : lost time. Held at Charlbury and left 23 late. Arrived Paddington 30 late.
1P63 14:30 Hereford  - Paddington : 6 late at Shrub Hill, 19 late at Charlbury. Arrived Paddington 31 late.
1P69 15:31 Hereford  - Paddington : 12 late at Charlbury. Arrived Paddington 13 late.
1P73 16:58 Great Malvern - Paddington : held at Charlbury and left 16 late. Arrived Paddington 16 late.
1P77 17:30 Hereford  - Paddington : left 25 late. Arrived Paddington 30 late.
1P81 18:58 Great Malvern - Paddington : held at Foregate St and Shrub Hill. Left Shrub Hill 48 late. Arrived Paddington 57 late.
1P85 20:16 Great Malvern - Paddington : started from Foregate St, 19 late. Arrived Paddington 35 late.
1P88 20:40 Great Malvern - Paddington : left 21 late. Scheduled wait of 7 at Evesham. Arrived Paddington only 4 late.

[Worcester_Passenger]

Monday July 10.

Ominously, train 1D10, 05:05 Paddington - Oxford (due 06:07), seems to have stopped at Appleford, with the stock for the 06:48 Oxford - Paddington trapped behind it.
CrossCountry's train 1M18, 05:15 Southampton - Manchester (due Oxford 06:37) is running wrong line from Didcot.

Train 1W11 05:53 Paddington - Great Malvern is reported by JourneyCheck as being delayed by this.