EMT 1C91 LDS-STP New Timetable

[MrPercy142]

Travelled on the 14:34 East Midland Trains this afternoon from Leeds toward St Pancras International.

The station boards and all online apps were displaying this service as calling at Swinton (South Yorkshire) SWN at 15.03 however on boarding the service the stops were read out omitting Swinton and an announcement was then made saying the service won’t call at Swinton.

After speaking with the train manager and EMT control, they were insistent the service couldn’t stop as the guard/driver didn’t have route knowledge at Swinton (even though we passed through) and the problem was with Network Rail not EMT. Now for NR to add this to their timetables EMT must have passed this info on.

There was no solution provided either other than to leave the service at WKF and wait over a hour there for the next stopping service. Should passengers have continued to SHF and back on a Northern train they’d have been in Swinton much quicker.

Does anyone have any info on why any of the above happened please?

 

[yorkie]

Should passengers have continued to SHF and back on a Northern train they’d have been in Swinton much quicker.

Yes, they should, as it would have been a much shorter delay.

 

[_toommm_]

I'm guessing it was meant to be a timed point where it was to stop, but obviously not for passengers to board and get off at - whoever did the schedule must have done it as an advertised stop as opposed to a non-advertised one.

 

[LowLevel]

It was evidently input as a station call in the schedule in error. HSTs can't call at Swinton except in emergencies thus the stop was deleted. Most unfortunate and delay compensation should apply but they couldn't just stop there anyway.

 

[cactustwirly]

Here's the offending train:

http://www.realtimetrains.co.uk/train/C69944/2018/05/20/advanced

Swinton is indeed listed as a calling point.
Looks like a timetabling error that escaped through the net.

 

[Class 170101]

I think that will be the least of NR's worries. The BBC are already berating NR / TSGN for the timetable at Harpenden (and its only Sunday).

 

[Starmill]

According to NRE, the stop was cancelled.

 

[Wilts Wanderer]

It’s a very common error at timetable change date. Someone forgot to put either an ‘N’ or * in the relevant data field in the schedule. For similar reasons, many Great Northern services to Kings Lynn are today being advertised as calling at LTLPL22, which is presumably the signal protecting the single line at Littleport. Similarly I’ve travelled on a West Highland Line train advertised as calling at Annat (a foot crossing / RETB board near Corpach) and a train to Newquay which was apparently calling at St Blazey and Goonbarrow Junction signal boxes!

 

[Mag_seven]

It’s a very common error at timetable change date. Someone forgot to put either an ‘N’ or * in the relevant data field in the schedule. For similar reasons, many Great Northern services to Kings Lynn are today being advertised as calling at LTLPL22, which is presumably the signal protecting the single line at Littleport. Similarly I’ve travelled on a West Highland Line train advertised as calling at Annat (a foot crossing / RETB board near Corpach) and a train to Newquay which was apparently calling at St Blazey and Goonbarrow Junction signal boxes!

There was a post on the forums recently that reported that "Brinklow" (closed station) was shown on the Euston departure board as a calling point for the Northbound Highlander sleeper. The schedule for the train concerned does show Brinklow but it only stops there to allow another train to pass.

http://www.realtimetrains.co.uk/train/C78554/2018/07/18/advanced