A short but eventful journey tonight (19/11)

[whole diary]

[BBM]

Tonight as usual I took the 17:06 to Bristol TM^‡(resolve) via Bradford-on-Avon for the short 21-minute journey to Twyford but quite a lot happened for me to report! Firstly the train took the recently reinstated route from Line 4 to Line 2 via signal SN109 at Ladbroke Grove, the first time I've been on a train on that route since the reinstatement.

Then just east of Maidenhead there was an almighty bang from underneath coach E in which I was travelling. I expected maybe a sharp brake application following that, but the train continued at normal speed to the first stop at Twyford.

The HST^▸ (High Speed Train) tonight was not only unusually in reverse formation but also it had 5 Standard coaches and a buffet with half First class (plus 2 full-length First Class) instead of 6 Standard including one with a small buffet. On arrival at Twyford the Central Door Locking only released on one door, which was at the front end of coach F (the buffet). Therefore everyone had to exit through that one door! Fortunately I was at the front end of coach E so I didn't have far to go but I notice from Live Departure Boards that the train appears to have been held at Twyford for 20 minutes, presumably to allow everyone to alight (and I saw that the connecting Henley Branch train departed on time without waiting for many people).

Could whatever the train might have hit on the track at Maidenhead (if it did hit anything) cause damage to the door locking?

[Ollie]

Hi BBM.

It's not certain what the train hit as yet. But whatever it was caused a couple of cables to be knocked resulting in the door locking to not release. The long delay at Twyford was due to the Driver and Train Manager putting these cables back in place for the train to proceed.

[BBM]

Hi Ollie,

Thanks for that explanation. The bang seemed to come from the front end of coach E so presumably cables between coaches F and E were affected, hence why the door locking was only released on the one door at the non-buffet end of coach F. (On reflection it's probable that the doors were also released on coach G, but not H because it would be beyond the platform.)

[Electric train]

I did wonder why the 17:18 ex Padd was still held at Plat 4 Maidenhead when the Marlow left at its usual time

[grahame]

Interesting how such a delay has a knock-on effect ... the 17:45 off Paddington was delayed and missed the last only connection of the day to Melksham. Top marks to the train manager who ensured that alternative arrangements were made for a first-time visitor who I spoke to about half an hour ago, and who was impressed.

[IndustryInsider]

Quite a bad evening all round.  The 17:18ex PAD^» (Paddington (London) - next trains) was actually delayed after reports of sparks coming beneath it between Slough and Maidenhead.  The all-clear was soon given and it arrived 5 minutes late at Oxford - faring better than most other services tonight!

[JayMac]

It's also interesting that the problem with 1C90 1706 Paddington to Bristol Temple Meads appears to have initially been brought to the attention of FGW^▸ (First Great Western) via twitter. A tweet from a passenger mentioning strange noises, possibly ballast hitting the train was made 5 mins before the train arrived at Twyford.

[Mookiemoo]

Might go to explain why my train was 30 late into Bristol Parkway....1815 to Swansea