Applying for certification for Tree Campus involves a very enjoyable day of taking stock of the previous year. They ask about tree plantings, removals, dollars spent, volunteer hours, and community service projects. During a terribly boring snowless winter, it was nice to sit down and revel in our accomplishments during the previous growing season.
2011 was a banner year for tree planting. With the Forest renovation, the CFA renovation, our normal tree planting program, and the Atwater Turf Battle construction, Middlebury planted nearly 100 trees on campus this year.
We’ve had to remove some too. Storms and hazard tree removals are the most common culprits, although occasionally construction takes it’s toll as well. (It’s this reason I get lots of input from many people before planting, including managers in Facilities and the Master Plan Implementation Committee.) This year 22 trees have been removed.
So our Tree Karma score for 2011 is a very healthy 4 1/2 trees planted for every one removed.
Informally we try to plant 2 trees for every one removed. Our six year karma average is 3.8 trees planted for each removed. I got asked the other day what my favorite trees planted this year were, and thought it was either the Arbor Day planting, the large trees planted around Ross Commons, or maybe the rare trees planted to the west of Munroe, including a Stewartia, a variegated Tulip tree, and a rare yellow Magnolia. Or maybe the disease resistant elm in Adirondack Circle. But how can I single out one child over another?
We’re planting this spring too, mostly locally grown trees, in various locations all over campus. There is a method to our madness, we don’t just randomly plunk trees down all willy-nilly. One example is this year’s Arbor Day planting, just north of Battell. That awkward little triangle of grass lets Battell Beach lose it’s structure on that corner, and the space of the beach bleeds into the quad in front of La Chateau. The trees planted there will form a wall of sorts, segregating two spaces, and probably extending the usable lounging space of the edge of the beach.
(Not making any sense, am I? The next good beach day, go look at where people are laying out on Battell Beach. The southeast corner, down by Forest hall, along the southern edge, near the Forest hall sidewalk and some pretty spectacular ash and beech trees, or along the base of the slope that heads up to Pearson hall. Think about all those spaces. Psycologically, they are all protected–your back is up against a building, or a line of trees, or a slope. The northeast corner, near Chateau? No wall, no back, just open space across the sidewalk. Almost no one sits there, preferring instead to be near the line of spruces on the north end of the beach.)
Other places trees get planted are near trees that are dying, albiet slowly. I don’t like removing trees, and it makes me feel better to know when I do remove a tree I’ve already got it’s replacement planted and well established nearby. Look for some new trees near the Davis Family Library for this reason.
And by all means, join us today at 1 to plant some more-north of Battell Hall. We’ll allow you to get dirty.
Anyone around this summer, or past readers of this blog, will remember a large thunderstorm that ripped through Middlebury two days after Independence Day. Several trees were struck by lightning, which I wrote about after the storm.
The largest tree struck was the Norway spruce in the Main Quad, one of the ones remaining after we removed part of the line. I wrote this summer how the tree was struck at the top, and exhibited a spiral shaped scar all the way down the trunk, exiting at the root flare. We didn’t know if the tree was going to make it or not, but had hopes.
It’s not the voltage that kills trees, but the water. Over 100 million volts strikes the tree, but it is the water heating quickly turning to explosive steam that causes failures. (Another blog post, on a lightning stuck Ginkgo, has much more detail) Damage in trees can be tricky, often with the worst of the damage unseen.
There was damage seen immediately. Long strips of bark went flying across the quad, and a scar opened up, spiral shaped, following the grain of the wood down the trunk. The high sap content of spruce makes it susceptible to such long scars.
I’d been worried about this tree all summer, and was watching it closely. All the limbs near the scar started to die, and the color of the remaining ones seemed a little off, but still green.
During a closer hazard evaluation this summer I discovered two things, one bad, the other worse. The first was the size of the scar, and while this shouldn’t have surprised me, it did.
The scar that formed in the summer seemed minimal. While very long, it only seemed an inch or so wide.
Scar in summer
The bark hid quite a bit of damage, and another small crack that wasn’t even open this summer showed another major wound. Peeling away at the wound showed extensive damage, much larger than we’d first thought. Overall, it seems about 1/3 of the sapwood (the live wood beneath the bark that conducts water and nutrients) around the trunk has died, severely compromising the tree.
I’ve seen trees limp along with scars like this for many years, most often in a forest setting. Trees in communities are connected in several ways, relying on each other for support and nutrients. They also tend to be the best trees for the site, adapted to soil and weather conditions. Trees in an urban or landscape setting are under more stress, either from a singular status in the landscape, more exposed to wind by themselves, or stress from poor soil conditions its genetics just can’t handle gracefully.
This fall was a good one for fungus, with cool moist conditions. The base of this spruce showed a colony of fungi following along one of the major roots of the tree. Later that same month the same fungus appeared following a different root. This indicates a root rot, a type of fungus eating away at the roots of the tree.
I’ve spoken with an arborist friend of mine who suggests immediate removal. He’s seen similar cases, where trees exhibiting root rot like this suffer from wind throw, heaving over in a storm. The clay soils of our quad make this species very susceptible to this, spruce not being a deep rooted tree to begin with, in clay soils even more so.
While I like this tree quite a bit, the chance this tree could suffer a catastophic failure in such a busy location on campus is too much of a chance to take. The remaining tree, the large Norway spruce with the interesting trunk, will remain.
Like most years, the landscape department takes advantage of the upcoming holiday break to do some tree removals. Not that we are doing anything under the cover of darkness-it’s more like we don’t want to break the solitude of campus with the cacaphony of chainsaws and tree chippers, not to mention the lack of stress we have when not having to do hazardous work with pedestrians walking around us.
Like last year, we’re working off of a hazardous tree list we’ve kept for several years now. Each year, the hazardous trees are inspected in the early fall, the best time to observe stress in the plant. We’re getting toward the end of the list of hazards that must be removed, as this year we’ve selected 6 trees that for reasons described below must be removed.
Actually, 7 trees, but one is sad and important enough to warrant it’s own post later in the week.
The first tree on the list is a big one, a Norway maple north of Starr/Axinn. Like I’ve written previously, this tree is held together by a web of cables up in the crown, two complete systems. The first set is a group of three cables holding the main scaffolds together, and the second set is a complete ring around the canopy. Like we’ve seen in the Black Willow that failed by Battell, failure of one of these limbs can compromise the rest of the cable system, and lead to total failure. For this reason cable systems should be inspected yearly, preferably whilst up in the crown of the tree.
This tree has been declining in health for the past several years.. Notice the greatly thinning canopy in the following pictures, with the interval between last year and this being by far the greatest loss.
Canopy fall 2006Canopy fall 2010Canopy fall 2011
The cabling systems were originally installed to protect against failure in the main trunk. Norway maples, though, have a life span, one that is quite a bit shorter than I’d thought, and this tree has reached the end of it’s life. Over 75% of the crown was dead wood, with hollow scaffold branches held up only by cable. Most worrisome was the appearance of several types of fungi, indicating rotten wood both in the trunk and in the root system. While I hate to see such a large tree go, we can’t risk failure in an area so heavily trafficked.
The next tree on the list is another large one, a Silver maple by the Davis Family Library.
Silver maples are poor compartmentalizers, meaning any wounds they suffer sit and rot, further decay going up the stem and into the trunk. This tree has a major defect at the attachment of the main scaffolds, and hollow limbs on two of them. This tree had a hanging branch several years ago, and I climbed up there on rope to remove it. After ascending, I noticed the branch I was tied into was completely hollow, an empty tube the length of the branch. I didn’t stay up long.
After any major windstorm I would always look towards this tree on my drive into work to see if it was still standing. The crack shown above has opened up in the last year.
Another Norway maple in need of removal is next to Centeno, another Norway at the end of it’s life. This tree, like the other, has poor scaffold attachments at the base, and suffers from major cavities with rot. The crown has also suffered major decline in the preceding year, losing much of it’s foliage.
Centeno maple 2010Centeno Norway 2011
The rot in the trunk holds water, and is actually deep, over 1 foot. Note how, typical of Norways, much of the leaf surface is on the ends of the branch, and therefore much of the weight is as well. This raises a red flag, as high wind events cantilever the branch, with the foliage acting like a sail.
At the top of the stairs leading to the east side of Gifford is a Black Cherry tree, leaning towards the stairs and a nearby light pole.
Lean in a tree towards a target is always troublesome, or at the least worthy of a second, closer look. This tree suffers from a cavity at the root flare in the direction of the lean, indicating a weakened or even missing root system in the potential failure direction.
The last two trees on this removal list are both Sugar maples, which, given the percentage of Sugars on campus, is hardly surprising. The first tree doesn’t really have an obvious cause of death, but is nearly dead nonetheless. It’s located up at the tailgate area, near Route 30.
The final sugar to remove is located up by Hepburn, and to be honest I didn’t really want to see this one go. In fact, it probably should have been removed several years ago, when its defect was first noticed. Students in my winter term class will recognize it, and the tree is prominent in all of my tree tours. Rarely do you see such a concrete example of girdling roots causing an untimely death.
Nobody ever said trees were terribly intellegent. This tree grew several roots that wrapped around the root flare, so as they grew the tree was slowly strangling itself.
Water couldn’t go up the trunk, nor nutrients down. It showed all the classic symptoms of root girdling over the last several years. First the top started to die back, as the very upper reaches of the tree starved. Next the side of the tree with the girdling died back, followed by major sections of the trunk. Finally the entire tree itself starved as it tried to reprioritize, but without sufficent water and nutrient flow just couldn’t retrench to live out its final days the way many mature trees do.
I’m compiling our Tree Karma score for this year as part of our Tree Campus re-application, but am fairly confident we’ve planted many, many more trees than we’ve removed, even with all the freak storms this summer. Feel free to contact me with further questions or concerns you may have.
You must be logged in to post a comment.