...and just to round off the day. The later services ran with a unit lacking a working toilet.
And to round off the month, a summary of performance for the last 28 days (I have chosen that rather than 30 days to get an equal number of each day of the week, and to have same period length as the railway)
Melksham stats - trains scheduled to call but not calling at Melksham. Compiled from the running log at
http://www.mrug.org.uk/record.html on the Melksham Rail User Group web site which is compiled from Tiger feeds.
day lost reason given
30 4 A shortage of train crew
29 1 A fault on this train
27 2 A shortage of train crew
27 1 no reason given, 13:55
25 4 a fault with the signalling system
22 2 A shortage of train crew
19 1 A fault on this train
14 2 a fault with the signalling system
10 2 A fault on this train
9 4 A shortage of train crew
6 1 Animals on the railway earlier today
6 1 a fault with the signalling system
6 1 A shortage of train crew
6 2 no raason given, 09:18 and 11:12
5 2 a broken down train
5 1 A shortage of train crew
31 cancellations in 28 days over 16 different incidents
Trains (or planned replacement buses) scheduled 476
Cancellation rate 6.5%
14 A shortage of train crew
7 A signalling fault
6 A train fault
3 Reason not logged (at least 2 are congestion, train ran but via Bathampton rather than Melksham)
1 Animals on the railway
Note - the stats are kind - i.e. could be worse
* "23 13 Bus " Recording systems do not log running of planned rail replacement buses.
* Cancellation that are notified but then trains re-instated loose confidence and business but are not logged
* Delays not analysed in detail; worst was 22 minutes , most just a few minutes. 283 trains "On Time".
Comment - if
GWR▸ had its own house in order (enough crews and trains that routinely worked when out in service), two thirds of the problem would be cured. We do get train faults on other operator's trains, but in June I believe none of the cancellations were due to freights "sitting down".