The Neighbor's Tree Is on Your Garage. In Minnesota, Your Own Policy Usually Pays First, and the Chainsaw Can Cost You Triple.

November 16, 2026 · David J.S. Madgett

The wind came through overnight and the neighbor’s silver maple is lying across your garage roof. The first thing most people want to know is whose tree it was. That’s the wrong first question.

In Minnesota the first call is to your own insurer, not to the neighbor. Whether the neighbor ends up paying anything depends less on whose yard the trunk grew in than on what the neighbor knew about the tree before the storm, and that’s a question no Minnesota appellate court I could find has squarely answered for a neighbor’s tree. And the one move that feels most natural, firing up a chainsaw and cutting the whole thing up, is the one with a treble-damages statute attached to it.

Who pays for my garage?

Start with your own homeowner’s policy. A tree landing on a covered structure is the sort of loss homeowner’s property coverage is written for, and most policies include some coverage for removing the debris. The details live in your policy’s own words: what’s covered, the deductible, the limit on debris removal, and whether the tree has to have hit a covered structure for removal to be paid at all. Read your policy before you assume anything. If you and your insurer can’t agree on the amount, there’s an appraisal route, and I walked through how it works at /news/minnesota-property-insurance-appraisal-65a01/.

The neighbor’s insurer usually doesn’t enter the picture unless the neighbor was at fault. If he was, your insurer may pay you and then go after him for what it paid. That’s subrogation, and it’s one reason your insurer will care what that tree looked like last summer.

So the practical sequence, in the order I’d do it:

Step Who Why
Photograph everything before anything moves You The stump, the break, the rot, the trunk’s position on the line, the damage
Report the claim Your insurer Your property coverage is the usual first source of payment
Tell the neighbor, in writing Neighbor It’s his tree; he may want his own arborist and his own insurer told
Cut only what’s on your side, and only what you must You or a tree service The rest of the tree is his, and § 561.04 is waiting
Decide whether there’s a fault claim You, your insurer, a lawyer Worth pursuing mainly where the tree was dead, diseased, or visibly failing and he knew or had reason to know it

When is the neighbor actually on the hook?

Here’s what surprised me. I expected to find a line of Minnesota cases on exactly this: a neighbor’s tree, a storm, a damaged house. I searched CourtListener’s Minnesota Supreme Court and Court of Appeals opinions in five phrasings, the doctrinal ones (“act of God”, “windstorm”, “duty to inspect”) and the plain ones (“tree fell”, “garage”, “neighbor”). I didn’t find a published Minnesota appellate decision deciding whether a homeowner owes a neighbor a duty to inspect a tree, or holding a homeowner liable to a neighbor for a tree that fell in a storm.

So what follows is my reading. No Minnesota court has said it in a tree case.

The Minnesota Supreme Court sorts negligence duties into two buckets. One: “general negligence law imposes a general duty of reasonable care when the defendant’s own conduct creates a foreseeable risk of injury to a foreseeable plaintiff.” Domagala v. Rolland, 805 N.W.2d 14, 23 (Minn. 2011). Two: when “action by someone other than the defendant creates a foreseeable risk of harm”, the defendant owes a duty to protect against it only if the two “stand in a special relationship.” Id. The court stressed “the historical distinction between misfeasance stemming from an actor’s own conduct and nonfeasance when someone other than the defendant creates the harm.” Id. at 24.

Notice the court is talking about people. “Someone.” Wind isn’t someone. A healthy tree that a storm snaps doesn’t sit comfortably in either bucket, and if it lands anywhere, I’d put it with nonfeasance. Nobody did anything. Wind did. I’d expect a Minnesota court to call that nobody’s fault, which means your policy is the whole answer.

A tree the neighbor knew was dead, rotten, or split, and left standing over your garage anyway, is a harder case, and that’s where the fight would be. The argument for liability is that keeping a known hazard on your land, pointed at your neighbor’s house, is your own conduct creating a foreseeable risk. The argument against is that the decay is nature’s doing and the neighbor simply didn’t act. Minnesota hasn’t picked a side in a neighbor’s-tree case that I could find.

The closest case I found shows how hard knowledge is to prove. In June 1981 a limb broke off a tree in Helmer Myre State Park during a storm with winds “of approximately 45 m.p.h.” and fell on a tent, killing one child and injuring another. Henry v. State, 406 N.W.2d 608, 610 (Minn. Ct. App. 1987), review denied (Minn. Aug. 12, 1987). The park manager had looked at the trees the day before. “He viewed the trees from the ground, but noticed nothing unusual or hazardous about the limb”. Id. After the accident the tree “showed internal decay and discoloration.” Id. The Court of Appeals affirmed summary judgment for the State. Id. at 612. Two cautions about that case. It was decided under a state-park immunity statute that sets a much harder standard than ordinary negligence, and one judge dissented. But the court’s last word on the facts is the line a neighbor’s lawyer will quote: “Certainly, the state employees had no reason to know that a severe windstorm would occur, causing the limb to break off.” Id.

What does that mean for you? If you want the neighbor to pay, you’ll need proof he knew or had reason to know the tree was failing. A dead crown everyone could see from the street. Bark sloughing off a trunk. A split leader. A letter you sent him last spring. An arborist’s report. A city notice. Without something like that, a storm is a storm.

Can the city make him take a dead tree down?

Often, yes, and that’s the cleaner route before the storm ever comes.

The Legislature lets a city collect the cost of “the treatment and removal of insect infested or diseased trees on private property” as a special assessment against the property, and the same for “removal or elimination of public health or safety hazards from private property”. Minn. Stat. § 429.101, subd. 1(a)(6), (3). A city can also, by ordinance, put “primary responsibility upon the property owner or occupant to do the work personally” upon notice, but the same sentence carves “tree trimming, care, and removal” out of that option. Id., subd. 1(b). Whether that carve-out reaches a dead tree in a back yard or only the street trees in clause (5), the statute doesn’t say. The Legislature wrote a tree exception into a statute that lists trees twice and didn’t say which ones it meant. Whether and how your city uses any of this is in its own code. A call to the city’s forester about a visibly dead tree is cheap, it creates a record, and that record is the kind of evidence that can turn a storm loss into a fault claim if the tree comes down later.

The trunk is on the line. Doesn’t that make it half mine?

Not by itself. This is the lead most people get wrong.

The Minnesota Supreme Court took this up in 1969 over a Minneapolis elm planted about fifteen inches from the line that had grown across it. Holmberg v. Bergin, 285 Minn. 250, 252 (1969). Owners of a true boundary-line tree “are considered tenants in common, neither tenant possessing the right to destroy the commonly held property without consent of the other.” Id. at 254. But the court held “that something more than the mere presence of a portion of a tree trunk on a boundary line is necessary to make the tree itself a boundary-line tree”. Id. at 256. Whether it’s a boundary tree “depends instead either upon the intention, acquiescence, or agreement of the adjoining owners or upon the fact that they jointly planted the hedge or tree”. Id.

So a maple your neighbor planted that grew into the line is still, in most cases, his tree. I wrote about Holmberg, boundary trees, and encroaching roots in detail at /news/minnesota-tree-damage-treble-561-04/, and about who owns and pays for the fence along that same line at /news/minnesota-boundary-fences-344/.

Can I just cut it up and haul it off?

Cut what’s on your side. Be careful past that.

Holmberg allowed, without holding it, that it “may be true” an owner “could resort to self-help by cutting the overhanging branches back to the property line and cutting out the offending roots”. 285 Minn. at 257. Notice where that stops. The property line.

Now the statute. “Whoever without lawful authority cuts down or carries off any wood, underwood, tree, or timber, or girdles or otherwise injures any tree, timber, or shrub, on the land of another person” is liable to the owner “for treble the amount of damages which may be assessed therefor”. Minn. Stat. § 561.04. Only single damages are awarded if “the trespass was casual or involuntary,” or if the defendant “had probable cause to believe that the land on which the trespass was committed was the defendant’s, or that of the person in whose service or by whose direction the act was done”. Id. That last clause is the tree service’s defense: it thought it was cutting on its customer’s land.

A tree lying across two yards is exactly where that statute gets interesting. The part on your garage, you can deal with. The stump, the root plate, and the trunk still standing on his side are his, and if you’re angry about your garage and you take the rest down while you’re at it, you’ve handed him a claim with a multiplier on it. Cut to the line. Tell him in writing what you cut and why. Let him and his tree service handle his side.

One more thing worth knowing if your own work made it worse. Minnesota has said since 1889 that a man “has no right to construct his roof so as to discharge upon his neighbor’s land, water, ice, or snow which would not naturally fall there”. Hannem v. Pence, 40 Minn. 127, 130 (1889). That’s the artificial-versus-natural line again, and I traced it through the sidewalk cases at /news/minnesota-sidewalk-snow-shoveling-liability-abutting-owner/. A tree is nature. What you build to throw water, ice, or debris onto the neighbor isn’t. When water rather than wood is the fight between neighbors, that’s at /news/minnesota-surface-water-drainage-disputes/.

Wind is nobody’s fault. What your neighbor knew about his tree, and what you do with a chainsaw the morning after, can be.

Madgett Law, LLC

Madgett Law, LLC handles Minnesota tree and boundary disputes between neighbors, including § 561.04 treble-damages claims, nuisance claims over encroaching trees, and the disputes that come out of property-insurance claims when an insurer and a homeowner can’t agree. If a neighbor’s tree has damaged your property, or you’re the neighbor being blamed, read about our general litigation practice, then send us a message.

Sources: Minn. Stat. § 429.101, subd. 1(a)(3) (removal or elimination of public health or safety hazards from private property), subd. 1(a)(6) (treatment and removal of insect-infested or diseased trees on private property), subd. 1(a)(5) (trimming, care, and removal of unsound trees from any street), subd. 1(b) (primary responsibility on owner or occupant upon notice, except street sprinkling or other dust treatment, alley repair, tree trimming, care, and removal, or street lighting); Minn. Stat. § 561.04 (treble damages for cutting or injuring a tree on the land of another; single damages where casual or involuntary or on probable cause to believe the land was the defendant’s or that of the person in whose service or by whose direction the act was done); Hannem v. Pence, 40 Minn. 127, 130 (1889) (no right to construct a roof that discharges water, ice, or snow on a neighbor’s land that would not naturally fall there); Holmberg v. Bergin, 285 Minn. 250, 252, 254, 256, 257 (1969) (Minneapolis elm about 15 inches from the line; boundary-line tree owners as tenants in common; trunk on the line not enough; intention, acquiescence, agreement, or joint planting; self-help to the property line allowed as something that “may be true,” not held); Henry v. State, 406 N.W.2d 608, 610–12 (Minn. Ct. App. 1987), review denied (Minn. Aug. 12, 1987) (45 mph storm; decayed limb not seen from the ground; summary judgment for the State under the outdoor-recreation immunity); Domagala v. Rolland, 805 N.W.2d 14, 23–24 (Minn. 2011) (general duty when the defendant’s own conduct creates a foreseeable risk; duty to protect against risks created by someone other than the defendant only in a special relationship; misfeasance and nonfeasance). This article is general information about Minnesota law, not legal advice. Reading it does not create an attorney–client relationship, and no outcome is promised or implied.

Get new guides by email

Plain-English guides to Minnesota law, sent when a new one is written. No schedule, nothing for sale.

Used only to send these guides. Unsubscribe from any email. This is attorney advertising — subscribing does not create an attorney–client relationship.

← All news & articles