Operators of injection and disposal wells owe their regulator a yearly account of what went down each well and at what pressure, and in Texas that account is the Form H-10. It is a per-well summary that walks month by month through the volume injected and the highest surface pressure reached, so the agency can see whether a well stayed inside the limits its permit set. The report looks like a simple table, but every number in it is supposed to trace back to a real measurement made at the wellhead throughout the year. Keeping those measurements honest and continuous is what turns the annual filing from a stressful reconstruction into a routine export.
Form H-10 disposal report in one line: A Form H-10 is the annual report an injection or disposal well operator files with the Texas Railroad Commission, summarizing for each permitted well the volume injected in each of the twelve months and the maximum surface injection pressure observed. It confirms the well operated within its permitted volume and pressure limits and ties to the mechanical integrity testing that proves the well is not leaking. The report is per well, filed once a year, and expected to reflect measured injection rate and pressure data rather than estimates.
The core of a Form H-10 is a twelve-month table filled in separately for every injection or disposal well the operator holds a permit for. For each month the operator reports the total fluid volume injected, usually in barrels, and the maximum surface injection pressure the well reached during that month. Those two columns are the heart of the compliance question, because the injection permit sets a maximum allowable volume and a maximum allowable surface pressure, and the H-10 is where the operator demonstrates that neither ceiling was crossed. A month that shows pressure above the permitted limit is a red flag the agency will want explained, and a volume above the authorized rate is the same.
Beyond the volume and pressure table, the form captures the identity and status of the well, the injection interval or disposal zone, and the source of the injected fluid, whether it is produced saltwater, fluid for enhanced recovery, or something else the permit authorizes. It also intersects with mechanical integrity, because a disposal well is only allowed to keep operating if it has passed the required integrity testing on schedule, and the annual report is a natural checkpoint for confirming those tests are current. An operator who lets an integrity test lapse cannot honestly represent the well as compliant on the annual filing.
The reason the pressure column matters as much as the volume is that surface injection pressure is a proxy for what is happening in the formation. A permit limits pressure to keep injection from fracturing the confining rock and letting fluid migrate out of the disposal zone. Reporting the maximum pressure per month, rather than an average, is deliberate: the agency cares about the worst moment, because a single excursion above the fracture-related limit is the event that could compromise containment. This is why an operator who only logged pressure occasionally can struggle to defend the maximum figure, while one with continuous pressure history can point to exactly when the peak occurred and show it was within limits.
The traditional way the H-10 gets built is painful: someone gathers a year of paper gauge readings, hand-written tank tickets, and occasional pressure spot-checks, then reconstructs a monthly volume and guesses at the peak pressure from whatever was written down. That reconstruction is slow, error-prone, and hard to defend if the agency questions a number, because the underlying records are sparse and scattered. The whole exercise assumes the operator has been diligently recording injection rate and pressure by hand all year, which in practice is exactly where gaps creep in.
Continuous logging changes the character of the report entirely. When injection rate is measured by a flow meter that records to a data historian around the clock, the monthly injected volume is simply the integral of that rate over the month, computed automatically rather than reconstructed. When injection pressure and annulus pressure are logged continuously as well, the maximum surface pressure for any month is just the peak value the historian already holds, timestamped to the moment it occurred. The twelve-month table stops being a research project and becomes a query against data that was captured the whole time, which is both faster and far more defensible.
The annulus pressure signal deserves its own mention, because continuous logging of it does double duty. Annulus pressure between the tubing and the long string casing is one of the classic indicators of mechanical integrity: a stable annulus pressure suggests the tubing and packer are holding, while a rising or falling annulus can signal a leak that would fail an integrity test. Logging it continuously means the operator sees a developing integrity problem in the trend long before the scheduled test date, and the same historized record that feeds the H-10 volume and pressure columns also supports the integrity-test recordkeeping the well's continued operation depends on.
A disposal or injection well that is monitored through a SCADA system already produces almost everything the annual report needs as a byproduct of normal operation. The flow computer or RTU at the wellhead is reading injection rate, injection pressure, and annulus pressure continuously and pushing them to a cloud platform where the values are historized. The annual filing then draws on a full year of real, timestamped measurements rather than a folder of intermittent notes, and the per-well monthly rollups can be produced on demand instead of assembled under deadline pressure.
The compliance value of this goes beyond convenience at filing time. Because the permitted volume and pressure limits are known, a monitoring platform such as Merobix can alarm the moment injection pressure approaches or crosses the permitted maximum, so an excursion is caught and corrected in real time rather than discovered a year later when the report is being compiled. Catching a pressure limit breach while it is happening is the difference between a brief documented event and a violation that colors the entire annual filing. Continuous surveillance turns the permit limits into live guardrails instead of numbers checked once a year.
There is also an audit-defense benefit worth naming. When a regulator questions a reported maximum pressure or a monthly volume, an operator working from historized SCADA data can show the exact trend behind the number, including the timestamp of the peak and the meter reading behind the volume, all the way back to the raw sensor signal. That provenance is far more convincing than a hand-copied figure whose origin no one can fully reconstruct. The same discipline that makes the annual H-10 easy to produce is what makes the reported numbers hold up when someone with enforcement authority decides to look closely at them.
The Form H-10 is an annual report, filed once each year for each permitted injection or disposal well. It summarizes the full prior year, reporting the volume injected in each of the twelve months and the maximum surface injection pressure reached in each month. A separate H-10 is required for every well the operator holds an injection or disposal permit for.
Because the permit limits surface injection pressure to protect the confining rock from being fractured, and the risk lives in the worst moment, not the average. A single excursion above the permitted maximum is the event that could let injected fluid migrate out of the disposal zone. Reporting the monthly maximum forces the operator to disclose that worst-case peak, which is exactly what the regulator needs to judge whether containment was ever at risk.
A disposal or injection well is only authorized to keep operating if it passes mechanical integrity testing on the required schedule, and the annual H-10 is a natural checkpoint for confirming those tests are current. Continuously logged annulus pressure supports both: it feeds the report and it also reveals a developing tubing or packer leak in the trend long before the next scheduled integrity test, so an integrity problem is caught early rather than at test time.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.