Official reporting systems can look alike at a distance, but their definitions and thresholds are not interchangeable. This guide keeps the source boundary visible, then shows where a reader can usefully connect the incident index with annual mileage context. This article is prepared by the PipeMag Editorial Desk as part of the pipeline safety topic; continue with the pipeline glossary.
Read the record before the pattern
A source file can be revised, a reporting form can change, and a blank can mean something different from zero. Good technical reading starts with those constraints. It then asks whether the comparison is warranted, rather than forcing a clean-looking conclusion.
| View | Source system | What remains distinct |
|---|---|---|
| Reported field | Original dataset | Source value remains available |
| Normalized view | PipeMag index | Only compatible fields are grouped |
| Derived observation | Documented calculation | Method and denominator are disclosed |
What this page can and cannot establish
PipeMag does not use a single event, a single field or an isolated count to rank operators or declare safety performance. Readers can follow source links, inspect definitions, and use the data methodology to understand what will change when verified snapshots are refreshed.
For operational context, continue with inspection and pigging or the safety-regulations guide. Each route is short by design: the point is to find the next reliable question, not a false final answer.
Primary links are provided for verification. This page was reviewed on August 23, 2026; agency datasets may change after supplemental reporting.