North Shields bridge repairs complete, Metro services resume
Summarised from 2 outlets · Updated 2 Nov, 21:08 · Archive
Metro services between Wallsend and Tynemouth will resume on Tuesday after bridge repairs in North Shields finished ahead of schedule.
Metro services between Wallsend and Tynemouth will return to their normal timetable on Tuesday after urgent repairs to a bridge in North Shields were completed ahead of schedule. The bridge had been inspected during a planned closure between St James and Monkseaton, which finished at the end of the weekend. Services were initially set to resume on Thursday.
The repair work proved complex. Nexus staff erected scaffolding above the track, removed vegetation from the bridge and rebuilt the bridge arch brick by brick. The stonework damage was identified during the planned inspection last week. The work required power to be turned off in sections to allow teams to work safely.
Kevin Storey, Operations Director at Nexus, said the team had allowed sufficient time in case unknown issues arose. He added: 'Safety is always our top priority.' Nexus is investigating what caused the recent damage. Customers were inconvenienced on Monday when services were suspended, with those travelling from the coast to Newcastle city centre told to use the Benton route instead.

How it is being reported
- North Shields bridge 'urgently repaired' as Metro services set to go 'back to normal'Nexus has shared that its trains between Wallsend and Tynemouth will return to the usual timetable on Tuesday, with the repair 'completed early'ChronicleLive · 2 Nov, 20:35
- Extended Metro closure ends after bridge repairsRepairs are completed to a bridge in North Shields, allowing the resumption of Metro services.BBC Tyne And Wear · 2 Nov, 17:00
In this story: Nexus · North Shields · Wallsend · Tynemouth · Tyne and Wear Metro · Kevin Storey
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem · Corrections log
Comments (0)