Pipeline crossing agreements: what they cover and who needs one
A pipeline crossing agreement is the paperwork a third party signs with the operator before they cross, parallel, or otherwise work inside the pipeline's right-of-way. It spells out how the work has to get done around a buried asset they didn't build and don't want to hit: minimum cover depth, casing requirements if it's a bore, hand-dig or pothole rules within so many feet of the line, insurance and bonding, and who's on the hook if something goes wrong.
Not every utility that touches your corridor needs one. A line running near the ROW without crossing it usually falls under a different kind of agreement, or none at all, as long as it stays outside the easement. The crossing agreement gets triggered the moment a third party's line, road, drainage structure, or fence actually enters or crosses the right-of-way.
Who needs one
The usual cast: another utility (gas, water, fiber, electric) boring under the line, a county or DOT widening a road that crosses the ROW, a developer running storm drain across the easement, a landowner putting in a field tile or driveway culvert across it.
Each of those parties is supposed to come to the operator's ROW department first, get the crossing specs, and sign before any equipment shows up. In practice, a fair number start digging first and call later. Some never call at all. That's less a legal failure than a damage-prevention one, and it's the piece that lands on the integrity team's desk.
Crossing agreement vs. encroachment agreement
A crossing agreement covers planned work, crossing or entering the ROW with the operator's advance knowledge and sign-off: specs, insurance, inspection requirements, usually an exhibit tied to station numbers.
An encroachment agreement covers something already built or installed in the ROW, discovered after the fact. A fence line crept in. A shed got built over the easement. A prior crossing never got documented and only turns up during a patrol or a survey. It's retroactive paperwork to formalize something that should have been a crossing agreement from day one, plus whatever remediation the operator now requires.
A one-call or 811 locate ticket is neither of these. It's a separate step ahead of any excavation, agreement or no agreement, and it doesn't substitute for the ROW paperwork on a genuine crossing.
Where it breaks down in the field
Most crossing agreements are an engineering and legal problem until something goes wrong, and then they're an integrity problem. The agreement can be signed, the specs correct on paper, and the crew on site still digs deeper than the exhibit allows, runs equipment past the marked limits, or shows up weeks ahead of the notified start date. Agreements that were never signed in the first place are worse: a contractor on a county road job, or a landowner putting in a culvert, with no ticket pulled, no agreement on file, no call made. Machinery just appears on the right-of-way one morning.
Either way, the first the integrity team usually hears about it is a landowner's phone call, a locator stumbling onto it during an unrelated ticket, or a patrol flight weeks after the equipment arrived. By then the trench is often already open.
That gap, between equipment showing up and someone on the operator side finding out, is the piece Pipeline Threat Alert is built to close. A dated, weekly briefing per segment flags machinery and material laydown near the line from VHR imagery, so an inspector can be sent while the crew and equipment are still on site, signed agreement or not.
A crossing agreement process can be airtight on paper and the integrity team can still learn about third-party work from a phone call weeks after the fact. That's a detection gap, and it sits underneath the paperwork no matter how solid the paperwork is. Worth a look if you'd rather know before the complaint than after.