Launch edition
Index architecture is live. Verified aggregates follow retained source snapshots.
The initial edition publishes the shared vocabulary, source routes and system boundaries first. Counts and rates will be added only after PipeMag can retain the file, checksum it, map its fields and reproduce the displayed result.
| View | Source system | What remains distinct |
|---|---|---|
| Gas distribution | PHMSA incident data, 2010–present | Incident definition and annual report fields |
| Transmission & gathering | PHMSA incident data, 2010–present | Transmission, gathering and facility scope |
| Hazardous liquid | PHMSA accident data, 2010–present | Accident threshold and release fields |
| LNG | PHMSA incident data, 2011–present | Facility context is not a mileage proxy |
What readers can verify now
PHMSA explains that incident files contain a data file and a field-description file. PipeMag will retain both, keep reported and normalized values side by side, and display a link to the originating official source. The methodology records the rules before numbers are published.
Use the failure-cause guide to understand why cause labels cannot always be pooled. For background on denominators, read U.S. pipeline mileage.
Official dataset collection is required before PipeMag displays an aggregate. This edition intentionally shows no incident total, rate, ranking or selected case match.
Readers who work through the Pipeline Incident Database will notice that not every recorded failure involves crude oil or natural gas. Mining operators move mineral waste as a dense fluid, and the same questions about pressure, corrosion and public records apply to that service. For a parallel treatment of how solids are carried in a carrier liquid, how water is recovered, and how a deposition plan is checked against published standards, see tailings slurry transport. The definitions and data checks used here follow the same principle: name the source, state the unit, and let the record speak.
Incident records answer what happened on a given pipeline segment, but they stop at the edge of the operator's system. Questions about who reads the meter, who bills the customer, and who responds when service fails sit with a different set of parties. For readers who need that split explained, the companion page on distribution and supply roles sets out how responsibility is divided between the operator running a local energy network and the company selling the energy, and how a customer identifies the right party and escalation route.
The same discipline applies elsewhere on this desk. A pipeline incident record is only as useful as the definitions behind it, and a lighting specification is read the same way: a figure means nothing until the unit, the test condition and the label are named. Readers who want that method worked through in another domain can start with lumens and watts, which sets out how a product label is read and what it does and does not establish. The habit carries across both pages: check the source, check the unit, then draw the conclusion.