Once a year, pipeline operators owe the federal Pipeline and Hazardous Materials Safety Administration a census of the pipe they run. The Form 7100 series is how that census is filed, with separate forms for gas transmission and gathering, gas distribution, and other regulated systems. The report is not about a single event; it is a portrait of the whole system: how many miles of pipe, of what material, at what diameter, operating at what pressure, and how many facilities and services hang off it, all as of the end of the reporting year. Assembling that portrait from scratch every year is a substantial asset census when the data lives in scattered maps and spreadsheets, but it becomes a straightforward export when the operator keeps a single system of record for its segments. This page covers what the annual report demands, the mid-June deadline, and why a maintained asset database turns the filing from a manual count into a query.
PHMSA annual report in one line: The PHMSA annual report, filed on the Form 7100 series through PHMSA's online portal, is a yearly inventory of a pipeline operator's system: total mileage broken down by material, diameter, decade of installation, and operating pressure, along with counts of facilities, services, and other assets as of year-end. Gas transmission and gathering operators file by June 15 for the prior calendar year, using the appropriate form for their system type. When an operator maintains a current system of record for its pipeline segments, the report is essentially a data export rather than a fresh asset census.
The core of the annual report is mileage, but not a single mileage number. PHMSA wants the system broken down along several axes at once: miles by pipe material such as steel, plastic, or cast iron; miles by diameter class; miles by the decade the pipe was installed; and miles by operating pressure or class location. The same mile of pipe is counted in several of these breakdowns simultaneously, so the totals have to reconcile across categories. This structure exists because the agency uses the data to understand the age, composition, and risk profile of the national pipeline network, not just its size.
Beyond mileage, the report inventories the facilities and features attached to the system. Depending on the form, that can include the number of services, meters, regulator stations, compressor or pumping facilities, and other components, along with information about the operator's integrity management and, for some systems, leak and repair activity. The gas distribution form in particular carries detailed counts of services and mains by material, reflecting the distribution system's structure of many small services rather than long transmission runs.
What makes the report demanding is not any single field but the requirement that all of it be current and internally consistent as of the end of the reporting year. Pipe added, retired, replaced, or re-rated during the year all has to be reflected, and the material and pressure breakdowns have to sum to the same totals. An operator whose asset data is fragmented across as-built drawings, GIS layers, and maintenance records has to reconcile those sources every year to produce numbers that add up, which is where the annual report consumes the most effort.
The annual report is submitted electronically through PHMSA's online reporting portal, where the operator selects the correct form for its system and enters or uploads the required data. The forms differ by system type because a gas transmission and gathering system, a gas distribution system, and a hazardous liquid system have very different structures and therefore very different data fields. An operator that runs more than one type of system files more than one report, each on its own form.
For gas transmission and gathering operators, the annual report is due June 15 covering the prior calendar year, giving operators the first months of the year to close out and reconcile the previous year's data before filing. The mid-year deadline is generous compared with some filings, but it can lull an operator into leaving the asset reconciliation until spring, at which point rebuilding an accurate year-end snapshot from a year of scattered changes becomes the bottleneck. The deadline is not the hard part; the accurate as-of-year-end data is.
Because the report is a snapshot as of December 31 rather than a running log, the operator has to be able to reconstruct exactly what the system looked like at that instant, including any changes made late in the year. This is straightforward for an operator whose asset records are updated as changes happen and impossible to do cleanly for one whose records lag reality. The difference between a filing that takes days and one that takes months usually comes down to whether the operator maintained its asset data through the year or has to reconstruct it in the spring.
The reason the annual report feels like an asset census for many operators is that the authoritative picture of the system does not live in one place. Mileage is in a GIS layer, materials and install dates are in as-built records, operating pressures are in engineering files, and recent changes are in maintenance logs that have not yet been folded back into the master. Producing the report means gathering all of that, reconciling the inevitable discrepancies, and rolling it up into the required breakdowns, which is slow and error-prone precisely because the data is scattered.
When the operator maintains a single system of record where every pipeline segment carries its material, diameter, install date, operating pressure, and status, and where changes are captured as they are made, the annual report becomes a set of queries against that record. Miles by material is a rollup. Miles by decade is a rollup. Facility counts are counts. The reconciliation that consumes the most effort disappears because the breakdowns are all views of the same maintained data, guaranteed to sum to the same totals because they come from one source. The census turns into an export.
A monitoring and asset platform reinforces this by keeping the operating side of the record honest, not just the physical inventory. Where a cloud SCADA platform such as Merobix trends the pressures at which segments actually run and logs the field changes made to the system, the operating-pressure and class breakdowns the report needs are grounded in observed data rather than in engineering assumptions that may be years stale. The same maintained record that answers the annual mileage report also feeds integrity management and day-to-day operations, so the effort of keeping it current is repaid across many uses, with the annual filing being one of the easier ones once the record exists.
The gas transmission and gathering annual report on the Form 7100 series is due June 15 covering the prior calendar year, filed electronically through PHMSA's online reporting portal. Operators running more than one type of system file a separate report on the appropriate form for each. The mid-year deadline gives time to reconcile the previous year's data, though the accurate year-end snapshot is usually the real bottleneck rather than the date.
It requires a system inventory as of year-end: total mileage broken down by pipe material, diameter, decade of installation, and operating pressure, plus counts of facilities, services, and other components depending on the form. The same miles are counted across several breakdowns that all have to reconcile to the same totals. Changes made during the year, such as pipe added, retired, replaced, or re-rated, must be reflected in the snapshot.
Because for many operators the authoritative picture of the system is scattered across GIS layers, as-built drawings, engineering files, and maintenance logs, so producing the report means gathering and reconciling all of them each year. When an operator instead keeps a single system of record with every segment's material, size, age, and pressure kept current, the report becomes a set of rollup queries rather than a fresh count, and the reconciliation effort largely disappears.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.