Southeastern disruption

[Bungle73]

How come SE seem to think that trains delayed by ~40 mins plus loads cancelled equals "minor disruption"? The former is what their app said when I checked it this afternoon, only to find the latter when I delved deeper.

I ended up waiting 40 minutes for a train at Chatham because of the delays ("signalling problem" at Rainham, plus a speed restriction through the tunnel - but no explanation as to why). A train did come along at about 15:15 which was suitable but it didn't stop, so I had to wait another 26 minutes! I'd already been waiting since about 15:00! The guy doing the annoncments at Chatham gave the people on platform one plenty of updates, but didn't seem to bothered about us standing on platform 2! When I did manage to get on the train there was some confusion over whether it was stopping at Newington and Sittinbourne (my station) or not. First it was only stopping at the former, then both, then only the latter, then both again!

Then when I finally got to Sittingbourne I got on the train to Kemsley which was supposed to leave at 16:10 and come that time it was just sitting there! There was a train in platform one not going anywhere so it looked like mine wasn't going to go any time soon so I decided to walk. I only wanted to go literally 5 minutes up the line to Kemsley!

 

[user15681]

Got caught in this too, SE said due to Network Rail emergency engineering works that services had to run a reduced speed.

In response to the other bit, as you know the Sheerness train crosses onto the up line temporarily. If there was a train in platform 1, the route was most likely already set for it to go first. Unfortunately, as a branch line, the Sheerness train often suffers during main line delays.

 

[Bungle73]

The train in platform 1 looked like it was gong no where fast though. Sure enough I had a look on the ex-NRE app on my phone when I was more than half way home and according to that the Sheerness train was still sitting in the platform!

I hate not knowing how long the delay is going to be. If it's not going to be moving for ~20 minutes or more I might as well walk because it takes me about that long to get home; but when I don't know I don't know whether to give it up and walk or just sit tight and wait!

There was an announcement made on the train but I couldn't understand a word of it because of the noise the other passengers were making (you'd think they'd have the sense to shut up for five seconds) and because it was rather quiet.

 

[Southern]

Chatham customers are lucky, down in Canterbury you don't get any announcements whatsoever! Walking back from College this evening, a train was just departing Canterbury East at about 1640 (delayed 1559), got to the platform to see the 1628 was running late as well. This disappeared off the board and was replaced by the 1659, which was listed as running "on time"...that is until 1659, when that vanished from the board and was replaced by the delayed 1628. This eventually turned up and we left at 1707...no platform announcements, no apologies from the guard, nothing.

Much the same happened on Wednesday night after the suicide at Teynham, I was using Canterbury West that day but that route was also affected. The apology from the guard of the delayed 2025 was much appreciated, just a shame the station staff couldn't have made more of an effort, very poor customer service if you ask me :roll:

 

[466.networkers]

The train in platform 1 looked like it was gong no where fast though. Sure enough I had a look on the ex-NRE app on my phone when I was more than half way home and according to that the Sheerness train was still sitting in the platform!

I hate not knowing how long the delay is going to be. If it's not going to be moving for ~20 minutes or more I might as well walk because it takes me about that long to get home; but when I don't know I don't know whether to give it up and walk or just sit tight and wait!

There was an announcement made on the train but I couldn't understand a word of it because of the noise the other passengers were making (you'd think they'd have the sense to shut up for five seconds) and because it was rather quiet.

Glad you walked in the end ...

1540 and 1610 Sittingbourne - Sheerness trains were cancelled.

Had both units at Sittingbourne until the 1640 which ran. 466040 making the 1710 was at the country end of Platform 3 at Sittingbourne when I arrived off 45 mins delayed 1F42 Javelin. The driver opened the train up, loaded pax and set off ... only to stop at the usual stopping place to pick people up!

The delays are due to a 5mph TSR in the Rochester area as well as a 20mph TSR in Chatham tunnel ... Add the peak time rush and there's congestion, fast running and delays everywhere.

Announcements at Chatham and Sittingbourne were manual as well as auto, so can't really complain. Lots of delay repay forms being submitted I think!

 

[Bald Rick]

Re-railing last night went a bit wrong; the job overran this morning and a couple of the welds were in danger of failing hence 5mph until they were clamped and fit for 20mph.

An unrelated track circuit failure compounded matters.

Due to their location, neither issue could be fixed with trains running, so the job had to be stopped for a little while to enable the repair.

 

[elementalpat]

Seems that NR also seems have discovered major issues with the track on the ECML too judging from the delays this evening.

 

[Class377/5]

Add in a fault train somewhere east of Bromley South seemed to cause issues as well when I saw SET twitter page.

 

[SETCommuter]

Don't forget to claim your money back:

http://www.southeasternrailway.co.uk/your-journey/delay-repay/delay-repay-form/

 

[Bungle73]

Don't forget to claim your money back:

http://www.southeasternrailway.co.uk/your-journey/delay-repay/delay-repay-form/

I will, but I won't get much back - the ticket was only £3.65!