Great Western Coffee Shop

Well after almost a year of 90% punctuality and not worrying about checking if the train is on time/running before leaving the house or office I think it is back to the bad old ways.

In the past 3 weeks I have managed a total of 3 trains on time (less than 5min late at end of my journey) between Oxford and Charlbury, this is from a total of over 25 train journeys. I also have had two cancellations (delayed my by 75min this evening.

At the moment the 0835 train from Charlbury is reliably  5min or more late.

Leaves have been an issue, but also train breakdowns and signal failures.

I totally agree.. my commute has got steadily worse too over the last months (Maidenhead to Paddington) and shows no sign of improving.. in fact I think it's still on the downward spiral.. Not sure what's up tho..

I think mostly due to the fact it's November, and so far it's been mostly a mild, wet and windy November.  I bet it's very slippy out there tonight for example.

Almost invariably caused by appalling timekeeping by the 06.48 from London to Malvern, which, although it is already allowed 74 minutes PAD-OXF (and this as a 'fast' service!) then runs non-stop Oxford-Kingham, still contrived today to be 15 minutes late through the single line from Wolvercot. Net result, 10-plus delay to the Cathedrals Express and cancellation of the 09.29 from Moreton-in-Marsh, because too little time was left for it to run empty from Wolvercot to Moreton, shunt and depart on time. Same happened one day last week and has been a close-run thing several more times.

As I use the 09.29, I take a keen interest in the 06.48 and its timekeeping is poor at the moment. Has rarely been less than five minutes late on to the Cotswold Line from Oxford for some weeks now and 10 down is more like it. There have been a couple of days when the ecs from Oxford for the 09.29 must have been absolutely thrashed in order to make an on-time departure from Moreton. It may be something to do with leaves, or delays to the halts train into Oxford but as one of those trains that can cause a lot of damage to others (which was why it lost its Hanborough and Charlbury stops), maybe the 06.48 needs a bit of special attention

Not really a fast service...

06:48 LONDON PADDINGTN to OXFORD.
First Class and Standard
LONDON PADDINGTN       06:48
SLOUGH.   07:04   07:04
READING.   07:19   07:22
TILEHURST   07:27   07:27
PANGBOURNE   07:31   07:31
GORING & STRTLEY   07:36   07:36
CHOLSEY   07:41   07:41
DIDCOT PARKWAY   07:49   07:50
OXFORD.   08:02

It might run under a class 1 headcode (1W12 for anyone who cares) but it's all stations between Reading and Didcot - I don't think anyone would call it a fast service, semi-fast at very best. And therein lies the problem at the moment I suspect - when adhesion's bad, that little cluster of station calls takes its toll on that train's punctuality.

As if to illustrate the fact - the 0648 left PAD on time, 2 late by Reading then gradually accumulated more delay minutes between there and Didcot, consistent with poor adhesion and all the station calls. Presented itself 6 down at Oxford, then lost another minute to station work and left 7 down. Next report shows it 17 late at Moreton (no report shown for Kingham) - some kind of pathing issue at Wolvercote Junc or was it just slipping like the proverbial north of Oxford?

Appeared to claw back a few minutes to Evesham but then things fell apart with it arriving at WOS 44 down and being terminated short at WOF, where it departed 2 minutes late in the path of the return working and kept reasonable time all the way back to Paddington. Probably the sensible decision to make operationally under the circumstances but I wouldn't have been best pleased were I travelling to Malvern.

So a relatively modest delay as far as Oxford, then it all comes tumbling down in a big way when the single line section gets involved. A risk of being a bit controversial, I think that at least some of the blame must go to BR...

But it could be worse. SEPTA announced with a straight face the other morning when there was a slight rain shower that all the Philadelphia-area regional rail services were likely to be delayed up to 30 minutes due to "slippery rail" as they call it here. Amazingly it was actually true, a bit of rain and the whole system went entirely to pot. I don't remember rain causing delays back in Blighty before except when it was absolutely tipping down and causing floods.

But it's been going on for months...

And duly appears in timetable 16, London-Oxford fast services, hence my description, borrowing FGW's description.

But can't actually afford it, because of the the Cathedrals Express coming the other way, and the ecs to Moreton that follows it on to the single line. What may look like a "relatively modest delay" soon spirals and spreads to other trains because of the way the timetable is structured in terms of where trains meet. And this is not the only example, the 17.22 from London also able to wreck things for several hours with a "relatively modest delay".

Maybe I'm just lucky but even in the middle of all this wet and windy stuff, I haven't been on a train that has had any apparent traction problems.

I have been on a turbo that stopped while waiting at wolvercote junction for access to the single line, it struggled to get moving again. several HSTs with
adhesion differences between front and rear causing shoving backwards and forwards.

Last nights problems were caused by a signal failure causing a delay in the 1551 from Paddington, this results at Oxford in a steadily increasing delay, so instead of 1647, it was 1654 when I arrived and slowly increased to 1705, then 1709. Then as seems to be standard operating procedure it gets cancelled at about 1715 and we all get piled onto another hst to replace the 1731 from platform 2. This is then delayed (it was 1746 last night).

I too have also noticed the poor time keeping on Services between Portsmouth - Cardiff and Bristol - Weymouth...!

Every day this week I have caught a train (about 8 different trains) they've been more than 15 minutes late! It's a little frustrating for me, because if I'm going to Bath after work, I take a bus from White Horse Business Park in Trowbridge, into the Town Centre then get a train because it is much quicker. That is something I am normally quite happy to pay for a train ticket and do. But it's getting a little tedious that I stand in the cold on a platform for an extra 20 minutes (like yesterday to Bath for example) to board a train that was overcrowded. That then by the time it arrived was 35 - 40 minutes late!! >:( Considering that the particular 265 bus I caught yesterday runs practically empty, is warm, doesn't cost me anything and would have been just as, if not quicker!!

I had a rant about the Frome trains... They are getting to the point now where the return in the evening is at least 15, but mostly 30 minutes late.

I don't like to rant or complain, but for me, lately train travel has become a rather unpleasant pleasure which is having a major impact, as I can't get to places that I need to without leaving ridicously early and losing time at work, or arriving too late for my meeting/appointment! Like when I missed an appointment with my doctor because the train to Frome was 45 minutes late a couple of weeks ago. I had been waiting for that appointment for 6 weeks, I had the letter in the post today from them with my new appointment. I won't been seen now till the new year >:(

Although I quoted you, Jo - I was particularly referring to the last 3 weeks post from IanL that started the thread off.  Other issues that have been prevalent over the last few months is the spate of cable thefts and the Turbo refurbishment which means it's far harder to 'step up' sets to cover late running.  NR's equipment also seems to have been suffering a little more than usual, so I guess of you put those issues together it might explain a drop in performance.


From my observations, it's mostly down to waiting the halts train to clear the single line (that's not to say it's never the 06:48 Paddington's direct fault).  That train is timed very tightly and due to clear the single line at 08:07 - by which time the 08:04 to Malvern should be arriving at Wolvercote Junction.  With so many stops in known poor rail adhesion areas (Hanborough is notorious) it is commonly losing a few minutes and seems to clear Wolvercote 5-10 minutes late.  A number of Turbo drivers have recently signed the Oxford to Great Malvern route and are understandably cautious on this new route during the leaf fall season until they get a bit more confident.  As you say, everything is then so tight with the two additional morning movements now that is hits the service after for some time.

 ::)

If you actually read what I wrote, you would have noted that that was my point - only 6 late at Oxford but as soon as the single line section gets involved the job goes to b*gg*ry.

In my ignorance, are the 6.48 Pad to Malvern and 9.29 Moreton to Pad turbos or HSTs?

If they are the former, could the empty set not go to Hinksey Yard, allow the 6.48 to pass and then couple at OXF and run locked OOU to Moreton, thus relieving the need to take up two paths?

This, of course, is irrelevant if HSTs are involved.

I don't know for certain but I'd make an educated guess that the 0648 is a Turbo, given its calling pattern between Reading and Didcot. Same applies to the 0929 Moreton - Pad, it's a stopping train with a class 2 headcode (2P42), so almost certainly a Turbo.

What you propose is interesting - haven't thought the logistics through in my head for too long but it sounds sensible. However I'm sure that those who know the Cotswold line set-up a little better than I do may be able to explain why it's not applied.

Edited to add...

Incidentally, the 0929 left Moreton right time this morning, 1 late at Oxford, 3 early on the blocks at Paddington. The 0648 also behaved itself, no more than 3 late at any point on the journey, only 2 late into Malvern.

Only problem is the stock for the empties comes down as a stopper from pad arriving at 0844.

That being the case, is this not also a VERY tight schedule, if this stopper is running late too?

I did read it. You wrote the following


And my point was that in this case and others, it is that delay from Oxford - incurred before the single line gets involved - that causes the problem, not the single line. It shouldn't be late in the first place - or the timetable should have been drawn up in such a way as to avoid the potential for trouble - see below.

If it wasn't late on to the single line, then there would not be a problem. End of story. And that is the case for all too many delays on the route. They actually originate off it, often between London and Oxford, but are then imported on to the single line, where, aided and abetted by the structure of the timetable (eg precious few trains actually meet in the middle of the double-track section) stuff up everything else on the route.

So you tell me, is that the fault of the single line - as you seem to be suggesting, or the fault of something somewhere else, miles away? The 17.50 got me home 10 minutes late tonight but every minute of that delay, plus five or so more clawed back out of the sitting around at Oxford station time and some fast running, was incurred south of Oxford. But seeing it limp into Worcester after two hours and 40 minutes, I'm sure someone will just assume 'blooming single line again'. Not true.

The 06.48 leaves Oxford when it does in order to form the 09.5X back from Malvern, so it simply couldn't wait for the ecs to Moreton, which is the 08.42 arrival at Oxford. I might add that the forerunner of the 06.48 actually used to head west later, but FGW decided to pull it forward to give 08.5X and 09.5X departures from Malvern, despite the CLPG and others pointing out that the last time someone tried to run a train westbound at that time, it often got in the way of the Cathedrals Express. It did just that again, so the Hanborough and Charlbury stops were removed from the 06.48 but it still gets in the way. At least the double track will allow the meet to happen at Charlbury. Just as well, given that the Hanborough and Charlbury stops by the Turbo are due to be reinstated next year.


As it does most days, just so long as it can get here in the first place...

And I can assure bigdaz that the working into Oxford that forms the ecs out to Moreton-in-Marsh is a pretty solid performer. Cancellations of the 09.29 almost invariably follow a contretemps between the 06.48 and the Cathedrals Express.

Some tree-felling at Hanborough would undoubtedly help there, but after making a start two winters ago, they just seemed to give up, which seems bizarre given it is a known problem area. Maybe someone though that with the disappearance of the Adelantes, which really struggled going west, they didn't need to bother finishing the job. Time to get out the chainsaws again, methinks.

Monday, 1519 from Oxford, 12 minutes late in the middle of the day and delay incurred before entering single lane.
0835 CBY to PAD at least 5min late wed and thursday (lift in on mon and tues so dont know about these). Wednesday's service started from Worcester SH due to train fault, missed out all stops from Hereford.

Also travelling chef announcements....sold out before reaching Charlbury three times in last 7 days

Thursday evening, 1647 due into Oxford on time, arrived 3min late, departed 5min late, still showing on CIS as on time. Delays before entering single line.

Friday morning, 0643, from hereford, started from Worcester, 19min late at CBY and OXF due to signalling problems.