GWSR Cotswold Festival of Steam 2015: 23rd to 25th May

The advertising poster doesn't give the number but it gives the name, Bouncy Castle. So that will be a first for your Spotter's Notebook eh FS123? That really was too easy wasn't it?

 

Just reread my last post, I forgot to include the smiley - never fear, even I'm not taken for a ride quite that easily! I'll admit I was caught by one of the GWSR's April Fools a couple of years ago abut EU regulations meaning no hot food for OTC!

 

Will certainly look out for pictures from that, and with our nice shiny new maroon rake as well!

 

I don't suppose they've got a ferret and dartboard on the side. Have they?

 

Nope!

 

5043 is down for a rail tour on the Saturday of the gala, and WCRC should be back operating by then I would imagine.

 

I like your style - Bouncy Castle!
I wish it could be that easy! We are indeed looking for that elusive third guest, I started at the top of my list and all i say is there are a lot of crossed off engine numbers.
We are of course delighted to have the two Spam cans booked but a third gives us a bit of breathing space in case of problems (heaven forbid - i think I'm already a little greyer).
You will of seen the news that P&O has been lit up this week for steam tests, as with all things, with only a month too go we are dissapointed she will miss the main party. This isnt too say that we dont intend to make the most having three Bulleids finest in steam together.
I hear that we still have 12 footplate rides to sell, so do get onto the GWSR website for details.
More to come as soon as i hear positive news.
thanks.

 

Unfortunately "yes" as I am working that weekend!

 

I am just wondering why it was decided to bring in two Bulleids this year rather than next year as 35006 should be up and running by then? It seems a lot of lines do this like they rush to get an engine into service in an unrealistic timescale and plan a gala around said locomotive maybe bringing in guests similar/the same to it but the engine misses it and then it's return to service isn't such a big event as possibly it could have been. An example is 6960 visiting the GCR last weekend when their own Mod Hall is due to return very soon, and the winter gala just gone, surely 7820 and 1501 visiting when 6990 was in traffic would have made more sense.

 

There's another way of looking at this - attract lots of Bulleid fans with the prospect of 34007 and 34092, have a wonderful gala with 35006 simmering away temptingly at Toddington and thus encourage everyone to come back for a second visit when 35006 is operating trains. After all, once 35006 is operational, it won't just be operating on galas so if someone makes two visits - one for the gala and one on a normal operating day featuring 35006, the railway's finances will benefit more than if 35006 were operational at the gala. I'm not for a moment suggesting that this was the deliberate strategy. I'm sure the ideal would have been for 35006 to be pulling trains at the gala if it could have been completed in time. I'm just pointing out that bringing in 34007 and 34092 without 35006 being ready for use isn't really a bad move from anyone's point of view.

 

What he said. I think it actually encourages reprobates like me to visit twice!

 

Totally agree with your thoughts, but there are sound reasons. When we decided some time ago to have the theme. 'Speed to the west ' we already knew that 35006 making the party was unlikely but with a lot of locos out there that could fill the southern/gwr theme we were quite happy to proceed. If the MN was ready then it was a huge bonus.
After securing wells as the first guest our list of first choice locomotives Slowly got smaller and smaller. Partly due to the date that our event takes place and a lack of available engines meant we had to rethink our plans. Why pay 10k to bring an engine in that might not bring that much to the event? 34007 and 34092 will hopefully do the business. Since then I've pretty well phoned every railway about a loco, unfortunately the third guest will more than likely be off theme (non southern or gwr). Worth remembering that 34007 and 34092 Handle Gwsr nornal services on Saturday 30th may while on Sunday 31st it will be wells and a home fleet loco (due to Mhr needing 34007 back)
Hope this clears up our thinking!

 

Thanks for that explanation Andy, off theme fine with me as less likely I'll have seen it! And for the running dates, hopefully I might be able to see both locos when I get home from holiday. Any idea when they are arriving/first operating at this stage?

 

Shame the T9 not available, nice Cornwall theme & she only come North once in her current ticket to SVR.

 

With the 50th anniversary of the closure of the Swift and Delightful (sorry, the Somerset and Dorset) looming, it may be more difficult to source Bulleid locomotives next year.

I'm really looking forward to seeing the pair of Spamcans at the GWRly this year. <BJ>

 

I'd agree with your way of looking at it John. I'm pretty sure most folks here would agree that a Merchant Navy returning to steam, on it's own is a huge event in itself, wouldn't they? Personally I'm not too fussed whether it runs at the event or not. All I want ideally is for the 2 Spam Cans to be lined up with P&O at some point, as seeing 35006 virtually complete alongside it's smaller semi-streamlined cousins will more then make the event for me, and as you say, wet the apeptite for it's long awaited maiden run.

And on a side note, perhaps the GWSR could consider securing another pair light bulleids, though this time one original and one rebuilt, for another gala a couple years down the line at some point. You'd have the complete set of surviving bulleids then, something which I believe is a rare sight in itself isn't it?

Though saying that, MHR achieved it recently... But it's somewhat rare.

 

Is she not available? I just had a look at the BWR site and can't see anything on there, is she off somewhere else?

 

Swanage did a few years back with Tangmere, Manston and Eddystone and again with the two latter and Clan Line.