Stonehenge and its Environs 134
Image by Chance
Stonehenge and its Environs

​…Road Finally Closed​….

Sanctuary S
Sanctuary Oct 8, 2013 17:18:49
Replying to Mustard

Mustard wrote:
Sanctuary wrote:
Are EH as keen to see the back of the road through Avebury as they are at SH? If not, why not? The A303 is nowhere near as evasive as the road passing straight through the middle of a stone circle of WHS status!
Bit different though, isn't it? Even if you dug a tunnel under Avebury, there's still a living community that would need vehicular access, so the road couldn't be removed. Best you could do would be to significantly reduce traffic.
I was thinking bye-pass and leaving the road down to the church and past the Red Lion the other way to Swindon open and cutting the road through the middle of the circle off. Along those lines anyway.

M Mustard
Mustard Oct 8, 2013 17:26:53
Replying to Sanctuary

Sanctuary wrote:
Mustard wrote:
Sanctuary wrote:
Are EH as keen to see the back of the road through Avebury as they are at SH? If not, why not? The A303 is nowhere near as evasive as the road passing straight through the middle of a stone circle of WHS status!
Bit different though, isn't it? Even if you dug a tunnel under Avebury, there's still a living community that would need vehicular access, so the road couldn't be removed. Best you could do would be to significantly reduce traffic.
I was thinking bye-pass and leaving the road down to the church and past the Red Lion the other way to Swindon open and cutting the road through the middle of the circle off. Along those lines anyway.
But you'd still have a road through the village, and a bunch of (legitimately) pissed off residents. Preferable from a conservation point of view maybe, but nowhere near the (relatively) simple solution that's available at Stonehenge. So it's kinda easy to see why it isn't up there on the EH priority list, nice though it would be from a TMA perspective.

© 2026 Head Heritage.

Unless otherwise stated, the copyright in each work is the property of the respective contributor. For usage or questions, contact [email protected].