Banwell bypass delayed again as costs rise to £114.6m
Summarised from 2 outlets · Updated 5 Nov, 11:28 · Archive
The Banwell bypass in North Somerset, first proposed in 1927, will now open in December 2027 rather than June, with costs rising by £9.5m.
The Banwell bypass in North Somerset, first proposed in 1927, has been delayed again. Work was expected to be complete by June 2027 but will now take until December 2027, meaning the village's wait will stretch to around a century since the original proposal.
North Somerset Council attributed the delay to Bristol Water's delay in relocating water mains, which disrupted contractor Galliford Try's progress on site. The project's budget has increased from £105.2m to £114.7m, a rise of £9.5m. Councillors will be asked at a full council meeting on 10 November to approve borrowing of £9.5m to cover the additional costs. The council is seeking legal advice on recovering the extra expenses from those responsible for the delay.
Council leader Mike Bell said the delay meant 'despite delay we continue to make good progress on site and the century-long wait will soon be over'. He added that when it opens, the bypass will improve road links between Weston-super-Mare and the A38. The project also includes miles of new walking, cycling and horse-riding tracks connecting with the Strawberry line, along with new woodland, wetland and grassland.
How it is being reported
- North Somerset village's century-long wait for a bypass is delayed againAnd it will cost £10m almost moreSomersetLive · 5 Nov, 10:49
- Century-long wait for £105m Somerset bypass goes on after new delayThe proposed Somerset route is officially the UK's longest-running road project after nearly 100 years - and has now been delayed againSomerset County Gazette · 4 Nov, 12:05
In this story: Banwell · North Somerset · North Somerset Council · Bristol Water · Galliford Try · Mike Bell · Weston-super-Mare
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)