2023 - Train update and amendment log - Swindon <-> Westbury

[whole diary]

[GBM]

06:11 Swindon to Southampton Central due 08:07 will be terminated at Salisbury.
It will no longer call at Romsey and Southampton Central.
It has been delayed at Westbury and is now 36 minutes late.
This is due to a broken down train.

[/quote]
Wonder if this was tied in with 1F01 failure at Romsey, and the subsequent knock on delays.
http://www.firstgreatwestern.info/coffeeshop/index.php?topic=27173.msg330624#msg330624

[grahame]

05:17 Westbury to Swindon due 05:59

05:17 Westbury to Swindon due 05:59 has been previously delayed, is being further delayed at Wootton Bassett Jn and is now expected to be 85 minutes late.
This is due to a points failure.

06:11 Swindon to Southampton Central due 08:07

06:11 Swindon to Southampton Central due 08:07 is being delayed at Swindon and is now expected to be 80 minutes late.
This is due to a points failure

[grahame]

06:35 Salisbury to Cheltenham Spa due 09:03

06:35 Salisbury to Cheltenham Spa due 09:03 has been delayed at Westbury and is now 29 minutes late.
This is due to a points failure.

[grahame]

09:14 Swindon to Westbury due 09:56

09:14 Swindon to Westbury due 09:56 will be starting late from Swindon.
This is due to the train departing late to maintain customer connections.
Further Information

Potentially, a good call.  Connections are more important than being bang on time.  Slight caution flag on TransWilts that a delay at Swindon to maintain connections from London could impact connections at Trowbridge for Bristol and at Westbury for Taunton and beyond, for Salisbury and beyond, and for the line to Weymouth.

[bobm]

Service arrived at Westbury eight minutes late.  As it happened the service to Penzance was also delayed so no problem there nor to Weymouth.  However the connection to Salisbury was lost.

[grahame]

Service arrived at Westbury eight minutes late.  As it happened the service to Penzance was also delayed so no problem there nor to Weymouth.  However the connection to Salisbury was lost.

Thanks for that, Bob - really good example of the complexities.  I would not like to even suggest which was the more important connection to maintain  - the one at Swindon or the one at Westbury.

Westbury "missed" by 4 minutes ... the Salisbury train left on time, and was 2 minutes early terminating there.   That left 12 minutes there for people to connect to the next departure which was a bus to Southampton.  Wonderful hindsight suggest that a hold of the Salisbury train at Westbury like the Westbury one was held at Swindon would have created a delay which worked its way out of the system very quickly, but hindsight is marvellous stuff that always comes too late.


No miss at Trowbridge - there wasn't a connection there in the first place, with a Cardiff train timetabled to leave there a minute before the train from Swindon arrived.

[TaplowGreen]

Cancellations to services between Westbury and Chippenham via Melksham

Due to the emergency services dealing with an incident near the railway between Westbury and Trowbridge all lines are blocked. Disruption is expected until 15:00 15/02.

Train services between Westbury and Chippenham via Melksham may be cancelled or delayed.

[grahame]

14:16 Westbury to Swindon due 15:01
 
14:16 Westbury to Swindon due 15:01 will be terminated at Chippenham.
It will no longer call at Swindon.
It has been previously delayed, has been further delayed between Trowbridge and Melksham and is now 23 minutes late.
This is due to a fault on this train.

15:14 Swindon to Westbury due 15:58

15:14 Swindon to Westbury due 15:58 will be cancelled.
This is due to a fault on this train.

[bobm]

Problems caused by an incident at a bridge just north of Trowbridge Station

https://www.wiltshire999s.co.uk/999-crews-scrambled-trowbridge-found-bridge/

[grahame]

Problems caused by an incident at a bridge just north of Trowbridge Station

https://www.wiltshire999s.co.uk/999-crews-scrambled-trowbridge-found-bridge/

For record
12:17 Westbury to Swindon cancelled
13:15 Swindon to Westbury cancelled

Reason code XA - "trespass" which I suppose is as accurate as they have available if you read the article.

[TaplowGreen]

16:25 Westbury to Swindon due 17:08
16:25 Westbury to Swindon due 17:08 has been cancelled.
This is due to train crew being delayed by service disruption.

17:36 Swindon to Westbury due 18:20
17:36 Swindon to Westbury due 18:20 will be cancelled.
This is due to train crew being delayed by service disruption.

[grahame]

09:45 Swindon to Salisbury due 11:06

09:45 Swindon to Salisbury due 11:06 will be diverted between Chippenham and Trowbridge.
It will no longer call at Melksham.
This is due to congestion.

Short term - if it's congested - why not stop something that's causing the congestion there??

Long term - if it's congested - why not put in an extra loop and signals - it was originally double track broad gauge after all!

[ChrisB]

Broken down train causing the congestion?

[grahame]

Broken down train causing the congestion?

Maybe - except that the Berks and Hants is closed through Newbury and Pewsey today with oodles of diverted trains passing through Melksham, and the ONLY train that Journeycheck flagged up as being "congested" off the line was the local one, nothing else delayed, short run or cancelled.  Circumstantial evidence suggests to me that it's not a broken down train - rather trying to fit a quart into a pint pot, and the casualty of that failing, as usual, is a cancellation of service(s) at Melksham.

[bobm]

The 08:44 from London Paddington to Plymouth was booked to operate via Melksham due to the engineering works on the Berks & Hants.  However it left London 17 minutes late due to crew issues.  That meant it was going to conflict with the TW service on the single line.