It was a woeful day across the
FGW▸ network. I happened to pick this day to visit the Melksham line!
The packed 10.45 from Paddington departed on time but soon the brakes were slammed on and we crawled through West London.
We finally shuddered to a stop at Slough. Dozy passengers on the train started leaning out of the windows, thinking it was Reading (it was ~20 minutes after leaving Pad to be fair!) leading the panicked guard to make an announcement. Passengers on the platform, who were expecting the Oxford service, attempted to board, leading to further delay as the doors had to be checked.
We were then abruptly shunted onto the relief lines and crawled at the lower top speed to Twyford, with other
HSTs▸ speeding past on the main lines. After Twford we were shunted back much to our relief. The breaks were slammed on again for no apparent reason at Didcot (perhaps the Oxford had overtaken us when we were on the reliefs and was having to wait - but why?) and we crawled through the station.
On arrival at Swindon just under half and hour late (
), the network was in meltdown. Digital Doris was apologising for one train after another and most trains on the screen were 25 late.
I took the 12.49 from Swindon, which didn't turn up until after 1pm. According to the apologetic guard, this was because of a problem at Bradford UA which was causing "chaos" at Westbury. About 11 people got off the incoming service. I and six others boarded. At Chippenham five more boarded. At Melksham two people and I got off, with two getting on. Not massive, but not bad for an off peak service.
The info screen was displaying an error message, so I and another passenger had to press the info button to ask when the next train was. The car park was full, although I'd imagine mostly by shoppers...
The stock running the service was a clapped out 153 that had clearly not had much maintenance (probably ex
ATW▸ or CT). The train was definitely struggling to stay at 75 mph on the main line with the engine sometimes spluttering out. We lost time in between each station.
Arriving just after 1.30, around 15 minutes late, I just had enough time for a cup of tea before the return. However, disaster almost struck. Despite normally having a good sense of direction, lack of signage meant that I took a wrong turn on the way back to the station and ended up at ASDA.
Signage needs to be made clearer to encourage visitors from the town centre.
After a dash across a dual carriageway and along a muddy verge, I arrived at the station. Luckily the 2.30 was running 10 minutes late, according to the screen, which had now fixed itself. Unfortunately, a few moments later is just switched off and went blank!
This screen needs sorting ASAP.The 2.30 arrived - one person got off, I got on; there were five others on board. It seems to me that most people are using the route as a quicker way to Swindon and not many using it for Melksham. Presumably this will improve.
At Chippenham were we arrived even later due to the unit struggling (I doubt the later services were cancelled due to traincrew shortages, more like the 153 finally gave up!), I got off, no-one got on.
After another cup of tea in Chippenham, I took the 3.25 back to London. This train arrived late, so I happened to see the next departure to Melksham. Four people boarded. I didn't spot how many other were onboard.
The 3.25 train was full and standing and seemed to crawl for most of the way, arriving late at about 5pm. I really don't know why they bothered upgrading the
GW▸ line to 125mph - the trains barely reach to 125 before the next red signal. When you consider that Chiltern get to Banbury in 50 minutes. Which is further than Oxford (plus on a congested 2 track, 100 mph railway), you wonder what's going on with FGW.
Overall verdict: encouraging. Good timetable, hopefully can become hourly at some point with some facilities at Melksham station. Hopefully 100mph stock can be used eventually to slash the journey time on the mainline.
Well, I hope I've done my bit to add to the passenger numbers!