Back to all reports

Number of areas damaged by pavement parking by heavy vehicles

Reported in the Pavement Defect category anonymously at 11:37, Mon 22 June 2020

Sent to Bristol City Council less than a minute later

There are a number of badly damaged and cracked areas mainly in the upper part of Coombe Bridge Avenue ie outside 39, 33 31 , 17 , 13, 22 ad 24 due to extensive building works and heavy vehicles parking on the pavement. Having talked to neighbours and kived in Sneyd Park where there are Tarmacked pavements I would favour that approach as being much more durable . What would be the next process to move this forward?

RSS feed of updates to this problem Receive email when updates are left on this problem.

Updates

  • A new enquiry has been raised for this issue.

    Posted by Bristol City Council at 10:37, Mon 22 June 2020

  • I would like to update my comments of the 26th November 2020 and to point out the many "trip hazards" the pavements of Coombe Bridge Ave due to seriously cracked and loose paving in a number of areas already highlighted. The hazard is particularly serious for our seriously visually-impaired neighbours. I suggest replacing all rectangular slabs by 40cm square pavers, already fairly widely used, which are much more durable to traffic mounting our pavements and would unify the appearance of the pavements.

    Posted anonymously at 10:25, Saturday 16 January 2021

  • A citizen has provided a follow-up to the original enquiry.

    Posted by Bristol City Council at 10:25, Saturday 16 January 2021

  • This issue is currently under investigation. We'll provide updates on the outcome as soon as we can.

    Posted by Bristol City Council at 11:34, Tuesday 9 February 2021

  • As this issue is not urgent we'll deal with it as part of a future planned work scheme in this area.

    State changed to: Closed

    Posted by Bristol City Council at 10:32, Thursday 18 February 2021

This report is now closed to updates. You can make a new report in the same location. Please reference 2166920 in your new report if it is an update on this one.