District Line - Earls Court to Parsons Green

[Hedgehog1977]

3rd day in a row delays Earls Court to Wimbledon. Anyone know exactly what is happening with the 'signal failure at East Putney' that seems to still be causing problems.

 

[Dstock7080]

W361 on DOWN after East Putney tunnel failing.
An NR asset.

 

[Hedgehog1977]

Don't suppsoe you know of timescales for a fix? Bet it was fun at Fulham broadway when Chelsea kicked out last night.

 

[pbin]

Don't suppsoe you know of timescales for a fix? Bet it was fun at Fulham broadway when Chelsea kicked out last night.

It was awful. Tapped in at South Kensington at 18:10 and tapped out at Parsons Green at 19:13… The Wimbledon trains were constantly switching between platforms 3 and 4 at Earl’s Court so I’d move to the opposite platform just for a train to arrive back at its original one.

 

[Hedgehog1977]

Still the delays continue. It would be good if TFL could put out a notice on the problem and when it's estimated to be fixed so passengers can plan accordingly. Status update changes between 'while Network Rail fix a signal failure at East Putney' and 'due to an earlier signal failure'. I think we had good service for about 30 mintues earleir this afternoon.

 

[Mojo]

Still the delays continue. It would be good if TFL could put out a notice on the problem and when it's estimated to be fixed so passengers can plan accordingly. Status update changes between 'while Network Rail fix a signal failure at East Putney' and 'due to an earlier signal failure'. I think we had good service for about 30 mintues earleir this afternoon.

I would imagine the main issue is that Network Rail really don’t know what the issue is. Despite multiple periods of track access and repairs undertaken both overnight and during the day, the issue persists.

 

[Hedgehog1977]

Another very poor day on the district Wimbledon branch. Lots of unhappy tweets coming into TFL. Although I completely understand this doesn't seem like a quick fix but surely now is the time for TFL to put out some customer guidence stating what the issue is, the delays it will cause and suggest customers take other routes. Just stating minor delays every single day isn't good enough.

 

[londonboi]

Normally running restored today and services running normally.

 

[Dr_Paul]

It was awful. Tapped in at South Kensington at 18:10 and tapped out at Parsons Green at 19:13… The Wimbledon trains were constantly switching between platforms 3 and 4 at Earl’s Court so I’d move to the opposite platform just for a train to arrive back at its original one.

Blimey! That's a long time. Even the 14 bus doesn't take that long.

 

[Hedgehog1977]

....and it's broken again...

 

[Mojo]

....and it's broken again...

The age old question of whether can something be broken “again” if it was never fixed?

 

[polecat170]

Still down and on SPAD braking then limping to next signal strategy, when it's not down entirely. This is day 9 I think? Contact to both TfL and Network Rail unanswered so far. Saw some orange jackets going in at Southfields at the weekend but seems they didn't have much luck

 

[lonogrol]

I have been reliably informed that despite all these days with network rail having replaced almost all of the signaling infrastructure at the location, and L.U.L P-Way having replaced track components, network rail teams overnight discovered a damaged cable.

 

[Hedgehog1977]

I have been reliably informed that despite all these days with network rail having replaced almost all of the signaling infrastructure at the location, and L.U.L P-Way having replaced track components, network rail teams overnight discovered a damaged cable.

Assume damaged cable has now been fixed and the East Putney signal problem will be no more?
(I hear it's damaged points at High Street Ken causing probs today)

 

[polecat170]

Thanks v much @lonogrol for the info! Yep it seems fine now - HSK thing seems good. It was a difficult 9/10 days though. Does anyone know what the incentives and agreements are on NR fixing signals that 99% affect TfL? Presumably outside scope of the performance regime for NR? Obviously the problem was a tricky one to diagnose, and no idea whether it was a factor this time, but I can't help feeling like we are worse off than single-operator based on speed of resolution.