You need to enable JavaScript to run this app.

Skip to main content

RE: Durham County Council
(21 Aug 2015, 8:03 pm)cbma06 wrote yep, I saw this on the council website awhile ago:

http://www.durham.gov.uk/scoot


http://www.durham.gov.uk/media/6878/Gile...t_plan.pdf 

http://www.durham.gov.uk/media/6879/Leaz...t_plan.pdf 

It is now proposed to commence on Gilesgate roundabout in early 2016 and Leazes Bowl in Summer 2016, to coordinate with required traffic surveys in Autumn 2015. Once completed we hope to start using the SCOOT system in 2017.

So hardly any delay then. Millburngate bridge has always been a pinch point with traffic often way up Gilesgate at peak times - the bridgeworks have simply extended those busy times but haven't made tailbacks any worse. (Buses have actually been more punctual for more of the day, most days, thanks to Arriva's contingency plans.) That bridge doesn't carry anything like the traffic of Millburngate Bridge, so the effects of the work will hardly be felt.

Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
RE: Durham County Council
Durham County Council
Durham County Council
RE: Durham County Council
RE: Durham County Council