Pavement on Dunkerton hill on the way to Peasedown where the road expands to 2 lanes
Reported via mobile in the Excessive or dangerous littering category anonymously at 15:05, Tuesday 5 May 2026
Sent to Bath and North East Somerset Council 1 hour, 53 minutes later. Council ref: 9403070.
There has been debris on the pavement on the way to peasedown from Dunkerton for years now. As a cyclist I would greatly appreciate being able to use the pavement (where I’ve never seen any pedestrians) to cycle on to avoid being involved in an accident. The straight from Dunkerton is fine as it’s so wide, but where the pavement lowers on the left just after the road expands to two, it would be really helpful and a lot safer if cyclists could use this to come off the fast road where it’s going round a corner too. As a cyclist it’s a big hill so comparison in speeds between car and bike is huge. Please could I request this is cleaned and debris/glass removed to avoid punctures. I’m sure other cyclists which I often see would benefit. Lastly to add this will help reduce casualties that has already happened, that is clearly signed between peasedown and bath. Perhaps a clear shared path for cyclists and pedestrians is needed to highlight use of this part of the hill.
Updates
-
Thank you for your report, it will be reviewed by the appropriate team.
State changed to: In progress
Posted by Systems Team at 15:05, Tuesday 5 May 2026
-
We've looked into this report and are investigating the issue.
We will update this report once we decide what action to take.State changed to: Investigating
Posted by Systems Team at 16:52, Tuesday 5 May 2026
-
We've passed this report to another team in the council. They will carry out any further work needed. Sometimes it can take a little longer as a result.
We'll update this report once we've decide what action to take.
Category changed from ‘Dangerous road surface (including ice, mud, spillage or debris)’ to ‘Excessive or dangerous littering’
State changed to: Open
Posted by Bath and North East Somerset Council at 16:57, Tuesday 5 May 2026
Provide an update
Your information will only be used in accordance with our privacy policy