GWR Dec 19 timetable

didcotdean · 6 Aug 2019

In the early schematic representation of the new timetable service provision, not only did the weekday Cardiffs stop at Didcot, they didn't stop at Reading except in peaks, although that didn't survive into the next iteration.

RailUK Forums

Wilts Wanderer · 6 Aug 2019

30907 said:
That's the pattern reported by Modern Railways this month - obviously overtaken by events, but I wonder why the change had to be made, and made so recently?

From what I’ve heard along the grapevine, it’s to do with creating freight paths between Swindon and Didcot.

800002 · 6 Aug 2019

Wilts Wanderer said:
From what I’ve heard along the grapevine, it’s to do with creating freight paths between Swindon and Didcot.

As in creating additional paths or mainintain the current level of existing paths?
What with the additional traffic going thatway, i would have thought there wouldn't be much more capacity to offer freight (above what is currently there).

800002 · 7 Aug 2019

Going to try to keep this HEX post contained - having now written out the potential diagrams (based on RRT / open data stream output).

Bikeman78 said:
I note the Heathrow Express will only need four sets of stock with the reduced turn round times as Paddington. Will some of these be 12 car? 12 units for eight diagrams is rather generous. What chance of a HEX unit chucking out on a GWR service when the need arises?

HamworthyGoods said:
HEX is still 5 sets of stock it’s simply the long turnaround moves from Paddington to Heathrow

Bikeman78 said:
Thanks to both of you. I hadn't spotted the long layovers at Heathrow.

irish_rail said:
Again, I just can't see this working. The minute a HEX arrives a few minutes late it is guaranteed to depart late and thus get in the way of GWR services departing after with further knock on delays. The more I see of this 2019 timetable, the more I'm convinced it is never going to work. I see operation princess mk2.

Wilts Wanderer said:
Are HEX planning driver changes at Paddington in a similar vein to the tube at terminal stations? If so that's a partial mitigation against at least minor delays to the service. Anything beyond 5 mins late will likely require cancellations.

Heathrow Express possible diagrams - from RTT platforms. NOT-OFFICIAL (in any way).
Five diagrams (presume eight cars each but could be only 4).
Note: appears all start as 8 x Cl.387, with evening divides. No current schedules to suggest a 4 car start with strengthening during the day. All the evening ECS paths are non-Q, suggesting all diagrams split in the evening to become 4 x Cl.387 from 2040 on wards. Further info suggests no splitting of diagrams is planned by HEx (GWR), planned ECS's reflect current need by HEx and to cover any overlap when timetable change occurs. [Thanks @JN114 ] A point i overlooked was that HEx (GWR) won't (and can't) be using the OOC EMU depot! Silly me (my apologies).

Note: there appears to be a few platform errors in the evening (so it seems, to my eye, in formulating the below diagrams). I've struggled to make sense of some of the workings (around 1Y84 onwards). The headcode increment at paddington is: Yxx = T+4, untill 1Y84 / 1Y85, when 1Y85 becomes 1Y90 and all then follow Yxx = T+5.
1Y84 (plat 6) = 1T88 (plat 7) + 1T89 (plat 6)
~~1T88 can not be formed by 1Y83 (HEx-02), the previous arrival on Plat 7, as that diagram splits later in the day as 1Y88 - 5Y88 and 1T91 (all plat 6).~~
Possible 1Y84 (currently showing #6 at PAD) is showing incorrect platform, and should make 1T88 (currently showing #7 at PD) and 1Y84 (currently showing #7 at PAD) should make 1T89 (currently showing #6 at PAD) and then the pattern prevails till close of play. Means that anything I've proposed after 1Y84 is incorrect. (again, apologies).
I've edited to remove the evening ECS moves (before close of play), and shall take a look at the late evening schedule when time allows.

So here is what it looks like is happening:
Using Terminal 5 as they currently use Paddington (two platforms in Dec 19, vice 1 platform currently)
Lay over of 25 minutes at Terminal 5 (vice the current 10 minutes)
Lay over of 8 minutes at Paddington (vice the current 20 minutes)

There looks to be sufficient turn time at Terminal 5 to absorb any late running, certainly on the down, ensuring a right time start for the up services. They should present to Hex Jn ontime. [the XR pad - T4 and shuttle appear to allow sufficient leyway if they are delayed, with the the up HEX having an on time start from T5]
I don't see much interaction with the tunnel services, within 6-7 minutes of ontime running, with the exception the the up HEx follows the up XR at heathrow central XR xx26-xx28 / HEx xx31-xx32 and XR xx56-58 / HEx xx01-xx02

Arrival at pad upto 5 minutes late and it can still probably get out ontime (or within 1 or 2 minutes). The late inward going straight back out when late is neither her nor there really, as it shouldn't be able to get to 25 late or more (affecting the back start from T5 - and if it is, I would suggest the whole of paddington is screwed and the XR will be getting curtailed (probably the Hayes stoppers, rather than Heathrows). I don't foresee the need to cancel HEx if they are within 10 / 15 minutes lateness (obviously depending on circumstances) - it'll just operate 1 in / 1 out at pad, as planned (albeit a bit delayed). If they are all running out of course, it's not an issue. If a single unit is out course however, that could be a different matter.

With regard to HEx starting late and knock on effects - there is a decent margin (to depart say 3 late, and only knock the incoming GWR - the other arrival are / should be parallel arrivals to the departing HEx). Running on the down at Hex Jn at xx19 + xx49 the HEx is followed by the non-stop bristol at xx23 and xx53; Wales at xx26 and xx59; and Oxfords xx28 and 58. There shouldn't be too much to overcome there.
Then the xx34 and xx04 HEx is followed by the cheltenham / Bristol slow at xx36 and 10; the bristol slow / WofE at xx40 and 12; and the Oxford / bedwyn at xx28 and 16. Again, this should be plenty of time for all to rumble through with minimum issue if HEx is a little late. They should be able to make up any time pre-reading.
But time shall tell.

I make no apologies for length of the post!

Possible diagrams:

HEx-01:
5T22 0402 ex-OOC [a. Pad 0419]
5Y22 0436 ex-Pad / 5T22 (Q) / 5T17 (Q) / 5Y22 (Q)*
5Y22 a. T5 0457 - 1Y22 d. 0512
1Y22 a. Pad 0535 - 1T26 d. 0540
1T26 a. T5 0602 - 1Y27 d. 0627
1Y27 a. Pad 0647 - 1T31 d. 0655
1T31 a. T5 0716 - 1Y32 d. 0742
1Y32 a. Pad 0803 - 1T36 d. 0810
1T36 a. T5 0832 - 1Y37 d. 0857
1Y37 a. Pad 0917 - 1T41 d. 0925
1T41 a. T5 0946 - 1Y42 d. 1012
1Y42 a. Pad 1032 - 1T46 d. 1040
1T46 a. T5 1102 - 1Y47 d. 1127
1Y47 a. Pad 1147 - 1T51 d. 1155
1T51 a. T5 1216 - 1Y52 d. 1242
1Y52 a. Pad 1302 - 1T56 d. 1310
1T56 a. T5 1332 - 1Y57 d. 1357
1Y57 a. Pad 1417 - 1T61 d. 1425
1T61 a. T5 1446 - 1Y62 d. 1512
1Y62 a. Pad 1532 - 1T66 d. 1540
1T66 a. T5 1602 - 1Y67 d. 1627
1Y67 a. Pad 1648 - 1T71 d. 1655
1T71 a. T5 1716 - 1Y72 d. 1742
1Y72 a. Pad 1802 - 1T76 d. 1810
1T76 a. T5 1832 - 1Y77 d. 1857
1Y77 a. Pad 1717 - 1T81 d. 1925
1T81 a. T5 1946 - 1Y82 d. 2012
1Y82 a. Pad 2032 (plat 6) - 1T86 d. 2040 (plat 6)
~~1Y82 a. Pad 2032 (plat 6) - 5Y82 d. 2045 (plat 6) (OOC EMU a. 2105)~~
1T86 a. T5 2102 - 1Y87 d. 2127
1Y87 a. Pad 2147 - 1T92 d. 2210
1T92 a. T5 2232 - 1Y93 d. 2257
1Y93 a. Pad 2317 - 5Y93 d. 2330 (OOC EMU a. 2250)**
*5T22 has two paths, from OOC, one 'Q' for ECL into Pad. 5T17 shares 5T22 timings, but ECL (vice RL)
**5Y93 + Q to Reading

HEx-02:
5Y23 (d. 0430 OOC) a. T5 0507 - 1Y23 d. 0527
1Y23 a. Pad 0550 - 1T27 d. 0555
1T27 a. T5 0616 - 1Y28 d. 0642
1Y28 a. Pad 0702 - 1T32 d. 0710
1T32 a. T5 0732 - 1Y33 d. 0757
1Y33 a. Pad 0818 - 1T37 d. 0825
1T37 a. T5 0846 - 1Y38 d. 0912
1Y38 a. Pad 0932 - 1T42 d. 0940
1T42 a. T5 1002 - 1Y43 d. 1027
1Y43 a. Pad 1047 - 1T47 d. 1055
1T47 a. T5 1116 - 1Y48 d. 1142
1Y48 a. Pad 1202 - 1T52 d. 1210
1T52 a. T5 1232 - 1Y53 d. 1252
1Y53 a. Pad 1317 - 1T57 d. 1325
1T57 a. T5 1346 - 1Y58 d. 1412
1Y58 a. Pad 1432 - 1T62 d. 1440
1T62 a. T5 1502 - 1Y63 d. 1527
1Y63 a. Pad 1547 - 1T67 d. 1555
1T67 a. T5 1616 - 1Y68 d. 1642
1Y68 a. Pad 1702 - 1T72 d. 1710
1T72 a. T5 1732 - 1Y73 d. 1757
1Y73 a. Pad 1817 - 1T77 d. 1825
1T77 a. T5 1846 - 1Y78 d. 1912
1Y78 a. Pad 1932 - 1T82 d. 1940
1T82 a. T5 2002 - 1Y83 d. 2027
1Y83 a. Pad 2047 - 1T87 d. 2055
1T87 a. T5 2116 - 1Y88 d. 2142
~~1Y88 a. Pad 2002 (plat 6) - 5Y88 d. 2215 (plat 6) (OOC a. 2235)~~
1Y88 a. Pad 2002 (plat 6) - 1T93 d. 2225 (plat 6)
1T93 a. T5 2246 - 1Y94 d. 2312
1Y94 a. Pad 2332 - 5Y94 d. 2340 (OOC a. 0003)**
**5Y94 + Q to West Ealing

HEx-03:
5T19 (Q) ex-OOC d. 0425 a. Pad 0441
5T18 (Q) / 5T24 (Q) ex-OOC d. 0423 a. Pad 0441
5Y18 (Q) ex-pad d. 0451 a. HEX Central 0511
5E23 (Q) ex-W. Ealing d. 0500 a. HEX Cental 0510
2E23 d. HEX Central 0513
2E23 a. T5 0517 - 1Y24 d. 0542
1Y24 a. Pad 0602 - 1T28 d. 0610
1T28 a. T5 0632 - 1Y29 d. 0657
1Y29 a. Pad 0717 - 1T33 d. 0725
1T33 a. T5 0746 - 1Y34 d. 0812
1Y34 a. Pad 0833 - 1T38 d. 0840
1T38 a. T5 0902 - 1Y39 d. 0927
1Y39 a. Pad 0947 - 1T43 d. 0955
1T43 a. T5 1016 - 1Y44 d. 1042
1Y44 a. Pad 1102 - 1T48 d. 1110
1T48 a. T5 1132 - 1Y49 d. 1157
1Y49 a. Pad 1217 - 1T53 d. 1225
1T53 a. T5 1246 - 1Y54 d. 1312
1Y54 a. Pad 1332 - 1T58 d. 1340
1T58 a. T5 1402 - 1Y59 d. 1427
1Y59 a. Pad 1447 - 1T63 d. 1455
1T63 a. T5 1516 - 1Y64 d. 1542
1Y64 a. Pad 1602 - 1T68 d. 1610
1T68 a. T5 1632 - 1Y69 d. 1657
1Y69 a. Pad 1717 - 1T73 d. 1725
1T73 a. T5 1746 - 1Y74 d. 1812
1Y74 a. Pad 1833 - 1T78 d. 1840
1T78 a. T5 1902 - 1Y79 d. 1927
1Y79 a. Pad 1947 - 1T83 d. 1955
1T83 a. T5 2016 - 1Y84 d. 2042
1Y84 a. Pad 2103 (plat 6) - 1T88 d. 2110 (plat 7 RTT)
1T88 a. T5 2132 - 1Y89 d. 2157
1Y89 a. Pad 2217 - 1T95 d. 2255
1T95 a. T5 2316 - 1Y96 d. 2342

1Y84 a. Pad 2103 (plat 6) - 1T89 d. 2125 (plat 6 RTT)
1T89 a. T5 2146 - 1Y90 d. 2212
1Y90 a. Pad 2232 - 1T94 d. 2240
1T94 a. T5 2302 - 1Y95 d. 2327
1Y95 a. Pad 2347 - 5Y95 d. 0003 (OOC a. 0021)**
*5T19 / 5T18 / 5T24 from OOC share same path into pad
*5Y18 / 5E23 share same path into Heathrow Central (ex-pad / ex-West Ealing EMU)
**5Y96 + Q to West Ealing
**5Y95 + Q to Reading

HEx-04:
3T24 (Q, RDG) d. 0408 a. Pad 0456 - 1T24 d 0510
1T24 a. T5 0532 - 1Y25 d. 0557
1Y25 a. Pad 0617 - 1T29 d. 0625
1T29 a. T5 0646 - 1Y30 d. 0712
1Y30 a. Pad 0732 - 1T34 d. 0740
1T34 a. T5 0802 - 1Y35 d. 0827
1Y35 a. Pad 0847 - 1T39 d. 0855
1T39 a. T5 0916 - 1Y40 d. 0942
1Y40 a. Pad 1002 - 1T44 d. 1010
1T44 a. T5 1032 - 1Y45 d. 1057
1Y45 a. Pad 1117 - 1T49 d. 1125
1T49 a. T5 1146 - 1Y50 d. 1212
1Y50 a. Pad 1232 - 1T54 d. 1240
1T54 a. T5 1302 - 1Y55 d. 1327
1Y55 a. Pad 1347 - 1T59 d. 1355
1T59 a. T5 1406 - 1Y60 d. 1442
1Y60 a. Pad 1503 - 1T64 d. 1510
1T64 a. T5 1532 - 1Y65 d. 1557
1Y65 a. Pad 1617 - 1T69 d. 1625
1T69 a. T5 1646 - 1Y70 d. 1712
1Y70 a. Pad 1732 - 1T74 d. 1740
1T74 a. T5 1802 - 1Y75 d. 1827
1Y75 a. Pad 1847 - 1T79 d. 1855
1T79 a. T5 1616 - 1Y80 d. 1942
1Y80 a. Pad 2002 - 1T84 d. 2010
1T84 a. T5 2032 - 1Y85 d. 2057
~~1Y85 a. Pad 2117 - 5Y85 d. 2123 (OOC a. 2143)~~
1Y85 a. Pad 2117 - 1T90 d. 2140
1T90 a. T5 2202 - 1Y91 d. 2227
1Y91 a. Pad 2249 - 1T96 d. 2310
1T96 a. T5 2332 - 1Y97 d. 2351
1Y97 a. Pad 0015 - 5Y97 d. 0028 (OOC a. 0101)**
*3T24 has no other path currently (NOTE: the 5T24 path above ex-OOC is same time as 5T18+19)
**5Y97 + Q path to Reading

HEx-05:
3T25 (Q, RDG d. 0419 a. Pad 0513)
5T20 (Q, OOC d. 0456 a. Pad 0515)
5T25 ex-OCC d. 0456 a. Pad 0515 - 1T25 d. 0525
1T25 a. T5 0546 - 1Y26 d. 0612
1Y26 a. Pad 0632 - 1T30 d. 0640
1T30 a. T5 0703 - 1Y31 d. 0716
1Y31 a. Pad 0747 - 1T35 d. 0755
1T35 a. T5 0816 - 1Y36 d. 0842
1Y36 a. Pad 0903 - 1T40 d. 0910
1T40 a. T5 0932 - 1Y41 d. 0957
1Y41 a. Pad 1017 - 1T45 d. 1025
1T45 a. T5 1046 - 1Y46 d. 1112
1Y46 a. Pad 1132 - 1T50 d. 1140
1T50 a. T5 1202 - 1Y51 d. 1227
1Y51 a. Pad 1247 - 1T55 d. 1255
1T55 a. T5 1316 - 1Y56 d. 1342
1Y56 a. Pad 1403 - 1T60 d. 1410
1T60 a. T5 1432 - 1Y61 d. 1457
1Y61 a. Pad 1517 - 1T65 d. 1525
1T65 a. T5 1546 - 1Y66 d. 1612
1Y66 a. Pad 1632 - 1T70 d. 1640
1T70 a. T5 1702 - 1Y71 d. 1727
1Y71 a. Pad 1748 - 1T75 d. 1755
1T75 a. T5 1816 - 1Y76 d. 1842
1Y76 a. Pad 1903 - 1T80 d. 1910
1T80 a. T5 1932 - 1Y81 d. 1957
1Y81 a. Pad 2017 - 1T85 d. 2025
1T85 a. T5 2046 - 1Y86 d. 2112
~~1Y86 a. Pad 2132 (plat 6) - 5Y86 d. 2145 (plat 6) (OOC a. 0205)~~
1Y86 a. Pad 2132 (plat 6) - 1T91 d. 2155 (plat 6)
1T91 a. T5 2216 - 1Y92 d. 2242
1Y92 a. Pad 2302 (plat 6) - 1T97 d. 2325 (plat 6)
1T97 a. T5 2346 - 5T97 d. 0003 (OOC a. 0041)
*3T25 ex-Reading TCD / 5T25 ex-OOC EMU / 5T20 is copy of 5T25 path

JN114 · 7 Aug 2019

The 387s aren’t planned to split on HX duties - the paths to Old Oak are just to provide continuity for the current 332 operations; which will almost certainly run for a short time into the new TT period.

Bikeman78 · 7 Aug 2019

didcotdean said:
Except at the weekends, when the Cardiff service stops hourly and the Swansea at the ends of the day.

Not regularly stopping the Cardiffs on weekdays except at the ends of a day and a few on peak is a change from all the indicative stopping plans published over the years for this timetable change and is a backward step in my view for connectivity not just to/from Didcot itself but also for Oxford.

I think the problem is mainly in the up direction. Originally they were planned to depart Cardiff Central earlier but they would have conflicted with the XX:45 Nottingham or XX:50 Manchester. If they depart at XX:54 and stop at Didcot, the fast train from Bristol will catch up.

LordCreed · 7 Aug 2019

Wilts Wanderer said:
Are HEX planning driver changes at Paddington in a similar vein to the tube at terminal stations? If so that's a partial mitigation against at least minor delays to the service. Anything beyond 5 mins late will likely require cancellations.

That's the current plan, stepping back each trip onto the following set.

800002 · 8 Aug 2019

JN114 said:
The 387s aren’t planned to split on HX duties - the paths to Old Oak are just to provide continuity for the current 332 operations; which will almost certainly run for a short time into the new TT period.

Thanks for point this out - I've edited my original post to reflect. (I was also silly enough to forget about HEx (GWR) not using OOC at all!

CharlesR · 10 Aug 2019

Does anybody know what the allocations will be like for December? i.e Will we be seeing 10 cars on the North/South Cotswolds at peak times?

FGW_Lad · 11 Aug 2019

I know this is not strictly GWR related but as the Reading to Paddington stoppers will be transferred to TFL, will the full 9 car 345s be used?

700007 · 12 Aug 2019

FGW_Lad said:
I know this is not strictly GWR related but as the Reading to Paddington stoppers will be transferred to TFL, will the full 9 car 345s be used?

Yes - some are already out testing after PM peak between London Paddington and Hayes & Harlington and it is expected to ramp up this week if all goes well.

Wilts Wanderer · 12 Aug 2019

FGW_Lad said:
I know this is not strictly GWR related but as the Reading to Paddington stoppers will be transferred to TFL, will the full 9 car 345s be used?

That is the eventual plan yes, in addition to 345 operation to Heathrow. However both are dependent on the current software/signalling problems being solved. I imagine the backup plan will be to retain enough 7-car sets to operate the Reading service and cut the Heathrows back to Hayes if these issues persist through the Autumn.

Edit - I believe Heathrow operation has already been deferred from Day One in December to a later date. What this means for 9-car operation is now anyone's guess as I was led to understand the two were analogous due to software patching.

kevin_roche · 12 Aug 2019

Wilts Wanderer said:
That is the eventual plan yes, in addition to 345 operation to Heathrow. However both are dependent on the current software/signalling problems being solved. I imagine the backup plan will be to retain enough 7-car sets to operate the Reading service and cut the Heathrows back to Hayes if these issues persist through the Autumn.

Edit - I believe Heathrow operation has already been deferred from Day One in December to a later date. What this means for 9-car operation is now anyone's guess as I was led to understand the two were analogous due to software patching.

Yes the Heathrow operation of 345s, known as Phase 2.2, is not planned until Phase 5a, Paddington to Reading, has been running for 3 months at the earliest.

There is a requirement to validate the running of the TPWS signalling under the ETCS which is how the software on the 9-car units is set up. The current 7-car operation is with standalone TPWS. I believe that the Hayes & Harlington service has also been operated by a 9 car units in the evening in order to test that configuration too.

DaveHarries · 12 Aug 2019

Just wondering but does anyone know why the semifast trains are not using the through lines at Swindon? They are all shown with platform numbers whereas if they used the through lines then any train stopped in the station could be more easily overtaken.

Dave

HamworthyGoods · 12 Aug 2019

DaveHarries said:
Just wondering but does anyone know why the semifast trains are not using the through lines at Swindon? They are all shown with platform numbers whereas if they used the through lines then any train stopped in the station could be more easily overtaken.

Dave

Depends what they need to overtake, your assumption is passenger overtaking passenger whereas it’s more likely to be passenger overtaking freight, with the freight in the centre roads.

Mintona · 12 Aug 2019

DaveHarries said:
Just wondering but does anyone know why the semifast trains are not using the through lines at Swindon? They are all shown with platform numbers whereas if they used the through lines then any train stopped in the station could be more easily overtaken.

Dave

There is only one centre road and it is the up main. Platform 4 is the down main so all down trains will pass through platform 4.

Wilts Wanderer · 12 Aug 2019

kevin_roche said:
Yes the Heathrow operation of 345s, known as Phase 2.2, is not planned until Phase 5a, Paddington to Reading, has been running for 3 months at the earliest.

There is a requirement to validate the running of the TPWS signalling under the ETCS which is how the software on the 9-car units is set up. The current 7-car operation is with standalone TPWS. I believe that the Hayes & Harlington service has also been operated by a 9 car units in the evening in order to test that configuration too.

Thanks Kevin, a most interesting confirmation of what Id heard.

FGW_Lad · 12 Aug 2019

Wilts Wanderer said:
That is the eventual plan yes, in addition to 345 operation to Heathrow. However both are dependent on the current software/signalling problems being solved. I imagine the backup plan will be to retain enough 7-car sets to operate the Reading service and cut the Heathrows back to Hayes if these issues persist through the Autumn.

Edit - I believe Heathrow operation has already been deferred from Day One in December to a later date. What this means for 9-car operation is now anyone's guess as I was led to understand the two were analogous due to software patching.

Perfect, thanks for the detailed response!

Mag_seven · 13 Aug 2019

30907 said:
That's the pattern reported by Modern Railways this month - obviously overtaken by events, but I wonder why the change had to be made, and made so recently?

Overtaken by what events?

HamworthyGoods · 13 Aug 2019

Mag_seven said:
Overtaken by what events?

The timetable offer and validation process.

Mag_seven · 13 Aug 2019

HamworthyGoods said:
The timetable offer and validation process.

Thanks - I actually realised that after I had posted.

cle · 13 Aug 2019

Do we think there might be scope for double-ending any of the stations, especially on the western end of the network? Many of these stations were used to having 2-3 car turbos, and will now have much longer trains. Not much has been done to any of those stations. The eastern ones too, but at least they've typically had longer trains (still single exits though)

There is tons of development - it would be great to increase the catchment at places like Hayes (tricky with huge building) and Southall.

traindoorshut · 14 Aug 2019

Bikeman78 said:
This is very similar to the pre Hatfield HST schedule. It departed Swansea at 0632, Cardiff Central 0725, Bristol Parkway 0800 and got to Paddington at 0914.

Envoy · 14 Aug 2019

From a quick glance, it looks to me that anybody travelling from say Swansea to Birmingham is likely to have a longer wait at Bristol Parkway for a connection with Cross Country. For example, a Swansea to PAD service arrives BPW at 9.14 but the next northbound XC is not until 9.44 (to Edinburgh). This is likely to mean that people going from places west of Cardiff to Birmingham and beyond are likely to make the change at Cardiff to the Nottingham services - which are usually only 2 or 3 coaches. Throw in the fact that Worcestershire Parkway station is also likely to open with the December timetable change and we could well find that the Cardiff to Nottingham services won’t be able to cope with the increased demand. (They can barely cope now - with most people from places west of Cardiff making the change at Bristol Parkway for the Midlands).

* Places west of Cardiff do of course have their own direct services to Manchester via The Marches route (Shrewsbury) which also has links to Scotland via a change at Crewe. It is people heading to/from The Midlands and north-east who are likely to be affected by a poorly matched change at BPW and would put added pressure on the direct Cardiff > Birmingham > Derby > Nottingham trains.

kevin_roche · 14 Aug 2019

FGW_Lad said:
I know this is not strictly GWR related but as the Reading to Paddington stoppers will be transferred to TFL, will the full 9 car 345s be used?

In Mark Wild's latest monthly report which is now published on the TfL website he says:

We are still on course for TfL Rail to start operating the stopping services from Paddington to Reading in December this year (known as Stage 5A). We plan to use the nine-car trains, extending the service from Hayes & Harlington to Reading but there is also a contingency plan if software updates mean that we have to run the seven-car trains. TfL Rail already staff 11 stations between Acton Main Line and Taplow (excluding Slough) as TfL Rail stations after taking over the running of these from Great Western Railway (GWR) in December 2017.

Bikeman78 · 14 Aug 2019

Envoy said:
From a quick glance, it looks to me that anybody travelling from say Swansea to Birmingham is likely to have a longer wait at Bristol Parkway for a connection with Cross Country. For example, a Swansea to PAD service arrives BPW at 9.14 but the next northbound XC is not until 9.44 (to Edinburgh).

It's not as bad as you think. Typically the trains from Swansea arrive at XX:53 and the XC to Birmingham departs at XX:09.

50031 · 16 Aug 2019

I notice the 387 Swindon Cocklebury-Didcot ECS movements, seem to be via Swindon platforms for reversal. No Swindon starters in the new timetable. Will GWR start some back from Swindon once the timetable beds in, or in May?
Also, they are marked as 75mph Sprinter when empty stock, then become EMU 110mph when in passenger service from Didcot.

JonathanH · 17 Aug 2019

50031 said:
No Swindon starters in the new timetable. Will GWR start some back from Swindon once the timetable beds in, or in May?

Why would they do that?

Are you suggesting some kind of demand between Swindon and the stations from Cholsey to Tilehurst?

Possible reasons why this could not happen include:
* They (presumably) can't operate DOO(P) from Swindon so would need a guard as far as Didcot
* I guess that LTV guards don't sign Didcot to Swindon
* I don't suppose that any other GWR train managers sign 387s
* Demand between Swindon and Didcot at the relevant times is met by the IEP services.

50031 · 17 Aug 2019

JonathanH said:
Why would they do that?

Are you suggesting some kind of demand between Swindon and the stations from Cholsey to Tilehurst?

Possible reasons why this could not happen include:
* They (presumably) can't operate DOO(P) from Swindon so would need a guard as far as Didcot
* I guess that LTV guards don't sign Didcot to Swindon
* I don't suppose that any other GWR train managers sign 387s
* Demand between Swindon and Didcot at the relevant times is met by the IEP services.

Because it was reported as a proposal to to start back some 387s from Swindon (Morning only) , in any case, the intention has been to clear 387s through to Cardiff as Crowdbusters for Rugby and other events..

Obviously I'm not suggesting demand from Swindon to Cholsey, Goring, Pangbourne, Tilehurst!

JN114 · 17 Aug 2019

No GWR Guards sign 387s full stop. They are only operated DOO(P) at present.

DOO agreement prohibits extensions of DOO operations beyond its current Geographical limits; so Swindon will require Guards.

There have been aspirations to run 387s in regular passenger service to/from Swindon; to date they are only aspirations with no firm/committed plans.

GWR Dec 19 timetable

Member

RailUK Forums

Established Member

Member

Member

Established Member

Established Member

Member

Member

Member

Member

Established Member

Established Member

Member

Established Member

Established Member

Established Member

Established Member

Member

Forum Staff

Established Member

Forum Staff

Established Member

Member

Established Member

Member

Established Member

Member

Veteran Member

Member

Established Member