• Our new ticketing site is now live! Using either this or the original site (both powered by TrainSplit) helps support the running of the forum with every ticket purchase! Find out more and ask any questions/give us feedback in this thread!

Network Rail at Doncaster

Status
Not open for further replies.

yorkie

Forum Staff
Staff Member
Administrator
Joined
6 Jun 2005
Messages
78,295
Location
Yorkshire
Can anyone from Network Rail (I'll refrain from using one of the many 'alternative' names!) explain why the 20:00 London to Newcastle (1N33), non-stop to York, was held for around 8 minutes at Doncaster station and did not even have the decency to offer any explanation to East Coast as to why they have done this? Trains are running normally in the area, and there is no train in front (well, that is, assuming they did not put the freight train that overtook us in front of us?!)

Unfortunately Doncaster box does have a reputation. On one particularly memorable occasion, a railtour organised by staff at the signalling centre was delayed (due to Network Rail I believe) and assurances were made that the last train to Leeds would be held for passengers. The train was not held, and a senior manager on board was furious. Given that some staff at Doncaster cannot even be honest with their own colleagues, I am not exactly surprised when Doncaster box stops fast trains for no apparent reason whatsoever, and then fails to provide an adequate explanation. The only way I can describe the quality of their regulation in a polite way would be 'below the standard one would reasonably expect at times'.

If someone can explain, it would be interesting to know what the reasons are.
--- old post above --- --- new post below ---
Looks like they did put a slow freight in front, as we crawled along to Shaftholme Jn, after which we quickly accelerated to full speed.

Unbelievable! Even by Doncaster standards!
 
Sponsor Post - registered members do not see these adverts; click here to register, or click here to log in
R

RailUK Forums

ralphchadkirk

Established Member
Joined
20 Oct 2008
Messages
5,754
Location
Essex
You were 5 late leaving Doncaster, and interestingly, 5 early at Doncaster Lower Junction. However I feel it to be unfair for you to berate and rant at Doncaster Signalling Centre when, with respect, you have no idea what the state of the rest of the line, or indeed the bigger picture, other than the train you are on.
 

yorkie

Forum Staff
Staff Member
Administrator
Joined
6 Jun 2005
Messages
78,295
Location
Yorkshire
You were 5 late leaving Doncaster, and interestingly, 5 early at Doncaster Lower Junction. However I feel it to be unfair for you to berate and rant at Doncaster Signalling Centre when, with respect, you have no idea what the state of the rest of the line, or indeed the bigger picture, other than the train you are on.
Erm, with respect, you have no idea what I do or don't have an idea of. The bigger picture was that all other trains in the area were on time!

Anyway, NR did later admit their mistake in letting a ballast train ahead of us. :roll:

Full marks to the superb guard who gave platform information at York, and they changed the Scarborough train to be a cross-platform connection so no-one was in danger of missing it.
 

nr_signaller

Member
Joined
6 Feb 2011
Messages
94
Erm, with respect, you have no idea what I do or don't have an idea of. The bigger picture was that all other trains in the area were on time!

Anyway, NR did later admit their mistake in letting a ballast train ahead of us. :roll:

Full marks to the superb guard who gave platform information at York, and they changed the Scarborough train to be a cross-platform connection so no-one was in danger of missing it.

Your train was 5 early approaching doncaster. The freight was 15 late and the signaller had the route set for the freight but it seemed to drop a further 10 mins through doncaster. The signaller obviously forgot his crystal ball last night so did not forsee that happening. Your comment about the bigger picture and all other trains being on time was competely wrong.


 
Last edited:
Status
Not open for further replies.

Top