For decades, large stretches of rural gas gathering pipe sat outside federal pipeline reporting altogether, treated as unregulated because of where they ran and how they were classified. A PHMSA rulemaking closed much of that gap by creating a category of regulated onshore gathering, including a set of lines designated Type C, and by extending annual reporting to them. For the operators of those lines, the change meant a pipeline network they had never had to report on federally suddenly owed the same kind of annual mileage and incident accounting that transmission systems had long filed. This page explains which previously unregulated gathering segments now fall under the reporting requirement, the scramble that created for operators who lacked a full picture of their own gathering footprint, and how mapping gathering assets into one platform makes the new annual report answerable.
Gas gathering annual report in one line: The PHMSA gas gathering annual report is a federal reporting obligation extended to regulated onshore gas gathering lines, including the newer Type C category, requiring operators to report annual mileage and incident information on gathering pipe that was previously outside federal reporting. It exists because a PHMSA rulemaking broadened the definition of regulated gathering to cover many rural segments that had never been reported. Answering it requires operators to know the mileage, material, diameter, and location of gathering lines many had never comprehensively mapped.
Gas gathering is the pipe that moves raw gas from wellheads to processing or to a transmission system, and historically much of it in rural areas was excluded from federal pipeline reporting because of location classifications that treated sparsely populated segments as lower risk. The PHMSA gathering rule reorganized this by defining regulated onshore gathering and creating designations, with Type C capturing a swath of previously unregulated lines based on diameter and operating conditions rather than only on population density. The effect was to pull rural gathering pipe that had never been federally reported into the reporting system.
The practical scope of the change surprised many operators because gathering footprints are large, old, and often poorly documented compared with transmission systems. Gathering lines were frequently built incrementally as fields developed, sometimes by predecessor companies, and the records for diameter, material, install date, and even precise routing can be incomplete. When the rule extended reporting to these lines, operators had to determine which of their gathering segments now met the Type C criteria, and answering even that threshold question required data many did not have readily assembled.
The distinction that matters for the report is which lines are in scope, and that turns on the classification criteria the rule sets rather than on whether a line was ever regulated before. An operator cannot answer the report without first mapping its gathering system against those criteria to sort regulated from unregulated segments. That classification exercise, more than the reporting itself, is what made the rule a compliance scramble: operators had to inventory pipe they had never had a federal reason to inventory before, simply to know what they now had to report on.
Once an operator knows which gathering lines are regulated, the annual report for them follows the pattern of PHMSA's other pipeline annual reports: mileage broken down by material, diameter, and operating characteristics, along with incident and, where applicable, integrity information for the regulated segments. The report is a snapshot of the regulated gathering system as of the reporting year, so it demands the same internally consistent breakdowns that reconcile across categories, applied to pipe that is often older and less documented than transmission.
Incident reporting is a particularly consequential piece for gathering, because these lines had not previously carried a federal incident-reporting obligation, so operators had to build the process for capturing and reporting incidents on segments they had run informally. An incident on a regulated gathering line now feeds the same federal accounting as one on transmission, which means operators need a way to recognize, log, and characterize incidents on gathering pipe against the reporting thresholds, something that did not exist for lines that had been unregulated.
The combination of a mileage census on poorly documented pipe and a new incident-reporting duty is what made the first cycles of the gathering annual report difficult. Neither piece is conceptually hard, but both depend on the operator having a current, complete inventory of its regulated gathering system and a live process for capturing events on it. Operators who had good gathering records adapted quickly; those whose gathering footprint lived in field knowledge and legacy maps faced a genuine data-assembly problem before they could even fill in the form.
The recurring theme in the gathering-report scramble is that operators could not report on what they had not mapped, so the durable solution is a single, maintained map of the gathering system that carries each segment's material, diameter, operating conditions, and regulatory classification. Once every gathering line is represented in one place with those attributes, the threshold question of which segments are Type C becomes a filter, and the mileage breakdowns the report needs become rollups against the mapped inventory rather than a fresh survey each year.
A monitoring and asset platform that already tracks gathering-system operations extends this from a static map to a living record. Where a cloud SCADA platform such as Merobix trends the pressures and flows on gathering lines and holds the segment inventory alongside them, the operating characteristics that feed the classification and the report are grounded in measured behavior, and changes to the gathering system as fields are developed or lines retired are captured as they happen. The map does not go stale between reporting cycles, so the operator is never reconstructing its gathering footprint from scratch.
The incident side benefits from the same consolidation. When events on gathering lines are logged in the same platform that holds the asset map and the operating data, an incident is captured against a specific, classified segment with its location and attributes already attached, which is exactly what the report and any follow-up investigation need. Bringing the asset inventory, the operating data, and the event log for gathering together in one place is what turns the new annual report from an annual scramble into a query, and it is the practical answer to a rule that regulated pipe many operators had never fully mapped.
Type C is a category of regulated onshore gas gathering created by PHMSA's gathering rule, capturing many rural gathering segments that had previously been outside federal reporting. The designation is based on characteristics such as diameter and operating conditions rather than only on how many people live nearby. Lines that meet the Type C criteria now carry annual reporting obligations they did not have before.
Because a PHMSA rulemaking broadened the definition of regulated onshore gathering, pulling rural gathering pipe that had long been treated as unregulated into the federal reporting system. Operators of those lines now owe annual mileage and incident reporting they never had to file before. The change surprised many because gathering footprints are large and often poorly documented compared with transmission systems.
Operators first had to determine which of their gathering segments met the new regulated criteria, and answering even that threshold question required a complete inventory of gathering pipe that many had never comprehensively mapped. Gathering lines are often old, built incrementally, and documented incompletely, so assembling accurate mileage, material, and location data was itself a major effort. On top of that, operators had to build an incident-reporting process for lines that had never carried one.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.