Timetables Change From Today

[whole diary]

[G.Uard]

I'm sure that regulars to these pages will be aware of today's changes,         but for the benefit of visitors...

Timetables change today.  Please check your journey times before travelling.

http://www.firstgreatwestern.co.uk/

[willc]

New timetable, but same old shambles on the Cotswold Line, though it all began in Bristol, when the set for the 5.35 from Hereford apparently failed on the depot, trapping the set for the 6.43 for some time, which meant this eventually ran about 35-40 minutes late.

A coach was definitely laid on from Charlbury to cover for the 05.35 but the halts train was still swamped with passengers, according to a colleague who travels in from Shipton.

The delay on the 6.43 disrupted the 5.43 London-Malvern so badly that it got no further than Worcester Shrub Hill, where it was turned back and ran five minutes late throughout to Oxford, where it was then delayed for another 10 minutes because the door bolts wouldn't release, which got my week off to a great start, on top of the train running 30 minutes later than it used to.

And finally, the return halts train was delayed at Oxford due to fault on the train, ran 25 late according to a travel alert of FGW^▸ (First Great Western) website, but actually looked to be about 15 down at Moreton according to live info screens. The 17.21 ex-PAD^» (Paddington (London) - next trains), 17.00 ex-Malvern, 17.51 ex-PAD and 18.47 ex-Worcester all suffered knock-on delays as a result.

[12hoursunday]

New timetable, but same old shambles on the Cotswold Line, though it all began in Bristol, when the set for the 5.35 from Hereford apparently failed on the depot, trapping the set for the 6.43 for some time,

It was failed by the guard in the station (Bristol Temple Meads) before it's departure to Hereford. The delay to other services were caused by a whole host of things but mainly that the 'Marsh' was well quite frankly overflowing with train set's on Sunday evening. The 01.30 arrival on to the Marsh (5C35) got there at 04.05. This could only be done after it's driver was taxied to the depot to bring off his other working (5A03) which was due to depart at 02.47 but left at about 03.25. This then freed up a space so the three sets stranded at the station could go around for their services and what not. This was done by a one on & one off basis.

Normally 5A03 becomes 1A03 06.00 to Paddington but due to problems they were having at St Phillips there was a step up of sets and this train formed the 04.47 to Paddington. The driver for that train was quickly taxied back from the shed after originally being driven around there by the Yellow Cab Co only to find that the set had been serviced, fuelled and watered but was only on it's way down for it's clean at about 04.00.

There was Chaos when I left for home at five o'clock!

[John R]

Prime service from Bristol TM^‡(resolve) (0800) is cancelled this morning, and the following one is only starting from Exeter not Plymouth. Everything coming west out of London was late last night. Usual great first week of the timetable then.

[BBM]

Everything coming west out of London was late last night.

As far as I could see at PAD^» (Paddington (London) - next trains) at around 17:30 last night the delays were being caused by the late arrival of drivers. My 17:36 to Oxford didn't leave until 17:39 which wasn't too bad but the 17:30 to Taunton via Bristol TM^‡(resolve) in the adjacent platform was still there with no apparent sign of anyone 'up front'.

[John R]

Yes, it was the Taunton train I was waiting for.