Found it. 1V91 1436 from Newcastle on Friday 25th May.
I don't suppose for a minute that the wrong route was set.
Maybe suppose a bit longer.
Wrong route set at Ferrybridge North for its booked diversion avoiding Doncaster. Was mistakenly routed to Doncaster. Both Network Rail and CrossCountry reported that internally. Driver accepted the wrong route and took it.
I'd say that is both driver and signaller error. Drivers are trained to be situationally aware of such possibilities and are meant to stop and inform if the wrong route is set.
According to another forum, the driver signed the route mistakenly taken but the guard didn't.
Well, the obvious reaction to that (apart from noting the amount of confusion still present) is that flagging the cause as "
TOC▸ Driver" seems wrong. The primary error was the signalling one, and any lack of vigilance by the driver is only a secondary matter. However, there is an official ruling on this, in the Delay Attribution Guide:
4.8.6 In the event of the route being set for an incorrect route that is not a booked diversionary route, or would involve a missed station for which prior advice of diversion had not been received, the Driver is expected to advise the Signaller at the junction signal controlling the junction, or if not possible to stop in time safely, at or before the next signal. In the event of the Driver not stopping and contacting the signalman at the appropriate point, a second incident should be created coded TG/T##* or FP/F##* and any delays divided equally between the two incidents.
Of course this incident doesn't quite fit that. It's not a delay issue, but the guide does cover "reliability events" such as cancellations. If the route taken had been viable, it would actually have restored the call at Doncaster due to be missed. (There probably isn't a specific code for that, though.) I think, from the record, Doncaster station was still closed by a trespass incident at the time, so the diversion was still needed.
In terms of time taken, stopping before the divergence would eliminate most of the delay, so maybe splitting it equally is fair after all. And a short delay is much less likely to lead to a cancellation, so you can see a justification of sorts for hanging that round the driver's neck - though it does still look harsh. Finally, can you divide a cancellation between two incidents and two causes? Maybe you can in the complete form-to-be-filled-in, but not in the brief version visible in
RTT» .
Click on the map to explore geographics
