The rules behind a report matter as much as the report itself. This orientation points to current primary text and explains how it frames the data shown in the incident index, without presenting editorial shorthand as legal advice. 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 |
|---|---|---|
| 49 CFR Part 190 | PHMSA procedural regulations | Enforcement and procedural context |
| 49 CFR Part 191 | Gas and LNG reporting | Gas-system reporting obligations |
| 49 CFR Part 195 | Hazardous-liquid reporting | Liquid and carbon dioxide reporting |
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.