CLPGMS
|
|
« Reply #45 on: March 01, 2014, 19:03:04 » |
|
Can Charles_uk tell us what happened to the Hanborough passengers? Was road transport arranged or did they have to wait for the next train, 43 minutes later?
|
|
|
Logged
|
|
|
|
charles_uk
|
|
« Reply #46 on: March 01, 2014, 20:14:21 » |
|
Can Charles_uk tell us what happened to the Hanborough passengers? Was road transport arranged or did they have to wait for the next train, 43 minutes later?
FGW▸ 's attitude on the platform was that as the delay was less than an hour they weren't obligated to do anything so we simply had to wait for the 1732 OXF» :GMV.
|
|
|
Logged
|
|
|
|
ChrisB
|
|
« Reply #47 on: March 03, 2014, 09:44:40 » |
|
Did it still stop at Hanborough (to pick up)?
Coz the Train Manager has NO authority to issue (non)stop orders, and knowing this, I'd have stayed on regardless, until at least a tannoy announcement made at Oxford saying it wasn't stopping...and if you did stay on knowing the train still had to stop, and you knew which carriages were on the platform (commuters would do), the TM‡ wouldn't be any the wiser that you hadn't got off....
|
|
|
Logged
|
|
|
|
charles_uk
|
|
« Reply #48 on: March 03, 2014, 10:21:36 » |
|
Did it still stop at Hanborough (to pick up)?
I've no idea whether it did stop to pick up as I was standing on the platform at Oxford! My partner did look at JourneyCheck (as I was late) which showed the HND stop as "cancelled". My assumption was that it was the train manager who was responsible for the cancellation. That is what we were told at Oxford but it may have been that they got the appropriate permission before we were told to get off. However, staff at Oxford were certainly taken by surprise. The fundamental problem though is that by taking 220 seats off what was already a very crowded service, FGW▸ have caused this gross overcrowing problem and have to manage it more intelligently than simply kicking passengers off the train.
|
|
|
Logged
|
|
|
|
ChrisB
|
|
« Reply #49 on: March 03, 2014, 13:39:44 » |
|
oh, agreed, and CLPG» Have taken it up urgently with FGW▸ .
If it were shown as Cancelled at HND, then someone must have iiaised with Control.
|
|
|
Logged
|
|
|
|
martvw
|
|
« Reply #50 on: March 06, 2014, 07:45:09 » |
|
I had a trip down to Oxford yesterday 5th , a good run both ways and made good time , but still had to wait at Charlbury and Evesham for trains to come off the single track !! A class 180 on both runs no problems.
|
|
|
Logged
|
|
|
|
Busboy W1
|
|
« Reply #51 on: April 10, 2014, 19:59:30 » |
|
And today due to a fault with 180102 this morning at Didcot 166211 came to the rescue which was rather full all day and 180104 seems to have had problems when arriving at Paddington after working 1P57 from Great Malvern.
|
|
|
Logged
|
|
|
|
IndustryInsider
|
|
« Reply #52 on: April 10, 2014, 20:12:52 » |
|
After months of pretty solid reliability there's been the odd hiccup over the last couple of weeks. Hopefully it is just a hiccup!
|
|
|
Logged
|
To view my GWML▸ Electrification cab video 'before and after' video comparison, as well as other videos of the new layout at Reading and 'before and after' comparisons of the Cotswold Line Redoubling scheme, see: http://www.dailymotion.com/user/IndustryInsider/
|
|
|
Southern Stag
|
|
« Reply #53 on: April 10, 2014, 21:01:03 » |
|
Looks like another sensible change to the 180 diagrams from May. The 0517 Paddington-Oxford and 0721 Oxford-Paddington will no longer be a 180. Neither service was particularly suitable for a 180 as they were both stoppers. The 180 will instead work a new 0734 Didcot Parkway-Paddington, calling at Reading only. As a result the 0630 Bristol Temple Meads-Paddington will start at 0635 instead and cease to call at Didcot Parkway.
|
|
|
Logged
|
|
|
|
bobm
|
|
« Reply #54 on: April 10, 2014, 21:42:50 » |
|
As a result the 0630 Bristol Temple Meads-Paddington will start at 0635 instead and cease to call at Didcot Parkway.
Putting it halfway between the current 06:30 and the old 06:40 which was withdrawn last year and never reappeared...
|
|
|
Logged
|
|
|
|
Southern Stag
|
|
« Reply #55 on: April 10, 2014, 23:28:28 » |
|
The 06:40 was a victim of the current overhaul programme for the MK3s, along with the subject of this thread, the 15:51 Paddington-Worcester SH. Whilst the 15:51 was replaced with a 180, the 06:40 was cut entirely. Maybe it will return once the overhaul programme is complete, but that will be some time yet I imagine.
|
|
|
Logged
|
|
|
|
stebbo
|
|
« Reply #56 on: April 11, 2014, 09:05:12 » |
|
15:51 Paddington to Worcester was a nightmare yesterday. A 3 car Turbo for what used to be a busy HST▸ then more recently a choc-ful Adelante. Absolutely ridiculous. Between Reading and Hanborough it was, as they say, "rammed". Why can't FGW▸ re-juggle the diagrams so as to switch an Adelante to this service - it's always very busy?
|
|
|
Logged
|
|
|
|
ChrisB
|
|
« Reply #57 on: April 11, 2014, 09:09:35 » |
|
The 06:40 was a victim of the current overhaul programme for the MK3s, along with the subject of this thread, the 15:51 Paddington-Worcester SH. Whilst the 15:51 was replaced with a 180, the 06:40 was cut entirely. Maybe it will return once the overhaul programme is complete, but that will be some time yet I imagine.
That is the current intention, it was the same diagrammed HST▸ .
|
|
|
Logged
|
|
|
|
ChrisB
|
|
« Reply #58 on: April 11, 2014, 09:10:43 » |
|
15:51 Paddington to Worcester was a nightmare yesterday. A 3 car Turbo for what used to be a busy HST▸ then more recently a choc-ful Adelante. Absolutely ridiculous. Between Reading and Hanborough it was, as they say, "rammed". Why can't FGW▸ re-juggle the diagrams so as to switch an Adelante to this service - it's always very busy? Coz it'd be an even busier HST right out of the evening peak. This was definitely the 'least-worst' solution.
|
|
|
Logged
|
|
|
|
Busboy W1
|
|
« Reply #59 on: April 12, 2014, 13:58:08 » |
|
Not sure wether this is going to be related in some way or another bit it looks like 180102 is having a jolly up North for the weekend with Hull Trains. Extra services due to the FA Cup Semi Finals At Wembley tomorrow.
|
|
|
Logged
|
|
|
|
|