Operational incident between Salisbury and Gillingham

[whole diary]

[bradshaw]

Reported by SWR^» (South Western Railway - about) this morning.

Due to an operational incident earlier today between Gillingham Dorset and Salisbury all lines are blocked.
What's Going On:
Train services running through these stations may be delayed or revised. Disruption is expected until 16:00 24/08.
What We're Doing About It:
Our control centre have received reports of an operational incident meaning that we are currently unable to run trains between Yeovil Junction and Salisbury.
The incident is currently being investigated.
This issue may cause services to be delayed, or revised at short notice. Trains are currently unable to call at Sherborne, Templecombe, Gillingham or Tisbury as trains are being diverted via Westbury.

The 1L11 RDG^▸ (Rail Delivery Group, or Reading station, depending on context) - Gillingham was turned back at Tisbury Loop; 1L13 WAT-EXD^» (Exeter St Davids - next trains) last reported at Wilton Jn and 1L28 seems to have been held at Gillingham.

The phrase operational incident is ominous, rather than a points failure - which was the first journey check comment earlier today.

[SandTEngineer]

Usually that means a SPAD^▸ (Signal Passed At Danger - very bad!) Incident.

[stuving]

IL28 is being shown in RTT^» (Real Time Trains - website) as:
"This service was cancelled between Gillingham (Dorset) and London Waterloo due to an error having been made (OC)."
And the guide lists that code thus:
code:OC
cause: Signaller, including wrong routing and wrong ETCS^▸ (European Train Control System)/ ERTMS^▸ (European Rail Traffic Management System. A future railway signalling system, with equipment located in the driver's cab, rather than lineside) instruction

That's also shown for 1L26 (EXD^» (Exeter St Davids - next trains)-RDG^▸ (Rail Delivery Group, or Reading station, depending on context)), due through at 08:11. It's hard to see more than that, as even those trains that ran through were not reported between Pinhoe and Tisbury this morning. 1L26 is shown as running 36 late Tisbury to Salisbury and being cancelled from there on.

[Louis94]

Points were ran through at Gillingham. 1L26 was cautioned past a signal at red and the points at the Tisbury end of the loop were set incorrectly.

[bradshaw]

There seem to be more faults than one would expect at Tisbury loop. Over the past few months it seems to have been the most problematical section of the route.