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 - Removal of Severn Bridge Tolls
22/12/2018 - Christmas service changes
04/01/2019 - Look forward - 2019 Severnside
07/01/2019 - JSP consultation closes
10/01/2019 - CHRUG
14/01/2019 - TWSW Board
Random Image
Train Running @GWR Twitter Acronyms/Abbreviations Station Comparator Rail News GWR co. site Site Style 1 2 3 4 Chat on off
December 17, 2018, 10:59:08 am *
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
[126] Santa's Melksham Christmas Fruit Machine
[99] XC Dawlish cancellations now beyond a joke!
[81] Closure of Old Oak Common (81A) December 2018
[76] Advent quiz 2019
[70] JourneyCheck ... reasons given
[46] Tube travel linked to the spread of flu-like illnesses
News: A forum for passengers ... with input from rail professionals welcomed too
 
   Home   Help Search Calendar Login Register  
Pages: 1 ... 49 50 [51] 52 53
  Print  
Author Topic: Cotswold Line - 2018 cancellation and amendments log  (Read 61278 times)
Richard Fairhurst
Global Moderator
Hero Member
*****
Posts: 705


View Profile Email
« Reply #750 on: November 28, 2018, 05:46:08 pm »

Following Halts service unsurprisingly rammed.

It would help if the tannoy announcement that “to alight at Hanborough, you must be in the rear three coaches” was made before the train had stopped...
Logged
charles_uk
Hero Member
*****
Posts: 423

thewalkingpage
View Profile
« Reply #751 on: November 29, 2018, 05:08:24 pm »

Looks like the halts service is going to be rammed again:

Quote
15:50 London Paddington to Moreton-in-Marsh due 17:26 was terminated at Reading.
It will no longer call at Oxford, Hanborough, Charlbury, Kingham and Moreton-in-Marsh.
This is due to a fault on this train.
Last Updated:29/11/2018 16:32

By my reckoning, that's the 37th time this year this train has failed to run through to Moreton-in-Marsh. It must be so frustrating for those who use this service (ir)regularly.

[edit to remove duplicate words]
« Last Edit: November 29, 2018, 05:43:18 pm by charles_uk » Logged
charles_uk
Hero Member
*****
Posts: 423

thewalkingpage
View Profile
« Reply #752 on: November 29, 2018, 05:15:04 pm »

And whilst I'm here, I've just picked up that it wasn't a great morning service either:

The 04:47 Hereford to Paddington "was cancelled between Worcester Shrub Hill and London Paddington due to the train operator's request (TB)"

And the following 05:28 HFD:PAD was 34 late by Oxford and 33 late into Paddington. The 07:10 Moreton-in-Marsh to Paddington ran on time but, I suspect, might have been quite cosy on board.
Logged
IndustryInsider
Hero Member
*****
Posts: 6842


View Profile
« Reply #753 on: November 30, 2018, 08:18:51 am »

The 04:47 HFD-PAD was cancelled at Wos due to engine problems on the HST.  Both following services are 9-car IETs so hopefully managed to cope ok.
Logged

To view my cab run over the new Reading Viaduct as well as a relief line cab ride at Reading just after Platforms 12-15 opened and my 'before and after' video comparison of the Cotswold Line Redoubling scheme, see: http://www.dailymotion.com/user/IndustryInsider/1
fladpass
Jr. Member
**
Posts: 13


View Profile Email
« Reply #754 on: November 30, 2018, 05:07:45 pm »

Quote
17:38 Moreton-In-Marsh to London Paddington due 19:03
17:38 Moreton-in-Marsh to London Paddington due 19:03 will be started from Oxford.
It will no longer call at Moreton-in-Marsh.
This is due to a broken down train.

Because 1W32 15:50 PAD MIM terminated at Oxford. For the third day in succession. This service's profile on OnTimeTrains is abysmal:

https://www.ontimetrains.co.uk/journeys/PAD/MIM/15:50/17:26/GW;dayOfWeekRange=Weekdays;dateRange=12W

Presumably the 'broken down train' referred to above isn't the HST on this service since the return (from Oxford) is still slated to run?
Logged
Adelante_CCT
Transport Scholar
Hero Member
******
Posts: 1183



View Profile
« Reply #755 on: November 30, 2018, 05:47:11 pm »

No, the one in front (15:45) run into trouble at Langley delaying services behind it


Having said that....

Quote
Due to damage to the overhead electric wires between West Drayton and Slough trains have to run at reduced speed on some lines towards Slough.

Train services running through these stations may be delayed by up to 15 minutes. Disruption is expected until 18:15 30/11.
Logged
charles_uk
Hero Member
*****
Posts: 423

thewalkingpage
View Profile
« Reply #756 on: December 06, 2018, 12:53:02 pm »

More afternoon congestion yesterday:

Again it was the 1322 Paddington to Worcester Foregate Street losing time on the Cotswold Line going through Norton Junction 9 minutes late.

The 1522 Worcester Shrub Hill to Paddington left on time but hit Norton Junction 11 late and was 20 late by the time it got to Charlbury.

That in turn held up the 1522 Paddington to Great Malvern by 16 minutes and which was terminated at Worcester Shrub Hill.

Surprisingly the 1550 Paddington to Moreton-in-Marsh was run through to MIM, and put ahead of the 1551 Worcester Foregate Street to Paddington which departed Oxford 31 late.

The 1514 Hereford to Paddington was terminated at Reading, arriving 44 minutes late.

The 1522 WOS:PAD has been late off the Cotswold Line every day this week delaying the 1522 PAD:GMV at Wolvercote Junction, partly due earlier late running services on the single track. And as I write this, I can see the 1209 Hereford to Paddington is already 22 minutes late which may well impact upon the 1322 PAD:WOF etc...
Logged
Richard Fairhurst
Global Moderator
Hero Member
*****
Posts: 705


View Profile Email
« Reply #757 on: December 07, 2018, 07:49:19 am »

Entertaining disruption this morning. The 7.12 ran fast through Charlbury at 7.30ish, at which point the display flipped to showing the two-coach 7.49 (exp. 8.04) Halts train as the next arrival... to the consternation of the many waiting passengers. Eventually the 7.31 turned up 15 minutes late, proudly displaying its next stop as “00.00 Hanborough”. The Midnight Express?
Logged
charles_uk
Hero Member
*****
Posts: 423

thewalkingpage
View Profile
« Reply #758 on: December 07, 2018, 08:24:07 am »

Entertaining disruption this morning. The 7.12 ran fast through Charlbury at 7.30ish, at which point the display flipped to showing the two-coach 7.49 (exp. 8.04) Halts train as the next arrival... to the consternation of the many waiting passengers. Eventually the 7.31 turned up 15 minutes late, proudly displaying its next stop as “00.00 Hanborough”. The Midnight Express?

The problem with this "fix" to bring the 05:28 Hereford to Paddington back on time is that the 07:10 MIM:PAD is inevitably delayed, so those waiting at Charlbury and Hanborough are doubly inconvenienced. And not helped today by the pouring rain and misleading display board.
Logged
JontyMort
Full Member
***
Posts: 61


View Profile
« Reply #759 on: December 07, 2018, 09:32:43 am »

Entertaining disruption this morning. The 7.12 ran fast through Charlbury at 7.30ish, at which point the display flipped to showing the two-coach 7.49 (exp. 8.04) Halts train as the next arrival... to the consternation of the many waiting passengers. Eventually the 7.31 turned up 15 minutes late, proudly displaying its next stop as “00.00 Hanborough”. The Midnight Express?

The problem with this "fix" to bring the 05:28 Hereford to Paddington back on time is that the 07:10 MIM:PAD is inevitably delayed, so those waiting at Charlbury and Hanborough are doubly inconvenienced. And not helped today by the pouring rain and misleading display board.

And last night's 2148 HST sat down at Reading. I was glumly contemplating a taxi but, to be fair, GW intelligently terminated an up train at Reading and turned it back.
Logged
DavidT
Newbie
*
Posts: 8


View Profile Email
« Reply #760 on: December 07, 2018, 04:21:00 pm »

Thursday's 19.22 from Paddington left 48 mins late -- and was then held at Slough to let the 20.22 overtake it. It ended up 72 mins late at Charlbury.  Another triumph.
Logged
charles_uk
Hero Member
*****
Posts: 423

thewalkingpage
View Profile
« Reply #761 on: December 07, 2018, 04:44:17 pm »

For the fifth time this week, afternoon congestion causing delays. Today, GWR have fallen back on another of their regular fixes:

Quote
15:50 London Paddington to Moreton-in-Marsh due 17:26 will be terminated at Oxford.
It will no longer call at Hanborough, Charlbury, Kingham and Moreton-in-Marsh.
This is due to congestion.
Last Updated:07/12/2018 16:12

From my records, this appears to be the 39th time this year GWR have failed to take this service beyond Oxford.

[later] and just to add to the pain, the following 16:22 PAD:GMV was delayed at Wolvercote Junction due to the late running 15:14 Hereford to Paddington service.

It's hard to see if there's a single reason for the congestion but it does seem that some of the timings on the single track can be quite tight and, this week, a number of these timings have slipped with all the knock on consequences.
« Last Edit: December 07, 2018, 05:54:13 pm by charles_uk » Logged
Dispatch Box
Sr. Member
****
Posts: 173



View Profile
« Reply #762 on: December 07, 2018, 06:54:19 pm »

For the fifth time this week, afternoon congestion causing delays. Today, GWR have fallen back on another of their regular fixes:

Quote
15:50 London Paddington to Moreton-in-Marsh due 17:26 will be terminated at Oxford.
It will no longer call at Hanborough, Charlbury, Kingham and Moreton-in-Marsh.
This is due to congestion.
Last Updated:07/12/2018 16:12

From my records, this appears to be the 39th time this year GWR have failed to take this service beyond Oxford.

[later] and just to add to the pain, the following 16:22 PAD:GMV was delayed at Wolvercote Junction due to the late running 15:14 Hereford to Paddington service.

It's hard to see if there's a single reason for the congestion but it does seem that some of the timings on the single track can be quite tight and, this week, a number of these timings have slipped with all the knock on consequences.

Flipping gets on your goat now, This often happens with a Weymouth to Great Malvern, if 20 mins late they get terminated at Worcester shrub hill.
Logged
JontyMort
Full Member
***
Posts: 61


View Profile
« Reply #763 on: December 08, 2018, 10:51:03 pm »

For the fifth time this week, afternoon congestion causing delays. Today, GWR have fallen back on another of their regular fixes:

Quote
15:50 London Paddington to Moreton-in-Marsh due 17:26 will be terminated at Oxford.
It will no longer call at Hanborough, Charlbury, Kingham and Moreton-in-Marsh.
This is due to congestion.
Last Updated:07/12/2018 16:12

From my records, this appears to be the 39th time this year GWR have failed to take this service beyond Oxford.

[later] and just to add to the pain, the following 16:22 PAD:GMV was delayed at Wolvercote Junction due to the late running 15:14 Hereford to Paddington service.

It's hard to see if there's a single reason for the congestion but it does seem that some of the timings on the single track can be quite tight and, this week, a number of these timings have slipped with all the knock on consequences.

Flipping gets on your goat now, This often happens with a Weymouth to Great Malvern, if 20 mins late they get terminated at Worcester shrub hill.

At least if they get terminated at Shrub Hill there's a chance of getting to Malvern on West Midlands, depending on the time of day. Not that at WMT are much better, as they often do the same thing coming late from Brum.
Logged
grahame
Administrator
Hero Member
*****
Posts: 22963



View Profile WWW Email
« Reply #764 on: December 09, 2018, 04:45:09 am »

For the fifth time this week, afternoon congestion causing delays. Today, GWR have fallen back on another of their regular fixes:

Quote
15:50 London Paddington to Moreton-in-Marsh due 17:26 will be terminated at Oxford.

From my records, this appears to be the 39th time this year GWR have failed to take this service beyond Oxford.

Flipping gets on your goat now, This often happens with a Weymouth to Great Malvern, if 20 mins late they get terminated at Worcester shrub hill.

At least if they get terminated at Shrub Hill there's a chance of getting to Malvern on West Midlands, depending on the time of day. Not that at WMT are much better, as they often do the same thing coming late from Brum.

GWR or any operator running to a timetable are caught between a rock and a hard place when a train's running late - especially where single track is involved - whether to inconvenience passengers on the current service by terminating it short of booked destination, or inconveniencing others on trains if the late running means it's going to get in the way and knock on effects continuing perhaps for hours or until close of service.

Solutions?  Sort out delays and run trains much better to time, and these problems will be reduced as a consequence.  Other possible solutions (scheduling fewer trains, providing spares so there's something to send back even if an incoming service is late, easing schedules, denying train use to slow-to-board people) are rather unattractive.

Personal favourite annoyance ... late (or even early) running freight train in the way.  Not thrilled when reliability goes to pot because of problems on other lines either and 'we' get used for diverted passenger trains which take up the capacity - without even the courtesy of stopping at the stations where they have removed services for many hours.
Logged

Coffee Shop Admin, Member of Melksham Rail User Group, on the board of TravelWatch SouthWest and some more things besides
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 ... 49 50 [51] 52 53
  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