Back to all reports

A number of very large potholes

Reported in the Pothole category anonymously at 15:27, Wed 21 August 2019

Received by Buckinghamshire County Council moments later

There are some increasingly large potholes on Crispin Way at Ashenden Walk. They are becoming a serious hazard particularly as the streetlighting in this area is very sparse. It is only a matter of time until a vehicle suffers serious damage or a cyclist is badly injured. These holes need urgent attention. They have been there for some time (months) and are getting bigger.

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

Updates

  • 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).
    Regards
    Transport for Buckinghamshire

    Posted by Buckinghamshire County Council at 15:30, Wed 21 August 2019

  • I'm appalled at the state of my road (Crispin Way) which seems to be getting steadily worse with potholes the size of craters! It's only a matter of time before I do serious damage to the suspension on my car. We are paying around the highest council tax in the country - what are we getting for it? Members of our council don't appear to be fit for purpose!

    Posted anonymously at 14:36, Thu 22 August 2019

  • Thank you for your report.
    We have assessed your report and the repair of this defect has been added to our programme of works.
    We will continue to update you by email when your report reaches key stages.
    Regards
    Transport for Buckinghamshire

    State changed to: Action scheduled

    Posted by Buckinghamshire County Council at 12:15, Fri 23 August 2019

  • Questionnaire filled in by problem reporter

    State changed to: Fixed

    Posted anonymously at 21:31, Wed 18 September 2019

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