martyjon
|
|
« Reply #15 on: February 11, 2018, 22:07:43 » |
|
20:48 Bristol Temple Meads to Weymouth due 23:07
20:48 Bristol Temple Meads to Weymouth due 23:07 will no longer call at Avoncliff, Thornford and Chetnole. This is due to a fault on this train.
Last Updated:11/02/2018 20:20
If this service was operated by a non SDO▸ turbo WHY tell lies to the travelling public, tell them the truth, THE TRAIN FOR THIS SERVICE IS NOT EQUIPPED WITH THE SPECIAL EQUIPMENT NEEDED TO STOP AT THESE STATIONS.
|
|
|
Logged
|
|
|
|
grahame
|
|
« Reply #16 on: February 11, 2018, 22:43:35 » |
|
20:48 Bristol Temple Meads to Weymouth due 23:07
20:48 Bristol Temple Meads to Weymouth due 23:07 will no longer call at Avoncliff, Thornford and Chetnole. This is due to a fault on this train.
Last Updated:11/02/2018 20:20
If this service was operated by a non SDO▸ turbo WHY tell lies to the travelling public, tell them the truth, THE TRAIN FOR THIS SERVICE IS NOT EQUIPPED WITH THE SPECIAL EQUIPMENT NEEDED TO STOP AT THESE STATIONS.
But there IS a fault - it's missing bits that it needs ... I do wonder how often that service actually calls at Chetnole and Thornford even if it can - not exactly a busy time at that remote location and it only calls on request.
|
|
|
Logged
|
Coffee Shop Admin, Chair of Melksham Rail User Group, TravelWatch SouthWest Board Member
|
|
|
martyjon
|
|
« Reply #17 on: February 12, 2018, 10:06:29 » |
|
If this service was operated by a non SDO▸ turbo WHY tell lies to the travelling public, tell them the truth, THE TRAIN FOR THIS SERVICE IS NOT EQUIPPED WITH THE SPECIAL EQUIPMENT NEEDED TO STOP AT THESE STATIONS.
But there IS a fault - it's missing bits that it needs ... NO, there isn't a fault as it was a non SDO turbo. It would have been a fault if it had been modified to a SDO turbo which had developed a fault which was not the case hence the capitalised TRUE reason suggested.
|
|
|
Logged
|
|
|
|
Timmer
|
|
« Reply #18 on: February 12, 2018, 10:11:00 » |
|
Makes you ask the question if the Turbos aren't ready to provide the required service then why are the running on this line instead of a 150/158 that can do the job? Once again it's the passenger inconvenienced at the convenience of the rail operator.
|
|
|
Logged
|
|
|
|
grahame
|
|
« Reply #19 on: February 12, 2018, 10:31:22 » |
|
Makes you ask the question if the Turbos aren't ready to provide the required service then why are the running on this line instead of a 150/158 that can do the job? Once again it's the passenger inconvenienced at the convenience of the rail operator.
Because the 150/1s almost all headed north 10 day ago, and the remaining ones, and the 150/2s are having to run the diagrams they used to cover in Devon and west thereof.
|
|
|
Logged
|
Coffee Shop Admin, Chair of Melksham Rail User Group, TravelWatch SouthWest Board Member
|
|
|
grahame
|
|
« Reply #20 on: February 22, 2018, 08:31:18 » |
|
Update on turbo stopping patterns at short platforms
Stonehouse and Melksham - special arrangements and signage in place and working for services run by turbo trains which do not have SDO▸ installed. Working well - turbo services are NOT missing out these stations, and the extra time taken at the stops is compensated by the running of 90 mph trains on 75 mph schedules.
Avoncliff - where a turbo without SDO is scheduled to stop, the stop is missed. Alternative arrangements - doubling back and an extra stop on another service on the line (trains run every 30 minutes) are available. And many services though there are not (yet) turbo.
Dilton Marsh - as Avoncliff, but a bit easier for arrivals as the stop's only made on request so train crew will know and personally be able to advise.
Chetnole and Thornford - GWR▸ are concentrating their precious few SDO fitted Turbos on this line to minimise the need for skips. Passenger numbers at these two stations are low (and I suspect seasonal), the stops are only "on request", and I suspect that the inconvenience when a skip is made will be to very few people. Mind you - no other trains typically close by to pick up the stops, so this is a low number but high inconvenience disruption.
The daily issue of the 05:17 Gloucester to Southampton terminating and restarting at Westbury makes for a noticeable number of unhappy people who are used to settling down at Swindon / Chippenham for the ride to Warminster / Salisbury and the last thing they want in the middle of their journey is to be turfed out of a nice warm seat and train for exercise via the subway and a cold wait for the arrival of the ongoing service!
|
|
|
Logged
|
Coffee Shop Admin, Chair of Melksham Rail User Group, TravelWatch SouthWest Board Member
|
|
|
phile
|
|
« Reply #21 on: February 22, 2018, 08:52:15 » |
|
Update on turbo stopping patterns at short platforms
Stonehouse and Melksham - special arrangements and signage in place and working for services run by turbo trains which do not have SDO▸ installed. Working well - turbo services are NOT missing out these stations, and the extra time taken at the stops is compensated by the running of 90 mph trains on 75 mph schedules.
Avoncliff - where a turbo without SDO is scheduled to stop, the stop is missed. Alternative arrangements - doubling back and an extra stop on another service on the line (trains run every 30 minutes) are available. And many services though there are not (yet) turbo.
Dilton Marsh - as Avoncliff, but a bit easier for arrivals as the stop's only made on request so train crew will know and personally be able to advise.
Chetnole and Thornford - GWR▸ are concentrating their precious few SDO fitted Turbos on this line to minimise the need for skips. Passenger numbers at these two stations are low (and I suspect seasonal), the stops are only "on request", and I suspect that the inconvenience when a skip is made will be to very few people. Mind you - no other trains typically close by to pick up the stops, so this is a low number but high inconvenience disruption.
The daily issue of the 05:17 Gloucester to Southampton terminating and restarting at Westbury makes for a noticeable number of unhappy people who are used to settling down at Swindon / Chippenham for the ride to Warminster / Salisbury and the last thing they want in the middle of their journey is to be turfed out of a nice warm seat and train for exercise via the subway and a cold wait for the arrival of the ongoing service!
Dilton Marsh is bring missed if there is a non SDO Turbo on a service, and the next Cardiff to Portsmouth calling in lieu
|
|
|
Logged
|
|
|
|
tomL
|
|
« Reply #22 on: March 22, 2018, 13:19:29 » |
|
Not sure if this has been posted elsewhere but I think its worth noting that a more detailed explanation has been posted on JourneyCheck entries with missed stops on Turbos. I’m all for more detailed explanations, even if they are a bit late. 14:38 Westbury to Bristol Parkway due 15:44 14:38 Westbury to Bristol Parkway due 15:44 will no longer call at Avoncliff. This is due to a fault on this train. Additional Information To increase capacity on our Weymouth and Southampton services we are introducing 3 coach Turbo trains. Turbo trains require the fitting of local door controls to allow them to stop at stations with very short platforms. A Turbo train not fitted with these controls cannot call at Avoncliff, Dilton Marsh, Chetnole or Thornford.
Unfortunately it has taken longer than expected to fit the controls and the Turbo train being used on this service today has yet to be fitted.
If you at one of the stations the train is unable to call at please use the help point or contact National Rail Enquiries on 03457 48 49 50 and we will arrange for an additional stop on another train, or alternative road transport if another train cannot be stopped within a reasonable time.
We would like to apologise for the difficulties we know this has caused to your journeys recently.
|
|
|
Logged
|
|
|
|
Alan Pettitt
|
|
« Reply #23 on: March 22, 2018, 14:44:40 » |
|
I have noticed (or not noticed actually) that a regular passenger who usually gets off at Thornford has not been seen on the train over the last few weeks, I do hope that he hasn't given up on train travel due to this "Train Fault".
|
|
|
Logged
|
|
|
|
hassaanhc
|
|
« Reply #24 on: March 27, 2018, 11:18:06 » |
|
And again 06:49 Worcester Shrub Hill to Weymouth due 11:03 06:49 Worcester Shrub Hill to Weymouth due 11:03 will no longer call at Avoncliff, Thornford and Chetnole. This is due to a fault on this train. Additional Information To increase capacity on our Weymouth and Southampton services we are introducing 3 coach Turbo trains. Turbo trains require the fitting of local door controls to allow them to stop at stations with very short platforms. A Turbo train not fitted with these controls cannot call at Avoncliff, Dilton Marsh, Chetnole or Thornford.
Unfortunately it has taken longer than expected to fit the controls and the Turbo train being used on this service today has yet to be fitted.
If you at one of the stations the train is unable to call at please use the help point or contact National Rail Enquiries on 03457 48 49 50 and we will arrange for an additional stop on another train, or alternative road transport if another train cannot be stopped within a reasonable time.
We would like to apologise for the difficulties we know this has caused to your journeys recently. Last Updated:27/03/2018 08:32 11:10 Weymouth to Gloucester due 14:31 11:10 Weymouth to Gloucester due 14:31 will no longer call at Chetnole, Thornford and Avoncliff. This is due to a fault on this train. Additional Information To increase capacity on our Weymouth and Southampton services we are introducing 3 coach Turbo trains. Turbo trains require the fitting of local door controls to allow them to stop at stations with very short platforms. A Turbo train not fitted with these controls cannot call at Avoncliff, Dilton Marsh, Chetnole or Thornford.
Unfortunately it has taken longer than expected to fit the controls and the Turbo train being used on this service today has yet to be fitted.
If you at one of the stations the train is unable to call at please use the help point or contact National Rail Enquiries on 03457 48 49 50 and we will arrange for an additional stop on another train, or alternative road transport if another train cannot be stopped within a reasonable time.
We would like to apologise for the difficulties we know this has caused to your journeys recently. Last Updated:27/03/2018 08:33
|
|
|
Logged
|
|
|
|
WSW Frome
|
|
« Reply #25 on: March 29, 2018, 17:04:41 » |
|
I made my first Turbo 166 journey (in First Group blue/pink livery) from Frome to Weymouth yesterday. On joining I realised I could travel in one of the (former?) First Class seats. The front section in this case was still labelled as First Class and had proper 2+2 table seats. The seats were trimmed in First blue with pink! and half had anti-macassers. Only one other person joined us, the rest being deterred by the signs. A comfortable journey but the air-conditioning was too fierce for "Spring." I did not inspect the rear of the train but are any first class designated areas to remain in the 166s once the trains are refurbished??
My return was on the 20.21 WEY and as usual this was a 3 car 158 finishing its day from the Brighton-Great Malvern circuit. We were delayed on departure awaiting the driver (to become a passenger) from the inbound service arriving slightly late around 20.16. According to RTT» this unit now needs to be placed after arrival in Jersey Siding for the night which was not previous practice. Later I pondered that the likely reason for this is because Plat 1 at WEY only holds 5 cars. So once we have a fully Turbo service, two units cannot be stabled there overnight. Naturally, the likely knock on is that any (shorter) delay in the 20.10 arrival will mean a late departure of the 20.21. A longer delay will mean the driver returns to WSB» ? by road? This is "positive progress" and great customer care.
|
|
|
Logged
|
|
|
|
bradshaw
|
|
« Reply #26 on: April 10, 2018, 09:02:10 » |
|
Three return journeys today are missing Avoncliff, Chetnole and Thornford,
06:49 Worcester Shrub Hill to Weymouth due 11:03 08:41 Gloucester to Weymouth due 12:09 08:45 Bristol Parkway to Westbury due 09:49 11:10 Weymouth to Gloucester due 14:31 13:08 Weymouth to Gloucester due 16:31 16:40 Gloucester to Weymouth due 20:10 This last returns to Westbury at 2021 Since the 0845 Parkway is the return of the 0533 Weymouth that adds another.
|
|
|
Logged
|
|
|
|
WSW Frome
|
|
« Reply #27 on: April 10, 2018, 10:34:54 » |
|
For clarity
The 20.21 WEY departure is formed from the stock of the 19.10 arrival from Great Malvern. I use this train frequently and (at least until recently?) has involved various shunting movements to organise things for the next morning. The use of Turbos now seems to complicate this even more.
The 20.21 is the final leg of a diagram that starts in Portsmouth (to Brighton) and is normally a 3 car 158 (on most weekdays?). The use of a 158 is perhaps likely to continue until, either the diagrams are revised (especially to cover Brighton services) or all the 158s disappear West.
|
|
|
Logged
|
|
|
|
RA
|
|
« Reply #28 on: April 10, 2018, 10:35:36 » |
|
Three return journeys today are missing Avoncliff, Chetnole and Thornford,
06:49 Worcester Shrub Hill to Weymouth due 11:03 08:41 Gloucester to Weymouth due 12:09 08:45 Bristol Parkway to Westbury due 09:49 11:10 Weymouth to Gloucester due 14:31 13:08 Weymouth to Gloucester due 16:31 16:40 Gloucester to Weymouth due 20:10 This last returns to Westbury at 2021 Since the 0845 Parkway is the return of the 0533 Weymouth that adds another.
08:45 from Parkway fortunately swapped out at Bristol for a 2-car class 158 so Avoncliff granted an additional call on that one in lieu of the Weymouth train. Thornford and Chetnole have the indignity of two successive services in each direction failing to call. That is a sizeable gap in the timetable.
|
|
|
Logged
|
|
|
|
bradshaw
|
|
« Reply #29 on: April 10, 2018, 13:35:29 » |
|
On Sunday the last down was cancelled at Westbury, lack of crew. As a result, on Monday, the 0533 Weymouth started at Westbury and an ecs movement ran to Weymouth to form the 0706 up service
|
|
|
Logged
|
|
|
|
|