Morning services 3 October 2017

[whole diary]

[charles_uk]

A patchy morning to say the least on the Cotswold Line:

05:11 Worcester Shrub Hill to Paddington cancelled;
04:50 Hereford to Paddington started from Worcester Shrub Hill, and 52 late by the time it came off the Cotswold Line at Wolvercote Junction;
05:28 Hereford to Paddington arrived roughly on time at Worcester Shrub Hill before losing time and getting to Wolvercote Junction 45 minutes late;
07:10 Moreton-in-Marsh to Paddington was squeezed in before the 05:28 HFD^» (Hereford - next trains):PAD^» (Paddington (London) - next trains) and only 11 late when it got to Wolvercote Junction;
06:53 Worcester Foregate Street to Didcot started dropping time from Evesham onwards, departing Oxford 50 minutes late;
06:42 Hereford to Paddington started from Oxford.

JourneyCheck seemed to suggest that these delays were in part unrelated, explaining them as caused by over-running engineering works, signalling problems, an earlier broken down train and an incident under investigation, and GWR^▸ (Great Western Railway)'s Twitter team helpfully added "services on the same line can be affected by different incidents".

Last autumn's Cotswold Line service was dire and early signs are it could be the same again this year.

[10:20am edit to add next two services]

08:26 Worcester Foregate Street to Paddington left Worcester on time, 16 late by time it departed Oxford;
10:22 Moreton-in-Marsh to Paddington to be started from Oxford.

In all, three of the first eight up services failed to run along the Cotswold Line today, and three others at least 30 minutes late.

[ChrisB]

The early HST^▸ (High Speed Train (Inter City class 43 125 units)) couldn't get up to HFD^» (Hereford - next trains) from Bristol as the engineering work hadn't cleared from yesterday

[IndustryInsider]

And the first up train failed at Evesham delaying everything else behind it.  So two main causes for the disruption.