Explanations - beginner's guides of why trains are not running to timetable

[whole diary]

[grahame]

Journey check has recently been adding explanations of technical issue and, whilst the more experienced of us may give a wry smile and say "surely we all know that" ... actually some of guest readers may not.  I suspect these explanations are prepackages chunks of text - I may be starting a collection here

We've received a report from Network Rail of a track circuit failure at Yeovil Pen Mill.

Track circuits help Signallers know if a section of the track has a train on it. If the track circuit fails, trains need to stop at each affected signal and speak to the Signaller to confirm the track ahead is clear. This can lead to delays, especially if mutliple track circuits have failed.

[Mark A]

Journeycheck's signal to noise ratio isn't good. It feels as though that approach risks boosting the noise.

Mark

[grahame]

Journeycheck's signal to noise ratio isn't good. It feels as though that approach risks boosting the noise.

Mark

I'm not suggesting it for every delay / change. No explanation needed - IMHO^▸ ('in my humble opinion') - as to what "train crew" are, and the explanations for why there aren't enough of them is a well played and worn record which would increase that ratio.

11:48 London Paddington to Carmarthen due 15:28 will be terminated at Swansea.

It will no longer call at Llanelli, Pembrey & Burry Port and Carmarthen.
This is due to a shortage of train crew.

[Mark A]

That made me laugh, thanks! I fear that what we'll get though is interminable repeats of an explanation that includes phrases like 'Track stones' - Network Rail's curious need to provide an expansion for the word 'Ballast'.

Mark