SWT major disruption 19/07

[greaterwest]

Looks like several issues on the network today are causing problems; SWT are not having a good day.

Signalling problem Basingstoke
Signalling problem Poole (as per yesterday)
Reported cracked rail at Havant

Trains are unable to use platforms 1 & 2 at Basingstoke and so 3 is being used as a down line and 4 as an up line.
There was, until recently, a queue consisting mainly of 2Lxx (Basingstoke stopper) and 2Bxx (Bournemouth/Poole stopper) trains on the down slow (platform 1) but that has since cleared.

 

[infobleep]

Great news. I was 40 minutes late yesterday. I saw there was disruption so decided to catch the 5.18 from Surbiton. Unfortunately there was a 455 train on platform 3 which had a green light to go but didn't move.

Eventually the green light went red. Not sure what this train was as it wasn't showing on real time trains. All the departure board was saying was something like please stand clear as this train is ready to leave.

Eventually there was a green light again and off it went. I then saw on the departure board that the 17.18 was cancelled. No announcement about this though. Very shortly it passed through on the fast line. It had left Waterloo on time but was 6 minutes late passing through Surbiton. I assume they couldn't be certain what time the 455 might leave and couldn't keep the fast line blocked, whilst waiting for the platform to become free.

No doubt the passengers on board for Surbiton had to alight at Esher. They had 3 minutes to make anither late running train at least.

At one point a non stop Basingstoke service went through on platform 3. A member staff announced this as a train passengers could board. It had left the station by this point t. With so much going on in not surprised they made a mistake. Probably saw Basingstoke and thought it must be the 17.39. We are all human.

I boarded the 17.39 which left 5 minutes late and did at least stop at Surbiton.

It was the kept on the slow line all the way to Woking, rather than other onto the fast line as sometimes happens. So I just missed the fast train to Portsmouth, which was also late but not as late as us. The Basingstoke one eventually left Woking 10-12 minutes late.

I then boarded the 18.16 to Guildford which arrived 4 minutes late. It then preceeded to sit at the station. I assume a late running Portsmouth Harbour service, which usually goes via the Guildford New Line needed to go in front of us.

We left 6 minutes late and then got held outside of Guildford. I couldn't see any train on platform 3 on Real Time Trains but perhaps if a train is using platform 4, it's not possible to access platform 3 from the lines coming from Woking.

Hopefully tonight it won't be as bad.

Given that South West Trains operate a policy of trying to ensure the same trains don't get cancelled or run late, each time, hopefully priority will be given to some of the trains held up yesterday.

I'm not sure how they can implement this policy during disruption, given drivers and guards work different trains after finishing a service and need to be in different places, not to mention breaks but they say they do.

The heat is never easy for rail companies and Network Rail to deal with so I can't really complain. It is annoying though at the time, even if it's understandable.

Sent from my SM-G925F using Tapatalk

 

[pompeyfan]

Basingstoke was good fun at about 4pm, for a short period trains began to use 1 and 2 again, but that soon stopped again. Most trains were about 30-40 minutes late. I feel for the passengers that were on a 1 wisky that was then diverted via Havant, to then be caught up in the issues there.

Platform staff were really good and gave as much info as was humanly possible.

 

[Monty]

The Portsmouth Direct has now reopened, my UP stopper has only lost two minutes in the end.

 

[Matt Taylor]

I take two days off and this is what happens!

I'm back at work tomorrow, on the same turn I had a few weeks back when they had a code black so we'll see what happens!

 

[alastair]

This was yesterday(18th) not today but utter shambles at Farnham early afternoon. Arrived to catch 1358 to Clapham Junction on way to Gatwick Airport and train drew in on time but then sat there whilst the driver announced we were "awaiting a guard",then 10 mins later it was announced as cancelled,but there "was a train 20 mins behind",so we all cleared off the train and it sped off empty. 1428 did not turn up but was then announced as "running 12 mins late" due to "signalling problems at Alton". Still nothing happened and when the 1458 didnt turn up either I was seriously concerned about my fast approaching latest check-in time (1655) at Gatwick. At 1510 I decided I had no option but to take a taxi to Gatwick which cost me £95,which I fully expect SWT to pay for after I have made a detailed report and claim.

The really depressing thing was that although there is a train crew depot on the platform at Farnham and there were at least 7 or 8 Drivers,Guards and other sundry SWT staff on the platform,NOBODY seemed to have any idea what was going on or where the errant trains had got to(and this in a case where the trouble was all less than 10 miles away,and on a line which has recently been resignalled!).

 

[infobleep]

The 17.39 was 53 minutes late leaving Surbiton tonight but I managed to arrive not to long before it left. As soon as it left Surbiton they were able to put it onto the fast line so it could pass the Woking stopper at Walton on Thames.

It was delayed due to waiting for the staff and there is a further crew change due at Woking. Parts of the air-condition are not working at the moment, as guard not aware of it before they left. The guard apologised for the train being crowded too. It's less crowded now as I think a lot of people get off at Surbiton. Some of those though may have transferred to the stoppers though which are being less delayed.

Train now into Woking with a better journey time than last night because it was able to overtake the stopper.

Sent from my SM-G925F using Tapatalk

 

[bb21]

This was yesterday(18th) not today but utter shambles at Farnham early afternoon. Arrived to catch 1358 to Clapham Junction on way to Gatwick Airport and train drew in on time but then sat there whilst the driver announced we were "awaiting a guard",then 10 mins later it was announced as cancelled,but there "was a train 20 mins behind",so we all cleared off the train and it sped off empty. 1428 did not turn up but was then announced as "running 12 mins late" due to "signalling problems at Alton". Still nothing happened and when the 1458 didnt turn up either I was seriously concerned about my fast approaching latest check-in time (1655) at Gatwick. At 1510 I decided I had no option but to take a taxi to Gatwick which cost me £95,which I fully expect SWT to pay for after I have made a detailed report and claim.

The really depressing thing was that although there is a train crew depot on the platform at Farnham and there were at least 7 or 8 Drivers,Guards and other sundry SWT staff on the platform,NOBODY seemed to have any idea what was going on or where the errant trains had got to(and this in a case where the trouble was all less than 10 miles away,and on a line which has recently been resignalled!).

So you left yourself 1 hour 21 minutes between the arrival time of your train and close of check-in (1358 gets you in at 1534 with a change at Clapham and then East Croydon, or 1547 if changing at Aldershot, Guildford, and Redhill)? hock:

Where is your contingency plan?

 

[fandroid]

I am on the 19.05 out of Waterloo for Weymouth. It left about 40mins behind schedule. At least it has working aircon! I sat for a while on the 18.50 to Exeter, but it was unbearably hot. I have a feeling that it was still in the platform when we left. I think we got first chance because we had a driver.

We are drifting through Woking, about 50 mins late now.

 

[CatfordCat]

Something hit the fan on the Windsor lines about 1740, but no information as to quite what.

1735 Waterloo - Reading ran, albeit a bit late, then apparently nothing for about an hour after that.

And it was stopped additionally at the stations between Wokingham and Reading (it was more or less on the times of the 1750 which is 'all stations' west of Ascot by the time it reached Berkshire) - unusually constructive work on SWT Control's behalf - their usual reaction to any problems is to curtail or non-stop trains...

 

[14sutton]

electricity supply problem between Strawberry Hill and Teddington. Line blocked towards Kingston

 

[infobleep]

The 17.39 was 53 minutes late leaving Surbiton tonight but I managed to arrive not to long before it left. As soon as it left Surbiton they were able to put it onto the fast line so it could pass the Woking stopper at Walton on Thames.

It was delayed due to waiting for the staff and there is a further crew change due at Woking. Parts of the air-condition are not working at the moment, as guard not aware of it before they left. The guard apologised for the train being crowded too. It's less crowded now as I think a lot of people get off at Surbiton. Some of those though may have transferred to the stoppers though which are being less delayed.

Train now into Woking with a better journey time than last night because it was able to overtake the stopper.

Sent from my SM-G925F using Tapatalk

I then picked up a 54 minute late running Portsmouth Harbour service, which last night I missed due to being delayed more than it was delayed.

Unfortunately it then developed a door fault at Worpolesden and the driver couldn't draw power. We all eventually detained. After 29 minutes and I believe the second coach doors locked out of use, we were back on the train and departing.

That would have blocked the down line between Woking and Guildford for a time. Still at least they had one working down line to Basingstoke

I noticed that they were saying in disruption notice for Havant that trains might be diverted via Basingstoke. In the Basingstoke disruption notice they were saying trains might be diverted via Havant. As someone pointed out above, one actually was.

Sent from my SM-G925F using Tapatalk

 

[greaterwest]

I then picked up a 54 minute late running Portsmouth Harbour service, which last night I missed due to being delayed more than it was delayed.

Unfortunately it then developed a door fault at Worplesdon and the driver couldn't draw power. We all eventually detained. After 29 minutes and I believe the second coach doors locked out of use, we were back on the train and departing.

That would have blocked the down line between Woking and Guildford for a time. Still at least they had one working down line to Basingstoke

I noticed that they were saying in disruption notice for Havant that trains might be diverted via Basingstoke. In the Basingstoke disruption notice they were saying trains might be diverted via Havant. As someone pointed out above, one actually was.

Sent from my SM-G925F using Tapatalk

Indeed, I couldn't quite believe it when I read that line, both diversionary routes were disrupted (broken rail Havant, signalling issues Basingstoke) so I don't know how they managed it.

1T33 was diverted via Havant
1P48 via Basingstoke
2P50 via Basingstoke

 

[alastair]

So you left yourself 1 hour 21 minutes between the arrival time of your train and close of check-in (1358 gets you in at 1534 with a change at Clapham and then East Croydon, or 1547 if changing at Aldershot, Guildford, and Redhill)? hock:

Where is your contingency plan?

.

Well,NRE gave me the connection you suggest off the 1358,or off the 1428 walking from Ash Vale to N Camp and arriving Gatwick 1551 - that was my contingency. For a journey which takes 50 mins door to door(M25 permitting!) by car I thought that was reasonable - clearly I was wrong.

 

[bb21]

.

Well,NRE gave me the connection you suggest off the 1358,or off the 1428 walking from Ash Vale to N Camp and arriving Gatwick 1551 - that was my contingency. For a journey which takes 50 mins door to door(M25 permitting!) by car I thought that was reasonable - clearly I was wrong.

You are certainly braver than me.

At 1h20, throw in a fatality (which is far from unusual these days) and all bets are off.

If measuring against check-in closing time, 2h30 is the least I will allow, more often 3h.

 

[CatfordCat]

electricity supply problem between Strawberry Hill and Teddington. Line blocked towards Kingston

can understand that stopping the Waterloo - Twickenham - Kingston - Waterloo services and any trains that a formed by units that have come to Waterloo that way, but everything seemed to come to a halt on the down lines including Reading and Windsor trains, which as far as I know aren't generally the same units.

 

[infobleep]

You are certainly braver than me.

At 1h20, throw in a fatality (which is far from unusual these days) and all bets are off.

If measuring against check-in closing time, 2h30 is the least I will allow, more often 3h.

I usually allow 2 hours myself. If driving I might be tempted to allow more, depending on the route needed to reach the airport.

If I had heavy cases though I wouldn't fancy the walk to North Camp
Not that I've done it mind you. Might be perfectly fine with heavy cases.

Sent from my SM-G925F using Tapatalk

 

[bb21]

I usually allow 2 hours myself. If driving I might be tempted to allow more, depending on the route needed to reach the airport.

If I had heavy cases though I wouldn't fancy the walk to North Camp
Not that I've done it mind you. Might be perfectly fine with heavy cases.

2 hours+ would be an absolute minimum in my view as that would just about put it above the reach of most fairly common types of incidents (obviously the definition of "fairly common" varies by person), and would take some monumental cock-up to exceed, or for one to be unlucky enough to be on a culprit train, or a trapped train immediately behind. (This all assumes a reasonably regular service, say, every 30 minutes or so.)

When one is into the "monumental" territory, he tends to get more sympathy from Customer Services too in the aftermath.

That's why I prefer to allow 2h30, taking into account other potential minor delays en route. 1h20 leeway is just far too short for my liking.

 

[Juniper Driver]

So you left yourself 1 hour 21 minutes between the arrival time of your train and close of check-in (1358 gets you in at 1534 with a change at Clapham and then East Croydon, or 1547 if changing at Aldershot, Guildford, and Redhill)? hock:

Where is your contingency plan?

This is a good point.Last time I caught a plane from Heathrow I do remember getting there at least five hours early and hanging about (which is better than missing the plane..As I was flying 6000 miles I wanted to virtually make sure I would get there in good time.Got the Central Line to Ealing Broadway but still had problems getting from Ealing Broadway to Heathrow on a Sunday.Learn't my lesson in 2007 when I caught the Victoria Line/Piccadilly Line and had a horrendous time getting there.Vowed never to use that route again.

On the disruption...My rounder was diverted from the W-M to Hounslow.Ended up on Platform 19 ~ Waterloo to work an Epson with all the passengers expecting my 455 to be the Reading train.Spent 5 hot hours on those units.

 

[fandroid]

I was travelling from Newcastle, having seen disruptions on the ECML due to the temperatures and could see online that Waterloo was a mess- most departures just showing 'delayed' - many of those already well past their departure times. The SWT website gave no news for Basingstoke after 13.00 (it was after 18.00 when I was looking). The use of only two platforms there was explained, but however nice it is to know such detail, that's operational stuff and passengers need to be given some clues about their actual services and how they are running. The Twitterati were in their usual rage. Mainly because SWT weren't saying anything except where you could catch buses with your rail ticket! It would help if the Twitterati stuck to saying what their own situations were and give out clues on the service on the ground.

Communications were a disaster. There weren't any announcements on the Exeter train despite it's total lack of movement. There could have been a suggestion to do what I did, which was to take the Weymouth train to Basingstoke as it did at least have functioning air conditioning, and at Basingstoke there is always a breeze! That train (10 coaches) had plenty of seats.

A last thought- Having forewarned myself of trouble at Waterloo, I was expecting that any train that ran would be packed. I was quite surprised how relatively empty they were. In normal times there are standing passengers. Where had everyone gone?

 

[infobleep]

I was travelling from Newcastle, having seen disruptions on the ECML due to the temperatures and could see online that Waterloo was a mess- most departures just showing 'delayed' - many of those already well past their departure times. The SWT website gave no news for Basingstoke after 13.00 (it was after 18.00 when I was looking). The use of only two platforms there was explained, but however nice it is to know such detail, that's operational stuff and passengers need to be given some clues about their actual services and how they are running. The Twitterati were in their usual rage. Mainly because SWT weren't saying anything except where you could catch buses with your rail ticket! It would help if the Twitterati stuck to saying what their own situations were and give out clues on the service on the ground.

Communications were a disaster. There weren't any announcements on the Exeter train despite it's total lack of movement. There could have been a suggestion to do what I did, which was to take the Weymouth train to Basingstoke as it did at least have functioning air conditioning, and at Basingstoke there is always a breeze! That train (10 coaches) had plenty of seats.

A last thought- Having forewarned myself of trouble at Waterloo, I was expecting that any train that ran would be packed. I was quite surprised how relatively empty they were. In normal times there are standing passengers. Where had everyone gone?

Perhaps they were on other trains, not knowing what was going on.

I assume the Exeter train had staff on it or you wouldn't have been able to board it. If it did then an announcement would be useful. Even if it's an I don't know what's happening yet but when I do I will let you know. I've had announcements like that before and they have always been welcomed by myself and no doubt others too.

Sent from my SM-G925F using Tapatalk

 

[alastair]

I usually allow 2 hours myself. If driving I might be tempted to allow more, depending on the route needed to reach the airport.

If I had heavy cases though I wouldn't fancy the walk to North Camp
Not that I've done it mind you. Might be perfectly fine with heavy cases.

Sent from my SM-G925F using Tapatalk

Ash V to N Camp is not bad actually. Less than 10 mins not hurrying. Perfectly doable with a (wheeled) case.

 

[RichardN]

Sent from my SM-G925F using Tapatalk

Ha. I'm in that photo and was on both the those trains last night, travelling from Surbiton to Witley...

 

[Deepgreen]

Basingstoke was good fun at about 4pm, for a short period trains began to use 1 and 2 again, but that soon stopped again. Most trains were about 30-40 minutes late. I feel for the passengers that were on a 1 wisky that was then diverted via Havant, to then be caught up in the issues there.

Platform staff were really good and gave as much info as was humanly possible.

Is this supposed to be phonetic alphabet speak? If so, why de-value the whole point of the system (which is supreme clarity) by; a) mis-spelling the words (One Whiskey), and, b) using it here when alternatives would be far more appropriate for a general audience (such as 'down fast', etc). Nothing personal (and conscious of a 'rant-alert'!), but jargon often doesn't work on wide-ranging forums like this.

 

[infobleep]

Ha. I'm in that photo and was on both the those trains last night, travelling from Surbiton to Witley...

I too a couple at ground level. Wonder if we were in those too. Below is one of them.

I quite enjoy photographing crowds beside trains. It highlights how popular they are.

Sent from my SM-G925F using Tapatalk
--- old post above --- --- new post below ---

Ash V to N Camp is not bad actually. Less than 10 mins not hurrying. Perfectly doable with a (wheeled) case.

May be one day I'll try it for the experience, probably without a case though.

Sent from my SM-G925F using Tapatalk

 

[greaterwest]

Ash V to N Camp is not bad actually. Less than 10 mins not hurrying. Perfectly doable with a (wheeled) case.

Until you reach the stairs at Ash Vale with your heavy wheelie-case and realise there isn't a lift

 

[43096]

Something hit the fan on the Windsor lines about 1740, but no information as to quite what.



1735 Waterloo - Reading ran, albeit a bit late, then apparently nothing for about an hour after that.



And it was stopped additionally at the stations between Wokingham and Reading (it was more or less on the times of the 1750 which is 'all stations' west of Ascot by the time it reached Berkshire) - unusually constructive work on SWT Control's behalf - their usual reaction to any problems is to curtail or non-stop trains...

Yes I noticed that - I was fortunately on the 1735. Even better, the TOSLW of 450007 was absolutely fridge like!

 

[Juniper Driver]

Also eight on top of five on platform 14/15? at Waterloo yesterday added to the fun.Poor signalman had a really rough day.

 

[infobleep]

Also eight on top of five on platform 14/15? at Waterloo yesterday added to the fun.Poor signalman had a really rough day.

What problem does 8 on top of 5 cause? Doe sit block access to other platforms?

Sent from my SM-G925F using Tapatalk

 

[Deepgreen]

What problem does 8 on top of 5 cause? Doe sit block access to other platforms?

Sent from my SM-G925F using Tapatalk

I'm almost certain that it would not sit inside the starting signal and thus cause a blockage. If so, it wouldn't allow the adjacent platform's signal to be cleared.