Turbos back on Thames Valley locals today

[181]

Thisafternoon stopping services between Didcot and Reading were being worked by turbo d.m.u.s running through from/to Oxford or Banbury. As far as I noticed, 387s seemed to be running in the normal timings east of Reading; changing from one to the other would, at least at the time I arrived at Reading, have involved crossing the bridge (which would have been annoying for anyone with heavy luggage or a bicycle expecting a through journey -- and in the down direction there would only have been a minute to make the connection). Realtime Trains suggests that 387s are running Paddington-Didcot as normal tomorrow.

Does anyone know a) what the reason for this is, and b) why there appears to be nothing on either NRE or the GWR website about this service alteration?

As a theoretical question (my journey wasn't delayed), can you claim Delay Repay compensation (or anything similar if the TOC in question runs a different scheme) if you're delayed by a timetable alteration that was planned but not publicised?

 

[sonic2009]

I believe there was issues with the OHLE in the Didcot area today.

I've read on a Facebook group that a driver was told by Thames Valley Signalling Centre not to pan up at Didcot, but wait until Reading on a Class 800.

 

[181]

Thankyou. Maybe they should be commended for running a near-normal service (at least for passengers not hoping to travel through Reading without changing) in the circumstances, but it seems odd to make no acknowledgment that it wasn't a normal service.

 

[hassaanhc]

On Friday the 2R60 1759 London Paddington to Reading was formed of a 5-car 165 (units '127 and '113) instead of the usual 8-car 387. There was nothing showing on JourneyCheck about it. On investigation using RealTimeTrains it appears that for that day and all weekdays next week (at least) the service is using DMU timings, and will have to be formed of DMUs as the previous working was the 1K27 1648 Newbury to London Paddington, then the following working for the front unit is the 2L64 1919 Reading to Oxford (rear unit goes into Reading Depot).

Then for Monday 23 April to Thursday 26 April inclusive, it becomes the turn of 1R06 1757 London Paddington to Reading to have DMU timings instead of the usual EMU timings.

 

[cactustwirly]

On Friday the 2R60 1759 London Paddington to Reading was formed of a 5-car 165 (units '127 and '113) instead of the usual 8-car 387. There was nothing showing on JourneyCheck about it. On investigation using RealTimeTrains it appears that for that day and all weekdays next week (at least) the service is using DMU timings, and will have to be formed of DMUs as the previous working was the 1K27 1648 Newbury to London Paddington, then the following working for the front unit is the 2L64 1919 Reading to Oxford (rear unit goes into Reading Depot).

Then for Monday 23 April to Thursday 26 April inclusive, it becomes the turn of 1R06 1757 London Paddington to Reading to have DMU timings instead of the usual EMU timings.

Witnessed this on the 6th April, my HST overtook a 5 car 165 pair at Hayes at around 16:15.

 

[pdeaves]

not to pan up at Didcot, but wait until Reading on a Class 800.

That's been the situation for ages. 800s on electric in the Didcot area cause signalling interference.

 

[FGW_DID]

That's been the situation for ages. 800s on electric in the Didcot area cause signalling interference.

Interference with Axle Counters at Cholsey. Diesel power only is only applicable to Down Trains. Up trains are unaffected and can pan up at Moreton Cutting or having stopped at Didcot, in the station.

I haven't seen anything else in the late notices or control updates relating to 800 power modes in the Didcot area.