Hello,
I have seen just this afternoon that several Greater Anglia services are being delayed due to an “Operational Incident”. It is quite a broad term, what sort of things could this supposed incident be?
Does it also get used when nobody knows what the problem is yet? I.e: “Well something happened but damned if I know what it is”I've added that reason myself for less serious things like rostering errors, missed station calls and train crew being late on duty. They all the affect the operation of the service after all!
There is a "cause not yet identified" delay code, which I have seen used.Does it also get used when nobody knows what the problem is yet? I.e: “Well something happened but damned if I know what it is”
A fatality is not an operational incident in phblic facing language. "Emergency services dealing with an incident" is the usual description for this now.Fatality,Spad,Signalling failure,derailment or other safety of the line incident.
Would be a genuine incident not a ‘supposed’ incident as you seem to be insinuating.
If the set is needed more elsewhere that sometimes happens - iirc I've seen it when Southern 171s get taken from the Marshlink to work Uckfield services if there's a unit that failed.On a similar vein what does 'This service was cancelled at the request of the operator' mean?
I've seen it a couple of times this week on RTT with cancelled trains on the Stansted - Birmingham route.
In that eventuality the usual phraseology of choice is "due to a problem under investigation".Does it also get used when nobody knows what the problem is yet? I.e: “Well something happened but damned if I know what it is”
Except I’ve seen LNER use it for en route delays incurred between stops, which stretches credibility a bit!At risk of derailing the thread further (though it is about delay/cancellation reasons, not a specific incident), I saw the delay reason of "This train has been delayed to maintain customer connections" for the first time recently. Certainly a positive!
I mean, isn't every delay technically caused by an 'Operational Incident'?Except I’ve seen LNER use it for en route delays incurred between stops, which stretches credibility a bit!
Very frequently used by Freight Operating Companies who routinely activate paths 3 hours before departure time, and then more often than not decide they won't be running today. E.g.:On a similar vein what does 'This service was cancelled at the request of the operator' mean?
SPAD, TPWS brake demand, AWS brake demand, wrong routing, station overrun/underrun, doors opened off platform, dispatch irregularities etc etcHello,
I have seen just this afternoon that several Greater Anglia services are being delayed due to an “Operational Incident”. It is quite a broad term, what sort of things could this supposed incident be?
Sorry, to clarify, I was referring to ‘departing late to maintain customer connections’I mean, isn't every delay technically caused by an 'Operational Incident'?![]()
Does it also get used when nobody knows what the problem is yet? I.e: “Well something happened but damned if I know what it is”
Linking with the thread about electric trains being wrongly routed...Normally "operational incident" means "somebody has done something wrong / something has gone wrong / an error was made" outside of the normal operating rules / requirements.
As I understand it, services can be pre-cancelled in TRUST so that the cancellation only gets reported at the time the service is called/activated (which happens automatically 3 hours prior to departure). It's not that the service gets activated and then the FOC decides to cancel it, but rather that the automatic calling of the service automatically sends out the cancellation message which has been added beforehand.Very frequently used by Freight Operating Companies who routinely activate paths 3 hours before departure time, and then more often than not decide they won't be running today. E.g.:
"Emergency services dealing with an incident" is the usual description for this now.
That’s clearly not what they were doing.Fatality,Spad,Signalling failure,derailment or other safety of the line incident.
Would be a genuine incident not a ‘supposed’ incident as you seem to be insinuating.
Unfortunately the terminology is often used without continuing the statement offering customers advice on what happens next for their journey.The public are not usually given any further info as to what the ‘operational incidents’ are.
I suppose as an ex-railway employee I don’t question it although I must admit to being interested in what’s occurred.Unfortunately the terminology is often used without continuing the statement offering customers advice on what happens next for their journey.
Sort of becomes the opposite, 'not operating' and railway doesn't want to tell you why in customers eyes. So I get why it is often seen as a cover up.
Well technically it was an operational incident, the guard/dispatch staff not noticing the junction route indicator wasn't lit and the driver for accepting the wrong routeLinking with the thread about electric trains being wrongly routed...
SWR described one such instance at Wokingham as an "operational incident" on Twitter and were very coy with anyone asking what had actually happened. Even when a couple of people had replied to the thread with a photo taken from a nearby bridge of the class 458 attempting to break for freedom towards Guildford!
Enjoying your retirement, finally?I suppose as an ex-railway employee I don’t question it although I must admit to being interested in what’s occurred.
Finally lol & yes thank you. Just waited for the two year dispute to be settled else i would've disappeared in 2023/4.Enjoying your retirement, finally?
Nice one. Knew you were wanting to finally push the button a while back. More time for enjoying those ‘Spoons old chap!Finally lol & yes thank you. Just waited for the two year dispute to be settled else i would've disappeared in 2023/4.