Problems caused by an XC Voyager today, 16/10.

[Mugby]

The 0900 Leeds to Bristol XC service this morning (220022) departed on time but was terminated at Derby 146 mins. late. Apparently 'Problem with traction equipment'

There were two bottlenecks where the delay accumulated considerably: between Masborough and Nunnery and between Dore South and Dronfield.
There seems to have been quite an extensive knock-on effect causing delays to other services, one Northern Nottingham service was terminated at Chesterfield.

Does anyone have any further details? Were any diversions put in place to mitigate the delays?

 

[skyhigh]

There was nothing wrong with the 220.

The service was initially delayed by a fault on 2N01 at Outwood. It was then further delayed by a points failure at Holmes Junction, which meant it had to set back to Aldwarke and then divert via Rotherham. It was then stuck behind 1Y21 which came to a stand at Dronfield due to an engine fault. This turned out to be an oil leak so it limped forward to Chesterfield where it terminated.

Very unfortunate to be caught up in 3 separate incidents.

 

[Adam0984]

2N01 had a big oil leak which lead to masses of smoke from one engine which then engulfed both saloons.

It terminated at Outwood and ran ECS back to Neville Hill via Wakefield Westgate with passengers picked up by 2A63 behind and taken to Wakefield Westgate.

As above 1A50 got to Holmes Jcn and sat there, then set back onto the Thrybergh line and went to Sheffield via Rotherham and Tinsley.

Then to top it all off got stuck behind 1Y21.

I'd imagine the delay bill will be huge for northern.

The conductor was stuck on 1A50 for 1Y18 Sheffield to Carlisle which ended up being about an hour late all the way to Carlisle despite being diverted between Sheffield and Leeds via Moorthorpe, but got stuck behind 2B08 Donny to Leeds, then stuck behind the 1216 Leeds to Skipton, so made no time up