Sun. Dec 22nd, 2024
alert-–-will-they-ever-get-the-elizabeth-line-into-gear?-tfl’s-troubled-year-old-line-is-hit-by-severe-delays-again-due-to-train-fault-at-paddington-–-sparking-travel-chaos-for-commutersAlert – Will they EVER get the Elizabeth Line into gear? TfL’s troubled year-old line is hit by severe delays again due to train fault at Paddington – sparking travel chaos for commuters

Commuters once again faced major disruption on the Elizabeth line this morning after the central section of the network was blocked due to a broken down train.

A faulty train at Paddington station blocked the £19billion line through Central London towards Whitechapel between Paddington and Tottenham Court Road.

A second issue involving rail defect in a set of points in the Hayes and Harlington area also hit services today, cancelling trains between Reading and Paddington.  

This resulted in severe congestion building up, meaning passengers were stuck on trains which were terminated early. Disruption is expected until the end of today.

The problems continues a week of chaos for the line which has suffered major disruption – after much of it was shut over the weekend for engineering works.

Commuter Emma Louise tweeted Transport for London (TfL), saying: ‘Hi. You’ve delayed me Tuesday evening (21st), Weds morning and evening, Thurs morning and evening, Fri morning and evening, Mon (27th) morning, Tues morning and evening, Weds morning and evening, and this morning. Can I claim for each delay? Thank you. #ElizabethLine.’

Judith Frank-Simon said: ‘The lack of information this morning for the Elizabeth line is terrible. We sat outside Paddington for 20 minutes only being told it was a red signal and the train would now end there. Not one bit of info to say line was now suspended.’ 

And commuter Sally Greenbrook tweeted: ‘I use the Elizabeth line all the time and generally I love it. But this morning we’ve been stuck outside Paddington for nearly an hour. The train went backwards for a bit and now sitting still again.’ 

More to follow 

error: Content is protected !!