Thank you for contacting the City of Huntsville with your service request. Your inquiry is being processed, and one of our departments will respond as soon as possible.

Thank you,
The Huntsville Connect Customer Service Team

Thank you for reporting your service request to the City of Huntsville.
Our City Arborist inspected this tree. He found that the tree is on private property, owned by the development company. The area the tree is located was designated as a common area by the developer. The removal of the tree is the property owner's responsibility.
Your issue has been handled and we are closing your request. If you need further assistance, please let us know.

Thanks for checking in with Huntsville Connect!

Your Customer Service Team

The builder is almost sold out of Clayton Cove, I don't think they will cut it at this point. Can the city make the builder cut it? If you look at the picture you can see it's near a sidewalk and what if one or some of those large dead branches on the top of it fall off?

Thank you for contacting the City of Huntsville with your service request. Your inquiry is being processed, and one of our departments will respond as soon as possible.

Thank you,
The Huntsville Connect Customer Service Team

Huntsville Landscape Management assigned this issue to Huntsville Engineering

We will evaluate this issue, and respond as soon as possible. Thank you Engineering

Thank you, hope to have an update soon on whether the city can do something about this issue.

Good morning Ruth,

We have looked into this issue and The Common Areas in Clayton Cove, as the Green Team mentioned, were recently turned over to the Clayton Cove Homeowner Association. The original developer of the subdivision has been contacted and was ask to see if they could have the tree removed. They were going to contact the company that is managing the homeowner association to see about getting the tree removed.

For more inquiries, you may contact our office at 256.427.5300.

Thank you, Engineering

Thanks for fixing this issue!

Issue 3631017 has been marked as a duplicate of this issue.

Issue 3640111 has been marked as a duplicate of this issue.