(1/9) - We’re sorry for disruption to some journeys on the northern end of the East Coast Main Line.
It’s caused by structural issues we’ve found on the viaduct at Plessey between Morpeth and Cramlington stations.
Thread ...
(2/9) –Please check your journeys before you travel with your train operator or via @nationalrailenq: nationalrail.co.uk
@nationalrailenq (3/9) - What’s happened between Morpeth and Cramlington stations?
During planned track work, we found that the viaduct’s parapet – the safety barrier at the edge of the bridge – had moved.
@nationalrailenq (4/9) – So why has this disrupted services? The site location, viaduct design and heavy machinery involved meant it was impossible to quickly move the parapet back to its original position. Our priority is to keep you safe, so one of the lines on the viaduct is currently closed.
@nationalrailenq 5/9) – And what’s happening now?
Structural engineers and other specialists are working on different options. These include rebuilding or realigning the structure. We’re also looking into the time and access each option will take.
@nationalrailenq (6/9) – We need to work through each option before we can open the line going north to traffic again.
We’re making a detailed plan and will do everything we can to minimise the impact on you and freight. We’ll continually review the plan to make sure it works well.
@nationalrailenq (7/9) – The viaduct’s structural integrity is intact. The damaged is contained to part of the parapet, which we strengthened in 2014.
The issue is with 20 metres of the wall leaning away from the north end of the viaduct, where the railway line goes north.
@nationalrailenq (8/9) – The movement has displaced about 30t of masonry and concrete on the bridge, which is 177 years and is Grade II listed.
@nationalrailenq (9/9) – We are sincerely sorry for the inconvenience this will cause you and our freight partners until we’ve completed the repairs.
We’ll give you more information as soon as we can.
• • •
Missing some Tweet in this thread? You can try to
force a refresh