Bishopstone
Established Member
Seems to be a focus on getting additional trains to Eastbourne, especially from the east, to cater for the Airbourne crowds.
Just wondering does anyone know why during this strike (and all of the previous ones as well) no trains are stopping at Faygate? As trains are running on that line why have they not been able to stop any trains at Faygate?
Are any of the trains that would normally serve Faygate running? How many people actually use the station? Is it worth slowing down the rare remaining services in the line to call there, given its in the middle of nowhere and those travelling already likely to be subject to delays, cancellations and ammendments?
I often wonder what the point of trains stopping at Faygate is during the normal timetable. The station (and the stop) would be more use picked up and moved to the West Ifield.
On the flip side I am on a class 700 train. Not been on one of these before. I assume it has no first class. It feels odd and more European metro than mainline service.
Sent from my SM-G925F using Tapatalk
Lol it does but if you stand on the wrong end of the platform, you are screwed.
Strange goings on at Falmer: station for the AMEX stadium.
Although the strike is off and the 'revised' timetable back in place, nothing is stopping at Falmer after 17.00 tonight, and (apparently) on subsequent match days, on police advice.
Now they ARE running to Falmer tonight, every ten minutes, having found some additional resource.
Now they ARE running to Falmer tonight, every ten minutes, having found some additional resource.
Should have checked earlier, but unimpressed to discover the Seaford branch is closed all weekend for engineering work, with a (halved frequency) replacement bus service.
Over the last five weeks Network Rail could have taken possessions Monday-Friday between 08.30 and 17.30, but instead are blocking the line to a coastal resort over a peak holiday season weekend.
Buses during the week, now buses at the weekend, too. It's very poor.
The engineering work will have been planned well in advance, prior to the revised timetable and strike that is going on. The works will need a lot of staff, engineers, and equipment, and they can't just juggle that around. The staff will have been working on other projects elsewhere earlier, making it impossible to have the Seaford branch works brought forward.
There was a Southern train taking the West London Line at Wembley today when I went past at 5pm. I tweeted Southern asking about it and they confirmed that the West London Line service has been restored to an amended timetable. This seems to be running to Watford.
There was a Southern train taking the West London Line at Wembley today when I went past at 5pm. I tweeted Southern asking about it and they confirmed that the West London Line service has been restored to an amended timetable. This seems to be running to Watford.
Passengers standing on Three Bridges station have described hearing a loud bang, as a fire broke out on the train tracks on at the weekend.
It is understood that Network Rail's engineers have been onsite for the past two days attending to the problem, and Southern Rail have explained today that speed restrictions will remain in place until the work is carried out to repair the damaged cables around the track.
On Saturday, shortly after 10.30am, commuters witnessed a fire on the tracks between Platform 4 and 5.
Right, that's actually a bit of a disservice to what happened. As it just so happens I was able to tell exactly what happened on that service. It's by no means as clear cut as you think.
The conductor and driver diagrams for that train stated that it would divide at Redhill and run all the way through to both destinations. This was also reflected by the information that staff looked up at stations using official software. None of the crew, of which 4 were involved in the operation of that train up to and including Redhill, were familiar with running this train under the emergency timetable and therefore presumed, as of course you would if your diagram said so, that it would divide. It was noted just prior to departure from Victoria that the CIS systems were not showing a split at Redhill, but Control could not be reached by phone to properly clarify the situation until the train had reached Coulsdon South. (The station staff were asked for advice at East Croydon, which was the next convenient point to reach such staff, but could not remember how the service should run.) At this point the onboard crew held a discussion and requested the onboard passenger information systems be deactivated by the driver, which failed to work (it sometimes does).
By this point the train was pretty much at Merstham and the automatic announcements were left to play for this station, after which two announcements were made manually and the audio (not also visual, sadly), PIS was eventually muted. There was a further announcement, repeated twice, at the platform at Redhill. Passengers were advised to change for all destinations not served by the Three Bridges portion.
The following evening, the crew had been made aware of the diagram error, and lessons were learned so this did not happen again. Once information had been relayed correctly, no complaints were made onboard before or at Redhill on either day, but there were two conductors onboard in the middle of the train (coaches 4/5) on both days to assist, had anyone asked for clarification (and a few people did).
By the way, the Three Bridges portion is first stop Earlswood, not Gatwick Airport...