What counts as unauthorized excavation near a pipeline?
Ask three different damage prevention coordinators where "unauthorized excavation" starts and you'll get three slightly different answers, because the term covers a lot of ground, literally. But the core of it is simple: any mechanized digging, boring, or grading inside a pipeline right-of-way that happened without a valid locate ticket and without the operator's knowledge counts. It doesn't matter whether the person doing it knew a pipeline was there.
The locate ticket is the dividing line
In most states, "authorized" excavation means someone called 811 (or the regional one-call center), got a ticket number, and the operator either marked the line or granted clearance before the first bucket of dirt moved. Everything else, a contractor digging a footing, a farmer deep-ripping a field, a neighboring utility boring a new service line, is unauthorized if it falls inside the tolerance zone and no ticket exists for it.
That tolerance zone is usually a fixed distance either side of the marked centerline, often 18 to 24 inches depending on state law, inside which hand-exposure or other precautions apply. Mechanized equipment working inside that zone without a ticket is the textbook case regulators and CGA's DIRT report are built around. In practice, though, right-of-way teams track a wider band than the legal tolerance zone, because the things that turn into a strike rarely start as digging right on top of the pipe.
What this looks like on the ground
Unauthorized excavation near a pipeline is rarely a crew with an excavator standing on the centerline. It's usually something upstream of that:
- A new building pad or shed foundation going in near the ROW with no ticket on file
- Farm tiling or subsoiling crossing the corridor at digging depths below the marked line
- A fence line replacement with post holes driven deeper than expected
- A road crossing or driveway cut that clips the edge of the easement
- A third-party utility (fiber, water, drain) boring or trenching through without coordinating a joint locate
- Pond or ditch excavation that encroaches on the corridor from an adjacent parcel
None of these show up as a "dig-in" on day one. They show up as a new pile of spoil, a piece of equipment parked where it shouldn't be, or a trench line that wasn't there two weeks ago. By the time a crew contacts the pipe, the unauthorized excavation has usually been underway for days, sometimes weeks, and patrol only catches it because they happened to drive that mile that week.
Why "unauthorized" doesn't mean malicious
A landowner who didn't know the easement ran where it does. A contractor working off an old plat. A utility crew that pulled a ticket for the wrong segment. That's what lands in most incident logs, not somebody deliberately digging into a known pipeline.
The regulatory definition doesn't care about intent: an excavation inside the ROW without proper notification and clearance is unauthorized whether it's willful or just a missed call to one-call. A pile of fresh dirt caught the week it goes in costs a phone call and a stop-work notice. The same dig caught after the equipment's gone and the trench is backfilled is how coating damage and ruptured lines end up in the DIRT numbers.
What most operators are fighting is a visibility gap, not a legal one. Foot and aerial patrol cover a corridor on a schedule, and a lot can get built, dug, or crossed in the days between passes. That's the window where unauthorized excavation actually turns into a dig-in: the activity started, nobody flagged it, and the next scheduled patrol is still a week out.
Closing that window is the whole idea behind Pipeline Encroachment: a biweekly flyover log that flags new structures, fresh excavation, and new road or utility crossings inside the corridor, indexed to milepost, so your patrol and landowner outreach teams aren't finding out about a dig two weeks after the equipment left. If your ROW team is still relying on the next scheduled drive-by to catch what's new in the corridor, it's worth seeing what a mile-by-mile log between patrols looks like.