Stumpy pieces of metal in ground from old barrier
Reported via desktop in the Pavements category anonymously at 13:49, Tuesday 4 April 2023
Sent to Bristol City Council less than a minute later. FixMyStreet ref: 4397607.
Stumpy pieces of metal in ground from old barrier In April 2020 a person decamped from a stolen car, running at speed down the lane between the play area at the back of Maskelyne Avenue, in doing so smashed into the barrier which was there. All that is left are the fittings for the no longer there barrier. These fittings are a trip hazard to people using the lane. The other issue with the lane is the hedges brambles and stinging nettles over grown making it a hazardous lane to walk.
THIS WAS REPORTED IN 2022, THE COMPLAINT WAS CLOSED IN JULY 2022. THIS HAS NOT BEEN RECTIFIED AND NEEDS URGENT ATTENTION, MY MOTHER HAS TRIPPED ON THESE STUMPY METAL PIECES THIS MORNING, AND NEARLY FALLEN FLAT ON HER FACE. HOW CAN THE COUNCIL CLOSE A COMPLAINT, WHEN NOTHING HAS BEEN DONE TO SORT OUT THE PROBLEM. THIS NEEDS URGENT ATTENTION.
A new enquiry has been raised for this issue.
Posted by Bristol City Council at 13:50, Tuesday 4 April 2023
This issue is currently under investigation. We'll provide updates on the outcome as soon as we can.
Posted by Bristol City Council at 12:44, Tuesday 11 April 2023
This enquiry has been referred to another team for action. They will provide further updates on the issue in due course.
Posted by Bristol City Council at 06:45, Wednesday 12 April 2023
Still there I have to swerve on my bike else I'll get a split tyre Rees needs the money to fly around the globe on green issues
Posted anonymously at 22:57, Sunday 16 April 2023
A citizen has provided a follow-up to the original enquiry.
Posted by Bristol City Council at 22:57, Sunday 16 April 2023
This Fix My Street enquiry has been automatically closed.
State changed to: Closed
Posted by Bristol City Council at 00:05, Tuesday 23 May 2023
This report is now closed to updates. You can make a new report in the same location. Please reference 4397607 in your new report if it is an update on this one.