Blog
Field notes: the hop that passed its flyover and failed six weeks later

A planner I know keeps a folder of hops that failed between flyovers. Not because anyone asked her to. She started it after the third time a site that had cleared its annual pass in March was back on the fault list by September, and she wanted to know if there was a pattern or if she was just unlucky.
There's a pattern.
The flyover tells you what the canopy looked like on the day the satellite passed overhead. That's it. It's an honest snapshot, not a forecast. A hop can clear its Fresnel clearance envelope with margin to spare in early spring and still be the one that goes down six weeks later, because six weeks in late spring is exactly when a lot of species do their growing. Cottonwood, poplar, some of the faster conifers in a wet year. A branch that was eight feet under the envelope in March doesn't need much of a push to start clipping it by June.
What makes this one sting more than a normal outage is the order of events. The annual pass said clear. Then signal degradation shows up as a slow BER creep that nobody notices until it crosses a threshold, and by the time it does, you're not scheduling a trim, you're dispatching on a fault ticket with a customer SLA clock already running. The crew drives out, climbs the tower or walks the right-of-way, and finds a limb swaying into the path on windy days and settling back when it's calm, which is exactly the kind of thing that looks fine from five hundred feet up and isn't fine from the antenna's point of view.
The planner's folder had a second thing in common across most of the entries, once she looked closely. The hops that failed early all had fast-growing stock nearby, regardless of how much clearance they'd shown at flyover time. A hop sitting at four meters of margin over slow-growing pine can coast most of the year. A hop sitting at the same four meters over young hardwood in good soil can burn through that margin before the leaves are even fully out, because deciduous growth in a wet spring doesn't read the calendar the way a maintenance schedule does.
None of this is an argument against annual cadence. Once a year is still the right interval for most links, most terrain, most budgets. It's an argument for treating the report as a starting point for judgment rather than a pass/fail stamp. A hop with six inches of clearance and hemlock underneath deserves a different trim schedule than a hop with six inches of clearance and alder underneath, even though the flyover numbers look identical on the day. The species matters as much as the measurement, and the measurement is only as good as how recently it was taken relative to how fast things are growing back.
Build margin into the clearance envelope on purpose, sized to the species growing underneath each span. A span under young hardwood needs a bigger buffer than a span under mature pine, even if this year's canopy-height reading looks the same on both. If a stretch of a hop runs through young hardwood with a short rotation, trim it earlier than the flyover technically requires. Don't wait for the number to go negative, because by the time it does, you're not looking at a maintenance item anymore, you're looking at a fault ticket and a crew that has to drop everything else on the schedule.
The planner closed her folder eventually, once the pattern stopped being interesting and started just being how she scoped trim priority every year. She pulls the per-link report, checks which spans sit over fast growers, and moves those to the front of the trim queue regardless of how much raw clearance the flyover showed. It just requires treating the canopy-height data as a starting point for scoping the trim queue each year, read fresh rather than filed away. Link Vegetation Monitor builds that baseline once a year, flagging where canopy is closing in on your Fresnel zone so the trim gets scheduled before the hop does.
If a hop on your network has ever cleared its last survey and gone down anyway, it's worth putting your next pass on the calendar now rather than after the next fault ticket.