What a fall zone is, and why it kills rooftop candidates in dense search rings

A city rooftop with antennas and relay towers against a clear sky at sunset.

A fall zone is the ground area a structure could occupy if it came down, and every jurisdiction that permits towers wants that area controlled before a permit gets issued. For a self-support lattice tower or monopole, engineers usually certify the structure to collapse within a defined radius, often the full height of the structure measured from the base, sometimes less for monopoles designed with a breakpoint. Guyed towers need a bigger zone, because the guy wires and anchor points push the collapse radius well past the mast itself.

That radius has to sit on land you control, lease, or hold an easement over, not a public sidewalk, not a neighbor's parking lot, not a right-of-way the DOT hasn't signed off on. If the fall zone crosses onto land you don't control, the site doesn't get built, no matter how good the RF numbers look.

Why rooftops in tight search rings run into this first

Ground-mount parcels in a rural search ring usually have room to spare. You draw the radius, it lands inside the fence line, done. Dense urban and suburban search rings are a different problem. The rooftops that show up as candidates are almost always hemmed in on every side, sidewalk out front, alley behind, an adjacent building sharing a property line six feet from the parapet.

The fall zone math for a rooftop installation is smaller than for a 150-foot lattice tower. You're usually looking at a setback from the roof edge for a monopole, guyed whip, or platform-mounted array, not a radius equal to building height. But it still has to clear the same obstacles: no spillover onto public right-of-way below, no encroachment onto a neighbor's roof or parcel without their sign-off, and in a lot of municipalities, no fall path over a sidewalk where people walk every day.

On a satellite basemap, a rooftop candidate looks fine. It's the right height, it sits near the search ring centroid, the roof reads flat and clear in the imagery. What the basemap doesn't show is that the parapet sits four feet from the edge, the mechanical penthouse eats the only usable corner, and the adjacent building owner has no reason to grant an easement for a fall zone that benefits a carrier they have no lease with. That's the kind of thing a field crew finds on the site walk, after the drive, after the ladder, after the day is gone.

Rooftop versus ground-mount, side by side

Ground-mount fall zone requirements are mostly a function of structure height and type: lattice and monopole collapse radius, guy anchor spread for guyed towers, plus whatever buffer the jurisdiction's zoning code adds on top of the engineer's certification. The land either has the room or it doesn't, and that's usually visible from a parcel map before anyone drives out.

Rooftop fall zone requirements fold in the building itself. Parapet height and setback. Structural load path to the roof deck. Access routes for install and maintenance crews. Sightline clearance to adjacent rooftops and towers that might sit in the beam path. A rooftop that clears height and RF line-of-sight can still get ruled out because there's no legal fall zone to put a mount in, especially on a packed block where every adjacent parcel has its own owner and its own idea about what it's willing to sign.

That gap between what a basemap shows and what a roof actually has room for is why screening a search ring by eye sends crews to sites that were never going to pencil. Rooftop Site Selection runs candidate structures through VHR imagery and photogrammetry before the site walk, flagging usable height, roof access, and clearance figures per structure so the crew gets sent to roofs that still have a fall zone to stand on.

If fall zones are what's killing your rooftop candidates on the back end, it's worth ruling them out before the first drive.

Start a pilot

Back to the blog