Indeed, and it's not just people in Weston that are affected -- what about the Crosscountry trains stuck behind a local train at Worle waiting for the single line to be free? I can't believe that doesn't still happen, especially at times of disruption.
As an
XC▸ passenger... I can comfirm my experiences are this:
1) XC Service is on time, generally no disruption unless a stopping service is around 45 - 50 minutes late... e.g. 13:53 Service will delay the 14:44 Service. In all honesty, that doesn't happen too often
2) XC Service is 10 - 15 minutes late, again using the 14:44 as an example, the stopper service leaves at 14:53, If the Crosscountry Service still hasn't platformed or hand hasn't finished pax boarding, The signallers will release the 14:53 onto the main line. 90% of the time, the stopper is held at the signal gantry at Bedminster, Where the XC Service passes on the adjacent line
3) XC Service is 20 minutes late, the 14:53 will be allowed to continue passed Bedminster. When the XC service catches up, pax on the 14:44 endure a motion of stop, start to Yatton, Where the 14:53 is moved onto the passing loop, so the XC Service can overtake.
4) XC Service is 30 minutes late, The 14:53 will be allowed to proceed past Yatton, this is where the bottleneck occurs. If there is a service from Taunton on the Up Main, the 14:53 has to wait for this to pass, before proceeding to Weston Milton. Once the 14:53 has proceeded onto the Weston Branch, the XC Service gets a clear signal to Taunton. Sometimes there is a delay on Cogload Junction Bridge for an
FGW▸ HST▸ to continue onto Taunton, thus only incurring one delay (to the XC Service)
I'm afraid to say it... But numbers 3 and 4 happen to me at least once a week, on the 14:44 or 15:44... Hardly suprising though as those services start at Dundee. But that doesn't alter the fact that the train is still late
I'm not critercising anybody for that list of scenarios, They are just what I have observed when travelling XC for the past 6 months