Back to all reports

Blocked drain o/s No 5 Ivy lane

Reported in the Blocked drain category by John Foord at 08:37, Thu 7 November 2019

Received by Buckinghamshire Council moments later

Very poor drainage over the last several weeks but has now developed into a full blockage. Pedestrians struggle to pass unless wearing waterproof boots.

NOTE: the drain is not shown on the map but is outside No 5 Ivy Lane see yellow cross on the picture above.

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 08:45, Thu 7 November 2019

  • Thank you for your report.

    This has been added to our programme of works. Unfortunately, we are unable to provide you with a timescale for this work to be carried out, 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.

    Please be assured this is on our list of works to be carried out, we will continue to monitor all defects to ensure the safety of our residents as part of our Highways Inspection Policy which can be accessed via the link below;
    Transport for Buckinghamshire

    State changed to: Action scheduled

    Posted by Buckinghamshire Council at 09:16, Thu 7 November 2019

  • Now 40 feet long by 10 feet wide, today 14th Nov

    Posted by Barry Hardwick at 08:00, Thu 14 November 2019

  • As soon as it starts to rain the "lake" reappears then takes a day or two to drain away after the rain stops

    Posted by John Foord at 08:29, Fri 6 December 2019
    Still open, via questionnaire

  • Gully sucker needed please! The lake has now grown so large/deep that is flowing down the hill and causing problems with standing water at the junction with the "main" road (Westbrook End). While I understand that you have to prioritise your work it is nearly 7 weeks since I first reported the problem and I would have thought that you could spare us half an hour to resolve this problem,

    Posted by John Foord at 10:57, Fri 20 December 2019

  • Still no action by the council - the drain is blocked and until it is cleared the problem remains. As soon as there is any rain at all (even a light drizzle) the road floods, because the road dips with the drain at the lowest point and it is not flowing - it's visibly blocked with sand and gravel and tarmac from the failed road surface (reported many months ago). There is no way this problem will resolve it's self, it needs a gully sucker!

    Posted by John Foord at 10:49, Friday 3 January 2020
    Still open, via questionnaire

  • Still open, via questionnaire, 18:43, Sunday 9 February 2020

  • Still no action by the council - 14 weeks after the initial report. This is pathetic - it needs a quick visit from a gully sucker and the problem would be solved - surely not beyond the whit of man/woman to get this resolved.....

    Posted by John Foord at 18:51, Sunday 9 February 2020

  • This problem was first reported on the 7th Nov 2019. Here we are 6 months later after one night of moderate rain following a month of dry warm weather. Reason: The Drain Is Blocked! This situation will not resolve itself - it needs council intervention. i.e. a gully sucker. I appreciate that in the current situation you will not regard it as essential but please put it somewhere towards to top of the list for resolution when restriction are lifted otherwise we will go through another autumn\winter with our road flooded.

    Posted by John Foord at 12:54, Saturday 18 April 2020

  • After a visit from a Gully Sucker the problem has finally been resolved. Thanks to the team involved.

    State changed to: Fixed

    Posted by John Foord at 10:28, Wednesday 29 April 2020

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