FGW, 17 December

[Capybara]

I'm surprised some delays on FGW haven't made it on to here. I caught the 16:31(?) from Taunton yesterday which was due in Paddington at 18:21. All went fine until the train came to a halt at Newbury Racecourse. After a time we were informed that we were behind a stationary freight train and they were trying to assess what the problem was. About 20 minutes after we came to a halt we were told that there was no way of passing the train and they were trying to work out what to do, although we could expect a significant delay. After a further 10 minutes we were informed that we were going to reverse and head back to Westbury and then on to Paddington via Melksham, Chippenham and Swindon. We would stop at Newbury for anyone who wanted to leave the train but that no alternative transport would be provided to Reading as it was rush hour and it was likely that the train would get to Reading first. An estimated arrival time at Paddington was given as 19:45. I couldn't see how this was realistic as previous incidents such as this I've been involved in have inevitably had slow running at some stage on the journey. Anyway, off we sped and I have to say I was impressed by the efforts of the train staff in trying to assist those who had ongoing trains, flights, etc. As it happened we ran at speed for the most part and non-stop all the way to Reading picking up some rare track on the way (for those who were interested!). A shame it was dark. We finally arrived at Paddington at 20:24, just over 2 hours late. The train staff were very open about what to do about claiming compensation. I don't know what happened in respect of any other trains but, apart from the original delay in providing information and the ambitious arrival time estimate, I thought it was a good effort from the staff.

 

[tsr]

I'm surprised some delays on FGW haven't made it on to here. I caught the 16:31(?) from Taunton yesterday which was due in Paddington at 18:21. All went fine until the train came to a halt at Newbury Racecourse. After a time we were informed that we were behind a stationary freight train and they were trying to assess what the problem was. About 20 minutes after we came to a halt we were told that there was no way of passing the train and they were trying to work out what to do, although we could expect a significant delay. After a further 10 minutes we were informed that we were going to reverse and head back to Westbury and then on to Paddington via Melksham, Chippenham and Swindon. We would stop at Newbury for anyone who wanted to leave the train but that no alternative transport would be provided to Reading as it was rush hour and it was likely that the train would get to Reading first. An estimated arrival time at Paddington was given as 19:45. I couldn't see how this was realistic as previous incidents such as this I've been involved in have inevitably had slow running at some stage on the journey. Anyway, off we sped and I have to say I was impressed by the efforts of the train staff in trying to assist those who had ongoing trains, flights, etc. As it happened we ran at speed for the most part and non-stop all the way to Reading picking up some rare track on the way (for those who were interested!). A shame it was dark. We finally arrived at Paddington at 20:24, just over 2 hours late. The train staff were very open about what to do about claiming compensation. I don't know what happened in respect of any other trains but, apart from the original delay in providing information and the ambitious arrival time estimate, I thought it was a good effort from the staff.

I heard that a freight train suffered a braking problem in the Theale area. I'm afraid that's all I know just now!

 

[TEW]

Originally it was thought that the freight train might have derailed though, which probably meant the delay was greater than it otherwise would have been. Most services diverted via Bristol or Melksham before passing Westbury so the delays were much less.