Train Graphic
Great Western Passengers' Forum Great Western Coffee Shop - [home] and [about]
Read about the forum [here].
Register and contribute [here] - it's free.
 today - Friends of Bridgwater Station
today - TW NorthWest / Liverpool
22/10/2018 - ACoRP board nominations close
29/10/2018 - Avocet line AGM
30/10/2018 - Minehaed Rail Link Group
31/10/2018 - CCIF Applications close
Random Image
Train Running @GWR Twitter Acronyms/Abbreviations Station Comparator Rail News GWR co. site Site Style 1 2 3 4 Chat on off
October 18, 2018, 05:28:33 pm *
Welcome, Guest. Please login or register.

Login with username, password and session length
Forgotten your username or password? - get a reminder
Most liked recent subjects
[148] Isambird Kingdom Brunowl
[125] Andrew Haines speaking yesterday (16/10)
[69] Temple Meads ranked one of the worst stations in UK for punctu...
[55] Infrastructure problems in Thames Valley causing disruption el...
[29] Getting Electrification Right
[12] BBC Radio Devon 17/10
News: A forum for passengers ... with input from rail professionals welcomed too
 
   Home   Help Search Calendar Login Register  
Pages: 1 ... 21 22 [23] 24 25 ... 39
  Print  
Author Topic: 2018 cancellation and amendment log  (Read 28990 times)
bobm
Administrator
Hero Member
*****
Posts: 6957



View Profile
« Reply #330 on: July 11, 2018, 10:41:57 am »

Have you asked GWR? As you know the reason given for delays/cancellations/alterations etc often has very little to do with reality.

Asking more out of interest in case anyone might know.  Further though suggests it might be a crew issue - either a need to swap over crew on the way at Bristol (hence the stop) or a route knowledge issue.

For the engineering works, we requested GWR to help local traffic by stopping a couple of the west country expresses that run via the TransWilts and have 'allowances' built into their schedules.  Very selective and careful requests, but "not possible" for reasons I'm not totally clear on.   At least that denial means we don't have a "real" cancellation today!

This has now appeared under Additional Information on JourneyCheck


Quote
Additional Information
Due to a timetabling conflict on the single track line between Westbury and Chippenham, it is not possible to run this train via Westbury this morning without causing significant delay to multiple services in the Westbury area. In order to minimise the impact to as few customers as possible the decision has been taken to divert this train away from its originally timetabled route. As such the train will not be able to stop at Westbury. This alteration is expected to apply all week.

The cause of this timetabling conflict is still being investigated.

Customers due to travel from Westbury to Reading and London Paddington are advised to travel on the 11:10 Westbury to Cardiff Central service, and change at Bath Spa for onward rail connections to Reading and London.

Customers travelling to Westbury are advised to change at Bristol Temple Meads and travel on the 11:22 Bristol Temple Meads to Portsmouth (via Westbury) service.

Customers who arrive at their destination more than 60 minutes after originally scheduled as a result of this alteration may be eligible for delay compensation. Please retain tickets and visit the GWR website for further details.

According to RTT the train ran via Bristol yesterday (but didn't call) but did run via Westbury on Monday.
Logged
martyjon
Transport Scholar
Hero Member
******
Posts: 1163


View Profile
« Reply #331 on: July 11, 2018, 10:47:56 am »

06:47 Penzance to London Paddington due 13:00
06:47 Penzance to London Paddington due 13:00 will be diverted between Taunton and Reading.
It will no longer call at Westbury but will call additionally at Bristol Temple Meads.
This is due to a problem currently under investigation.
Last Updated:11/07/2018 05:07

Now a fuller explanation ;-

Additional Information
Due to a timetabling conflict on the single track line between Westbury and Chippenham, it is not possible to run this train via Westbury this morning without causing significant delay to multiple services in the Westbury area. In order to minimise the impact to as few customers as possible the decision has been taken to divert this train away from its originally timetabled route. As such the train will not be able to stop at Westbury. This alteration is expected to apply all week.

The cause of this timetabling conflict is still being investigated.

Customers due to travel from Westbury to Reading and London Paddington are advised to travel on the 11:10 Westbury to Cardiff Central service, and change at Bath Spa for onward rail connections to Reading and London.

Customers travelling to Westbury are advised to change at Bristol Temple Meads and travel on the 11:22 Bristol Temple Meads to Portsmouth (via Westbury) service.

Customers who arrive at their destination more than 60 minutes after originally scheduled as a result of this alteration may be eligible for delay compensation. Please retain tickets and visit the GWR website for further details.

Logged
bobm
Administrator
Hero Member
*****
Posts: 6957



View Profile
« Reply #332 on: July 11, 2018, 07:16:01 pm »

This certainly does count as a cancellation....

Quote
19:15 Frome to Cheltenham Spa due 21:33

19:15 Frome to Cheltenham Spa due 21:33 will no longer call at Melksham.
This is due to congestion.
Logged
grahame
Administrator
Hero Member
*****
Posts: 22105



View Profile WWW Email
« Reply #333 on: July 11, 2018, 07:38:58 pm »

This certainly does count as a cancellation....

Quote
19:15 Frome to Cheltenham Spa due 21:33

19:15 Frome to Cheltenham Spa due 21:33 will no longer call at Melksham.
This is due to congestion.


or does it?

Quote
19:15 Frome to Cheltenham Spa due 21:33
19:15 Frome to Cheltenham Spa due 21:33 is now running as scheduled.
Last Updated:11/07/2018 19:34

Yes,  in my view that counts as a cancellation.   Having told people "find another way" ... to turn it back on after i was due to set out ....
Logged

Coffee Shop Admin, Member of Melksham Rail User Group, on the board of TravelWatch SouthWest and some more things besides
bobm
Administrator
Hero Member
*****
Posts: 6957



View Profile
« Reply #334 on: July 11, 2018, 07:39:07 pm »

..and again re-instated!
Logged
martyjon
Transport Scholar
Hero Member
******
Posts: 1163


View Profile
« Reply #335 on: July 12, 2018, 06:44:31 am »

06:47 Penzance to London Paddington due 13:00
06:47 Penzance to London Paddington due 13:00 will be diverted between Taunton and Reading.
It will no longer call at Westbury but will call additionally at Bristol Temple Meads.
This is due to a problem currently under investigation.
Last Updated:11/07/2018 05:07
Now a fuller explanation ;-

Additional Information

Due to a timetabling conflict on the single track line between Westbury and Chippenham, it is not possible to run this train via Westbury this morning without causing significant delay to multiple services in the Westbury area. In order to minimise the impact to as few customers as possible the decision has been taken to divert this train away from its originally timetabled route. As such the train will not be able to stop at Westbury. This alteration is expected to apply all week.

The cause of this timetabling conflict is still being investigated.

Customers due to travel from Westbury to Reading and London Paddington are advised to travel on the 11:10 Westbury to Cardiff Central service, and change at Bath Spa for onward rail connections to Reading and London.

Customers travelling to Westbury are advised to change at Bristol Temple Meads and travel on the 11:22 Bristol Temple Meads to Portsmouth (via Westbury) service.

Customers who arrive at their destination more than 60 minutes after originally scheduled as a result of this alteration may be eligible for delay compensation. Please retain tickets and visit the GWR website for further details.

Again today, why investigate today what we already knew yesterday.
Logged
bobm
Administrator
Hero Member
*****
Posts: 6957



View Profile
« Reply #336 on: July 12, 2018, 07:36:58 am »

Quote
07:21 Westbury to Swindon due 08:05

07:21 Westbury to Swindon due 08:05 will be cancelled.
This is due to the fire alarm sounding in a signalbox earlier today.

Quote
08:28 Swindon to Westbury due 09:14

08:28 Swindon to Westbury due 09:14 will be cancelled.
This is due to the fire alarm sounding in a signalbox earlier today.

Additional Information
Customers at Swindon and Chippenham travelling to Trowbridge or Westbury should travel on the 09:01 Bristol Temple Meads service from Swindon (09:15 from Chippenham) and change at Bath Spa for the 09:36 service towards Portsmouth Harbour which calls at Trowbridge (09:54) and Westbury (10:01).

Customers travelling to Melksham should change at Chippenham and speak to station staff.

Customers at Melksham will be provided road transport from the station car park.
Logged
grahame
Administrator
Hero Member
*****
Posts: 22105



View Profile WWW Email
« Reply #337 on: July 12, 2018, 07:45:46 am »

Quote
07:21 Westbury to Swindon due 08:05

07:21 Westbury to Swindon due 08:05 will be cancelled.
This is due to the fire alarm sounding in a signalbox earlier today.

Quote
08:28 Swindon to Westbury due 09:14

08:28 Swindon to Westbury due 09:14 will be cancelled.
This is due to the fire alarm sounding in a signalbox earlier today.

There are only two trains cancelled across the whole of the GWR area.   Why should incidents such as this have such a narrow effect?   Melksham Box closed in the 1960s, and Bradford Junction box in 1990. Thingley was gone around that time too.
Logged

Coffee Shop Admin, Member of Melksham Rail User Group, on the board of TravelWatch SouthWest and some more things besides
grahame
Administrator
Hero Member
*****
Posts: 22105



View Profile WWW Email
« Reply #338 on: July 12, 2018, 08:08:01 am »

There are only two trains cancelled across the whole of the GWR area.   Why should incidents such as this have such a narrow effect?   Melksham Box closed in the 1960s, and Bradford Junction box in 1990. Thingley was gone around that time too.

Further report suggests it's Westbury panel box where the alarms went off - all signals back to danger / all trains stopped while they investigated.    Source currently believed to be external to railway - Westbury is / was "blanketed in smoke from Salisbury Plain where the army have been carrying out an exercise".
Logged

Coffee Shop Admin, Member of Melksham Rail User Group, on the board of TravelWatch SouthWest and some more things besides
stuving
Transport Scholar
Hero Member
******
Posts: 3389


View Profile
« Reply #339 on: July 12, 2018, 09:24:50 am »

There are only two trains cancelled across the whole of the GWR area.   Why should incidents such as this have such a narrow effect?   Melksham Box closed in the 1960s, and Bradford Junction box in 1990. Thingley was gone around that time too.

Further report suggests it's Westbury panel box where the alarms went off - all signals back to danger / all trains stopped while they investigated.    Source currently believed to be external to railway - Westbury is / was "blanketed in smoke from Salisbury Plain where the army have been carrying out an exercise".

It's not just the exercises per se, but the army have set fire to the plain itself. The report talks about smoke spreading to Steeple Ashton, Trowbridge, Bradford on Avon, Frome, Shepton Mallet and Wells

Standard policy is not to attempt fire-fighting on live firing ranges, for obvious reasons. However this may have consequences that haven't been through through, such as "in very dry weather, don't do exercises likely to ignite vegetation".
Logged
Timmer
Global Moderator
Hero Member
*****
Posts: 4786


View Profile
« Reply #340 on: July 12, 2018, 11:31:20 am »


It's not just the exercises per se, but the army have set fire to the plain itself. The report talks about smoke spreading to Steeple Ashton, Trowbridge, Bradford on Avon, Frome, Shepton Mallet and Wells

Standard policy is not to attempt fire-fighting on live firing ranges, for obvious reasons. However this may have consequences that haven't been through through, such as "in very dry weather, don't do exercises likely to ignite vegetation".
It's been absolutely awful at times these past two weeks whenever the wind comes in from the east. The fire brigade cannot intervene and would be dangerous for them to do so as it's MOD land.

I totally support the army doing training exercises whatever the weather but using live ammunition when the ground is tinder dry is not a good idea. Causing many people issues with smoke when we've got to have our windows open because it's so warm.
Logged
bobm
Administrator
Hero Member
*****
Posts: 6957



View Profile
« Reply #341 on: July 12, 2018, 11:33:50 am »

Yes the MOD advice on Twitter for affected residents to stay indoors and close windows and doors provoked a predictable, and very understandable, response.
Logged
Clan Line
Full Member
***
Posts: 70



View Profile
« Reply #342 on: July 12, 2018, 12:04:53 pm »


Standard policy is not to attempt fire-fighting on live firing ranges, for obvious reasons. However this may have consequences that haven't been through through, such as "in very dry weather, don't do exercises likely to ignite vegetation".

Any sort of Military exercise where things "go wrong" are of much more use than one where everything goes like clockwork. This is when we might actually find out that our optical equipment, on our guns/tanks, doesn't work very well in grass smoke - despite the manufacturer saying that it would !
Are we to assume that a potential enemy would only attack when vegetation wont catch fire; or when it's not muddy ? I seem to recollect one adversary setting fire to all the oil wells - our forces couldn't see a thing !!  I bet we never thought of that one in advance - now, had there been oil wells around Imber.........who knows ?
I know it's not very pleasant - I have just shut my windows - but are our armed forces expected to train only when there is absolutely no possibility of  "upsetting the neighbours" ?  For a few days every 20 years - surely not that unreasonable ?
Logged
bobm
Administrator
Hero Member
*****
Posts: 6957



View Profile
« Reply #343 on: July 12, 2018, 12:10:47 pm »

I don't think the majority of people would disagree with you.  I think people were more incensed that having set fire to the heathland it was left to burn over last weekend after training had been suspended.  Clearly fire fighting on foot was not an option but many have suggested dropping water from the air.  Who knows that could form a basis for different training which could then be put to use on places like Saddleworth Moor where the forces were recently drafted in.
Logged
Timmer
Global Moderator
Hero Member
*****
Posts: 4786


View Profile
« Reply #344 on: July 12, 2018, 12:17:28 pm »

MOD have recently tweeted:
https://twitter.com/mod_dio
We have reviewed the risks of continuing live firing on Salisbury Plain training area and have made the decision to cease artillery live firing on the Salisbury Plain training area until further notice.  We will continue to monitor the situation and share updates.
Logged
Do you have something you would like to add to this thread, or would you like to raise a new question at the Coffee Shop? Please [register] (it is free) if you have not done so before, or login (at the top of this page) if you already have an account - we would love to read what you have to say!

You can find out more about how this forum works [here] - that will link you to a copy of the forum agreement that you can read before you join, and tell you very much more about how we operate. We are an independent forum, provided and run by customers of Great Western Railway, for customers of Great Western Railway and we welcome railway professionals as members too, in either a personal or official capacity. Views expressed in posts are not necessarily the views of the operators of the forum.

As well as posting messages onto existing threads, and starting new subjects, members can communicate with each other through personal messages if they wish. And once members have made a certain number of posts, they will automatically be admitted to the "frequent posters club", where subjects not-for-public-domain are discussed; anything from the occasional rant to meetups we may be having ...

 
Pages: 1 ... 21 22 [23] 24 25 ... 39
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.2 | SMF © 2006-2007, Simple Machines LLC Valid XHTML 1.0! Valid CSS!
This forum is provided by a customer of Great Western Railway (formerly First Great Western), and the views expressed are those of the individual posters concerned. Visit www.gwr.com for the official Great Western Railway website. Please contact the administrators of this site if you feel that the content provided by one of our posters contravenes our posting rules (email link). Forum hosted by Well House Consultants