What counts as third-party damage under PHMSA reporting rules
When a backhoe hits your line and nothing leaks, do you have to report it? When a contractor's auger comes close enough to gouge the coating but the pipe holds pressure, does that count? These questions come up in the integrity office every time a third-party incident report lands on someone's desk, and the answer depends on reading PHMSA's definitions carefully instead of guessing.
What PHMSA means by "third-party damage"
Under Part 191 and Part 195 reporting requirements, PHMSA classifies damage by cause, not by outcome. "Third party" means the damage came from an outside party unrelated to pipeline operations: an excavation contractor, a farmer, a utility crew, a developer, anyone digging, boring, or running equipment near the right-of-way who isn't your operator or your contracted crew working under your own one-call ticket. That's distinct from "operator excavation damage," which covers hits caused by your own people or your own hired crew.
The classification matters because it feeds the root-cause coding on the incident report, and third-party damage is the category your damage prevention program exists specifically to catch before it turns into one.
When excavation contact triggers a report
Not every scrape or gouge is reportable. PHMSA's thresholds turn on consequence: a release of gas or hazardous liquid above the applicable volume, a fatality or injury requiring hospitalization, an explosion or fire, or property damage above the reporting threshold. A contractor's bucket that nicks the coating without breaching the pipe wall, with no release, isn't a reportable incident under 191 or 195, even though it's a damage-prevention event worth logging internally.
That gap, between "near miss worth tracking" and "PHMSA-reportable incident," is where most of the paperwork confusion lives. Your program should be capturing every contact, every call-before-you-dig violation, every piece of equipment found working inside the right-of-way, whether or not it ever rises to a reportable release. PHMSA's definitions set the floor for what you must report to them. They don't set the floor for what you should be watching on your own ground.
The classification call usually happens after the fact
What matters for how you run the yard is this: by the time anyone is filling out a PHMSA form, the digging already happened. The call between third-party and operator-caused, reportable and non-reportable, gets made by looking backward at a hole that's already backfilled and a crew that's already gone. An inspector who gets there while the excavator is still running the ditch can confirm depth of cover, document exposed pipe, and settle the one-call status while the crew is still standing there, instead of reconstructing it from a landowner's phone call three days later.
That's the gap between how damage prevention programs are supposed to work and how most of them run day to day: reactive, built on someone noticing after the fact and calling it in. A locate ticket tells you where digging is authorized. It doesn't tell you where digging started, when the equipment showed up, or whether the contractor who pulled the ticket is the one doing the work.
Pipeline Threat Alert exists for that gap. It checks the ground over each segment weekly against VHR imagery and flags where machinery or material laydown has shown up near the right-of-way, so the integrity team gets a dated briefing while the equipment is still parked on site, not after the crew has moved on and the classification argument starts.
If your damage prevention metrics are built entirely on landowner calls and one-call audits, you're finding out about third-party activity after the ground's already been disturbed. Catching it while the machine is still there is a different job, and it's the one this site is built around.