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!
LNER seem to be using this a lot lately, even for delays which occur en route, which suggests a fundamental misunderstanding about when this reason should be used.
Even outside of major disruption, LNER’s approach seems to be to announce the initial delay on JourneyCheck once, and then not update it until it ‘falls off’ the screen some time after it arrives at its final destination.
In the past, I’ve made day trips by air to Amsterdam, Dublin, Düsseldorf and even visited the Netherlands one way by air and returning by sea from the Hook of Holland.
Sadly it’s very difficult to achieve this today (at least, at reasonable cost), because budget airlines seem more interested in...
I was specifically referring to customer support roles within Control: 6x Duty Customer Info Managers 1x Customer Info Manager and 1x Customer Info Systems Manager does seem to me significant, especially on top of the splitting of Customer Info/Customer Experience roles which took place around...
But there has been a significant INCREASE in the staffing levels on the customer information side within Control, with no discernable improvement in the quality of output that I can see.
The Highland Chieftain
The Flying Scotsman
The Northern Lights
The North Briton
The Hull Executive
The Bradford Executive (now apparently The West Riding Limited)
These are the names which have persisted most in the face of corporate indifference!
Do LNER still produce a printed oublic timetable...
In this case, it was decided the night before and seems standard practice whenever the Inverness service is unable to make its 0755 departure time due to crew rest period issues the previous night.
It used to be possible to send a replacement Guard up earlier to ensure a RT departure, but now...
I note that the INV-EDB portion ran as 1E13 (the usual headcode) and the 1130 EDB-KGX ran as 1Z13. Would it not be better reflected in downstream systems if the starter from Edinburgh ran as 1E13 and the starter from Inverness (which is actually running two hours out of path) ran as 1Z13?
Goole Tom Pudding Way sounds strange to the uninitiated. Also Goole Hospital Reception conjures up an image of the bus smashing through the walls of said hospital!
There’s a road closure in place West of Ulleskelf, so the only route for the RRB betwern York and Ulleskelf would be from the A19 and Cawood, which might explain why the bus didn’t turn up (on time).
Yes, it’s a proper ‘dog’s breakfast’. In order to see the service disruptions, you have to click on the ‘travel updates’ tab, then specify a route. You will be presented with a list of trains, each one is labelled as ‘on time’ ‘delayed’ ‘part-cancelled’ or ‘cancelled’.
It seems ‘on time’ trains...
We are aware of an issue with emails from the Forum to Microsoft-based email accounts (hotmail/outlook/live.com email addresses). This is being looked into currently, thanks for your patience meanwhile.