|
stuving
|
 |
« Reply #30 on: February 18, 2020, 10:01:37 » |
|
The line closure tagged by the signallers is east of Tilehurst on the Up Main. I guess there may be restricted working on the Down lines (either side) if repair work is going on. So all the up trains are being channeled towards P12-15 at Reading.
One odd effect of this is that TfL» Rail trains have been swapped across to reverse in P10 (and at times P9 too), as this is operationally a bay at the moment.
|
|
|
|
|
Logged
|
|
|
|
|
SandTEngineer
|
|
« Reply #31 on: February 18, 2020, 11:25:15 » |
|
Here's the reason: A signalling cable for SB901 on the Down Main became loose and was struck by the pantograph of 800304 on 1A17. This pulled the signalling cable onto the OLE▸ on the Up Main causing damage to both. SB901 signal is one of a couple that are mounted on the OLE support rather than a seperate signal structure (there is a similar one, T596 at Maidenhead). |
|
|
|
|
Logged
|
|
|
|
|
IndustryInsider
|
|
« Reply #32 on: February 18, 2020, 11:33:02 » |
|
Indeed. The signal is now repaired and the overheads in the process of being repaired, but until they are nothing is able to use the Up Main between Didcot East and Reading - there are a couple of trains 1P24 and 1L13 showing as on the Up Main on OpenTrainTimes, but they have hung in their system from yesterday and aren't actually there!
|
|
|
|
|
Logged
|
To view my GWML▸ Electrification cab video 'before and after' video comparison, as well as other videos of the new layout at Reading and 'before and after' comparisons of the Cotswold Line Redoubling scheme, see: http://www.dailymotion.com/user/IndustryInsider/ |
|
|
|
SandTEngineer
|
|
« Reply #33 on: February 18, 2020, 15:48:47 » |
|
Indeed. The signal is now repaired and the overheads in the process of being repaired, but until they are nothing is able to use the Up Main between Didcot East and Reading - there are a couple of trains 1P24 and 1L13 showing as on the Up Main on OpenTrainTimes, but they have hung in their system from yesterday and aren't actually there! I hope not, as the signals in rear of each train description are showing clear on the OTT▸ map!  |
|
|
|
|
Logged
|
|
|
|
|
TaplowGreen
|
|
« Reply #34 on: February 18, 2020, 17:57:38 » |
|
Line closed between Didcot and Reading from 2130 tonight until 0600 tomorrow in an attempt to get it fixed.
GWR▸ telling everyone to travel early tonight.
|
|
|
|
|
Logged
|
|
|
|
|
lbraine
|
|
« Reply #35 on: February 18, 2020, 18:06:41 » |
|
Line closed between Didcot and Reading from 2130 tonight until 0600 tomorrow in an attempt to get it fixed.
GWR▸ telling everyone to travel early tonight.
Ummm - where exactly are they saying this ! Not on any public presence that I can see (and I’ve just arrived at Paddington )  |
|
|
|
|
Logged
|
|
|
|
|
grahame
|
|
« Reply #36 on: February 18, 2020, 18:11:58 » |
|
Line closed between Didcot and Reading from 2130 tonight until 0600 tomorrow in an attempt to get it fixed.
GWR▸ telling everyone to travel early tonight.
Ummm - where exactly are they saying this ! Not on any public presence that I can see (and I’ve just arrived at Paddington ) @GWRHelp on Twitter ⚠️ Emergency work will take place from 21:30 this evening to repair storm damage to overhead electric wires between #DidcotParkway and #Reading. Please travel earlier this evening if you can. Image with that tweet:  |
|
|
|
|
Logged
|
Coffee Shop Admin, Chair of Melksham Rail User Group, TravelWatch SouthWest Board Member
|
|
|
|
lbraine
|
|
« Reply #37 on: February 18, 2020, 18:48:17 » |
|
Fair enough  I’m just surprised there was no mention (announcements or on screens) at Reading or Paddington .... |
|
|
|
|
Logged
|
|
|
|
|
|
|
Sixty3Closure
|
|
« Reply #39 on: February 18, 2020, 20:45:21 » |
|
Not quite the same as on the GWR▸ website but that often takes second place to Twitter now something I find frustrating. Why should I have to sign up and give my information to a third party to get current or accurate information?
|
|
|
|
|
Logged
|
|
|
|
|
paul7575
|
|
« Reply #40 on: February 18, 2020, 21:26:31 » |
|
I’m a bit suspicious of this, a signalling cable came into contact with Over-Head Line Equipment (OHLE▸ ) because of recent bad weather?
I’d be wondering whether it had ever been correctly secured in the first place, this shouldn’t really be able to happen...
Paul
Edit: VickiS - Clarifying Acronyms
|
|
|
|
« Last Edit: April 14, 2021, 15:28:47 by VickiS »
|
Logged
|
|
|
|
|
lbraine
|
|
« Reply #41 on: February 19, 2020, 07:20:35 » |
|
Looks like we are entering day 3  Hard to comprehend how much damage a signal cable coming loose can do ! |
|
|
|
|
Logged
|
|
|
|
|
ray951
|
|
« Reply #42 on: February 19, 2020, 08:42:06 » |
|
Looks like we are entering day 3 Hard to comprehend how much damage a signal cable coming loose can do ! Similiar to yesterday 4 out of 6 peak services cancelled between Didcot and Oxford. I gave up and took the car again, along with the daily delays I am not sure why I bother commuting by train these days. And then I remember I have to use the A34. |
|
|
|
|
Logged
|
|
|
|
|
SandTEngineer
|
|
« Reply #43 on: February 19, 2020, 09:59:55 » |
|
According to information posted elsewhere, the OLE▸ has been repaired but the signal hasn't. Don't quite understand why one signal being out of use should result in so much disruption (unless the damage was more extensive than originally reported).
|
|
|
|
|
Logged
|
|
|
|
|
eightonedee
|
|
« Reply #44 on: February 19, 2020, 10:16:25 » |
|
The stopping trains between Didcot and Reading also remain considerably reduced (less than a third running I'd guess), with fast London bound trains all using the relief line.
Presumably they will try again to fix tonight?
|
|
|
|
|
Logged
|
|
|
|
|
Click on the map to explore geographics
