Great Western Coffee Shop

From Go By Train :

Service: 17:51 London Paddington to Worcester Shrub Hill on 01/07/2008 operated by First Great Western.

Details: This train will be terminated at Oxford. It will no longer call at: Charlbury, Shipton, Kingham, Moreton-In-Marsh, Evesham, Pershore and Worcester Shrub Hill. This is due to an earlier train fault.

The 17:51 was the train with the fault.
Got problems getting air for the brakes between Southall and Hayes, got to Oxford 1 hr late.

Yep - I've now updated that information in the database...

And a fun evening on the Cotswold Line ensued, with nothing west from Oxford for 95 minutes.

The 17.51 made it to Oxford at 19.40, just under an hour late. The 18.21 was not far behind by this stage and eventually left Oxford 35 minutes late. Had lost no more time by Moreton-in-Marsh despite making an extra stop at Shipton, but looked likely to drop another five minutes or so at Moreton waiting for the single line on to Evesham.

There was a knock-on delay to the 18.49 from Worcester, which was held at Ascott-under-Wychwood, to keep it out of the way of the 18.21. I'd guess the London-bound train was about half-an-hour late at Charlbury, although the monumental padding in its timing from Charlbury into Oxford would have had it back to about 15 minutes late reaching there.

Time to dig out that compensation claim form.

Hi, which database and can we get access?

So Glad I escaped early and got the 1721!

I asked something similar yesterday, Andy. Apparently the information is not for public consumption.

Which to my mind renders the information about as trustworthy as government statistics....

The information is as accurate as it is given...

And coming eastwards, the worst pathed train of the day, the 19:27 from Worcester Foregate Street to Oxford, spent its booked 30 minutes sat at Evesham waiting for zero trains to come the other way. Then it got delayed at Ascott for 15 minutes, and arrived Oxford over two hours later at 21:30. The following train being cancelled meant the last up service would have mopped up any stragglers.

If you read what I said to you properly, you'll note it clearly said that it isn't for public consumption yet. There will be a mobile phone version (which will work on normal PC browsers) released later today after testing is complete.

In my eyes, why release something before we know it works? Problems with the system so far (and have only come up during testing) include a small problem of no logging if there are no LU problems... rest assured, coffee shop readers will get it first.

Getting back on topic, sort of, the 17.51 tonight ran as a 3-car Turbo, started at Reading, due to a train fault.

Not sure whether this was with the Adelante that was on the diagram this morning, 180102, which didn't exactly seem in the best of health accelerating away from stations when I rode it on the 08.37 ex-Worcester. It must have spent a good few weeks laid up at Oxley before returning to FGW - seems to have replaced 108 or 109 at Old Oak.

Reliability of the 180s is becoming an issue by the look of it, with several substitutions in recent days on this diagram, as they can't seem to struggle to get two out of three Adelantes working for the 7.10 from Oxford. Availability at 33% doesn't exactly inspire confidence if the survivors are meant to be soldiering on for another eight or nine months.

No it doesn't, Will. But that's one of the disadvantages of having such a small fleet - availablility of spares etc, which has been plagued by reliability issues since they arrived, especially in the summer. Even a small fleet size of 14 caused problems in that respect.