Great Western Coffee Shop

Cancellations to services between Trowbridge and Chippenham via Melksham

Due to heavy snow at Westbury disruption is expected until the end of the day.

Train services between Trowbridge and Chippenham via Melksham will be cancelled.

Customer Advice
Due to engineering works in the Westbury area, rail services are already disrupted.

Rail replacement road transport was in operation, however due to the snow, some coach operators are standing down and therefore the advertised rail replacement road services may not run.

Slightly confusing message in that there were no *train* services planned through Melksham today in any event due to the engineering work.

Oh dear ...

During the Westbury closure the 17:35 from Swindon has been operated with the unit which worked the morning service from Trowbridge.    The unit has spent the day idle in Platform 2 at Swindon.

Whatever the fault with it was, it left Swindon at 17:00 today to head to St Philips Marsh depot in Bristol.

As far as I am aware it is the only train, or bus replacement, not to operate for passengers over the duration of the works.

Celebration!    The triains are back and running again.   Lots of  2 <-> 3 carriage swiches today and in this queter season that won't make a huge difference (2 carriages on "The Weymouth" in the summer WOULD)

Running time 52 minutes, Warminster to Swindon.  What a wonderful contrast to the last month.  Buses have performed well, but the journey has taken twice as long.

Those are the "clever" services which are crewed by staff coming off the 10:35 London to Exeter at Westbury which has been cancelled due to flooding ... not sure flooding where ... and our fair weather railway fails again!

Ah  - it must be this


And they are economic with the truth there - disruption is expected until 13:57 and not just until 13:00 ...   

Woohoo - my 07:21 Melksham-Chippenham this morning was on time, and I was able to catch the 07:34 Weston service at Chippenham without 'sprinting' (I use the term loosely) across the platform. All those upgrades have worked :)

Appreciate there have been fewer trains so far this year, but by this stage of 2024 we were on page six of the disruptions topic.

Indeed.   With the engineering hand we were dealt this year, thiough, a comparison to previous years can only be a distant one.

A*week* between entries? Strewth!! :o :o ;D

Not a problem of the early part of the route though it may get cosy into Southampton.  At least it's running now - giving s Southampton arrival at ten past 8 rather that ten past 10 as it was a month ago.

Good - makes sense

Sensible.  On schooldays should always be 3 carriages - otherwise it overloads in the Stroud Valley. During covid was the "most overcrowded train" on GWR ...

Journey Check reports just 3 cancellations (and no short runs and  just one delayed train) across the whole of the GWR network as I write.


and in case you wondered

Restored (hope not too many people have replanned their journey) but now


Edit to add ... 7 minute delay, mostly made up by a quick reversal at Swindon

If it can get to Westbury - am I to read it / can I guess that the train is being raided off the Southampton service to go somewhere else instead?

Yes, it went to Weymouth at 06:50.

Perhaps it always should - with a train starting from Westbury forming the Southampton service a few minutes later.  Discussion point but the failure of the train from Swindon (and Trowbridge) to connect onwards to Weymouth is one of life's frustrations ... not on the same scale as war and famine, but still a frustration ...

Out of order - from yesterday:

(https://www.wellho.net/pix/fym.jpg)

The railway was closed at Trowbridge "at the request of the police due to ammunition being found near the line" and these things happen.   The ongoing information at Melksham was AWFUL - for the longest time the 06:32 just said "delayed"  and the 07:21 was on time.  Even when the southbound train was stated with a time again - estimated 07:18 - the northbound train at 07:21 still said "on time".   That makes a mockery of the "system knowledge" as it's predicting an impossibility on the single line and I found myself chatting with other passenger and telling them "not before 07:33" for the Worcester train.

"Delayed" on a 3 line screen is useless; there IS a big screen there (facing the car park) and all that was saying was the same thing with 2 lines each for the following 3 or 4 services.   Could have been more descriptive.   When I eventually got to Westbury, the screens there were showing distrupted train departures alternating with a desciption of what the problem was and why.   Why on earth could the same not be done - automatically share across stations big and small with responsive design so there's no need for human input on a. station by station business at the time of extreme re-organisation?   

I was at the Rail Innovation Exhibition yesterday (ironic) and lots of clever stuff. BUT there could be so much basic stuff done getting information right for passengers at the time of disruption - accurate (and not afraid to say "don't know"), consistent, and perhaps with interactive tools.  Lots of things being displayed but frightening on the information display side as to how fragmented, partial and at times embryonic it is - leaving passengers literally out in the cold.   I did a better job in Melksham reading my phone and helping to explain roughly what was going on from scant evidence.

Yes, I did try the help point.  It was obvious to me that the 06:32 would miss the connection at Westbury on into the 07:00 to Paddington with my "this train only" ticket, and if that misses the next fastest way to London in the 07:21 change at Swindon.   The nice chap on the help point told me that my next train was the 07:58 from Westbury and my ticket would be accepted on it, but that my advanced ticket was for that route only and would not be accepted if I took the next alternative which happened to use a different route (via Swindon) even if it got me there quicker. He then told me that I COULD use my ticket on SWR trains such as one that was running from Yeovil Pen Mill because "ticket acceptance is in place".  I got the impression that his geography was not great and he was of the understanding that Yeovil is just a short walk up the road from Melksham.

2O19 "adjusted" to not run beyond Salisbury (it was so late that the school traffic it normally carries south of there would have gone on the following train operated by SWR if they could all get in!)

2M81 got to Westbury on time, and sat there until the line re-opened ... and for some considerable time thereafter.  It was still there when I arrived at 07:30 when it should have left at 07:05 ... and stayed even longer as trains via Bath Spa were displatched out of order - perhaps because it was so late that "what's another 10 minutes?".  There were hard decisions to make here - a backlog of trains and a limited line.

Net result ... 2M81 ran only just ahead of the path of 2M13, probably took much of its traffic, and delayed 2M13 as well.   Two trains at Melksham, 14 minutes apart, to Swindon must be close to a record.   Interesting to see it can be done, and perhaps just a gentle warning of how NOT to do it if we end up with competing Go-op trains - they need to be spaced out!

Zero information about any alternative ... but you are told about delay/repay.   Another micro example of the macro failure to look out for the passengers - the customers?

Rather than just criticise, I should offer an alternative.   The x34 bus now runs on a Sunday from Trowbridge to Chippenham, and tickets should be accepted on that and it should be included in the journey planner.  Passengers who normally travel through Melksham should be allowed to travel via Bath Spa, changing trains there, and be advised they can do so at the same price which should be offered by the online booking applications once the cancelled train is removed from them. You will note than none of this "looking after the passengers" results in extra vehicle or staff miles on the ground - it's helping people use what's already there!

---

Looking wider (and not just for a solution this Sunday morning) in terms of train and bus interconnection at stations, the x34 is a fascinating case.   The service runs seven days a week, daytime only; the Sunday service was revived quite recently after a gap of many years.  Evening services, provided by a competing operator, were lost a decade ago when that operator pulled out of the route.  Further study to follow ....

Still connected with the Paddington train at Swindon - which looks like it might have been held back a few seconds. Good - no problem here.

The 05:11 from Gloucester in reality is a chaining together of a series of separate workings and through passengers from Gloucester to Southampton must be rare as hen's teeth.  Even the crew changes along the way. It is scheduled to stop longer than is needed purely to drop off and pick up passengers at Swindon, Chippenham, Westbury and Salisbury and paths allowing could (and has been know to) make up much more time.   Good - whilst extended station dallies are not to be encouraged, a margin of time in schedules to ensure that trains turn up and connect on time even if held up earlier in their or a previous journey makes sense - especially where though passengers at "pause" stations are a minority of passengers.

 

Here we (don't) go again


At least it says "this" train - so it's not been theived off the Southampton service to run the Weymouth train from Westbury this time

And again ....

That is very odd indeed ...

(https://www.wellho.info/pix/rusurecan.jpg)

So it was capped at Westbury due to a fault on the train, but then 5 minutes later conveniently able to form a train to Weymouth?   Yes - there is a fault on the train (no loos reported on the Weymouth train) but it very much looks to me that "this is due to a fault on this train" is NOT why it didn't continue to Southampton - it was "hijacked" to form the Weymouth service.  Am I reading this wrong?   Are we being fed porkies?

16:23 Westbury to Swindon due 17:05
16:23 Westbury to Swindon due 17:05 will be cancelled.
This is due to a shortage of train crew.

17:35 Swindon to Westbury due 18:19
17:35 Swindon to Westbury due 18:19 will be cancelled.
This is due to a shortage of train crew.

Clearly not telling public the truth.

Train is announced as terminating early at Westbury (but the alleged fault allows it to continue from time of announcement through to Westbury, so if it could continue that far, could have got to Southampton).

Train is miraculously fixed at Westbury, and can be used to form another service missing a train. 

2V58 the return train from Southampton is showing as cancelled for reason M8 (problem with the train), ie it's not available, although codes YR or YU (tactical unit swaps) sound more likely

Busiest train of the day ... no alternative suggested except "get your money back and have a free journey on the next train" as it's over an hour later.  Why chose this train to cancel if you're short of crew?

Strangely, it seems to have disappeared from Real Time Trains altogether.

On RTT, it has acquired "VCN" status, so you need to select the "CAN" option to view cancelled services. The reason given is ZW - unknown cause.

Also bearing a VCN status and ZW code on RTT is 2M34, the 20:14 Swindon-Westbury. There's nothing on Journeycheck about this service, and it is currently (at 19:22) shown on TIGER as "on time". Watch this space!  ???

Incidentally, the 18:37 Westbury-Swindon was delayed at Trowbridge for about 25 minutes (due to a "broken down train"). It lost a further 5 minutes due to missing its slot on the single line through Melksham.

2M24 (see above) is running.  :)

Nothing on journey check about what passengers should do - purely "feature" not "benefit" which I was taught was not the way to do it in my sales training.

There is an x34 bus at 08:48 from Melksham to Chippenham (railway station if required) that goes past the top of station approach in Melksham - doesn't actually stop there normally, but it [sh/c]ould.

There is an x34 bus at 09:25 from Chippenham railway station to Melksham and Trowbridge (on Sunday, of course, it does not go to the stop near Trowbridge station, and even by the time it reaches Melksham and passes close to the station, the train will have left.

Lots of things illustrated by these goings on ...

Alterations to services between Westbury and Swindon via Melksham

Due to engineering works not being finished on time at Swindon all lines are closed. Disruption is expected until 10:30 23/02.

Train services between Westbury and Swindon via Melksham may be delayed by up to 45 minutes or revised.
Customer Advice
As a result of engineering work not being finished on time there will be severe delays / disruption to services on this route this morning. Please accept our aplogies for any inconvenience this may cause.

A few years back there was a Sunday train from Westbury which was timetabled to terminate at Melksham and then return.  However in the end it was extended to Chippenham as it was reported you couldn't turn a train at Melksham as it "confused" the axle counters.   Perhaps that is no longer the case.

Not sure - there is "can't" and there is "CAN'T".

Trowbridge is a classic example - you can't turn a train arriving from the north there but yet it HAS been done when line to the south was blocked by an "incident".

and now ...


I guess that it was re-instated?  Not sure where the service disruption is - could it be the disruption caused by engineering works that mean the is bustitution from Westbury in the Frome direction?

I'v said it before but rather than a frightening will be cancelled from the earlier report which has a degree of finality about it, and suggests it's not even with checking back later, could we have a may be cancelled early caution system - rather like signals are not just red and green, but red, amber and green?

In the end it left on time,

... which supports grahame's suggestion: how many potential passengers on that service were put off by that original report, and made (subsequently proving to be unnecessary) alternative travel arrangements, such as taking the car instead?

 ::)

Person hit by the 13:03 London Paddington to Plymouth near Pewsey.

Still saying disruption expected until 17:00, although just noticed that the 17:50 from Swindon is cancelled (I go Chippenham-Melksham). I start at Bristol so I'll be taking the normal bus to Melksham from Bath.

Line re-opened at 4pm.

 :(

Oh dear - https://www.wiltshire999s.co.uk/person-dies-struck-train-pewsey/?


Hugest sympathy and thoughts with relatives, friends and staff involved.     Not for immediate consideration, but we really need to allow diverted trains to double up for local ones when diverted.

Reinstated as a result:
16:23 Westbury to Swindon due 17:05
17:35 Swindon to Westbury due 18:19

Some sort of problem on the 17:50 Chippenham to Melksham as well - stopped at Melksham on time I think but then doors didn't open for over 5 minutes. Train was still sitting there as I headed back to Whitley over the railway bridge, although I believe it did eventually continue on to Westbury.

I am hoping the 21:16 from Westbury runs (selfish  ;D ) as I'm connecting into it from Portsmouth.  As the connection train from Portsmouth has 5 carriages (2 + 3), GWR could split it at Westbury if the train that would normally go to Swindon is in need of fixing.    That late of the evening, 5 carriages not needed all the way to Cardiff?

It ran ... not sure where the rolling stock came from, 158745 whereas it had been 158767 on the service in the morning. nice sprinting of passengers - I guess there were 20 into Melksham and (I did not walk through as I ate my bike) and perhaps a third got off. Not sure how many joined.

For today.


There's a shock - it's because the 10:35 Paddington to Exeter is late and the crew due off that at 11:56 at Westbury are not expected until 12:30.

Sorry, as typos go - this is one of the best.   ;D

Oh dear ....

Due out at 12:17, but the crew didn't arrive on the express from London until 12:35 and the Swindon train left at 12:37 (20 minutes late).  But then it got held up at Bradford Junction awaiting the single line to Chippenham, and was no less that 33 minutes late at Melksham. Why the extra delay?

A freight train due to follow the 12:17 at 12:30.  It was at Westbury early, and was allowed to leave at 12:21 - 9 minutes early.    Which should have been OK - except that it got held on the single line awaiting the other main line at Thingley and from being 11 minutes early at Melksham it was 3 minutes late by Chippenham - 27 minutes from Melksham to Chippenham.   And while it waited for the line to Swindon, the passenger train sat waiting for the single line,

A suggestion was made at one time to have an intermediate signal on the single line, and that would have helped today. Better is the more recent favoured plan of an intermediate loop which implicitly lets trains follow each other at a closer headway that a whole-single-line solution.

The freight struggled to get up the bank at Dauntsey trapping the Melksham service behind it.  Both now on the move.

The return working, the 13:15 from Swindon, left just over an hour late.

And the next round ...

Ketchup or brown? I had a pasty for lunch myself, but chacun à son goût as they say.

I knew it rang a bell.........

https://historicflix.com/michel-lotito-the-man-who-ate-everything/

Moving on from bikes eaten with Branston pickle ...

The staff connection off the London to Exeter train at Westbury once again triggered ongoing disruption ...
33 minutes late
66 minutes late
60 minutes late and terminated short
18 minutes late and started short
... major disruption all afternoon.

Naughty thought - if we had an hourly train, couldn't it have simple been a single train lost - one wait of 60 minutes rather than a a total of 177 minutes lost even before you look at extra delays and missed connections with a change of trains along the way.

20:08 Westbury to Chippenham due 20:34
20:08 Westbury to Chippenham due 20:34 will be cancelled.
This is due to a shortage of train crew.

No problem ... and will reduce (over)crowding at the very end of that journey


No problem ... and will reduce (over)crowding from Swindon to Stroud

17:50 Gloucester to Salisbury via Swindon:

Hold it!

Coincidentally(??), the same train as was on the 17:50 Gloucester to Salisbury yesterday (165132 according to RTT).

Swapping units at Westbury this morning caused an eleven minute delay to the TransWilts train, but presumably there were working toilets on the substitute train (and an extra carriage), so not all bad news (unless you were on the Castle Cary to Filton train without a working loo from Westbury….)

Just back from a week in Lanzarote, and was pleasantly surprised to find my 0721 Melksham-Chippenham train on time this morning. But it didn't last - the Paddington service that precedes it into Chippenham was running a bit late, so mine was delayed and I just missed the (unofficial) connection with the 0734 Chippenham-Bristol service. Then the next 0809 was cancelled (train fault). And now the 0832 is showing as 'running late' by 11 mins.

Good to be back :)

Welcome home ... what more can I say?

Looks like a 'false' report - just 1 minute late off Westbury in the end

Have to love this - NOT a points failure anywhere near us but a knock on delay from

Indeed not anywhere near Wiltshire - actually this points failure mentioned by GBM elsewhere on the forum https://www.firstgreatwestern.info/coffeeshop/index.php?topic=28556.msg359538#msg359538 (https://www.firstgreatwestern.info/coffeeshop/index.php?topic=28556.msg359538#msg359538), which was in Cornwall.

Ah hmm. Point of order m'lud https://www.firstgreatwestern.info/coffeeshop/index.php?topic=29650.msg359540#msg359540  ;)

I’ll concede the Twyford points failure didn’t help matters, but maintain that had the 05:03 Penzance to Paddington not lost over half an hour in Cornwall this morning due to a points failure, the train’s next working (1C77, with the TM for the TransWilts on board), would probably not have been late enough into Westbury to have knocked-on to the 12:17 to Swindon.  ;)

Both re-instated half an hour later.

Oh dear - I think.

I have written before of how difficult it must be for the decision makers as a situation arises as to when to say something in public.  - but, really, broadcasting in public will be cancelled is a very definitive statement and to my gives no room for doubt - it's a statement that the train in question won't run.

I would (personally - is it just me?) like to see an option where a train service could be reported as being at  [low/some/high] risk of cancellation and with a note of a time by which the record will be updated.

No - it's very annoying when you change your plans to take a less convenient (or, based on recent experience, more inconvenient :) ) form of commute and then find out you needn't have bothered.

Thank you for that confirmation.

There are times I feel that I am reflecting the needs / concerns of members and and the many people I talk with who are not Coffee Shop members - and that's good.    There are also time that I find myself wondering if I am the only one concerned at something - in which case I should probably move on from that issue.

Cancellations to services between Swindon and Westbury via Melksham

Due to a points failure at Swindon some lines are blocked. Disruption is expected until 15:00 21/03.
Train services between Swindon and Westbury via Melksham may be cancelled or delayed.

Customer Advice
Apologies for the disruption to your journey today.

Network Rail advise that a set of points has failed just outside Swindon station; this is affecting journeys in both directions as local services are caught up in the congestion on the Main Lines.

12:17 Westbury to Swindon due 12:59
12:17 Westbury to Swindon due 12:59 will be cancelled.
This is due to a points failure.

13:14 Swindon to Westbury due 13:57
13:14 Swindon to Westbury due 13:57 will be cancelled.
This is due to a points failure.

14:18 Westbury to Swindon due 15:00
14:18 Westbury to Swindon due 15:00 will be terminated at Chippenham.
It will no longer call at Swindon.
This is due to a points failure.

15:15 Swindon to Westbury due 15:59
15:15 Swindon to Westbury due 15:59 will be started from Chippenham.
It will no longer call at Swindon.
This is due to a points failure.

Problems had started this morning ... I walked to the station and saw the dreaded word "delayed" against the 09:10 to Westbury. Checking Open Trains Times and Real Time Trains and another regular checked on her phone other sources, and on principle asking on the help point too, we were told 09:31 and that the connection at Trowbridge to Bath and Bristol would make, and a couple of minutes later Open Train Times map showed it coming.  Display changed to 09:34 which was going to be really tight at TRO.   No clues as to why ...

Good TM when it rolled in / explained about a point or track failure at Swindon and apologised - "I realise you don't have much information available at Melksham" which shows an excellent understanding.  Connection to Bath and Bristol made.  Connection to Warminster was lost / 30 minute delay to there. I'm not aware of where others were connecting to.

Just gotta get home now  ;D

How it should work (timing wise) - 17:53 from Taunton to Bristol, 18:30 on to Chippenham and 19:00 to Melksham arrived 1 minute down at 19:09 - 76 minute journey.

21:50 Chippenham to Westbury due 22:16
21:50 Chippenham to Westbury due 22:16 will be cancelled.
This is due to a shortage of train crew.

Have just seen this. Yes this is definitely an issue which needs resolving. I have often gone to an unmanned station and been confronted with a screen just saying the service I am aiming to catch is cancelled. It has often meant that I have had to cancel a trip I was intending to make, or if possible to very hurriedly find another way of making the trip (for me this has often been to cycle very quickly from Oldfield Park to Bath Spa). It is exceptionally annoying to find that the service did run after all (at Oldfield Park it has often been that the train was running but late and was missing out our station). Screens, announcements and websites need to have much more information given in these circumstances.

In a way, if a service is even announced as cancelled (or part-run), for a portion of passengers it *is* cancelled - it ought to go into the cancellation stats whatever happens subsequently. If it doesn't, the industry's running for its own benefit rather than for its customers.

Mark

It does - as a part cancellation.

21:16 Westbury to Swindon due 21:58
21:16 Westbury to Swindon due 21:58 will be cancelled.

This is due to a shortage of train crew

22:31 Swindon to Westbury due 23:12
22:31 Swindon to Westbury due 23:12 will be cancelled.

This is due to a shortage of train crew.

There goes my train home ... advance ticket on the 21:31 off Paddington .... it always pays to have a plan "B" ... think I have one somewhere  ...

Looks like it's reinstated...along with several others!

Is that the plan "B"?  Take anything from JourneyCheck more than a few hours in advance with a huge pinch of salt?  :-\

Both now reinstated.

... and I have checked in to stay in Lambeth ...

No - "Plan B" was to stay over.  Today was planned at January sale time - but then in February I got an invite for tomorrow that I could not refuse and I was going to be pretty tired.  Plan B was "if return train cancelled, stay over" and button pressed to implement that.  I have emergency supplies anyway.

18:37 Westbury to Swindon due 19:21
18:37 Westbury to Swindon due 19:21 will be diverted between Trowbridge and Chippenham.
It will no longer call at Melksham.
It will be delayed due to the diversion and is expected to be 9 minutes late.
This is due to a safety inspection of the track.

Luckily, the Wiltshire Metro will sort all this lot out.
https://www.railadvent.co.uk/2025/04/plans-discussed-for-a-metro-system-for-bath-and-wiltshire.html

His name is Dan Okey, not Dan Oakey, and it's Okehampton, not Oakhampton: more examples of shoddy journalism - perhaps using autocorrect, without bothering to make sure it is in fact correct.  ::)

Someone's got acorns for brains.

(https://www.mbob.co.uk/rforum/2M16.jpg)

Ah yes - added after my original post (and I admit I had changed my plans for today overnight and hadn't checked back this morning)

and now - not surprised ...


... only surprise is that they cancelled the up service and lunchtime, but left the return service running until 4 hours later

20:38 Westbury to Swindon due 21:23
20:38 Westbury to Swindon due 21:23 will be cancelled.

This is due to trespassers on the railway.

21:34 Swindon to Westbury due 22:16
21:34 Swindon to Westbury due 22:16 will be cancelled.

This is due to trespassers on the railway.

I wonder whether they had the crew?  We only ever get one reason and, somewhat uncharitably, I sometimes wonder if we are told the reason for cancellation that brings the least criticism onto the operator.

I see Melksham now has IET stop boards on the platform.

Presumably IETs can now stop there which will come in handy when they’re diverted for whatever reason.

I understand that is the plan  ;D - I understand that there's a need to do some sort of final check out of the system / test stop perhaps and fill in risk assessment paperwork perhaps so I am not counting my chickens, but clearly with it being programmed into the units and also having the stop boards in place it's coming into place.

Probably a daft question... I can only imagine that they'd want to stop at a specific point relative to the platform (on a single track line) to allow passengers on/off. But under what circumstances would they do that?

Yes - for passenger purposes.    When planned works or an emergency stoppage take place between Westbury and Reading, trains to / from the South West get diverted either via Bristol Temple Meads or via Melksham.  The very long distance expresses often go via Bristol, but the semi-fasts always go via Melksham so that a service can be maintained from Castle Cary and Westbury into Reading and London, and they'll be able to call at Trowbridge, Melksham and Chippenham and reduce the need for some of the rail replacement buses and taxis.

Happy with that ... and if it weren't school holidays that would be very welcome indeed beyond Swindon

At around 08:45, re-instated, I notice.

Damage already done - day planned and planned without a return to Melksham on those trains, comment made in public at https://www.passenger.chat/t30162.html and onto Facebook.

Stay-at-home Sunday for me then ... on an 8 out of 15 FOSW ticket and Sundays have the advantage of the early start being allowed, but I'me replanning for this to be a day of rest.   Yes, I know that evening round trip might get re-instated but there's no comfortable "Plan B" for Sunday evenings

08:06 Warminster to Swindon due 09:02
08:06 Warminster to Swindon due 09:02 was terminated at Westbury.
It will no longer call at Trowbridge, Melksham, Chippenham and Swindon.
This is due to engineering works not being finished on time.

09:08 Swindon to Westbury due 09:49
09:08 Swindon to Westbury due 09:49 will be cancelled.
This is due to engineering works not being finished on time.

Oh goodie - 4 out of 14 (28% cancellation rate) not calling at Melksham on what's probably going to be the first really busy Sunday of the year. Just taken a look at the two morning cancellations and there's nothing helpful there about buses or taxis - just an offer to give you your money back ...

Over running engineering works have also done for the first service from Swindon to London Paddington (starts Didcot Parkway) and first westbound service to Bristol and Exeter St Davids (starts Bristol Temple Meads).

Oh dear ...  From Swindon to London, there's an 08:00 bus (change Reading) and an 09:40 train ... first train to Westbury now 2 hours after that. Passenger volumes are of course very different, but it's also a reminder of just how serious cancelling even one train on an infrequent service is.

Nearly 4 hours to wait for public transport home to Melksham now if you miss the 17:44 (and on a Sunday, the evening buses from Bath don't run so even those of us in "the know" would struggle)

(https://www.wellho.info/pix/leftwith20250420.jpg)

17:50 Gloucester to Salisbury via Swindon:


Very late cancellation - hasn't made it to JourneyCheck.

What, if anything, would delay / repay get me on an FOSW for a delay of 72 minutes (projected). No, I probably won't bother - pragmatism over principle!

The 17:50 from Gloucester via Melksham was cancelled at 18:05 (the train sitting in the platform with passengers in it waiting to go - so I did not get into Melksham at 19:09 as per plan "A"

I took the 18:10 from Gloucester which also runs via Trowbridge to Westbury (via Bristol, this one) with the intent of changing into the 20:12 from Trowbridge back to Melksham - however that was cancelled at very late notice (about 5 past 8) so I did not get to Melksham at 20:21 which was plan "B"

The help point told me that I should wait for the 21:22 train which would bring ne into Melksham at 21:32 - plan C.   As far as he knew it would run but he couldn't promise anything.   He suggested I call GWR if I wanted to be more certain.  I did, but they were unable to give me any re-assurance.  They told me to wait and see if it ran - and if it was cancelled, I should then take a taxis and try and claim for it.    They were unable to explain why they only told the public that they had no staff for the 20:12 a couple of minutes before it was due ...

I ended up getting home last night at around 21:15 when I had planned to be home around 19:30 (very last minute cancellation ) and then - plan B - at around 20:45 (another very last minute cancellation). 

I made a thought out but quick decision in Trowbridge to take a taxi that was sitting on the rank; there are NOT always taxis there, and I've had to wait up to 90 minutes during the evening before.  I spoke to both the help point gentleman and a lady at GWR, and both told me that the final train could not be guaranteed but at the time of speaking it was still showing as running.  That would have got me home at 22:00 if it ran. 

Having had two trains cancelled in succession on my, in both instances at or after the time they were due to leave, and seeing a taxi available - pragmatic decision.  There was no fall back bus via Bath as it was a Bank Holiday bus service, and I was disinclined to take up the GWR suggestion to wait over an hour to see if that final train ran, and if it didn't then set about finding a taxi.

"Small beer" perhaps in yesterday's chaos across the GWR area, but cancellations - especially ones that are very late in the day, and advise which is not customer supportive (saving them money over customer's time / comfort / peace of mind) really don't help promote the railway.   And cancellations because of a faulty train, and because of a lack of available crew, are not the sort of reasons that well up mounds of sympathy in the same way that a passenger being taken ill on a train does.

A week is a long time in politics ... a quarter hour is a long time in a train service. 20:02, 20:10 and 20:14

(https://www.wellho.info/pix/at_2002.jpg)

(https://www.wellho.info/pix/at_2010.jpg)

(https://www.wellho.info/pix/at_2014.jpg)

14:18 Westbury to Swindon due 15:00
14:18 Westbury to Swindon due 15:00 will be cancelled.
This is due to a shortage of train crew.

15:15 Swindon to Westbury due 15:59
15:15 Swindon to Westbury due 15:59 will be cancelled.
This is due to a shortage of train crew.

..and here they are

(https://www.mbob.co.uk/rforum/mkmiet3.jpg)(https://www.mbob.co.uk/rforum/mkmiet4.jpg)

Interesting to note that Real Time Trains shows an on time arrival at Westbury and reports

So which is it - perhaps the fault on the train was that there was no-one to drive it  ;D ;D.

P.S. There is routinely a crew change at Westbury on this service

A driver was allocated to it and they arrived on time from Fratton on 2V52.

Doesn’t mean the RTT code is wrong (short notice illness etc.), but codes on RTT are unofficial and on JourneyCheck are ‘official’…but with a pinch of salt!

Journey check looking good today - flagging up just two cancellations across the whole GWR area.   Guess where


OK - so I notice a day when we are the only cancellations ... but this is not a unique occurrence!

Cancellations to services between Westbury and Swindon via Melksham
Due to a safety inspection of the track at Pewsey the line towards Reading is closed. Disruption is expected until 13:00 25/04.
Train services between Westbury and Swindon via Melksham have been cancelled.
Customer Advice
Due to a safety inspection of the track, all train services between Westbury, Melksham and Swindon are cancelled.

Customers travelling between Westbury, Trowbridge, Chippenham and Swindon are advised to change at Bath Spa.

Melksham is not being served by trains for the time being. Road transport is being organised.

((A section of track between Westbury and Pewsey is being examined for a possible defect. As a precaution we are not currently running trains along this stretch. This affects services to London Paddington from Devon and Cornwall. Where possible trains will divert, taking an alternative, slightly longer route. Where this is not possible, train services may be terminated at short notice.))

Typical "because of a problem on another line we're cancelling the trains on your line".

Hopefully, we have a better solution for the future ...only yesterday, I was photographing the new Stop boards for IETs at Melksham, and a train manager was telling me how they've had a circular around telling staff that the long distance trains can stop here.  Ideal for the sort of thing we have going on today? If the none-stop Taunton to Reading services run via Bristol and Bath, the semi-fast can run via Westbury and serve Trowbridge and Melksham in addition to Castle Cary and Westbury.  But it will take a bit of getting used to - oy, anyone in GWR reading this  ;D

Unless these IETs stop at roughly the same time as timetabled services however (and I doubt they'd be advertised given the necessarily ad hoc nature), wouldn't they largely find an empty platform at Melksham due to people having drifted off/not expected to find a train stopping at a given time?

I suppose some hardy souls may hang around in the hope of something stopping!

It needs to be used carefully and is far more relevant during planned engineering works.   Today's disruption turned out to be over almost before it began, with a handful of long distance expresses running via Swindon rather than Newbury, and as far as I can tell the biggest service disruption was a four hour gap each way on trains between Westbury an Swindon.

Agreed re: engineering works, a proper "timetable" could be put in place and advertised.

The lineside fire related disruption bit Bath rugby going home time, a bit of a queue outside the station and at least one bus driver being generous to people travelling back to places that suddenly had no train service. The bus station wasn't quite coping with the volume of people some of which were displaced from the trains and some *waves at the bus to Wells* definitely weren't.

Mark

14:22 Frome to Swindon due 15:34
14:22 Frome to Swindon due 15:34 will be terminated at Westbury.
It will no longer call at Trowbridge, Melksham, Chippenham and Swindon.
This is due to a shortage of train crew.

15:44 Swindon to Frome due 16:38
15:44 Swindon to Frome due 16:38 will be cancelled.
This is due to a shortage of train crew.

16:43 Frome to Swindon due 17:34
16:43 Frome to Swindon due 17:34 will be started from Westbury.
It will no longer call at Frome.
This is due to a shortage of train crew.

and some additional information.

17:50 Gloucester to Salisbury due 20:06
17:50 Gloucester to Salisbury due 20:06 was terminated at Westbury.
It will no longer call at Dilton Marsh, Warminster and Salisbury.
This is due to train crew being delayed by service disruption.

Only 2 trains in GWR area cancelled through lack of crew ... guess where

Cancelled as the guard for those services is booked to arrive at Westbury on the 1C77 10:35 Paddington to Exeter St Davids service which is currently being diverted via Swindon. Not the first time that problems or delays with 1C77 see the Swindon services cancelled.

For the record, the points failure at Westbury yesterday caused the cancellation of the 2M28 15:15 Swindon to Westbury and 2M21 16:23 Westbury to Swindon services. The unit stayed in the bay platform at Swindon and became the 17:35 departure to Westbury.

It's in "Oh no - not AGAIN" territory ...  known as being a risky train. I will look at putting some numbers on it some time.

This train has run 89 times in the last six months, in which there have been 130 weekdays.  28 of those days it was cancelled because of planned engineering, 2 because it was Christmas / Boxing Day.   So 100 "should" have run. 11% cancellation rate - a very high percentage for a weekday.

Here's the proof, and comparison to other services:

(https://www.wellho.info/pix/fail6m_202504.jpg)

Because of the very thin service, any cancellation is serious.

Hold it!


Opportunities if the train is running to time, you have ...
1 minute (no chance!) at Westbury
7 minutes at Swindon (*)
9 minutes at Gloucester (*)
17 minutes at Worcester Shrub Hill
* - Train calls at platform away from station building

17:50 Gloucester to Salisbury due 20:06
17:50 Gloucester to Salisbury due 20:06 will be cancelled.
This is due to a fault on this train

At least they've given is two hour's notice this time rather than cancelling it at 18:08 as they did on Easter Monday.   One of those "don't ask" days.

Interesting that it's the 17:50 to Salisbury that's cancelled rather than the 18:10 to Westbury, on a service with a far more frequent service where a gap might be less missed.

Agreed at Swindon but the toilets are on the same island platform and I reckon, even at the speed I walk, you could get to the lavatory and back in the time allowed.

No suggested alternative ... late notice cancellation.  There may be operational reasons but it's the very late changes without an (it could be automatic) passenger-focused advise line are highly damaging to customer morale.

Has 6A16 (Whatley Quarry to Oxford) sat down?

Looks like it ...

(https://www.wellho.info/pix/can1_20250502.jpg)

Too late to do anything about it today, but a proper integrated transport system should offer an alternative when you look up your train and try to book.  Rather that cancelled and a note that the next train is 151 minutes later, if the 09:52 id cancelled what not suggest that people catch the 09:55 bus from the top of the Trowbridge station approach - 10:29 in Melksham Town Centre and about 10:33 at the top of the Melksham Station Approach?   The fact that the bus goes past Melksham Station Approach and does not actually stop there is another issue ...

According to Traksy, 6A16 is still somewhere between Bradford Junctions and Melksham, at 1040

Without inside information, we can only guess.  JourneyCheck was telling us about problems until the end of the day, and I speculate that a skate might be needed to get something with wheel problems out of the way.   With lack of bypass loops and sidings, perhaps they are waiting for the more important lines between Chippenham and Swindon, and between Trowbridge and Westbury to become clear after service? 

Just knock the faulty vehicle out of the train and drop it onto the North Loop to await attention from C&W.  Nothing booked to run over that today.  Oh.  Wait.

I know, I know.  If only

Guessing on what's wrong with the train - but there IS a siding still at Thingley Junction.

Although the siding is not easily accessible from the Melksham line

The problem is with the freight loco itself and fitters are having difficulty isolating components on it before it can be moved.    A rescue loco is on site ready to move it once that becomes possible.

Thanks for that, Bob ....

At least there is a replacement bus in place (scheduled to arrive Westbury 40 minutes after the train, but better than telling people to wait hours) ... not a clever day today. 

20:14 Swindon to Westbury due 20:57
20:14 Swindon to Westbury due 20:57 will be cancelled.
This is due to a broken down train.

"Short" runs this evening too - the 17:50 Gloucester to Salisbury and the 20:06 Westbury to Cheltenham Spa both missing out Melksham.  Makes sense to be reversing TransWilts trains at Bathampton - remembering that 2 out of 3 passengers along the single line on a normal day are going through (not from or too Melksham) and so this is the best solution for them.

I have to ask ... why does it take so LONG to get a failed locomotive out of the way?  Is it part of a more general set of things that seem for whatever reason to take fare longer to sort out when things go wrong?  No backup plans?  No spares/staff around?  Extra Health and safety requirements? Everyone a specialist?

Oops - and sadly that's not what they have done with the evening trains after all


So "disruption until 20:00" is the operational description.  Anyone who hopes to head from Melksham to Cheltenham Spa (agreed not a huge flow) at 20:25 won't get there until - what - 11 p.m. or later?  [Edit - looked it up - 23:31!]

I'd point that question at Hopwood if I were you, after all it's his trains that are being cancelled and his customers inconvenienced.  Given that, I'm sure he's all over those responsible and should be able to address your points.

A summary from yesterday - of 18 calls planned, just 7 happened.

(https://www.wellho.info/pix/can2_20250502.jpg)

Southbound at 06:32, 20:39 and 23:12
Northbound at 07:21, 08:02, 18:52 and 21:31
Early evening calls at 19:09 and 20:22 were cancelled, even though the line had been re-opened by that time.

Let's record a day when it all worked - Saturday, 3rd May.

Back to a familiar scene this morning

Reinstated.

Thank you.  I wonder, sadly, just how much damage cancellation and re-instatement of services does on a line where waiting for the next service will be a significant change to plans.

It is a question asked many times.  Unfortunately I suspect we will only ever have anecdotal answers.

It would require considerable data logging and analysis and work to try to remove other factors from the results.

It is probably a fair assumption that it makes SOME difference, with their being some people who don't book / make other plans when a train is recorded as cancelled.    An on that basis is worth pointing out to the people who cancel and then re-instate services that this practise reduced the number of passengers carried and p***es off quite a number too, and is a practise they should avoid.. If something is bad, it's not necessary to put a number on exactly how bad it is before you fix it!

I think most people would check to see if the service is running and if it isn't, they will make other plans - realistically, no-one is going to keep checking back on the off chance of a reinstatement.

The 06:32 service from Melksham to Southampton was uncharacteristically late this morning - departed at 06:38, which meant I just missed the (official) connection with the 06:46 Bristol service at Trowbridge. Don't know what caused the delay to the Melksham train - it left Chippenham on time, and was just described as 'running late'. Not a disaster though - caught the 07:05 Cardiff train.

First time there's been any sort of problem taking this route to Bristol for quite a few weeks. It's so much more reliable than the alternative via Chippenham, and is worth the very early start.

No obvious reason - it seems to have left Chippenham on time and then been stuck for 5 minutes at Thingley - however that was NOT waiting for something else to clear the single line.

Next train from Trowbridge was only a 19 minute wait ... next train from Chippenham when the unofficial connection fails is a 34 minute wait (it did connect this morning). Because it's official you can claim delay / repay for an 07:28 expected arrival to an 07:48 actual arrival into Bristol whereas you have no claim via Chippenham.  Only negatives about the Trowbridge change are the earlier start and the need to cross the footbridge which if you have heavy luggage or are in a wheelchair is not clever.

Looks like a special train went though Trowbridge while you were waiting?

Yes - there was an announcement that a charter service was due at 0653, and I wondered whether it might be worth leaving the waiting room if it was going to be steam powered. I didn't, and it wasn't - a diesel of some sort, obviously old and 'special', but not a Deltic. It stopped to pick up a lucky few - looked like they were in for a very nice breakfast :)

Golden Arrow - diesel (47) from Bristol to West London (Hanwell)  then Brittania London to Canterbury. 

Well it flippin should be for £425 :o
https://saphostrains.com/journey/the-golden-arrow-07-05-2025/

"The day starts as you settle into your seat with a glass of chilled bucks’ fizz..." - before 7am...

05:11 Gloucester to Southampton Central due 08:09
05:11 Gloucester to Southampton Central due 08:09 will be diverted between Chippenham and Trowbridge.

It will no longer call at Melksham.
It will be delayed due to the diversion and is expected to be 7 minutes late.
This is due to a fault with the signalling system

06:35 Salisbury to Worcester Foregate Street due 09:47
06:35 Salisbury to Worcester Foregate Street due 09:47 will be started from Westbury and diverted between Trowbridge and Chippenham.

It will no longer call at Salisbury, Warminster and Melksham.

It will be delayed due to the diversion and is expected to be 10 minutes late.
This is due to a fault with the signalling system.

Yeah and the 06:35 Salisbury to Worcester Foregate Street, which I would have caught at Melksham at 07:21 instead, is also showing as cancelled due to a signalling problem. Will wait for the 07:45 Westbury - Swindon (Melksham 08:02) and hope they've fixed things by then - I'm not buying a ticket, yet...

To confirm to anyone who might be reading this in GWR - these are not just "7 minute delay"s - they are cancellations as far as Melksham (population 25,000) is concerned

(https://www.wellho.info/pix/can_20250508.jpg)

Cancellations to services between Trowbridge and Chippenham

Due to a fault with the signalling system between Trowbridge and Chippenham the line towards Melksham is closed.
Train services running through these stations may be cancelled or delayed. Disruption is expected until 08:00 08/05.

Cancellations to services between Trowbridge and Chippenham
Due to a fault with the signalling system between Trowbridge and Chippenham the line towards Melksham is closed.
Train services running through these stations may be cancelled or delayed. Disruption is expected until 08:00 08/05.
Customer Advice
Taxis have been sourced as below:

Bath Taxis - 06.35 Chippenham calling Melksham, Trowbridge and Westbury. Please wait for the taxis at the rail replacement bus tops.
Bath Taxis- 07.11 Trowbridge calling at Melksham and Chippenham. Please wait for the taxis at the rail replacement bus tops. Passengers can use any London Paddington train from Chippenham to Swindon.

We're sorry for the delay to your journey.

The Salisbury-Worcester service now showing as running (on National Rail app), due Melksham 07:23  ???

(started from Westbury I think)

In summary ... the 06:32 call didn't happen at Melksham and a taxi at 06:35 from Chippenham was added at some point.  Useful for those headed towards Southampton though it would have arrived at Trowbridge / Westbury well after the diverted train had passed there, so passengers for Salisbury who joined at Melksham and normally carry on at 06:55 would drop back to the 07:40 as far as Salisbury, or the 08:01 if headed for Southampton (yes, there is a commuter flow)

Personally I was trying my luck with a sub-5-minute change at Westbury onto the Weymouth train which runs every 2 hours and of course that would have failed.  With the taxi added, I would have left Westbury 2 hours after plan, and without the taxi (on the 09:10 from Melksham) 4 hours late. For a day trip, a 4 hours delay kills the day and I didn't try it once the cancellation came up (decision made before the taxi got added).  Had I been required to travel, I could have caught a bus to Frome and picked up the train there 2 hours after my plan.

For Bristol, the 06:32 connects into Bristol with an arrival at 07:28.   That would have failed this morning as taxis are slower.  Arrivals into Bristol at 07:48 or (more likely) 08:11 depending on how long the taxi too.

The 07:21/07:23 did call in the end, and the quick connection into Bristol that sometimes worked appears to have done so ... not sure how many people got put off and looked at other alternatives such as the bus or waiting (with fingers crossed) for the 08:02.

There are some slight but noticeable improvements in how issues are handled, but the rail industry seems to be intensely unreliable, with shortages of crew, trains breaking down, signalling failures. Short term cancellation rates are 5% at present and that's 3 times what "Which?" described as "dreadful" for an airline - it means that if you commute from Melksham Station for a fortnight, 5 days a week, you can expect one journey to be cancelled.  For passengers on the 07:21 to Chippenham or Swindon, that's "just" a 40 minute delay - with almost all other trains, especially with connections, it's far worse.   With a proper (every 30 minutes or better) service, a 5% cancellation rate could perhaps be shrugged off, but with a 120 minute frequency, every one hurts and damages the public confidence.

There IS a "thank you" due to the people who fixed the line, to the people who arranged the taxis.  But [they/you] should not be put into a position of having to do that so often, and they should have tools to give better feedback to the customers.  To some extent, they are victims of a skimping on maintenance and a reduction of available staff below sensible limits, just as the passengers are.  Here's looking to you - management and controllers ...

I was put off, but happy to take the less stressful 08:02 option :)

12:17 left Westbury on time but was stopped outside Trowbridge for 20 minutes as the preceding train to Cardiff had come to a stand due to a fault with the driver vigilance device.  It got on the move after systems were isolated and terminated at Bath Spa.

The Swindon service didn't make up any lost time and arrived in Swindon 20 minutes late before leaving 12 down on the return journey.

16:23 Westbury to Swindon due 17:05
16:23 Westbury to Swindon due 17:05 has been cancelled.
This is due to a fault on this train.

17:35 Swindon to Westbury due 18:19
17:35 Swindon to Westbury due 18:19 will be cancelled.
This is due to a fault on this train.

I have a funny (peculiar, not haha) feeling that trains get swapped around and "fault on this train" is reported because an old crock or a train someone was doubtful about was assigned to the service.  The feeling is boosted by the reaction when I made a comment at Westbury about waiting for / catching the Swindon train (I forget the comment exactly) and eyes were rolled in such a way that indicated the staff see it as the flakiest that runs from there.

And now ...


Would someone please fix the bl**dy thing or split a couple of carriages off another train?    You could even split 5 cars off a London to Plymouth evening service now as they get quieter when they get past Westbury.

I've taken the liberty and had a look in a couple of directions ... not ideal, but here are some multiple units passing through Westbury.  16:08, 17:06 and 18:03 could all drop 2 carriages on their way to Portsmouth.  The first one would get a bit crowded further south, but the latter 2 with 3 and 2 carriages

What heads west - 10 carriages just after 6 p.m. and I'm sure only 5 are needed beyond Westbury. And there's that 9 car that goes out of service at Frome ;-)


(https://www.wellho.info/pix/sources_wsb_1.jpg)

(https://www.wellho.info/pix/sources_wsb_2.jpg)

08:44 Swindon to Westbury due 09:25
08:44 Swindon to Westbury due 09:25 is being delayed between Swindon and Chippenham.
This is due to a broken down train.

20 minutes late into Westbury and no significant connections missed, return train left on time.   This turned out to be a pinprick of a delay compared to yesterday's major rupture when the train broke down which lead to the complete cancellation of six services.

This is NOT the right forum section BUT.
10:45 London Paddington to Weston-Super-Mare due 12:35
10:45 London Paddington to Weston-Super-Mare due 12:35 will be cancelled.
This is due to a broken down train.
11:12 Salisbury to Bristol Temple Meads due 12:31
11:12 Salisbury to Bristol Temple Meads due 12:31 will be cancelled.
This is due to a broken down train.
15:00 Cardiff Central to Penzance due 20:42
15:00 Cardiff Central to Penzance due 20:42 will be cancelled.
This is due to a broken down train.

One unit breaks down and three services cancelled?

Now changed to


Still cancelled for my station, then ...

I am getting confused ... and not risking any trains today!

I am interested in the reasons why trains are often delayed for, apparently, no obvious reason and in the explanations provided to passengers.

In this particular instance the journey check text should have read '17:50 Gloucester to Salisbury due 20:06 departed Gloucester 8 minutes having returned to Platform 1 from it's waiting point 10 minutes later than scheduled, because the platform was occupied by the late running 2T49 WOF>BRI service until 1748, and has been further delayed on the approach to Stonehouse.'

Too much information obviously but I think the majority of people understand what is meant by the term 'depot' and I doubt the Gloucester Loco Spur qualifies.

And I can't figure out why the service lost another c. 8 mins between Standish Junction and Stonehouse.

Can't get the train out of platform 2??

Greetings from the Dutch traveller where I have proof that connections don't always work here.  I have just HAD TO DROP BACK to a train 7 minutes later that I planned.  It's a DIS-GRACE  ;D ;D

With crew shortages all over the place, so far the Westbury to Swindon service is doing far better than most today, having said which even a single cancellation on that line leaves a huge gap.   I have to personally wonder at why, after so many years, crew shortages seem to be almost routine and look to the management and direction (from inside and outside the TOC) for having failed to avoid such issues being so frequent, or to cynically have passed them off as an acceptable lack-of-service level.

Succinctly, because those at the upper reaches of GWR tend to be Managers rather than Leaders, and there are few better examples than this long running issue.

06:35 Salisbury to Worcester Foregate Street due 09:47
06:35 Salisbury to Worcester Foregate Street due 09:47 will be started from Westbury.
It will no longer call at Salisbury and Warminster.
This is due to a fault with the signalling system.
Will be formed of 3 coaches instead of 2.

21:16 Westbury to Swindon due 21:58
21:16 Westbury to Swindon due 21:58 will be cancelled.
This is due to a fault on this train.

22:31 Swindon to Westbury due 23:12
22:31 Swindon to Westbury due 23:12 will be cancelled.
This is due to a fault on this train.

Portsmouth to Cardiff running 50 minutes late ... now arrives in Westbury at 14:02 and I suspect the crew is transferring and is progammed to take a personal needs break.   

All a very long way from Mockava I'm travelling on, which is supposed to pause at Trakiszki for 8 minutes but but was there for more like 30 ... couple of Polish border guards going through and checking passengers. Not sure whether it was just the two who got on, but the two who came to all compartments in uniform left with two others not in uniform.

Argh! First commute in over 2 weeks and the trains...  >:(

When I left the house, it was looking good. But then the 0632 Southampton service I catch from Melksham to Trowbridge got delayed and was showing as 20 mins late, meaning I'd miss the 0646 Trowbridge Bristol. And the next option, the 0705 Cardiff service, was also showing as delayed, with the following Filton Abbey Wood cancelled.

So I'm on the bus to Bath, where I should be able to catch the 0747 Weston service. What's even more annoying is that the 0705 Trowbridge Bristol that was showing as delayed ended up being on time - it just started from Westbury instead of Frome.

Try again tomorrow...

Yeah ...


... it appears to have arrived on time in Swindon but spent 30 minutes rather than 10 there.  Looks like it will be on time from Salisbury, in spite of Journey Check assuming "once delayed, delayed all the way". Guessing it was some sort of issue the crew on local staff at Swindon were able to sort out.

That would have been the last leg of my commute home. Looks like another £3 on the buses  ::)

...and if I search for Bristol Temple Meads - Melksham on the National Rail app it also shows the earlier 1545 option as cancelled as well, although I can't be bothered to check which of the 2 trains on that route aren't running.

Both now re-instated.

21:16 Westbury to Swindon due 21:58
21:16 Westbury to Swindon due 21:58 will be cancelled.
This is due to a shortage of train crew.

Followed, as sure as night follows day, by

14:18 Westbury to Swindon due 15:00
14:18 Westbury to Swindon due 15:00 will be cancelled.
This is due to a shortage of train crew

15:15 Swindon to Westbury due 15:59
15:15 Swindon to Westbury due 15:59 will be cancelled.
This is due to a shortage of train crew

16:23 Westbury to Swindon due 17:06
16:23 Westbury to Swindon due 17:06 will be cancelled.
This is due to a shortage of train crew.

17:35 Swindon to Westbury due 18:19
17:35 Swindon to Westbury due 18:19 will be cancelled.
This is due to a shortage of train crew.

17:50 Gloucester to Salisbury due 20:06
17:50 Gloucester to Salisbury due 20:06 will be terminated at Swindon.
It will no longer call at Chippenham, Melksham, Trowbridge, Westbury, Dilton Marsh, Warminster and Salisbury.
This is due to a shortage of train crew.

Depressing ... and it feels it's getting even worse again.

Gap at Melksham ...
12:32 to 18:53 northbound
13:39 to 20:38 southbound
... and that's for a town of around 25,000 where an appropriate service would be running hourly each way; the timetable is thinner (just one every 2 hours) and the sort of thing being offered today has six hour gaps. Sadly, this is not unusual - it's ongoing.   The trains MAY end up being re-instated later but that's cold comfort to people who need to have their days planned. 

Things WILL go wrong occasionally ... but this is an ongoing problem and it is NOT occasional. It's difficult to see anything being done to provide a reliable service ... words are spoken, actions being taken explained and promised and there are even good patches for a while with it running a bit better, but it falls over again. Sad.

The 16:23 from Westbury and the 17:35 from Swindon now re-instated.

However

Just looking at options for my usual commute home Bristol-Melksham (on the National Rail website) and of 9 options between 13:00 and 19:25, 4 are currently showing as "This service is cancelled". 2 cancellations are for the Chippenham-Melksham leg, 2 for Trowbridge-Melksham.

It is a "joke" ... a humeourless joke ... today. Goodness knows what has been cancelled and what has been re-instated and what ends up running in the end.    It  may feel OK to the folks who run the trains to chop and change during the day depending on staff availability - after all, a driver coming in to work at X O'clock doesn't need to know where he's going to be until a few minutes before.   However, for passengers (customers) rather more planning is needed, especially on services which are infrequent in the first place.  Perhaps more thought should be given to customers and the effect on them of all these "will-it, won't-it" flip-flops.

And now cancelled throughout ... no real difference on the TransWilts section where it was cancelled anyway!

20:06 Westbury to Swindon due 21:21
An additional bus service has been planned to operate as shown 20:06 Westbury to Swindon due 21:21.

Additional Information
Four people carriers from Bath Taxis. Before getting in any taxi vehicle please check with the driver that they are working on behalf of GWR, the driver should not ask for payment.

I understand that Gloucester drivers have had Melksham work removed with the change of timetable. Along with Bristol drivers losing Weymouth, it would appear Westbury depot are too thin to cover all the gaps.

There are ... times ... I wish I had provided an "amazed" button answer as well as a "like" button. If you have understood correctly (and I have no reason to doubt it) it looks to be rather backward step in terms of providing a reliable service, doesn't it?

Has the new timetable change sorted out the lunchtime problem where a crew arriving off the semi-fast London to Exeter service do a round trip to Swindon ... notorious for being cancelled, turned at Chippenham or delayed if anything goes wrong (does it ever?) between London and Reading,  delaying the Exeter.

Explains why Weymouth trains often end up terminating at Westbury in both directions if Bristol drivers no longer sign the route down to Weymouth. Might be good for operators but not good for passengers.

The change only happened last weekend!

The lunchtime train is still booked with an Exeter guard who arrives on the London to Exeter service.  The 1623 Westbury to Swindon and 1735 Swindon to Westbury services are now booked to have a driver who travels up from Exeter! I think Westbury have covered it (when possible) every time it has run since the timetable change though. ???

The evening 1750 Gloucester to Salisbury service is now booked from Swindon for a driver from Reading depot who is then booked to bring back the 2006 Westbury to Cheltenham service as far as Swindon.

17:50 Gloucester to Salisbury due 20:06
17:50 Gloucester to Salisbury due 20:06 will be cancelled.
This is due to a shortage of train crew.

20:06 Westbury to Cheltenham Spa due 22:06
20:06 Westbury to Cheltenham Spa due 22:06 will be started from Swindon.
It will no longer call at Westbury, Trowbridge, Melksham and Chippenham.
This is due to a shortage of train crew.

So as of last night it was 50% of the days since the change that the peak evening train was declared cancelled then re-instated.  Unclever - very unclever.

Let's hope that THIS crew shortage issue (or the way of reporting it in a way that scares the customers away) is shortlived - teething troubles.  Sadly, I am not holding my breath as prior experience of staff shortages is that they go on. And on. And on.

Almost all depots have lost routes with the May timetable. I guess it works on paper. Believe Oxford are the odd ones out who’ve actually gained a new route.

---

Time flies - it's been two weeks not one, hasn't it, ChrisB?   And I fell for that without doing a fact check ... I have not looked back at the first week after the changes; that record commented on is for the second week as they should be bedding in.

I guess it does.  Problem is ... railways don't run on paper ... they run on people, and engineering, and trains and rails, all of which have less continuous availability than a sheet of paper which remains a miracle that can be written on and still read years later.

And six hours later ... the almost inevitable cancellation of the train in the return direction

1 cheer not 3. Not "reinstated" as far as passengers wishing to join at Swindon, Chippenham, Melksham or Trowbridge are concerned ...

Somewhat better news (2 cheers not 3) that the following return trip is no longer on the cancellation report, so id probably re-instated throughout.

Just noticed ...


So is that 2 trains with faults at Westbury this morning, or a fault on the train planned to run to Weymouth and then a decision to use the one planned for the TransWilts service for the Weymouth instead?

Something looked odd here ... then I found it ... the fault isn't even on our line ...

With the power to the signalling at Newbury restored, the latter pair above have now been re-instated.

but ... another two cancellation.  Not exactly customer friendly, is it?

It ran last night - we was on it - 3 carriage train, 10 in our carriage (so guessing around 30 in the train), 8 off and perhaps 2 or 3 on at Melksham (we were slow getting off so I may have missed 1 or 2. So that is  [32/10] which is not bad going for one of the very quietest trains of the day. 

This is the descendant of the 19:35 service from the bad old decade of "2 trains a day - too early and too late" when we were a line without a train - borrowing one from another line to run when it really wasn't much use there (either) ... and in those days we would have been lucky to see 5 people using the train.  How well we have come forward, even allowing for the flakiness and the 30 minute later running, timed (I suspect) to allow for the personal needs break of the crew arriving from Gloucester rather than to connect with the service from Salisbury of provide an evenly spaced service.

And this morning ...

17:50 Gloucester to Salisbury due 20:06
17:50 Gloucester to Salisbury due 20:06 will no longer call at Chippenham, Trowbridge and Dilton Marsh.
It will be starting late from Gloucester.
This is due to trespassers on the railway earlier today.

You may wonder why I am quoting the Basingstoke service too - which is cancelled "due to more trains than usual needing repairs at the same time".   That's because these are the ONLY two trains across the whole of the GWR area which are cancelled at short notice this morning.  It is not unusual to see this sort of metric, where a very high proportion of cancellations are on our little line - from our 14 services out of around 2,000 that GWR should run.

Oh - and


So that's a cancellation in all but name ...

2/14 is a 14.5% cancellation rate ...

A major signalling failure at BRI means nothing moving until around 1000

Now both re-instated.

::)

...and the 17:35 Swindon-Westbury left Chippenham on time, but then stopped for about 5 mins somewhere before Thingley, due to a red signal according to the train manager. Wasn't obvious why; I assumed something had got delayed coming from Melksham in the opposite direction on the single track we were waiting to turn into, but nothing came past us. Strange.

Nothing obvious on Real Time Trains ... the other possibility that I looked at was the possibility of something ahead of it that had to clear Bradford Junction before you could proceed, but that was NOT showing on RTT.

Signalling experts may be able to help me - but I think that the train is passed from Didcot to Westbury sit passes along the line and signallers at both ends have to co-operate to pass trains.  I get the impression that the paths / this is occasionally done very late.

The signaller at Westbury controls the single line through Melksham. In order to route a down train from Thingley Junction towards Bradford Junction, the signaller on the TVSC Swindon workstation has to request the slot from their counterpart at Westbury. If the slot is not requested or given in good time, the Automatic Route Setting will set the route up only as far as the signal before the Thingley crossovers. This is to ensure that the junction is not blocked if there was to be a train coming up from Bradford Junction first.

Perhaps a good place to log my two journeys Swindon to Melksham

Yesterday at 22:31 (Friday 13th) from Swindon
18 passengers on train into Melksham. where 10 got off and 3 on. [21/13]

Today at 15:14 from Swindon
36 passenger on train into Melksham, where 18 got off and 2 got on.  [38/20]

22:12 Swindon to Westbury due 22:55
22:12 Swindon to Westbury due 22:55 will be cancelled.
This is due to a fault with the signalling system.

Sun, 15 June 13:32 Swindon to Weymouth due 15:45
15/06/25 13:32 Swindon to Weymouth due 15:45 will be cancelled.
This is due to a shortage of train crew.

Wonderful end to a day trip

And for today ... the first train is replace by a bus because, as far as I can tell, the line is needed to run a more important West Country express that calls at Westbury, with engineering works closing the normal line through Pewsey.   Then ...

Quoting from Heart of Wessex ...


On the TransWilts service, don't forget that the first round trip was a rail replacement bus this morning - not really a replacement but a substitution by something different and inferior.

A lot of TransWilts southbound in the morning use it for onward connections which leave Westbury (today) at ...
09:32 and 09:57 (yes, 2 at 25 minutes apart) for Weymouth
09:37 for London
09:54 for Penzance
10:02 for Portsmouth
and these would normally offer connections off the train from Swindon.   Guess what - the bus arrives at Westbury at 10:14 and that breaks all of these connections.   Only 2 other GWR trains are timetabled to leave Westbury before 11:00 and could be described as connection - 10:40 to London (by Real Time Trains tells me it's not expected until 11:10)  and a train at 10:41 which - oh dear - heads up to Swindon which is where the direction the bus came in from in the first place!

I am not sure if that was the case.   The up train from Warminster is usually timed to be on the single line between 08:26 and 08:38.    Today the Penzance train was slightly early and was on the line between 09:02 and 09:14.

The return service from Swindon is usually between Thingley and Bradford Junctions from 09:27 and 09:38.

I couldn't see any other reason ... and it was planned in well ahead and wasn't an "oops - we've no staff or train" on the morning!

Performances like yesterday's will happen but should be so rare they take us by surprise.  As something that happens all too often, and digging into the data the cancellations are again all "rail industry" rather than "act of God" attributable, this is not marketable to new and nervous users.  The risk of mucking up people's plans to the extent of having them put off the railway for a long time to come is just too high.

(https://www.wellho.info/pix/notfit20250615.jpg)

On a service that was scheduled to run every 20 minutes, alternate cancellations may not be an issue that seriously damage people's whole day / plans.  On a service that runs every 120 minutes, it renders what's left as unfit for the purpose of getting people around and if we can't fix it, why/should we bother?

The sad thing is that it's a day when services DO run to schedule that's so rare it takes us by surprise.

06:35 Salisbury to Worcester Foregate Street due 09:47
06:35 Salisbury to Worcester Foregate Street due 09:47 has been cancelled.
This is due to a fault on this train.

And

False alarm?  Pretty well on time all the way and no delay off Swindon.

There used to be two trains each way in the middle of Saturday afternoon and GWR were having trouble crewing them both.  I went public in support of cutting out one of the two in order to make the system and remaining train robust.   Sad that they can't even find crew for the remaining mid-afternoon train.  Do I feel mislead and shortchanged?  Is that a reasonable feeling in the circumstances??

Not really "reinstated".   Still cancelled as far as the TYransWilts line is concerned.

Fair comment. And how many of the potential passengers for that service would have been those travelling from Swindon to Westbury, proportionately?

I don't know: how busy is that remaining service between Westbury and Weymouth on a Sunday, during a heatwave?  ;D

CfN.

16:43 Frome to Swindon due 17:34
16:43 Frome to Swindon due 17:34 will be reinstated.
It will be terminated at Westbury.
It will no longer call at Trowbridge, Melksham, Chippenham and Swindon.
This is due to the train conductor being taken ill

17:44 Swindon to Salisbury due 18:55
17:44 Swindon to Salisbury due 18:55 will be started from Westbury.
It will no longer call at Swindon, Chippenham, Melksham and Trowbridge.
This is due to a shortage of train crew.

16:23 Westbury to Swindon due 17:06
16:23 Westbury to Swindon due 17:06 will be cancelled.
This is due to a shortage of train crew.

17:35 Swindon to Westbury due 18:19
17:35 Swindon to Westbury due 18:19 will be cancelled.
This is due to a shortage of train crew.

16:47 Bristol-Warminster I was going to take to get off at Bath, instead of the 17:00 Paddington getting off at Chippenham, has also been cancelled. That's after my train up from Trowbridge this morning was cancelled due to the tree.

At least the 7:21 Melksham-Chippenham ran on time, so shouldn't complain.

I stand corrected.


The only cancellations in the region - notable that alternative transport is actually flagged up (rare but not unheard of) and the delay stated is 43 minutes.

Passengers onwards toward Weymouth hoping to connect with the 18:50 off Westbury  to Frome will have to wait for the 19:45 - a 55 minute late arrival - and for Weymouth the next train isn't until 21:40 as far as I can see

The Journey Planner IS offering you the train-bus combo at £9.80 single Swindon to Westbury and also offering a 17:22 getting to Westbury at 18:34 which will connect with the 18:50 onwards - 13 minutes earlier from Swindon, a useful alternative, and getting there 15 minutes after the cancelled train would have done - but they are pricing a £19.80 - that's right, £10 more.  Whatever happened to the promise that if a train via Melksham was cancelled and passengers had to travel via Bath that the via Melksham fare would be honoured?. It feels like an immoral thing to do to commit to providing a train service, cancel it, and then ask people to pay more for the journey because of your failure to deliver.

Looks ok at the moment - can I assume it's been reinstated?
https://www.nationalrail.co.uk/live-trains/departures/chippenham/melksham/

It was reinstated at 15:35.   However now the 21:16 from Westbury and the 22:31 from Swindon have both been cancelled.

The last round trip has now, just, been reinstated. 

08:06 Warminster to Swindon due 08:58
08:06 Warminster to Swindon due 08:58 will be cancelled.
This is due to a shortage of train crew.

09:08 Swindon to Westbury due 09:49
09:08 Swindon to Westbury due 09:49 will be cancelled.
This is due to a shortage of train crew.

10:38 Weymouth to Swindon due 12:57
10:38 Weymouth to Swindon due 12:57 will be terminated at Westbury.
It will no longer call at Trowbridge, Melksham, Chippenham and Swindon.
This is due to a shortage of train crew.

10:41 Westbury to Swindon due 11:24
10:41 Westbury to Swindon due 11:24 will be cancelled.
This is due to a shortage of train crew.

11:32 Swindon to Weymouth due 13:45
11:32 Swindon to Weymouth due 13:45 will be started from Westbury.
It will no longer call at Swindon, Chippenham, Melksham and Trowbridge.
This is due to a shortage of train crew.

13:32 Swindon to Weymouth due 15:45
13:32 Swindon to Weymouth due 15:45 will be started from Westbury.
It will no longer call at Swindon, Chippenham, Melksham and Trowbridge.
This is due to a shortage of train crew.

14:05 Frome to Swindon due 14:58
14:05 Frome to Swindon due 14:58 will be cancelled.
This is due to a shortage of train crew.

15:44 Swindon to Frome due 16:38
15:44 Swindon to Frome due 16:38 will be started from Westbury.
It will no longer call at Swindon, Chippenham, Melksham and Trowbridge.
This is due to a shortage of train crew.

20:38 Westbury to Swindon due 21:23
20:38 Westbury to Swindon due 21:23 will be cancelled.
This is due to a shortage of train crew.

21:34 Swindon to Westbury due 22:16
21:34 Swindon to Westbury due 22:16 will be cancelled.
This is due to a shortage of train crew.

That looks like 5 out of the 7 round trips cancelled ... wasn't someone telling us just in the last 24 hours that there IS no crew shortage - just that not enough crew know the routes needed.   

I gave up on the train yesterday - the intent was Melk (in Austria) to Melksham.  Got as far as Bath Spa ...

17:44 Swindon to Salisbury due 18:55
17:44 Swindon to Salisbury due 18:55 will be terminated at Westbury.

It will no longer call at Warminster and Salisbury.
This is due to a shortage of train crew.

21:35 Swindon to Westbury due 22:52

An additional bus service has been planned to operate as shown 21:35 Swindon to Westbury due 22:52.

17:50 Gloucester - Salisbury "cancelled because of more trains than usual needing repairs at the same time"

(Sorry - does this count as TransWilts?)

Sadly, yes, Transwilts ... again ... that's the train that runs via Swindon

The choice of reason "Trespassers on the railway" wasn't, I think, the best choice in this case (I accept that the person adding details to the system may not have been aware of the incident's details)

I wondered why there was no train through Stroud until 15:13. It turns out that there was a main road closure also, connected with what the police referred to as a "concern for welfare incident" involving one male.

So that's both the 18:44 and the 20:12 from Swindon to Westbury cancelled - service gap from 17:35 to 22:30.  How about marrying up the working trains with the working crew?

This feels like a repeat ...


But clearly something going on ...

Report of a woman seen on Stroud viaduct. 

...hence lines closed between Gloucester and Swindon. Early Gloucester-Southampton diverted to Bristol Parkway, and was initially showing as on time at Swindon. Then it changed to delayed. Then it was back on time, so I had to jog to Melksham. Now it's delayed by 15 mins.

Report I saw earlier said lines were expected to be closed until 9:00.

EDIT sorry didn't see Graham's post (on phone).

.

Twenty minutes later - reinstated.

FRUSTRATION ... I know that things have to be moved around during the day sometimes, but flagging up trains as cancelled, letting people know that they won't be able to get home anything like as easily as normal ... and then saying "just kidding" or "we didn't really mean that" is enough to put people off using the train!

True, although that's 6.5 hours in the future so perhaps it allows them a bit more freedom.

Not like this morning's early Gloucester-Southampton (which I mentioned above - apologies for the repetition). I normally leave the house at ~6:05 to catch the 6:32 Melksham departure, and at that time it was showing as 'delayed' (after previously being 'on time', and 'delayed' before that). So I went from the front door back to my room and got my laptop out to start working, planning on catching one of the later services.

Then at ~6:15 I refreshed the web page and it had gone back to 'on time' :o Laptop back in rucksack, dash downstairs and jog most of the 1.6 miles to the station. Where it was now showing as 15 minutes late  :-X

Part of my frustration is that the information systems have just green and red lights.  I know that in the end it runs or it doesn't, but a "This train may be cancelled" or "this train may be delayed" warning with "please check back in an hour" might do wonders.




Better still - have enough of the right people available at the might time in the right place and don't have to cancel, or say you're cancelling, so many trains!

I have spent a bit of time trying to find the specifics of the cancellation and reinstatement of these services without success.

However it seems GWR are in a bit of a no win situation when it comes to cases like this.   When the services were cancelled it was in the earnest belief that they would not run.   They could have delayed the announcement but then run the risk of being criticised for making it even more short notice.  Control and the rosters staff are eternal optimists and always hope they can pull something out of the hat and run a service.  So work continues behind the scenes to rescue a service or reduce a shortform until they run out of all options.   If they waited until they reached that point there would be a rash of last minute cancellations/alterations.   The current situation is not ideal, but personally if there are going to be cancellations I'd rather know as early as possible, even if it is later reinstated.

As for this morning's service from Gloucester, the confusing messages are down to the way the automated system works.  Once it went off its booked route at Standish Junction the system lost it and so defaulted to delayed.   It was only when it approached Swindon and picked up its planned route that the system started to update again.

Yeah I appreciate that. As Graham says it would better/great if they fixed the root cause.

Thanks - I can understand that, although I'm fairly sure that it was showing as 'on time' at least for a short time on the National Rail app when the route included Bristol Parkway (which I assume corresponds to 'went off its booked route' - might have misunderstood).

Until just now when I went to quote Graham's message did I spot his postscript about solving the root cause - clearly (pardon the pun) my eyesight isn't up to seeing that colour against the background.

Thanks so much for that Bob - I have to agree that leaving it to the last minute is NOT the way to go.  And indeed the very good and often successful work of those involved to getting a service back, which is appreciated, leads to them being criticised for a false "the xx:xx train is cancelled" but it ends up running.   The very last thing  I would want encourage is a mentality that says "once a cancellation is broadcast, it is never re-instated".

I guess that a sizeable minority of cancellations are reversed - if only there was a tag line that could be added "but we are still trying to find a way of running it"; my understanding is that's a systemic problem - the options available don't include that ...


Again - a systemic option.   Journeycheck assumes once delayed, always delayed.  It is often "hilariously" wrong on certain trains such as the sleeper ... and the very train in question in this thread - the 05:11 from Gloucester to Southampton can be as much as 20 minutes late as it passes Standish Junction, projected as 08:30 rather than 08:09 into Southampton and yet arrive there on time.   Real Time Trains makes rather better predictions, by various methods like taking the time that trains sit at intermediate stations (Swindon, Salisbury and a little at Westbury on the 05:11) and trimming then back as it predicts.  In reality, once a train is significantly delayed, it comes down to a complex mesh of factors such as platform availability at Westbury which can add significantly to the delay, together with factors already mentioned like timetabled intermediate dwells, and it's pretty unpredictable by current algorithms as to whether the delay is recovered, maintained, or gets worse.

My naughty little postscript in orange was supposed to point out that [they/we] are treating the symptoms and not the cause / disease - easing the pain when what is needed is action to fix the causes as far as possible. 

My guesstimate is that 75% of the problems are fixable at source. Whilst that would cost money to do, it would also bring about a huge saving on the work stress of those who are trying to ease the pain, a big saving on delay/repay, and a boost to confidence in the system so that people who are wary about using the train because of its unreliability would (re)turn to rail.

I am disappointed that these fixings at source have not been done - it almost defies logic that they have not. I do have indications that much background work has been done so "they" know what to do.  Perhaps they are waiting for GBR for it to be a flagship policy of improvements once the government takes over the TOCs? 

I don't disagree with the message, my point was as orange on cream I didn't spot it.   It was only when I went to quote the message and it was black on white that I saw it.

I tend to use National Rail for checking for delays etc., and on the odd occasion I've tried RTT I've found it's not showing the problems being reported by the National Rail app. Like on Monday, while NR showed the diversion via Bristol Parkway and a delay, RTT didn't.

So while RTT is great for history, I'm sticking with NR for predictions.

21:34 Swindon to Westbury due 22:16
21:34 Swindon to Westbury due 22:16 will be cancelled.
This is due to a shortage of train crew.

Not fit for purpose ...

(https://www.wellho.info/pix/mkm_20250706.jpg)

(https://www.wellho.info/pix/mkm_20250705.jpg)

It's striking that this is now commonplace. Historically, the railway ran on the principle of infrequent services with a lot of thought put into ensuring that these ran to time - and this carried over into the age of more frequent train provision: the quieter parts of the network didn't experience multi-hour gaps in service caused by cancellations.

As far as certain parts of the rail network goes, in the south west in particular, this principle seems to have gone out of the window. Given the inflexible costs involved in a railway operation, the industry's position on this is... odd.

Mark

Commonplace indeed.   There was no shock over the weekend that half the service was lost, and no external cause - "act of god" - to explain it.

The industry's position is indeed odd, and frustrating.

05:11 Gloucester to Southampton Central due 08:09

05:11 Gloucester to Southampton Central due 08:09 was terminated at Swindon.
It will no longer call at Chippenham, Melksham, Trowbridge, Westbury, Dilton Marsh, Warminster, Salisbury, Romsey and Southampton Central.
This is due to a fault on this train.

This morning's Gloucester-Southampton (Melksham 6:32) service was cancelled after reaching Swindon due to a fault on the train. Hopefully delay/repay will cover the cost of the 271 bus I'm currently waiting for...

and


Yeah, right ... the southbound train failed at Swindon, stranding a crew there ... so at Melksham, that's 06:32 cancelled, 07:21 cancelled ... first train (we hope) 08:02. It's not a Saturday, it's not a Sunday, and the train to form the 07:21 was in working order ...

For what it's worth, the bus was surprisingly prompt - managed to catch the 7:33 Cardiff train at Bath instead of the expected 7:47 Weston (would have been on the 7:10 Bristol service without the cancellation). So only 20 mins later than planned into the office.

Good job I hadn't waited for the 7:21 at Melksham.

BTW apologies to TaplowGreen for missing the post before mine about the cancellation; only just seen it. In my defense I was on my phone :)

18:37 Westbury to Swindon due 19:21
18:37 Westbury to Swindon due 19:21 will be cancelled.
This is due to a fault on this train.

20:14 Swindon to Westbury due 20:56
20:14 Swindon to Westbury due 20:56 will be cancelled.
This is due to a fault on this train.

17:50 Gloucester to Salisbury due 20:06

17:50 Gloucester to Salisbury due 20:06 will be terminated at Westbury.

It will no longer call at Dilton Marsh, Warminster and Salisbury.
This is due to a shortage of train crew

Let me guess ... because the crew are coming in on a delayed Berks and Hants semi-fast .... this arrangement does not seem to be robust.

I really wish it mattered .. with a reliable service, we could be doing so much more to promote rail use and days out - and because of loadings it could matter.

seems to be an epidemic affecting Turbos today - or maybe the warm weather.

20:14 Swindon to Westbury due 20:56
20:14 Swindon to Westbury due 20:56 will be cancelled.
This is due to a fault on this train

21:16 Westbury to Swindon due 21:58
21:16 Westbury to Swindon due 21:58 will be cancelled.
This is due to a fault on this train.

22:31 Swindon to Westbury due 23:12
22:31 Swindon to Westbury due 23:12 will be cancelled.
This is due to a fault on this train.

And 4 more gone ...


... it was 158769 on earlier services so perhaps not a turbo failure this time

Warm weather doesn't create faults, but it does reduce the ability to use worn or poorly fitted components without problems.  

In a way any poor / shoddy maintenance tends to show up as problems and faults more quickly.  The old adage a stitch in time saves nine applies, and if get lots of breakdowns, run out of usable trains short term.

In the end it departed 12 minutes late - four minutes after the West of England service arrived.  At least it ran.

I know it’s a bit off the Transwilts, but the service at Dilton Marsh since 4pm onwards has been next to non existent with cancellations in both directions with Warminster/Salisbury services being cancelled.

 https://transwilts.org/2025/07/11/no-transwilts-trains-on-sunday-13th-july/ (https://transwilts.org/2025/07/11/no-transwilts-trains-on-sunday-13th-july/)

There are supposed to be automatically added stop orders - that may only be on certain trains though - have extra stops happened?

If there have been, they haven’t appeared on the Tiger Departure Board this afternoon/evening or Journeycheck saying Cardiff-Portsmouths making additional stops.

Saturday 12th July


Sunday 13th July


Faresaver buses leave Chippenham Railway Station on Sunday at 09:25, 10:25, 11:25, 12:55, 13:55, 14:55, 16:25, 17:25 and 18:25 for Melksham Market Place (26 minutes later) and all up to and including the 17:25 continue to Trowbridge (Manvers Street).   

Return buses leave Manvers Street in Trowbridge at 09:20, 10:20, 11:20, 12:50, 13:50, 14:50, 16:20, 17:20 and 18:20.. All call at Melksham Market Place 28 minutes later and all up to and including the 16:20 bus continue to Chippenham Railway and the bus stations. There is an extra bus from Melksham to Chippenham at 08:48.

Sunday buses on route x34 do NOT serve Trinity Church which is adjacent to Trowbridge Railway Station - they terminate in Manvers Street (behind Sainsburys) which is a few minutes walk away if you are able bodied and know where you are going.    They do not serve Melksham Railway Station, but call (nearest stops) at Broughton Road and on the main Chippenham road outside Aldi / McDonalds

A maximum fare of £3 per individual journey applies on these buses, but to my knowledge there is no rail ticket acceptance in place.

16:23 Westbury to Swindon due 17:05
16:23 Westbury to Swindon due 17:05 will be cancelled.
This is due to a shortage of train crew

17:35 Swindon to Westbury due 18:18
17:35 Swindon to Westbury due 18:18 will be cancelled.
This is due to a shortage of train crew.

18:35 Westbury to Swindon due 19:17
18:35 Westbury to Swindon due 19:17 will be cancelled.
This is due to a shortage of train crew.

19:38 Weymouth to Swindon due 22:00
19:38 Weymouth to Swindon due 22:00 will be terminated at Westbury.
It will no longer call at Trowbridge, Melksham, Chippenham and Swindon.
This is due to a shortage of train crew.

19:44 Swindon to Westbury due 20:29
19:44 Swindon to Westbury due 20:29 will be cancelled.
This is due to a shortage of train crew.

22:12 Swindon to Westbury due 22:55
22:12 Swindon to Westbury due 22:55 will be cancelled.
This is due to a shortage of train crew.

Gosh, never mind tomorrow, not much of a service today.

But don't forget, as we are repeatedly told, apparently there is no shortage of staff  ::)

Our risk assessment has been NOT to market day trips from Melksham to Weymouth at present due to the significant risk of people having a severely upset trip in one or both directions.  The other part of the risk assessment related to how bad the effect of the risk would be.   The next train from Westbury to Melksham as I understand it is 34 hours later;  robust passengers who know what they are doing could travel on to Bath and catch the 23:20 bus into Melksham at midnight.  And in theory there will be/ would be station staff around to help with onward transport, which in the evening sometimes involves a wait of 90 minutes.

I wish our decision had not been vindicated. And a corollary question is to ask what to do - as a community where we want to use the train -  about this state of affairs. 

Being the last train of the day AND knowing there will be day trippers from Weymouth, onward travel from Westbury should be made available?

Indeed - but the word "should" can cover a whole host of evils.  They "should" have enough staff in the right place, at the right time, with the right route knowledge and other training, and enough working trains, to provide a full service in all but the most exceptional circumstances.

Interestingly the banner headline on GWR seems to imply multiple failings on GWRs part.

1) failed to have enough serviceable staff
2) failed to update journey planners in timely way
3) failed to hire in replacement buses (or coaches, or charter train)
4) what trains they run will be busy because not lengthening them

And what do they mean by "Your comfort and safety are our priority.  Please check live updates...."   is that PR speak for we can't be bothered to get you there.

https://www.gwr.com/sunday-disruption

Given that these franchises are now management contracts that are micromanaged by DfT, how many of these things are actually in GWR's power to change?

1) I suggest that increasing staff is probably subject to DfT approval, and even then would take many months.
2) Yes as far as I can see this is down to GWR
3) I am not sure where they are going to get these from at certain times.  The bus/coach industry is cut-throat and a company that has vehicles and drivers sat around is likely to go out of business very quickly. 
4) Again DfT have demanded that they reduce the number of trains in service to cut costs.  That is why the HSTs have largely gone and other so called surplus stock. 

But surely the management contract specifies a minimum level of service, and thus that implies a certain number of staff contractually employed to work it.

Or are you saying GWR have accepted a contract that can only be performed if volunteers choose to help up, and GWR cannot incentivise the staff to volunteer.  Illogical (but if DfT are involved, plausible)

The railway, nationally, has always run on volunteers working additional shifts.

Indeed - and it makes sense.  For it to work well, it needs staff (volunteers) who have reason to want to work extra - to earn extra money, because they enjoy the work and the folks they work with, to support the team/organisation they work for,  to provide mental stimulation, or to get out of the house away from the screaming kids / in-laws ...

Once it becomes "expected" of them and less enjoyable and they feel "obliged", a system which is good for both employee and employer ceases to work well.   A story was told to me about a bus company who employed a bus-washer six days a week (Saturday overtime) ... so good was his work that he was given a pay rise - a big "thank you" from him and he cease Saturday work because he didn't need the extra money.  I wonder sometimes about just how much staff enjoy working on a variety of routes, and I wonder if restricting route knowdledge also restricts volunteering ... I wonder if so much chopping and changing between trains along the way rather than driving the whole way is a de-motivator.

Nothing about what people should do from Melksham or Trowbridge - but we did do what GWR asked of us from Melksham which is put out a "don't use GWR" message.   What an extraordinary thing for a company to do ...

And ironically, since privatisation, salaries have risen to such an extent that those volunteers no longer want the overtime, and their employers have done nothing to fill the gap.

That's true, though there are still plenty of additional shifts being worked, just not enough. 

Also, since privatisation, there has been a significant uplift in the number of daily services run without enough additional drivers taken on.

26 minutes late departure from Trowbridge. As it is due to sit at Swindon from 10:28 to 11:05 before returning it should be just the one run that's delayed.

Originally, the 10:02 from Melksham was planned to be at 10:32, and at the time the previous train was 07:50 ... suggested by the community (and perhaps others and an analysis of passenger needs) these trains are now 08:02 and 10:02, with a longer gap then to 12:32.

Root cause was a SPAD by a freight train at Thingley Junction, with the driver unable to continue. The freight train has just resumed its journey with a relief driver.

BBC Bristol referred to cancellations from Swindon due to a late running freight train. I thought that was a bit strange but your post explains it JayMac

21:16 Westbury to Swindon due 21:58
21:16 Westbury to Swindon due 21:58 will be cancelled.
This is due to a shortage of train crew.

22:31 Swindon to Westbury due 23:12
22:31 Swindon to Westbury due 23:12 will be cancelled.
This is due to a shortage of train crew.

That 21:16 is the train that I would expect to be the quietest of the day. However - Lisa and I returned on it on Monday evening (14.7.2025) from Trowbridge into Melksham.  With Lisa's mobility issues and my 40lb pack, I was more concerned at getting us on and off the train than counting passengers, but 8 people got off at Melksham.  On the normal ratios I would expect that a couple of people got on as well, and that for every 1 who got on/off at Melksham there were 2 through passengers - so that's an educated guess of 30 passenger in total - [30,10].

I was very concerned as we travelled up from Portsmouth that the train manager checking our tickets when I said we would be changing at Westbury advised us to carry on to Bath Spa and change there because the service "is poor from Westbury but every half hour from Bath".    But we were actually on the train from Portsmouth that has a good (5 minute) connection at Westbury up to Chippenham and Swindon, and with staff advice to avoid the TransWilts train even on a weekday when it's supposedly running, it's a wonder that numbers are not floundering far more than they are.


Had we taken train manager advice, we would have had to change trains in Bath Spa, arriving there at 21:34, taking two awkward lifts with a mobility scooter to catch the 22:12 London train and arriving into Chippenham at 22:25 ... whereas with the change at Westbury or Trowbridge, the arrival was at 21:40 - three quarters of an hour earlier.  (I have checked how they ran on Real Time Trains).   The service from Bath Spa to Chippenham is every half hour during the day but every hour in the evening, so even if we were both able bodied to make a quick connect at Bath we would have been stuck there for quite a while in the evening when all we wanted to do was to get home.

I was puzzled by the advice to go to Bath ... realised why it was practical when I remember that we had Chippenham to Portsmouth period returns as we went out from Bath and were coming back to Melksham and these were tickets valid to/from either actually used stations.  Still poor advice indeed ...

Once I recalled the ticket was a Chippenham one, I did explain to our train manager - who was a trainee with a supervisor watching and then helping - that we were headed for Melksham - "in which case change at Westbury". And a further question from me "why Westbury which will involve a change with 2 lifts and a subway with a mobility device when it's same platform at Trowbridge?".   The train manager and supervisor agreed that Trowbridge made sense - "we advised Westbury because there are staff there who can help if the Swindon train is not running but you clearly know what you are doing ..."

Worked like a treat - saw others dashing through to the stairs at Westbury and the Swindon train waiting on the other island platform, but we just dropped back at Trowbridge - easy!

... and now re-instated.....

Through service running from Swindon Chippenham and Melksham to Weymouth for a day out ... unmarketable as  there's no through train coming back ... and the last service at Melksham is cancelled. 

Sun, 20 July 14:05 Frome to Swindon due 14:58
20/07/25 14:05 Frome to Swindon due 14:58 will be terminated at Westbury.
It will no longer call at Trowbridge, Melksham, Chippenham and Swindon.
This is due to a shortage of train crew

Sun, 20 July 15:44 Swindon to Frome due 16:38
20/07/25 15:44 Swindon to Frome due 16:38 will be started from Westbury.
It will no longer call at Swindon, Chippenham, Melksham and Trowbridge.
This is due to a shortage of train crew


Sun, 20 July 18:10 Castle Cary to Swindon due 19:34
20/07/25 18:10 Castle Cary to Swindon due 19:34 will be cancelled.
This is due to a shortage of train crew.

Sun, 20 July 19:43 Swindon to Westbury due 20:25
20/07/25 19:43 Swindon to Westbury due 20:25 will be cancelled.
This is due to a shortage of train crew.

Oh dear ... this is what I have purchased for tomorrow - first stage of a journey by ferry and train.  No through ticket available so split along the way, and a number of reservations ...

(https://www.wellho.info/pix/st1inarv.jpg)

We have been factually logging failures ... some feedback from local social media that points to the consequences ...   last weekend when the return train from Weymouth did not run beyond Westbury


and


and


and

Much better advise than I got when I phoned in to GWR last night ... asking what I should do with the 14:31 (which connected to the London train at 15:14 from Swindon was cancelled.   I was told I should catch the 11:57 instead and my ticket would be honoured, on I could wait for the 17:08 which (there was some confusion on the agent's system) was probably running.

When I demurred, the agent suggested I get a taxi to Swindon to pick up my connection there and then see if GWR would refund it because the change otherwise was going to be so long.   He suggestd I call I again in the morning to see if the situation had changed, and advised me that my ticket might not be accepted if I made my own way to Chippenham to join the London train there.

Very pleasant and polite conversation - and in terms of practical suggested alternatives as useful as a chocolate teapot. 

19:38 Weymouth to Swindon due 22:00
19:38 Weymouth to Swindon due 22:00 will be cancelled.
This is due to a shortage of train crew.

22:12 Swindon to Westbury due 22:55
22:12 Swindon to Westbury due 22:55 will be cancelled.
This is due to a shortage of train crew.

Message for Melksham ... "We'll get you there for a day out - just won't get you home ...".

09:52 Westbury to Swindon due 10:36
09:52 Westbury to Swindon due 10:36 will be cancelled.
This is due to a broken down train.

11:05 Swindon to Westbury due 11:48
11:05 Swindon to Westbury due 11:48 will be cancelled.
This is due to a broken down train

12:17 Westbury to Swindon due 13:01
12:17 Westbury to Swindon due 13:01 will be cancelled.
This is due to a broken down train.

13:13 Swindon to Westbury due 13:55
13:13 Swindon to Westbury due 13:55 will be cancelled.
This is due to a broken down train.

Earlier today that quartet were advertised as being three coaches instead of two. Now shrunk to zero.  Underlines the chronic shortage of rolling stock in the central region.  The cascade of more units from the west cannot come soon enough. 

15:14 Swindon to Westbury due 15:58
15:14 Swindon to Westbury due 15:58 has been cancelled.
This is due to more trains than usual needing repairs at the same time.

16:23 Westbury to Swindon due 17:05
16:23 Westbury to Swindon due 17:05 will be cancelled.
This is due to more trains than usual needing repairs at the same time.

17:35 Swindon to Westbury due 18:18
17:35 Swindon to Westbury due 18:18 will be cancelled.
This is due to more trains than usual needing repairs at the same time.

18:35 Westbury to Swindon due 19:17
18:35 Westbury to Swindon due 19:17 will be cancelled.
This is due to more trains than usual needing repairs at the same time.

19:44 Swindon to Westbury due 20:29
19:44 Swindon to Westbury due 20:29 will be cancelled.
This is due to more trains than usual needing repairs at the same time.

Frankly, I wish that was a problem.  It's not - the services have been so unreliable of late that people are put off using them.

Yesterday ...

(https://www.wellho.info/pix/failedservice20250726.jpg)

 
Err ... what sort of repairs are needed to a train that can number into Westbury from the South West, but then not carry on North East to Melksham and Chippenham?

Cab satnav equipment failure?  :P

The 11:27 Weymouth-Chippenham terminated at Westbury and ran ECS to St Philips Marsh.

Could be a number of faults occurring en route which require the train to be taken out of passenger service at the first opportunity.  Driver vigilance device, other fault in the cab, windscreen wiper failure, door issue etc.   Then no available spare to pick up the return working even from Westbury (or possibly crew if the driver took the defective unit to Bristol).

Worse than expectations - 20 minutes late on leaving Melksham and failing to make the onward connection which is very popular.   Beyond Warminster that's a one hour delay.  Never mind - at least it's running - just another (this one relatively minor) hiccough in the system.

Or put another way - cancelled throughout with the 18:10 Gloucester to Westbury extended to Salisbury?  (EDIT - looking at RTT it does look the 5O09 becomes 2O09 at Westbuty)

Real Time Trains shows the 17:50 running - as 5O09 (empty coaching stock). Are we sure that's a track safety inspection as nothing else seems to be disrupted, or is its really a shortage of train managers?

And it now suggests

Cancellations to services at Westbury
Due to a safety inspection of the track at Westbury some lines are blocked.
Train services running through this station may be cancelled or delayed. Disruption is expected until the end of the day.

09:52 Westbury to Swindon due 10:36
09:52 Westbury to Swindon due 10:36 will be cancelled.
This is due to a safety inspection of the track.

11:05 Swindon to Westbury due 11:48
11:05 Swindon to Westbury due 11:48 will be cancelled.
This is due to a safety inspection of the track.

Thanks for flagging those up.   

Reading carefully, it would appear that the problem is not on the line through Melksham - but rather on the Westbury to Pewsey and Newbury segment - so long distance trains are being diverted along the line through Melksham which is single track and has inadequate capacity, and the local service which is all we have at Melksham Station is being culled/ sacrificed once again.


I note that no alternative bus service is reported here for Westbury to Swindon or part thereof.  I live in hope that with stop boards now in place at Melksham, the semi-fasts from Exeter and Taunton, Castle Cary and Westbury will also be calling at Trowbridge, Melksham and Chippenham.

Well whatever the issue with the track was, it isn’t a problem now:

Driver reported a rough ride near Lavington viaduct on the London bound line.

20:06 Westbury to Cheltenham Spa due 22:06

20:06 Westbury to Cheltenham Spa due 22:06 will be terminated at Gloucester.

It will no longer call at Cheltenham Spa.
This is due to a shortage of train crew.

16:23 Westbury to Swindon due 17:06
16:23 Westbury to Swindon due 17:06 will be cancelled.
This is due to a shortage of train crew.

17:35 Swindon to Westbury due 18:19
17:35 Swindon to Westbury due 18:19 will be cancelled.
This is due to a shortage of train crew

A fatality between Avoncliff and Bradford on Avon seemingly involving the 0546 Bristol Portsmouth has prevented the unit for the Westbury Swindon and return working to Weymouth getting to Westbury, resulting in their cancellation
https://www.journeycheck.com/greatwesternrailway/

07:45 Westbury to Swindon due 08:28
07:45 Westbury to Swindon due 08:28 will be cancelled.
This is due to the emergency services dealing with an incident.

08:44 Swindon to Weymouth due 11:08
08:44 Swindon to Weymouth due 11:08 will be cancelled.
This is due to the emergency services dealing with an incident.

I was on the 22:31 from Swindon to Melksham last night.  A significant flow (guessing 20+) off the Cheltenham Spa train onto it at Swindon, in addition to the 'local' traffic ... it provides an extra service into Chippenham that fills the first gap in the evening in the half hourly service as well as the Melksham / Trowbridge link.  Not sure how many got off at Chippenham but certainly more got on as well - perhaps 10 off at Melksham and I don't know how many remained on the train.    It astonishes me that traffic remains so robust in spite of - as we see this morning - 6 out of 14 services that call at Melksham cancelled already for the day. 

Sundays are said to be a problem - but this is a Saturday.   Special cases will always be raised and, yes, there is a fatality this morning at Bradford-on-Avon (but how much is that a special case? Another fatality yesterday at Hitchin threw my travel plans - it's a daily toll).  I hear of new incentives and initiatives to sort these things out - but heard those things before and after a week or two it sinks back ... the $64,000 question - what can be done to fix the issues and how can passengers work together to help it?    Our problems on this line are not unique, but they seem to be on steroids compared to elsewhere.

On some routes especially it would seem that "Saturday is the new Sunday" when it comes to crew shortage.

09:52 Westbury to Swindon due 10:36
09:52 Westbury to Swindon due 10:36 will be starting late from Westbury.
This is due to train crew being delayed.

27 minutes late off Westbury, so first train on the day left Westbury at 10:19. 

Arrived at Swindon 23 minutes late, but the return working left on time at 11:05.

Yes, it could.   That's a service which in the early days of our service improvements, GWR were going to run about half at hour later (on weekdays anyway). We asked them, and they agreed and implemented , the earlier time.  It cuts that gap from what was the 07:50 to about 10:30 (Melksham times) at the very time people want(ed) a first off peak train.

On a Saturday there were two trains from Westbury to Swindon - 08:00 and 08:40 I think. "For robustness" GWR cut the second one - we've one train less in the Saturday timetable now - but the robustness has not been delivered and at times I feel we were cheated.

22:12 Swindon to Westbury due 22:55

22:12 Swindon to Westbury due 22:55 will be cancelled.

This is due to more trains than usual needing repairs at the same time.

And there's no getting back from the seaside - not that you could have got there in the first place!!

Alterations to services between Westbury and Swindon via Melksham

Due to a shortage of train crew between Westbury and Swindon disruption is expected until the end of the day.

Train services between Westbury and Swindon via Melksham may be suspended. Melksham will not be served.

Customer Advice
As the result of a shortage of train crew we are unable to operate the Westbury - Swindon - Westbury via Melksham train service in either direction for the remainder of the day. Road transport will operate in place of the trains but will not be running to the same schedule as the train they replace.

Robustness - not bustness then?

Quoting a friend who's up in Reading for the day from his timeline:


A cancellation of the first train this morning because of the person hit by train on the neighbouring line was understandable.   But if the empty / feeder was coming in that way, it could simply have gone to Swindon and picked up the diagram from there.  Yes, I know others will tell me that the robustness capacity has been taken out of the system and that wasn't possible because [insert reason given here].

Edited by bobm to remove profanity in quote

18:10 Castle Cary to Swindon due 19:34
18:10 Castle Cary to Swindon due 19:34 will be cancelled.
This is due to a shortage of train crew.

19:43 Swindon to Westbury due 20:25
19:43 Swindon to Westbury due 20:25 will be cancelled.
This is due to a shortage of train crew.

Yesterday (Saturday 9th August 2025) was one of those days where so many trains were cancelled and some of it was bit by bit that I have used Real Time Trains to summarise:

(https://www.wellho.info/pix/rtt_20250809.jpg)

The first cancellation was understandable due to "person hit by train" though that happens far too often and at dreadful cost.  The second train should have run with the empty going up to Swindon for it from Bristol rather than through the closed line at B-o-A.  The later cancellations were TOC failures to provide enough trains or staff to work them.

At face value it would have seemed sensible to send the empty stock from Bristol straight to Swindon.  However it is formed of two units totalling five carriages.  One unit is normally detached at Westbury station and goes to the sidings. Unfortunately it had already set off and reached Bath before being blocked.  Had it reached Swindon it would have been too long for the bay platform so would have taken up one of the through platforms until time to set off for Weymouth. 

It could probably have run to Westbury as a five with the rear two locked out of use but I suspect the bigger issue was crewing.  The empty units would have had no guard and there probably wasn’t time to get one up from Westbury even if the driver was able to take the train forward.   In the limited time available I suspect Control went for the defensive option.

Good summary ... Services from Swindon to Westbury and beyond usually *do* use the short bay platform 2, but it's far from rare for them to use platform 1 or platform 3.    In summary, a system that is so stretched that when something goes wrong there aren't the resources available to organise or run the logically mitigated services.

Of course, we're talking one service here as to why it didn't run ... and just accepting the seven that were cancelled later in the day with a stoic shrug of the shoulders. 

Which means the 19:43 from Swindon to Westbury will now also run.

Only the 18:10 from Castle Cary has been cancelled again because crew were delayed so the 19:43 is also a non runner.

Oh no they won't.



Perhaps that's a service that is supposed to be staffed by an Exeter crew for route learning and crowds at Newquay are delaying trains and have a knock on in Wiltshire?

It reminds me of a pantomime - "oh yes it will" - "oh no it won't" - "oh yes it will" - "oh no it won't".  How are the customers supposed to organise their day with this going on?

Look behind you!

I suspect because the site seems to be running a little slow, you didn't see my post just before yours.   Mine took 30 seconds from pressing post til actually submitting.

Aware of the slow running, BobM ... will be taking a look at the pattern of traffic that's causing it.  It's intermittent but I do have logs to go back through when I'm fresher over the next couple of days.   I came home a week before originally planned / both Lisa and I find that beyond 2 weeks apart gets hard / so have a quiet few days once I recover from my 04:10 to 23:30 journey (door to door) on Friday.

Here we (don't) go again


After twenty to seven in the evening, the Cardiff -> Portsmouth service is not going to be rammed - any chance of dropping 2 cars of one of the longer ones to maintain service?   

The train from Portsmouth to Cardiff that calls at 19:11 is 2x158s this evening, one of which is detached at Temple Meads anyway.  Just saying.  It would be significantly late up to Swindon but has a long layover there so the rest of the evening service would be saved and on time.  Just wondering what I have missed ...

There may be fuel or maintenance considerations in play, I don't know.    The unit removed at Bristol Temple Meads usually goes to St Philips Marsh overnight and then comes out to form the 05:51 to Portsmouth Harbour the following morning.