Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by matth1j at 07:54, 6th November 2024 |
Yep, in a Chippenham station waiting room now
When I first looked at the National Rail app (~0540) the service was completely cancelled and I'd started making alternative arrangements. Was going to catch the 271 bus and would probably have made it to Bath in time to pick up the train I've missed at Chippenham. Oh well...
Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by grahame at 07:25, 6th November 2024 |
Picking up on a post in the TransWilts thread
I also note this
So the unofficial connection at Chippenham will certainly not ‘make’ this morning as the Worcester train is going to run behind the diverted Plymouth - Paddington. Looking at the OpenTrainTimes signalling map, it appears the Worcester train is being held-back at Westbury so the line towards Bath isn’t blocked at Bradford Junction while it waits to go onto the single line to Melksham.
06:35 Salisbury to Worcester Foregate Street due 09:47 will be reinstated.
It will be started from Westbury.
It will no longer call at Salisbury and Warminster.
This is due to a shortage of train crew.
It will be started from Westbury.
It will no longer call at Salisbury and Warminster.
This is due to a shortage of train crew.
I also note this
04:54 Plymouth to London Paddington due 08:37 will be diverted between Westbury and Reading.
It will no longer call at Pewsey, Bedwyn, Hungerford and Newbury.
This is due to the emergency services dealing with an incident.
It will no longer call at Pewsey, Bedwyn, Hungerford and Newbury.
This is due to the emergency services dealing with an incident.
So the unofficial connection at Chippenham will certainly not ‘make’ this morning as the Worcester train is going to run behind the diverted Plymouth - Paddington. Looking at the OpenTrainTimes signalling map, it appears the Worcester train is being held-back at Westbury so the line towards Bath isn’t blocked at Bradford Junction while it waits to go onto the single line to Melksham.
Just left Westbury and switched from "Delayed" to "07:36" on the board at Melksham
Where there's a quarter hour delay, it does nit make sense to try and maintain the connection, as this morning.
Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by brooklea at 07:14, 6th November 2024 |
Picking up on a post in the TransWilts thread
06:35 Salisbury to Worcester Foregate Street due 09:47 will be reinstated.
It will be started from Westbury.
It will no longer call at Salisbury and Warminster.
This is due to a shortage of train crew.
It will be started from Westbury.
It will no longer call at Salisbury and Warminster.
This is due to a shortage of train crew.
I also note this
04:54 Plymouth to London Paddington due 08:37 will be diverted between Westbury and Reading.
It will no longer call at Pewsey, Bedwyn, Hungerford and Newbury.
This is due to the emergency services dealing with an incident.
It will no longer call at Pewsey, Bedwyn, Hungerford and Newbury.
This is due to the emergency services dealing with an incident.
So the unofficial connection at Chippenham will certainly not ‘make’ this morning as the Worcester train is going to run behind the diverted Plymouth - Paddington. Looking at the OpenTrainTimes signalling map, it appears the Worcester train is being held-back at Westbury so the line towards Bath isn’t blocked at Bradford Junction while it waits to go onto the single line to Melksham.
Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by matth1j at 09:55, 5th November 2024 |
But it really should NOT be this game and big smileys as to whether a daily commute works!
To be fair to FGW, 3 of those misses were mainly due to the speed restriction (reported by brooklea) around Westbury.Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by Mark A at 16:52, 4th November 2024 |
Having travelled that way a couple of times in the past, both missed, the first one because the Melksham train came alongside at Chippenham a little late and the connecting train was leaving.
The second time, a little late but less so, and the Melksham train sat at the platform for a full minute until the Bristol train's doors locked at which point we were allowed off (and the Bristol train then sat, doors locked, for what felt like another minute.)
That second event event caused me to mutter the words of a friend's father (whose work included being deployed to various ports and commercial docks along the south coast...)
"GWR always made sure they never connected with anything".
(Things seemed to have progressed that day, in that case they didn't connect with themselves...)
Mark
Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by grahame at 14:19, 4th November 2024 |
... than the odd (Sorry Mat, I'm sure you aren't, but you know what I mean) customer might be making a connection from Melksham ....
Passenger journeys between Melksham and Bath / Bristol by train are over 12,000 per annum, and those are the 3rd and 5th most popular destinations from Melksham, even though a change of trains is required. In fact they are the two most popular destinations beyond the TransWilts service - even more than London, Salisbury, Warminster ...
Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by grahame at 12:48, 4th November 2024 |
With respect, there may ne a good reason that these trains aren't a booked connection - maybe it makes an important connection in Bristol say? More people are likely to need that to work than the odd (Sorry Mat, I'm sure you aren't, but you know what I mean) customer might be making a connection from Melksham. Trains make connections all over the network, and these connections have to be prioritised, of course.
With respect, Chris, these issues have been raised and addressed already in this thread for this particular "connection". The little matter of why Chippenham remains a "5 minutes needed to change" station when it's just a single Island has been conveniently overlooked. It seems to come down to "we can't run trains reliably and it would cost us too much in delay/repay to make them a connection in any of the three ways suggested by the customer'. There are times I feel that we are having wool pulled over our eyes, and perhaps this is one of them - done this time by applying blanket rules to which there are exceptions elsewhere to justify the status quo.
Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by ChrisB at 12:24, 4th November 2024 |
With respect, there may ne a good reason that these trains aren't a booked connection - maybe it makes an important connection in Bristol say? More people are likely to need that to work than the odd (Sorry Mat, I'm sure you aren't, but you know what I mean) customer might be making a connection from Melksham. Trains make connections all over the network, and these connections have to be prioritised, of course.
Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by grahame at 11:49, 4th November 2024 |
This is exactly why it isn't a booked connection though.
If you're saying that to make it a connection by adjusting the time of the Bristol train (or putting a short "hold" order on it if the supposed incoming connection was crossing in front of it) would be operationally inconvenient, yeah, I agree. But the railway is there for the passengers not for the convenience of those who run them.
And, yes, were it a booked connection (and it would be at so many other stations that have same-platform connections - see my Hove / Worthing / Chichester example upthread) without a hold order, it could get expensive on delay/repay. But I can't help feeling that the tail is wagging the dog on this one.
Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by ChrisB at 11:26, 4th November 2024 |
This is exactly why it isn't a booked connection though.
Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by grahame at 10:16, 4th November 2024 |
But it really should NOT be this game and big smileys as to whether a daily commute works!
Image from ... https://www.trophiesplusmedals.co.uk/fun-smiley-face-centre ... where you can buy them as stickers
Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by matth1j at 09:55, 4th November 2024 |
Oh dear ... please keep logging.
Made it!! 6th time lucky Only by the skin of my teeth though; 3 minutes late departing Melksham so I didn't rate our chances, but those were improved by the Paddington train being cancelled (shortage of train crew) so no additional delays into Chippenham. Boarded the Bristol train moments before the doors closed.
Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by matth1j at 14:11, 24th October 2024 |
Most of last week apparently there was a temporary speed restriction delaying trains into Trowbridge from Westbury
Ah - well I guess that would explain it, and today's delay wasn't on that line. Thanks for the infoI'm going to be working from home next week due to the absence of direct Chippenham/Bath-Bristol trains. (The official route if I catch the usual 0721 Salisbury-Worcester service at Melksham is to continue on to Swindon before changing to one that goes to Bristol Temple Meads via Bristol Parkway I think. At least there's no bus replacements )
Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by brooklea at 12:15, 24th October 2024 |
Each of the 3 times I've caught it this week it has departed Salisbury on time at 0635, but has accumulated delays through Warminster, Westbury and Trowbridge to end up being at least 4 mins late by the time it reaches me at Melksham.
No, 4 mins isn't that bad, but it means I (and others) miss my unofficial connection at Chippenham, where its departure time of 0731 is 3 mins before the Paddington - Weston-super-Mare 0734 that I catch to Bristol, ideally. Missing that means hanging around Chippenham station for ~30 mins for the next 0809 Bristol service (the official connection).
I would normally expect to catch the 0734 at least 2 out of 3 times per week, and I think missing it 3 times in a row is a first.
Anyone know if there is anything going on that might explain this eg. engineering work?
No, 4 mins isn't that bad, but it means I (and others) miss my unofficial connection at Chippenham, where its departure time of 0731 is 3 mins before the Paddington - Weston-super-Mare 0734 that I catch to Bristol, ideally. Missing that means hanging around Chippenham station for ~30 mins for the next 0809 Bristol service (the official connection).
I would normally expect to catch the 0734 at least 2 out of 3 times per week, and I think missing it 3 times in a row is a first.
Anyone know if there is anything going on that might explain this eg. engineering work?
Most of last week apparently there was a temporary speed restriction delaying trains into Trowbridge from Westbury - it’s been removed now I understand.
Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by grahame at 09:55, 24th October 2024 |
It's already on "Next Door" - BUT there is so much material out there that it's hit and miss whether you'll see it. Also on Facebook, signs in the bus stops, various group emails, and in the Melksham News. [[[ snip - etc ]]]
P.S. I sometimes publicise things through my LinedIn account too, and through TravelWatch SouthWest and other regional and industry feeds. As a meeting for the Melksham Community to look at getting our own house in partnership and campaigning order for the future, I have chosen not to shout loudly about these particular meetings at those places. Anyone welcome - but I would hate industry /operato and regional specialists to turn up and be disappointed at the more local nature of the proceedings.
Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by grahame at 09:40, 24th October 2024 |
Are you coming along tomorrow (14:30 or 18:30 at The Campus)
Thanks for the heads up - will try to make the 1830.I don't know where else you have publicized it, but might be worth mentioning it on the Nextdoor website if you haven't already. Seems to be quite popular: https://nextdoor.co.uk/
It's already on "Next Door" - BUT there is so much material out there that it's hit and miss whether you'll see it. Also on Facebook, signs in the bus stops, various group emails, and in the Melksham News. Past members have been emailed and community transport contacts and both Melksham Town and Melksham Without have helped spread the word.
There is so much news / information out there these days that there are going to be people missed ... I recall when I was on the SCOB (Shadow Campus Operation Board) we counted ten publicity channels and still had people say "we hadn't heard" ... and in those days / on that group we had a budget where we could spend a few £ to reach people.
Could always do more ... at this point, please tell friends, familiy, colleagues and even people you don't like but could work alongside ;-) ... I am in process of getting final stuff together ...
Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by matth1j at 09:28, 24th October 2024 |
Are you coming along tomorrow (14:30 or 18:30 at The Campus)
Thanks for the heads up - will try to make the 1830.I don't know where else you have publicized it, but might be worth mentioning it on the Nextdoor website if you haven't already. Seems to be quite popular: https://nextdoor.co.uk/
Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by grahame at 08:32, 24th October 2024 |
No idea when Chippenham's other platforms were taken out of use
There used to be a line running to Calne https://en.wikipedia.org/wiki/Chippenham_and_Calne_line which the disused platform served.It wasn't [always] that simple. I recall that at one time, the out of use platform was the main line towards Bristol, and the centre platform where the Bristol line now runs was two terminal platforms - one in each direction. That arrangement was taken out to simplify the track and to allow faster non-stop running on a straighter line.
Times have changed again and all regular scheduled trains (I think) now call at Chippenham - there may be just one early Sunday morning train London to Penzance that's routed via Swindon and Westbury that does not. Perhaps it would make sense to re-instate the 3rd platform as the main through road, with the current Bristol platform having access at both ends off both lines - a "W" arrangement. Provide a lay-by in either direction, and a terminal platform in either direction that can be entered and left without effecting trains in the other direction. I believe there may be a precedent for this layout at Arnos Grove.
Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by grahame at 08:21, 24th October 2024 |
Missed the connection again today; that's 5 times in a row now (for my commute). Doors on the 0734 Bristol train closed as we pulled in Probably would have been ok if we hadn't got held up behind the late running Paddington service.
This is getting ludicrous. Are you coming along tomorrow (14:30 or 18:30 at The Campus) - not a bad idea to have dealing with this on the agenda of ideas. Something we can apply some gentle pressure on to get a few seconds hold on a train that doesn't conflict with anything else on its way into Bristol and just sits there for 10 minutes ...
I am minded of all those signs we see around these days saying "don't abuse our staff and be considerate of them" ... but apparently it's OK for staff who are 'just following the rules' to take inconsiderate actions like locking train doors in passenger's faces. Please take that as a comment on modern society and how things are managed, and not on individual operational staff.
Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by matth1j at 07:47, 24th October 2024 |
No idea when Chippenham's other platforms were taken out of use
There used to be a line running to Calne https://en.wikipedia.org/wiki/Chippenham_and_Calne_line which the disused platform served.Missed the connection again today; that's 5 times in a row now (for my commute). Doors on the 0734 Bristol train closed as we pulled in Probably would have been ok if we hadn't got held up behind the late running Paddington service.
Something a bit odd this morning - the Salisbury-Worcester train departed on time, and was only a minute late when I caught it at Melksham. But by then the National Rail app was saying 'This train has been delayed by train crew being delayed'
Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by Mark A at 12:05, 21st October 2024 |
No idea when Chippenham's other platforms were taken out of use, perhaps the 5 minutes dates from past times.
Mark
Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by grahame at 11:01, 21st October 2024 |
A question for our rail experts. The standard interchange time between trains is 5 minutes but there are exceptions around - here's an example from a timetable showing a whole cluster of them.
Why? Well - 10 minutes to change in Brighton makes sense. It's a big station and arriving from Lewes and leaving for Worthing is a bit of a walk around - it has to make sense. On the other hand, Worthing and Chichester don't need as long, and it's amazingly short at Hove.
For Swindon, arriving on platform 4 and leaving on 2 and even the five minutes may be tight. For Bath Spa, with long sets of steps or queues for the lifts, again it makes sense. And both Trowbridge and Westbury can involve a change or platform too so you can sorta-get the logic. But why on earth is it 5 minutes at Chippenham - an island platform when all changes are cross-platform, or to a following train on the same track?
Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by grahame at 08:30, 21st October 2024 |
Typing this in Chippenham station waiting room... yep, late again. 6 minutes at Melksham, made some of that up I think so pulled into Chippenham just as the Bristol train was pulling out. Great
Oh dear ... please keep logging. The Coffee Shop will not get any "official action" on this frustrating issue, but it does keep it bubbling along and we are read. No promises of a result, but a promise to try further for a practical change.
Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by matth1j at 07:43, 21st October 2024 |
Typing this in Chippenham station waiting room... yep, late again. 6 minutes at Melksham, made some of that up I think so pulled into Chippenham just as the Bristol train was pulling out. Great
Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by grahame at 09:44, 19th October 2024 |
Reading Real Time Trains, the 4 minutes (so unofficial) connection missed again yesterday by between 30 and 45 seconds. The delay to the 06:35 from Salisbury was picked up in the short stretch from Westbury to Trowbridge - on a 7 minute schedule from arriving Westbury to leaving Trowbridge yesterday took 12. It was back on time when it departed Swindon, but of course that's too late in its journey for the Chippenham connection.
The train that left Chippenham spot on time as the train from Melksham pulled in arrived a minute early into Bristol at 08:02. The next train to Bristol from Chippenham arrived there at 08:39 - 3 minutes late.
Edit to correct - the words had not come out right this morning and the original was unclear and incomplete - my apologies to members who were trying to work out what I meant!
Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by IndustryInsider at 15:28, 17th October 2024 |
In the interest of safety (good card to play ) could the Bristol train have one of those rare "hold" orders on it such that if the train coming up from Melksham has to cross in front of it anyway, it connects? If the train from Melksham is so late that the Bristol train crosses first, fair enough.
Might that minute or two extra delay potentially cause a safety problem at Bristol Temple Meads as passengers rush to try and make the unofficial connection towards Gloucester at 08:06?
Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by grahame at 14:11, 17th October 2024 |
For readers of this thread - if the train from Melksham is arriving into Chippenham a couple of minutes late...
If the train does happen to depart Melksham on time, it's even more frustrating when it gets held up by the late running Bristol-Paddington service, due to depart Chippenham at 0726...And it's that Paddington express which prevents it running earlier to increase the margin THAT way ... quite apart from it being threaded through Westbury!
edit to add Westbury comment
Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by matth1j at 13:35, 17th October 2024 |
For readers of this thread - if the train from Melksham is arriving into Chippenham a couple of minutes late...
If the train does happen to depart Melksham on time, it's even more frustrating when it gets held up by the late running Bristol-Paddington service, due to depart Chippenham at 0726...Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by matth1j at 13:04, 17th October 2024 |
Until moving to Melksham in 2016 I used to commute to Bath from Reading (Earley actually) 3 days a week, catching what was the 0726. And that was great; hardly anyone on it, until a load boarded at Chippenham. I suspect the pre-7 (the 0656 in my day) would be even quieter.
Only problem was I had to buy advance tickets a couple of months beforehand to bring the cost down from over £100 to something under £30 IIRC. No digital option in those days so always had a pile of tickets waiting to used
Re: 0635 Salisbury - Worcester Foregate Str thru Melksham keeps running late Posted by grahame at 12:26, 17th October 2024 |
For readers of this thread - if the train from Melksham is arriving into Chippenham a couple of minutes late, passengers in the know are watching out for the departing train to Bristol as they pull in ... and there is an almighty scramble across the platform to transfer if it's still there, before the doors get locked. Can't be safe. In the interest of safety (good card to play ) could the Bristol train have one of those rare "hold" orders on it such that if the train coming up from Melksham has to cross in front of it anyway, it connects? If the train from Melksham is so late that the Bristol train crosses first, fair enough.
P.S. The train from London leaves Reading - last stop before Swindon - before 7 a.m. - how busy is it that early in the morning with passengers travelling to Chippenham and beyond?