Cancelled 'due to a delay on a non-Network Rail line'

[TUC]

The 1745 Reading-Newcastle on 21 November was cancelled as far as Birmingham New Street due to what is described on RTT as being 'a delay on a non-Network Rail line'.

Anyone know what this may relate to?

 

[Mcr Warrior]

Had the XC train in question been in some depot?

 

[norbitonflyer]

I can only think of fallout from a problem in the Crossrail Core somehow affecting other services to/from/through Reading.

 

[Whistler40145]

The 1745 Reading-Newcastle on 21 November was cancelled as far as Birmingham New Street due to what is described on RTT as being 'a delay on a non-Network Rail line'.

Anyone know what this may relate to?

The inbound service from Newcastle was terminated at Birmingham New Street

 

[voyagerdude220]

The inbound service from Newcastle was terminated at Birmingham New Street

You're correct.
Trust confirms the "real" reason for the cancellation being no Driver.

 

[800001]

You're correct.
Trust confirms the "real" reason for the cancellation being no Driver.

Maybe driver delayed on Metro on way to work.

 

[mrcheek]

This sounds altogether more like someone input the wrong code!

 

[Whistler40145]

The service lost time enroute from Newcastle and arrived in Birmingham New Street approximately 32 minutes late

 

[norbitonflyer]

Maybe driver delayed on Metro on way to work.

If he was coming on duty at reading, he may have been delayed on the Liz Line by a problem in the core

 

[Horizon22]

RTT does not always accurately transfer real delay reasons over.

 

[Whistler40145]

If he was coming on duty at reading, he may have been delayed on the Liz Line by a problem in the core

The train didn't work to Reading, so never returned to Birmingham New Street

 

[185]

Guessing as mentioned above this was yet another mis-typed attribution, unless Crosscountry control had it diverted via the Lagos red line. This happens a lot.

 

[Stephen42]

Guessing as mentioned above this was yet another mis-typed attribution, unless Crosscountry control had it diverted via the Lagos red line. This happens a lot.

It looks that way. One of the annoying quirks of the open data TRUST feed is that it only provides the reason when cancelled with no clear method of communicating subsequent corrections to the cancellation reasons. Means that even if the error is spotted within minutes it is present for days on the various sites relying on Network Rail open data feeds.

 

[Towers]

Utter nonsense explanation; not only is it meaningless word soup but who amongst the travelling public gives a toss whether a delay is on an NR line or a “non-NR” line

 

[Horizon22]

Utter nonsense explanation; not only is it meaningless word soup but who amongst the travelling public gives a toss whether a delay is on an NR line or a “non-NR” line

It's also not a Darwin delay reason, so RTT is translating into something that never would have been passenger-facing.

 

[Towers]

It's also not a Darwin delay reason, so RTT is translating into something that never would have been passenger-facing.

Glad to hear that!

 

[Jimini]

Conversely, TfL are always happy to point the finger at NR on their disruption statuses where appropriate!

 

[Horizon22]

Conversely, TfL are always happy to point the finger at NR on their disruption statuses where appropriate!

Fed up of being blamed for NR asset failures! Often see this on Overground and Bakerloo line statuses, although surprisingly less so Elizabeth line.

 

[Jimini]

Fed up of being blamed for NR asset failures! Often see this on Overground and Bakerloo line statuses, although surprisingly less so Elizabeth line.

Aye, understandable, particularly on the bit I use the most between Richmond and Gunnersbury where problems tend to be relatively frequent!