Back to all reports

1 metre square pothole

Reported in the Pothole category anonymously at 11:11, Sun 7 June 2020

Received by Buckinghamshire Council moments later

Pothole been there for at least one month. Vehicles swerving to avoid it. Collision danger.

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


  • Thank you for your report which is currently under review.
    We will investigate this and if you have provided an email address, we respond to you within 10 working days.
    We will continue to update you by email (if provided) when your report reaches key stages.
    IMPORTANT: To report anything dangerous, please call us on: 01296 382416 (09:00 – 17:30 Mon-Thurs, 09:00 – 17:00 Friday) or 01296 486630 (out of hours and weekends).
    Transport for Buckinghamshire

    Posted by Buckinghamshire Council at 11:11, Sun 7 June 2020

  • Thank you for your report.

    We have recorded it and will consider it when we are planning future works in the area. Please note we work on a priority based risk matrix in line with our Highway Inspection Policy and therefore programme times can change due to priority based working.
    Our Highways Inspection Policy can be accessed via the link below;
    Transport for Buckinghamshire

    State changed to: Action scheduled

    Posted by Buckinghamshire Council at 07:47, Mon 8 June 2020

  • Still open, via questionnaire, 18:21, Mon 6 July 2020

  • The hole remains a danger to road users, especially cyclists when vehicles are overtaking them at that spot. The cone placed in the hole to warn road users has, however, been removed so the danger is now greater than before.

    Posted anonymously at 18:38, Mon 3 August 2020
    Still open, via questionnaire

  • One of several holes on the edge of this busy cut through causing vehicles to drive in the middle of the road and posing a serious injury threat to cyclists.

    Posted anonymously at 20:31, Mon 31 August 2020
    Still open, via questionnaire

  • Questionnaire filled in by problem reporter

    State changed to: Fixed

    Posted anonymously at 22:43, Mon 28 September 2020

This report is now closed to updates. You can make a new report in the same location.