• 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!

Well thats a new reason for a train cancellation

Status
Not open for further replies.

syorksdeano

Member
Joined
7 Jan 2011
Messages
780
This morning the 556 train from Sheffield to London is cancelled because of a late arrival of the service from Europe.
 

Attachments

  • Screenshot_20241129_061609_Chrome.jpg
    Screenshot_20241129_061609_Chrome.jpg
    700 KB · Views: 851
Sponsor Post - registered members do not see these adverts; click here to register, or click here to log in
R

RailUK Forums

Merle Haggard

Established Member
Joined
20 Oct 2019
Messages
3,921
Location
Northampton
E.M.R. have a history of coming up with bizarre delay explanations. Waiting for a London train at Chesterfield last week, E.M.R. announced that 'the 13.54 to Norwich is delayed by 108 minutes owing to waiting for a faster train to be attached'. Difficult to understand the rationale there.

Did any intending passengers show a reaction to the announcement you heard? It's an insight into the value attached to cause-of-delay announcements by passengers that, however bizarre the announcement, they usually show no reaction whatever. By that observation, one might question whether these are of practical use outside the enthusiast passenger.
 

skyhigh

Established Member
Joined
14 Sep 2014
Messages
6,868
Did any intending passengers show a reaction to the announcement you heard?
Who says there was an announcement? The OP only says they saw it on RTT.

The most likely explanation is someone selected the wrong reason code. If it was subsequently corrected I'm unsure if RTT would reflect it?
 

hexagon789

Veteran Member
Joined
2 Sep 2016
Messages
18,306
Location
Glasgow
Who says there was an announcement? The OP only says they saw it on RTT.

The most likely explanation is someone selected the wrong reason code. If it was subsequently corrected I'm unsure if RTT would reflect it?
It is now showing as 'problem with the train (M8)'
 

Indigo Soup

Established Member
Joined
17 May 2018
Messages
1,486
The most likely explanation is someone selected the wrong reason code. If it was subsequently corrected I'm unsure if RTT would reflect it?
IIRC, the system that RTT gets data from doesn't communicate updates to reason codes.
Did any intending passengers show a reaction to the announcement you heard? It's an insight into the value attached to cause-of-delay announcements by passengers that, however bizarre the announcement, they usually show no reaction whatever. By that observation, one might question whether these are of practical use outside the enthusiast passenger.
FWIW, my fellow passengers on a badly delayed train yesterday seemed to appreciate being told that the issue was a broken-down freight train.
 

Robin Edwards

Member
Joined
1 Dec 2013
Messages
688
I keep thinking of Reginald Perrin :)
Ep.1 "Eleven minutes late, staff difficulties, Hampton Wick."
Ep.1 "Eleven minutes late, signal failure at Vauxhall."
Ep.1 "Eleven minutes late, staff shortages, Nine Elms."
Ep.1 "Eleven minutes late, derailment of container truck, Raynes Park."
Ep.1 "Eleven minutes late, seasonal manpower shortages, Clapham Junction."
Ep.2 "Eleven minutes late, defective junction box, New Malden."
Ep.4 "Eleven minutes late, overheated axle at Berrylands."
Ep.4 "Eleven minutes late, defective axle at Wandsworth."
Ep.5 "Eleven minutes late, somebody had stolen the lines at Surbiton."
 

Merle Haggard

Established Member
Joined
20 Oct 2019
Messages
3,921
Location
Northampton
Who says there was an announcement? The OP only says they saw it on RTT.

The most likely explanation is someone selected the wrong reason code. If it was subsequently corrected I'm unsure if RTT would reflect it?

I had assumed / jumped to the conclusion that the O.P. had heard a station announcement and looked to RTT for 'hard copy' evidence.
It does seem that the reason code is used as a source of displays on stations and on trains. The announcements on trains seem to be in sync with the rolling display, so I would suggest that the reason on RTT was also given in announcements.



IIRC, the system that RTT gets data from doesn't communicate updates to reason codes.

FWIW, my fellow passengers on a badly delayed train yesterday seemed to appreciate being told that the issue was a broken-down freight train.

To be clear, I'm not challenging the usefulness of the announcements but remarking on the indifference to announcements displayed by passengers. Displayed by continuing to talk loudly/play music over the conductor/T.M.'s first announcement of the reason the train's been stationary for a while, for instance. Or not realising the significance of 'Due to reason X this service termites at this station, All change please'.
There always seems to be a delight in blaming another rail operator or N.R., too; losing sight of the railway being the customers' supplier.
 

railrambler

Member
Joined
25 Apr 2024
Messages
42
Location
appleby
I had assumed / jumped to the conclusion that the O.P. had heard a station announcement and looked to RTT for 'hard copy' evidence.
It does seem that the reason code is used as a source of displays on stations and on trains. The announcements on trains seem to be in sync with the rolling display, so I would suggest that the reason on RTT was also given in announcements.





To be clear, I'm not challenging the usefulness of the announcements but remarking on the indifference to announcements displayed by passengers. Displayed by continuing to talk loudly/play music over the conductor/T.M.'s first announcement of the reason the train's been stationary for a while, for instance. Or not realising the significance of 'Due to reason X this service termites at this station, All change please'.
There always seems to be a delight in blaming another rail operator or N.R., too; losing sight of the railway being the customers' supplier.
Hi Merle.
Can you give us a rendition of “workin’ man blues”
 

AndrewE

Established Member
Joined
9 Nov 2015
Messages
7,345
Should it be interpreted as "Train cancelled from Sheffield because it was turned back at Derby owing to late arrival there from St P International?
 

Spartacus

Established Member
Joined
25 Aug 2009
Messages
3,828
Should it be interpreted as "Train cancelled from Sheffield because it was turned back at Derby owing to late arrival there from St P International?

Not at that time, it's empty from Etches Park. Predictably just another RTT screw up, it doesn't even look like anything's been recoded in TRUST that'd make the difference.
 

Frontera2

Member
Joined
11 Dec 2007
Messages
268
The reasons given on RTT are those entered into the operational system ( TRUST ) which has no direct correlation to what you’ll see announced / displayed.

There’s a lexicon of some 413 or so reasons which the industry can use to publicly advise of a delay and these are hard coded into CIS etc. The list is here: https://wiki.openraildata.com/index.php/Darwin:Late_Running_reason_codes_and_text

So the operational code “M7 - Doors” will become “ a Fault on a train / fault on this train” in public facing channels - provided of course that the relevant manual action has been carried out eg adding the delay reason to the train in CIS or other systems.
 

StoneRoad

Member
Joined
6 Jan 2010
Messages
484
Location
Haltwhistle
I, for one, do like to know why my train is delayed --- sometimes it can be useful to appreciate the problems. An esoteric reason can alleviate the annoyance somewhat, even if there isn't an obvious solution, bar waiting.
 
Status
Not open for further replies.

Top