Upcoming Games

(UTC times)


Full list
Add a game

Upcoming Events

No events to display

Who's Online

Person82 (1 users seen recently)

WTT question

You are here: Home > Forum > Miscellaneous > The real thing (anything else rail-oriented) > WTT question

Page 1 of 1

WTT question 27/05/2023 at 09:36 #151971
ajax103
Avatar
1120 posts
I'm slightly confused trying to understand a WTT and a specific service in this case, it's 6L36 19:52 Hoo Junction Up Yard to Whitemoor Yard L.D.C Gbrf.

In the May to December 2014 WTT LD edition, it's last reporting location is Whitemoor Yard GBRF at 00/14 which I believe is simply to mark it as a passing point.

Yet if I look at another train in the form of 4M98 17:30 Southampton M.C.T. to Garston F.L.T in the May to December 2014 WTT CZ edition, it clearly shows in bold the arrival time of 01.34

So how come Network Rail can't or don't show the arrival time at Whitemoor Yard L.D.C Gbrf yet are able to do so for Garston F.L.T?

Is this a regional thing? Would the last reporting location of 6L36 actually be classed as the arrival time yet is clearly marked as a passing point?

I've checked WTT LD to see if 6L36 is shown as arriving at Whitemoor Yard L.D.C Gbrf with the driver having changed ends but there's nothing.

Anyone able to explain the logic behind 6L36 being shown as it is please?

Log in to reply
WTT question 27/05/2023 at 11:20 #151972
bill_gensheet
Avatar
1413 posts
Looks like the result of separating up and down direction trains and a triangular layout.
The only surprise to me is that it is that way round, keeping all the 'down' direction travel and missing the short 'up' would seem more likely.

Same applies in the other direction, the WTT only shows the whole timetable for Whitemoor <-> Peterborough.
Likewise on page 51 you have 6P20 appearing at Whitemoor Yard GBRF 08/18

Whitemoor yard (GBRF) is always a pass, so would seem more like Whitemoor Jn.

Yes you'd expect to see 6L36 on the opposite direction times like this:
Whitemoor yard (GBRF) 00/14
Whitemoor yard LDC (GBRF) 00:19

and for 6P20:
Whitemoor yard LDC (GBRF) 08:12
Whitemoor yard (GBRF) 08/18

but those times are missing - maybe as it is yard internal.

Deep link
https://history.networkrail.co.uk/uncategorized/IO_0c840292-167c-4ceb-b539-661021da241c/

Log in to reply
WTT question 27/05/2023 at 11:59 #151973
ajax103
Avatar
1120 posts
Maybe the arrival times are internal only, I know there's a triangle there as it's local to my home city. It's just disappointing that Network Rail can't do WTTs properly and show arrival times as they've done so on other WTTs.

After all, as you've pointed out a propelling move over the junction is timed to take 5 minutes but not knowing the layout itself, it's only guesswork.

I can see another train is marked as passing Whitemoor Junction at 15/27 and arriving at Whitemoor Yard L.D.C Gbrf at 15.32 so would Whitemoor Yard GBRF and Whitemoor Junction actually be the same location but using different names to complicate matters?

Log in to reply
WTT question 27/05/2023 at 14:54 #151977
Hap
Avatar
1037 posts
ajax103 in post 151973 said:
Maybe the arrival times are internal only, I know there's a triangle there as it's local to my home city. It's just disappointing that Network Rail can't do WTTs properly and show arrival times as they've done so on other WTTs.

After all, as you've pointed out a propelling move over the junction is timed to take 5 minutes but not knowing the layout itself, it's only guesswork.

I can see another train is marked as passing Whitemoor Junction at 15/27 and arriving at Whitemoor Yard L.D.C Gbrf at 15.32 so would Whitemoor Yard GBRF and Whitemoor Junction actually be the same location but using different names to complicate matters?
WHTMLDC - Whitemoor Local Distribution Centre. WHTMJN is the same location for Whitemoor Junction/Yard GB Railfreight. The Junction isn't a Contractual Mandatory Timing Point and it's up to the Yard operator (GBRF) to input timings. It's not really complicating anything.

How to report an issue: www.SimSig.co.uk/Wiki/Show?page=usertrack:reportanissue
Log in to reply
The following user said thank you: ajax103