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

Unusual delay reason shown on departure board

Status
Not open for further replies.

Krokodil

Established Member
Joined
23 Jan 2023
Messages
6,598
Location
Wales
You don't just press the uncouple button 'by accident'. To accidentally uncouple you'd need to go into the coupled cab, key in, cancel the AWS, set the desk up correctly and then press the uncouple button (and on modern units such as 195s and I suspect 80x the train will automatically recouple if not moved apart a certain amount of time since they were uncoupled). You don't just accidentally push a button from the front cab and leave a unit behind on the move!
When I first read the message (before scrolling down for context), my first assumption wasn't "train divided", more that someone had uncoupled a pair of units that weren't due to be split, or whatever. I've certainly seen instances where drivers have uncoupled a late-running train that had fallen into the path of the one they were supposed to be splitting (that caused a few please-explains). Alternatively it could have been "delay while detaching a unit", 15x sometimes take quite a few attempts which might lose a path.

None of these turned out to be the case here of course.

I do remember a driver who used to be with Northern telling me that they had a 142 where the "uncouple" pin and the "notch 5" pin had become transposed. So that when the train accelerated through the Edge Hill Tunnels the rear unit would detach itself. I hope that as soon as this was discovered someone was sent quickly with "non-multi" signs.

Indeed, but in this case the PIS was set (whether manually or by default) to replace it with a message that sounds potentially a little less dramatic.
"A broken down freight train" would have been better. Easier for a layman to understand and tells them as much as they need to know.

That one will be ‘an unusually large passenger flow’, it’s just the word ‘flow’ has been cut off.

Most TOCs are using newer delay reasons with the equivalent reason for this being ‘overcrowding’.
I was glad when this change happened. It always irked me that there were TDA codes covering overcrowding due to a special event, unusually high footfall, or disruption; yet there was no code for "overcrowding because it's always overcrowded at this time on a Saturday". At least they're now admitting that overcrowding is normal, rather than it being considered unusual.
 
Sponsor Post - registered members do not see these adverts; click here to register, or click here to log in
R

RailUK Forums

Spartacus

Established Member
Joined
25 Aug 2009
Messages
3,836
"A broken down freight train" would have been better. Easier for a layman to understand and tells them as much as they need to know.

Agreed.

I was glad when this change happened. It always irked me that there were TDA codes covering overcrowding due to a special event, unusually high footfall, or disruption; yet there was no code for "overcrowding because it's always overcrowded at this time on a Saturday". At least they're now admitting that overcrowding is normal, rather than it being considered unusual.

That'd just be RB, station overtime caused by passenger volumes boarding and alighting, no causal incident identified. Of course what the platform systems might say is another matter...
 

Krokodil

Established Member
Joined
23 Jan 2023
Messages
6,598
Location
Wales
That'd just be RB, station overtime caused by passenger volumes boarding and alighting, no causal incident identified. Of course what the platform systems might say is another matter...
There's a code for short-forms, but no code for "the service was never planned with enough carriages in the first place, and never is".
 

Efini92

Established Member
Joined
14 Dec 2016
Messages
2,137
It appears the issue was on a freight train.

No, nothing at all like that... If you don't really have a clue probably best not commenting something completely wrong!
Ha ha that reminds me of a trainee driver a few years ago who thought pressing uncouple in the leading end would split the units.
 

Krokodil

Established Member
Joined
23 Jan 2023
Messages
6,598
Location
Wales
Ha ha that reminds me of a trainee driver a few years ago who thought pressing uncouple in the leading end would split the units.
That would actually be quite a useful feature. Saves the leading driver keying out, waiting for whoever is splitting it to key in and do so (assuming that he doesn't have to walk back and do it himself), and then setting the cab back up again (particularly if ERTMS is involved).
 

Efini92

Established Member
Joined
14 Dec 2016
Messages
2,137
That would actually be quite a useful feature. Saves the leading driver keying out, waiting for whoever is splitting it to key in and do so (assuming that he doesn't have to walk back and do it himself), and then setting the cab back up again (particularly if ERTMS is involved).
What happens when you have more than 2 units?
 
Status
Not open for further replies.

Top