IndustryInsider
|
|
« Reply #195 on: February 03, 2020, 10:45:24 » |
|
And keep moaning. 😉
And you're perfectly entitled to do so as the performance of that particular train is shocking. I'm not aware of any infrastructure issues at Oxford as the track is level and pretty much arrow straight at Platform 3. It is a combination of staff unfamiliarity and the IET▸ couplers still not behaving themselves, mostly the latter it seems. It is pretty hopeless that day after day at Oxford the following trains 2V11 (06:04 BAN- RDG‡) and 1P01 (04:48 HDF- PAD» ) keep on being allowed as far as OD2378 and OD2386 and 1T03 (06:25 BIT- OXF» ) is allowed as far as OD2380. All three trains are then stranded outside with nowhere to go whilst the fallout of coupling problems is dealt with. It would be rather more sensible to hold these three trains at OD2392/2408/2490 until it is known the coupling has been successful - and then if there's problems they can be routed round it via platform 4 rather than locking up a large portion of the station and it subsequently taking far longer to catch up from the delays. Either that or put the offending train through platform 4 anyway and put anything heading north through platform 3 if there's problems with it.
|
|
|
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/
|
|
|
ray951
|
|
« Reply #196 on: February 03, 2020, 11:16:09 » |
|
So I assume this is why the infamous 0740 RDG‡ - OXF» was cancelled again, and the following 0834 DID» to BAN also left late due to the late running 1V17 BAN - PAD» , all caused by the same issue.
What a lot of delays caused by the inability to couple a two sets together.
How can it be that after 2 years of running these trains there are still basic issues with them?
|
|
|
Logged
|
|
|
|
Sixty3Closure
|
|
« Reply #197 on: February 04, 2020, 08:33:32 » |
|
A delayed 17.08 to Bedwyn again yesterday evening which seems to be one of the equivalents to the morning trains.
And a delayed 06.54/07.01 again this morning possibly due to the irregular freight train that runs at the same time some days.
|
|
|
Logged
|
|
|
|
TaplowGreen
|
|
« Reply #198 on: February 04, 2020, 09:18:04 » |
|
And a delayed 06.54/07.01 again this morning possibly due to the irregular freight train that runs at the same time some days.
- I believe the 0633 (non stop to Paddington) was cancelled too this morning?
|
|
|
Logged
|
|
|
|
NickB
|
|
« Reply #199 on: February 04, 2020, 09:56:56 » |
|
And a delayed 06.54/07.01 again this morning possibly due to the irregular freight train that runs at the same time some days.
- I believe the 0633 (non stop to Paddington) was cancelled too this morning? Indeed it was, making the (slightly delayed) 06.45 quite busy. I suspect that this was all due to the same freight train that came bowling through Maidenhead on the main line at about 06.35.
|
|
|
Logged
|
|
|
|
mjones
|
|
« Reply #200 on: February 04, 2020, 10:47:02 » |
|
.. the late running 1V17 BAN - PAD» , all caused by the same issue.
What a lot of delays caused by the inability to couple a two sets together.
How can it be that after 2 years of running these trains there are still basic issues with them?
This forms the 0820 from Didcot I think? I caught it three times in the last two weeks, late and missed connection at Reading each time. Waiting for it provided an opportunity to watch people going to Oxford struggling to get into the 0834, rammed because of the cancellation of the 0807. These problems are causing serious disruption to Didcot to Oxford commuters who must be late for work several days a week at the moment.
|
|
|
Logged
|
|
|
|
ray951
|
|
« Reply #201 on: February 04, 2020, 12:03:32 » |
|
.. the late running 1V17 BAN - PAD» , all caused by the same issue.
What a lot of delays caused by the inability to couple a two sets together.
How can it be that after 2 years of running these trains there are still basic issues with them?
This forms the 0820 from Didcot I think? I caught it three times in the last two weeks, late and missed connection at Reading each time. Waiting for it provided an opportunity to watch people going to Oxford struggling to get into the 0834, rammed because of the cancellation of the 0807. These problems are causing serious disruption to Didcot to Oxford commuters who must be late for work several days a week at the moment. Yes it does form the 0820. No late to work every day and several people were left behind at Didcot and Radley yesterday as train so full.
|
|
|
Logged
|
|
|
|
TaplowGreen
|
|
« Reply #202 on: February 05, 2020, 07:13:51 » |
|
0648 fast service from Twyford cancelled this morning which should ensure that everyone is nice & cosy when the 0702 arrives at Maidenhead......
|
|
|
Logged
|
|
|
|
Sixty3Closure
|
|
« Reply #203 on: February 05, 2020, 08:16:06 » |
|
Yep - that's what I get for getting up earlier and trying a different train.
Bit more crowded that usual on the platform although for some reason no one got on at Maidenhead. I was in coach 4 or thereabouts and after we'd set off loads of people appeared and started moving to the front. Don't know if there was a problem with the doors or something?
|
|
|
Logged
|
|
|
|
NickB
|
|
« Reply #204 on: February 05, 2020, 10:38:18 » |
|
In terms of passenger numbers at Maidenhead this morning the 6.45 didn’t arrive until 6.53 and so picked up a number of 07.02 customers who were already on the platform. That in turn left standing room only (in my carriage) at Slough.
|
|
|
Logged
|
|
|
|
Sixty3Closure
|
|
« Reply #205 on: February 06, 2020, 10:13:33 » |
|
Decided to work from home for the rest of the week to give my colleagues a break from daily updates on the new timetable so probably all worked perfectly if I wasn't there to see it.
|
|
|
Logged
|
|
|
|
BBM
|
|
« Reply #206 on: February 06, 2020, 10:30:51 » |
|
I made one of my now very irregular TWY▸ -PAD» journeys this morning and all seemed well from my point of view, I caught the 0654 from TWY, and coach 11 where I sat was only half-full after MAI▸ . One thing I did notice was that the 0648 (a 5-car IET▸ from BDW which is non-stop from TWY) was full and standing on departure and if more people were prepared to wait for the 0654 (like me!) then that later train would be rather busier.
|
|
|
Logged
|
|
|
|
IndustryInsider
|
|
« Reply #207 on: February 06, 2020, 10:49:20 » |
|
I made one of my now very irregular TWY▸ -PAD» journeys this morning and all seemed well from my point of view, I caught the 0654 from TWY, and coach 11 where I sat was only half-full after MAI▸ . One thing I did notice was that the 0648 (a 5-car IET▸ from BDW which is non-stop from TWY) was full and standing on departure and if more people were prepared to wait for the 0654 (like me!) then that later train would be rather busier.
All was well with the 07:02/07:07 off of Maidenhead again this morning, though it looks like the previous Class 387 semi-fast from Didcot ran fast from Reading (that's the 06:26 off of Twyford, and 06:33 off of Maidenhead) and might explain why the 06:48 off of Twyford was busy this morning? The decision to run the 06:26/06:33 fast from Reading was due to it being delayed at Reading for 21 minutes due to unit problems. MODS: Perhaps we should rename this thread as it now discusses other trains from Maidenhead and the commuter services into London from Twyford as well?
|
|
|
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/
|
|
|
Sixty3Closure
|
|
« Reply #208 on: February 11, 2020, 13:21:29 » |
|
07.01 didn't stop at Maidenhead this morning. It was only 2-3 minutes late leaving Twyford (freight train again) so not sure what the problem was.
|
|
|
Logged
|
|
|
|
NickB
|
|
« Reply #209 on: February 11, 2020, 19:00:43 » |
|
07.01 didn't stop at Maidenhead this morning. It was only 2-3 minutes late leaving Twyford (freight train again) so not sure what the problem was.
As was reported to rather cold customers at Maidenhead this morning: MAI▸ to PAD» on your route: 07:02 - cancelled - a problem currently under investigation. The 06.37(?) and 06.45 ran with delays today. The 06.37 was held back to allow other HS▸ services to pass it.
|
|
|
Logged
|
|
|
|
|