My Neighbor's Tree Is Over the Property Line: What Utah Law Actually Says

The argument almost always starts the same way

A limb is over the fence. Needles are filling a gutter. Roots have found a sprinkler line. Or the neighbor has a leaning spruce that looks, from your deck, like it is aimed at your roof.

Someone then says the sentence that starts most boundary disputes on the Wasatch Back: I am within my rights to cut that.

Sometimes that is true. Often it is only half true, and the half that is missing is expensive. Utah has a statute that triples damages when someone cuts or injures a tree on another person’s land without authority, and the leading Utah case on neighbors and trees says considerably less than the websites quoting it suggest.

This is a working summary for property owners in Park City, Heber City, Midway and the surrounding towns. It is not legal advice, and it flags the places where Utah law is genuinely unsettled rather than papering over them.

The one part that is reasonably settled: you may trim to the line

The common-law rule, applied in most states, is that you may cut back the parts of a neighbor’s tree that cross onto your property, subject to real limits:

• Only to the boundary.Not past it, and not “a little past it to make the cut look right.”
• From your own side. Stepping onto their land to make the cut is trespass, whatever the state of the branch.
• At your own expense. The encroachment does not hand you a bill to send them.
• Without killing or wrecking the tree. A pruning cut that happens to be at the property line can still be the cut that kills a tree, and that is the cut that gets litigated.

That last limit is where most homeowners get into trouble, because a tree does not care where the line is. A large conifer whose crown is half over your lot has roughly half its live foliage over your lot. Removing all of it in one pass is not maintenance, it is a serious injury to the tree, and “I only cut what was on my side” is a weaker defense than people expect.

What Utah’s leading tree case actually decided

Search for Utah tree law and you will be told, repeatedly, that Utah follows the so-called Massachusetts Rule, under which encroaching branches and roots are not actionable and self-help is your only remedy. The case cited for that is Cannon v. Neuberger, 1 Utah 2d 396, 268 P.2d 425 (1954). It is worth knowing what that case really involved, because the summary is misleading in both directions.

A Logan homeowner sued to abate a nuisance: three Carolina poplars and two Siberian elms on his neighbors’ property. He wanted the trees removed, or the neighbors ordered to keep the branches from overspreading, the roots from permeating, and the leaves and twigs from blowing onto his lot.

He did not get that. What the trial court ordered instead is the interesting part: the poplars were to be topped, twenty feet off the tops, with the dead wood removed, along with enough of the branches “to overcome a danger of the trees being blown over onto plaintiff’s property.” The Utah Supreme Court affirmed that judgment.

So the real holding is narrower and more useful than the slogan. On the ordinary nuisances of living next to trees, the court was blunt. Treating trees as abatable nuisances merely because leaves, twigs or even branches blow onto a neighbor’s lot, it wrote, would “condemn to abolition all shade trees in communities sufficiently settled to have perils of such experiences,” until Utah’s towns “revert to blistering, windswept desert.” It also noted that the plaintiff had a fast-growing Siberian elm of his own, nearer the excavation he complained about than any of the neighbors’ trees, and that under a stricter reading he “would, himself… probably be defendant tomorrow in suits by his neighbors on all sides.”

The test the court applied, drawn from Dahl v. Utah Oil Refining Co., is reasonableness: a nuisance is the “unreasonable, unwarrantable or unlawful” use of property, judged by “the reasonableness of the use complained of in the particular locality and in the manner and under the circumstances of the case.”

And here is the part the summaries leave out

The court expressly declined to decide the questions everyone cites it for. In its own words, it was not called upon to determine whether a tree “whose roots may, in fact, destroy the reasonable and proper use of a neighbor’s land, or whose branches may overhang to the same extent” could be subject to damages or abatement — nor to determine “when, if ever,” the affected owner is left to the common-law right to cut off the offending roots and branches. It held only that the evidence supported the judgment.

Two practical conclusions follow, and they point in opposite directions:

• Annoyance is not a case.Leaf litter, needles in gutters, shade, twigs after a windstorm, ordinary root spread — that is the cost of living somewhere with trees, and a Utah court said so in memorable language.
• Demonstrable danger is a different conversation. The remedy a Utah court actually approved was targeted mitigation: take the deadwood out, reduce the crown, remove enough sail area to defeat the blowdown risk. Not removal. Mitigation.

That is the lever. The question that moves a tree dispute in Utah is not is it annoying, it is can the danger be demonstrated— and the court placed real weight on the trial judge having walked the property himself. Physical condition, documented, is what decided it.

The expensive mistake: Utah triples the damages

Before anyone starts cutting, this is the statute to know. Utah Code § 78B-6-1002 provides that a person who, without authority, willfully or intentionally cuts down or carries off wood or timber, or girdles or otherwise willfully or intentionally injures any tree on the land of another, is liable to the owner for treble the amount of damages assessed in a civil action.

Three things make that more dangerous than it sounds:

• Mature trees appraise high. The number is not what a replacement sapling costs at a nursery. Established landscape trees are appraised by recognized methods, and a large specimen spruce or a mature aspen group can be valued in the thousands before the multiplier is applied.
• It covers injuring, not just felling. Girdling is named explicitly. Over-pruning, root severing during trenching, and herbicide drift are all injuries.
• Hiring someone does not move the risk off you. If a crew you hired cuts past the line, you are in the dispute with your neighbor. This is the practical reason to insist the boundary is established before work starts, and that the written scope names which trees are coming down.

The statute has one carve-out worth noting: it does not apply to tree damage arising from a wildland fire, which is handled separately. More on that below, because on the Wasatch Back it matters.

When the tree sits on the line itself

This is the genuinely murky case, and we would rather say so than invent a rule. Utah has no statute squarely addressing jointly owned boundary trees, and Cannon did not reach it. The practical approach we see work:

• Establish where the line actually is. Fences are not boundaries, and on steep Wasatch lots they are often well off.
• Get the scope and the cost split in writing before anyone touches the tree, even between neighbors who get along. Especially between neighbors who get along, because that is when nothing gets written down.
• If you cannot reach agreement and the tree is a hazard, document the hazard and get advice before cutting. A line tree is the single easiest way to end up inside § 78B-6-1002.

When the dangerous tree is on their side

You cannot usually force a neighbor to remove a healthy tree. What changes the picture is notice: the difference between a tree that failed unexpectedly and a tree whose owner knew it was defective and did nothing.

Which makes the sequence straightforward:

1. Document the condition.Dated photographs, from angles that show the defect rather than the inconvenience — the lean with a reference line, the cracked union, the fungal bracket at the base, the soil heaving on the uphill side.
2. Get it assessed properly. A written assessment from a qualified arborist describes the defect, the likelihood of failure, and what the tree would hit. That is the document that converts your opinion into evidence.
3. Deliver it in writing, and keep proof. A friendly conversation leaves no record. A dated letter with the assessment attached does, and that record is the whole point.
4. Then escalate if nothing happens.Their insurer, the city, or an attorney. Insurance mechanics are their own subject — our guide to whether homeowners insurance covers tree removal covers who typically pays in which scenario.

Worth knowing: this cuts both ways. If a neighbor hands you a written report on a tree of yours, that report is now part of the record. The cheap response is to deal with the defect. The expensive response is to file it and hope.

Park City adds a layer most owners do not expect

“It is my tree, on my land” is a good starting point and not always the end of the question. Park City’s Land Management Code protects what it calls Significant Vegetation, defined to include large trees six inches in diameter or greater measured four and a half feet above the ground, along with groves of smaller trees and clumps of oak and maple covering fifty square feet or more at the drip line.

That definition has teeth where development is involved. Development plans must show Significant Vegetation within twenty feet of proposed development, and the property owner is required to demonstrate the health and viability of large trees through a certified arborist. A 2023 water-wise amendment went further: landscape plans must identify existing Significant Vegetation, it is to be maintained on site and protected during construction where possible, and replacement is expected to be equivalent in type and size, with exceptions granted by the Forestry Manager or Planning Director.

So the practical rule in Park City is that a six-inch tree near a project is a planning matter, not just a landscaping choice. If you are mid-permit, the tree you were about to settle with your neighbor over may also be a tree the city has an opinion about. Our guide to protecting trees during construction goes through how that plays out on an active site.

Two more layers sit on top. Park City’s forestry ordinance governs trees on city property and in the right-of-way, and reserves the city’s ability to prune private vegetation that interferes with city infrastructure. And if the tree is anywhere near a power line, the utility’s easement rights usually outrank both you and your neighbor — which we cover in trees and power lines, and who trims what. Separately, if you are in an HOA, its CC&Rs may require written approval before removal regardless of what state law permits.

The wildfire clause nobody reads

Remember that carve-out in the treble damages statute. Wildland fire damage is governed by Utah Code § 65A-3-4, and the operative language deserves to be read slowly: a person who negligently, recklessly, or intentionally causes or spreads a wildland fire is liable for the cost of suppressing that fire, regardless of whether it begins on private, state, federal or tribal land.

Suppression cost is not property damage. On a bad day in the Wasatch Back it is air support, multiple agencies and a long perimeter, and it is not a number a homeowner’s policy was built around.

The statute also contains an instructive detail. Utilities get a safe harbor from a negligence finding if their approved wildland fire protection plan addressed the cause and the identified mitigation work had actually been completed at the point of origin. Homeowners do not get that statutory protection — but the logic is the one worth absorbing: documented, completed mitigation is what distinguishes reasonable care from negligence.

Which is why the slash pile matters. Burning debris outside a permitted window is the most common way an ordinary property owner walks into this statute. Our guide on what to do with the wood after a removal covers the burn windows and permits, and the hazardous fuel guide covers reducing the fuel in the first place.

What to do, in order

1. Find the line before you form an opinion. Survey pins, plat, or a surveyor. Not the fence.
2. Separate annoyance from danger. Needles in the gutter are maintenance. A defect that could put a stem through a roof is a different category with different remedies.
3. Get the condition in writing if it is the second one. Undocumented danger is just an opinion.
4. Talk first, in writing second. Most of these resolve with a conversation and a shared invoice. The written step is what you need if it does not.
5. Check the other rulebooks— municipal code if you are near a permit, CC&Rs if you are in an HOA, the utility if there is a line nearby.
6. Do not cut past the line without written authority. Treble damages.

Where we fit

Most of what we do in these situations is unglamorous: walk the property, say plainly whether a tree is actually defective or just inconveniently large, and put that in writing so you have something better than a photograph and a strong feeling. Sometimes the honest answer is that the tree is fine and the dispute is about something else. We would rather tell you that than sell you a removal.

When a tree genuinely is a hazard, the remedy a Utah court approved seventy years ago is still usually the right one: take out the deadwood, reduce the sail area, defeat the failure mode. Removal is the last option, not the first.

Reach out through our contact page or call (201) 960-8275. Assessments come in writing, and if the tree is on a boundary we will tell you plainly what we can and cannot touch without your neighbor’s sign-off.

This article is general information about Utah law, not legal advice, and nothing here creates an attorney-client relationship. Cannon v. Neuberger was decided in 1954 and interpreted a nuisance statute that has since been renumbered; statutes are amended and recodified, and § 78B-6-1002 was last amended in 2020. Municipal code provisions change, and the Park City provisions summarized here should be confirmed against the current Land Management Code with Park City Planning. For a specific dispute, talk to a Utah attorney.