Conflicting Headcodes

[DR18037]

5L49 ended up being duplicated at Cambridge tonight as at 20:02, 5L49 [Hornsey E.M.U.D. to Norwich Cpt.] was passing through. Meanwhile 5L49 [Cambridge - Cambridge T&R.S.M.D.] was departing into the depot after coming off of 1L49 [Birmingham - Cambridge]. What are the repercussions of this mishap, if it is even considered a mishap. Of course I have full faith that the signaller on the PSB took extra care to not accidentally send a Cross Country 170 to Norwich, but someone behind the scenes must be red in the face surely?

 

[WAB]

If anyone spotted it, there might be an entry in the control log so the relevant planner can be advised. I doubt there would be any repercussions in any case when there's no wrong-routing.

 

[norbitonflyer]

There is, somewhere on another thread, a report of a similar coincidence at Redhill not long ago

 

[LA50041]

5L49 ended up being duplicated at Cambridge tonight as at 20:02, 5L49 [Hornsey E.M.U.D. to Norwich Cpt.] was passing through. Meanwhile 5L49 [Cambridge - Cambridge T&R.S.M.D.] was departing into the depot after coming off of 1L49 [Birmingham - Cambridge]. What are the repercussions of this mishap, if it is even considered a mishap. Of course I have full faith that the signaller on the PSB took extra care to not accidentally send a Cross Country 170 to Norwich, but someone behind the scenes must be red in the face surely?

Looks like different operators using the same headcode, so this should really have been picked up by Network Rail as part of the validation process but was obviously missed.

 

[Wilts Wanderer]

AFAIK its not an operational incident per-se, but potentially leaves the door open to one occurring if something else happens while both trains are on the same signalling area/panel/workstation etc. Just a timetable error that needs correcting at the first practical opportunity.

 

[172007]

if its the same Network Rail route which in think it is then the second train to register with the GSMR (in-cab cell phonel) won't register and that driver will end up using a wild card after speaking to the signaller.

Not sure what other ramifications this has on a duplicate except i am guessing if Network Rail regional control try to contact the that train then the GSMR may throw am error or end up with an odd confusing group call.

*no clue why this is in bold, sorry.