Description
In mid December of 2016 a Gloucester City Plow truck backed into the led light pole at the corner of Castleview drive and Seafox lane in Gloucester Ma., damaging and knocking the pole into the street. They pulled the pole to the side of the road and approximately two weeks later Siemens company rremoved the pole. The incident was witnessed by one of our residents. The Castleview Homeowners Association is composed of 2 miles of roadway and has many city lights on those roads.Castleview dr,Seafox ln, and Saltmarsh ln... Within a week I informed the Siemens Company of the pole problem
and they gave me a Service Notification Number: 005002992264. I assumed it would be taken care of. In around May of 2016 I called Siemens to find out about progress and they said they could not talk to me they would have to talk with the City to do anything. I then called the city several times and was forwarded to a number which I called and left a message and a return number. No one returned the call. After several attempts to contact the City I decided to write an email on the city website copied to the city DEP director, explaining the situation leaving email, name and number. No return call no email no acknowledgment at all of any action that either we should take or they will take. We are now coming up to the 1 year anniversary of the incident and still no resolution let alone acknowledgement of the issue at all. Currently the pole stantion has an orange cone above it and the 220 volt wires are tied off with one swath of electrical tape.
What is going on? The pole is across the street from the public buss stop. How long do you think it will be before some kid picks up the cone and grabs the 220 volt line? Where is our light pole and light? Why don't they respond to requests?
Thanks for your help.
also asked...
A. Streetlight damaged
A. No Answer Given
2 Comments
Acknowledged Rose - DPW Admin (Verified Official)
Joe Lucido - Assistant Director, DPW (Verified Official)
This issue has been marked as a duplicate of issue 3951101.
If you are already receiving notifications regarding this issue,
you will now receive updates regarding issue 3951101.