Blog

Multipath fade vs vegetation fade: how to tell them apart on a link budget

Morning fog rolling over a forested ridge at sunrise.

A hop starts eating into fade margin and the first question is always the same: is this atmospheric, or is something growing into the path. Both show up as a drop in received signal level. Both can trip the same threshold alarm on the same radio. But they leave different fingerprints in the data you already have, and reading those correctly saves a truck roll to a tower that's fine as it stands.

What multipath fade looks like in the logs

Multipath fade comes from the atmosphere, not the terrain. Classic signature: it clusters in the early morning hours, often 2am to 6am local, when temperature inversions and still air let the atmosphere stratify into layers with different refractive indices. A reflected or refracted ray arrives out of phase with the direct ray and the two partially cancel.

A few tells that point here:

  • Events are short, seconds to a few minutes, and RSL snaps back once the layer breaks up with sunrise or a bit of wind.
  • It's seasonal in the predictable way ITU-R P.530 models it, worse in calm, humid, clear-sky conditions, worse over water or flat terrain, worse on longer hops.
  • There's no trend. Look at a month of RSL history and the baseline is flat; you just get occasional deep, fast dips superimposed on it.
  • It shows up across the whole path length and terrain type, regardless of which tower leg or azimuth sits near a known tree line.

If your fade events match that pattern, your link budget's existing multipath margin is doing its job, and the fix, if any, is antenna height or path geometry.

What vegetation fade looks like instead

Vegetation fade reads almost opposite. It builds over weeks or months as a growing season progresses, it doesn't snap back, and it correlates with wind and rain in a different way than multipath does.

Things to check:

  • Trend the RSL baseline over three to six months, not just the last alarm. Vegetation fade shows up as a slow downward drift in the floor, not isolated dips off a flat baseline.
  • Check for a flutter component on windy days. Leaves and branches moving in and out of the Fresnel zone add a fast, shallow ripple on top of the slower trend; multipath doesn't do this.
  • Look at seasonal leaf-out. If a hop with deciduous trees near the path degrades every summer and recovers every winter, that's foliage attenuation, not atmosphere.
  • Rain makes it worse faster than it should, because wet leaves attenuate more than dry ones. A fade event that's deeper than the rain fade model alone predicts is a hint something in the path is absorbing extra signal.
  • It's directional in a way multipath isn't. One specific point along the path, usually near one end where a tree line has grown up, is doing the damage. A path profile survey or an updated clearance check against that point will usually confirm it.

Confirming it before you dispatch a crew

A link budget alone can't fully separate the two causes. It tells you fade margin got consumed; it doesn't tell you why. What closes the gap is knowing what's actually standing in or near the Fresnel zone along that specific hop, which is a question the budget and the alarm log were never designed to answer. That's the piece an annual canopy-height pass against your clearance envelope fills in, so when a hop's RSL trend starts drifting, you can check the flagged encroachment points on that path instead of sending someone to walk the whole route or wait for a second fault ticket to confirm the pattern. If vegetation fade is the pattern you keep seeing, a per-link encroachment report tied to your actual Fresnel geometry is the faster way to confirm it and schedule the trim before the link degrades further.

← Back to the blog