A supplier sees cast iron miles in a gas operator’s annual report. The next move is tempting: call the operator and say those miles prove an urgent replacement need. The report supports a narrower and more useful conclusion. It describes a reported system at a year-end date. It does not identify a project, a purchase plan, or the condition of a particular main. PHMSA’s gas distribution annual report form shows the fields that create this distinction.
For equipment, software, and service suppliers, the report is a starting map. It can tell you which questions to ask and which public records to read next. It cannot substitute for an operator’s engineering assessment or procurement plan. That boundary makes the research more credible.
Start with the reporting unit
The form asks for an operator identification number, the operator’s name, its headquarters, the state, and the type of operator. The type choices include investor-owned, municipal, private, and cooperative. The report is tied to the system covered by that operator ID, so a familiar parent brand may not be the right unit for account work. Check the exact legal and operating name before you attach a report to a CRM record. PHMSA’s form makes these identifiers explicit.
Record the calendar year as well. A 2024 form is a description of the 2024 reporting period, not a live inventory. If an operator has sold assets, expanded, or changed its name since then, the old row still describes the old period. PHMSA keeps forms and instructions by reporting year. Use the instructions for the year you analyze rather than applying a later definition without checking.
Read the denominator before the count
Part B asks for miles of main and numbers of services by material. It also asks for main diameter and decade of installation. The 2024-and-beyond form includes an “unknown” installation period. That matters when a supplier tries to estimate the scale of a serviceable market. A material count without total system size, service count, and unknown-age share can create a false comparison between operators.
For example, two operators could report the same cast iron mileage. If one manages a much larger network, the same mileage has a different place in its system. Even that ratio is only context. It does not show which segments are scheduled, accessible, funded, or suitable for a specific method. A supplier of pipe, valves, locating tools, or GIS software should carry the figure into a research brief as a dated inventory observation, then look for a public replacement plan or a regulator filing.
Do not turn leak fields into a safety score
Part C reports leaks eliminated or repaired during the year, hazardous leaks within that set, and known system leaks scheduled for repair at year-end. It groups repaired leaks by cause and separates mains from services. These are different measures with different time meanings. The PHMSA instructions also exclude some non-hazardous leaks resolved by adjustment or tightening and specify how leaks on replaced segments are counted.
The instructions add an important comparison limit. An operator that repairs every leak when found and does not grade leaks can report equal values for total and hazardous repaired leaks. A supplier who treats that equality as proof of a worse system would misread the reporting convention. Similarly, a high repaired-leak count could reflect detection and repair activity as well as asset condition. The public form alone does not separate those explanations. PHMSA’s detailed reporting definitions should sit beside every interpretation.
Convert fields into questions
Make a short evidence table for each operator: year, operator ID, material mix, service count, unknown installation period, and the precise leak measure used. Add a source link to each entry. Then write two columns: “publicly observed” and “needs operator confirmation.” A useful question might be, “Does the replacement plan prioritize the reported cast iron inventory?” An unsupported statement would be, “The reported inventory will be replaced this year.”
Compare several years only after checking whether the form or instructions changed. The current form introduced more detailed excavation-damage root-cause categories for calendar year 2024 reporting, according to the form. A chart spanning that change needs a note; a newly visible category is not automatically a new field condition.
Use the report to prepare a specific, respectful discussion about scope and data needs. If your team needs help building an operator research brief with source dates and clear unknowns, discuss the proposed research scope with GasUtility.ai. The brief should guide discovery, not claim to grade operator safety or predict a bid.