Get the data

Heads up on Original: the Commission does not publish this table on its own. It publishes Gas Ledger, which this was parsed out of — so Original gets you that whole file, not just this table. Every other format is this table alone.

Free. You will be asked to confirm an email address before the files are built — that is the only gate, and it is there so we can tell you when a large export is ready.

Preview the first 100 rows

What this is

The FLD-MONTH group of the GSA020K field record, normalised: 589,862 rows, fourteen months for each of the 42,133 gas fields. It carries the per-well, acreage and 'other' factors of the field's allocation formula for that month, and the special limited-allowable code its wells will carry.

What you can do with it

Follow a prorated gas field's allocation factors through the cycle, and find the months a field's wells were put on a special limited allowable.

Gotchas

Prorated gas fields are rare, and it shows: per_well is non-zero on 51 of 589,862 rows and the acreage factor on 1,692. Most gas fields are exempt or one-well fields whose allowable needs no formula.

special_lmt_allow is the exception -- non-zero on 501,161 rows, which makes it the one column here with something to say about most fields.

For a wildcat field, acreage_factor holds the number of days in the month and other_factor the monthly production factor. They are not acreage or 'other' at all in those rows.

sw_split, split_date, sw_exc_206_code, sw_exc_8609_limit and change are zero in every row of the current tape. month_ordinal is a slot on a rolling tape: filter on cycle_yyyymm.

Record layout

16 columns. Byte positions are 1-based and come from the RRC record layout, so you can check our decoding against the original file yourself.

`gas_ledger_field_month` 16 columns

Record layout for `gas_ledger_field_month` — 16 columns, with byte positions
#	Column	Type	Bytes	RRC name	Meaning	Lookup
1	`district` key join	text	2-4	`DIST`	RRC district of the field this month belongs to, in the ledger's spelling. e.g. 01	RRC district (proration ledger spelling)
2	`field_no` key join	integer	5-12	`PERM-FLD-ID`	The eight-digit field number this month belongs to. e.g. 256500	—
3	`month_ordinal` key	smallint	—	—	Which of the fourteen month slots in the field record this row came from, 1 to 14, oldest first. The tape rolls every cycle, so the ordinal is a position and not a date; cycle_yyyymm is the month. e.g. 14	—
4	`cycle_yyyymm`	integer	583-588	`FLD-DATE`	The schedule month this row is for, CCYYMM. The August 2026 tape runs 202506 to 202607 and every one of the 42,133 fields carries all fourteen. e.g. 202607	—
5	`change`	smallint	589	`F-CHANGE`	1 when the field number changed this month. Zero in every row of the August 2026 tape.	—
6	`per_well_code`	smallint	590-591	`PER-WELL-CD`	The per-well allocation factor code for fields with per-well in the formula; the codes are in the manual's Appendix B.	—
7	`per_well`	integer measured in MCF	592-595	`PER-WELL`	The per-well allowable in MCF for a prorated field with per-well in its formula. Non-zero on 51 of 589,862 rows -- prorated gas fields are rare.	—
8	`acres_code`	smallint	596-597	`AC-CD`	The acreage allocation factor code, one of 02, 03, 07-12 per the manual.	—
9	`acreage_factor`	numeric	598-605	`ACRG-FACT`	The acreage factor amount, seven whole numbers and seven decimals. For a wildcat field it holds the number of days in the month instead, which is how a wildcat allowable is figured.	—
10	`other_code`	smallint	606-607	`OTHER-CD`	The allocation factor code for a field using something other than per-well or acres.	—
11	`other_factor`	numeric	608-613	`OTHER-FACT`	The amount of that other factor, with seven implied decimals. For a wildcat field it holds the monthly production factor.	—
12	`sw_split`	numeric	614-615	`SW-SPLIT`	A second statewide production factor for the month, where one took effect mid-month. Zero throughout the August 2026 tape.	—
13	`split_date`	smallint	616-617	`SPLIT-DATE`	Day of the month the second production factor took effect. Zero throughout.	—
14	`special_lmt_allow`	smallint	618	`SPECIAL-LMT-ALLOW`	The type of special limited allowable assigned to wells in the field: 0 none, 1 special three-month monthly, 2 special one-month daily, 3 special three-month high daily. Non-zero on 501,161 of 589,862 rows, which makes it the most-used code in this table. e.g. 1	—
15	`sw_exc_206_code`	smallint	619	`SW-EXC-206-CODE`	2 where House Bill 206 -- the rule against producing more than twice the allowable in a month -- was suspended for this month. Zero throughout the current tape.	—
16	`sw_exc_8609_limit`	smallint	620-621	`SW-EXC-8609-LIMIT`	The statewide multiple of the monthly allowable that wells with an exception may produce: '04' is four times, '00' unlimited. Zero throughout the current tape.	—

Code lookups used here

Every coded column in this dataset resolves to a real lookup table, so a well code of G can be read as what it actually means.

RRC district (proration ledger spelling) 14 values

Read by district

The district as the oil and gas proration ledger tapes write it, which is NOT how the rest of the corpus writes it. The ledger pads the lettered districts to three bytes -- 06E, 07B, 07C, 08A -- where the W-10, the G-10 and PDQ's district_name write 6E, 7B, 7C and 8A. That difference is worth a code set of its own because it is invisible in a join: a query matching ledger.district against w10.district returns rows for the ten numeric districts and silently drops the four lettered ones, which are 24% of the oil ledger's wells. Strip the leading zero before joining, or add it coming the other way. `canonical_value` is the internal district number, the same convention rrc.district uses, so a ledger district resolves to the same district in either numbering.

RRC district (proration ledger spelling) — 14 codes and their meanings
Code	Means
`01`	District 01 — San Antonio Written 01 here and 01 elsewhere.
`02`	District 02 — San Antonio Written 02 here and 02 elsewhere.
`03`	District 03 — Houston Written 03 here and 03 elsewhere.
`04`	District 04 — Corpus Christi Written 04 here and 04 elsewhere.
`05`	District 05 — Kilgore Written 05 here and 05 elsewhere.
`06`	District 06 — Kilgore Written 06 here and 06 elsewhere.
`06E`	District 6E — Kilgore The ledger writes 06E; the W-10 and PDQ write 6E.
`07B`	District 7B — Abilene The ledger writes 07B; the W-10 and PDQ write 7B.
`07C`	District 7C — San Angelo The ledger writes 07C; the W-10 and PDQ write 7C.
`08`	District 08 — Midland Written 08 here and 08 elsewhere.
`08A`	District 8A — Midland The ledger writes 08A; the W-10 and PDQ write 8A.
`08B`	District 8B — reserved The manuals list 08B as reserved for future use. No record of any ledger tape has ever carried it.
`09`	District 09 — Wichita Falls Written 09 here and 09 elsewhere.
`10`	District 10 — Pampa Written 10 here and 10 elsewhere.

Source: RRC manuals OLA013K, GSA020K and OLA028K (DIST/DIST-NO items); the thirteen spellings in use confirmed as the complete distinct set in texas.oil_ledger_field, texas.oil_ledger_well and texas.oil_detail_well on 2026-08-21

What this joins to

The Railroad Commission never states these keys anywhere in the files. They are the reason the data is hard to use, so here they are with the exact columns on both sides.

Gas Ledger — Field Months joins to Gas Ledger on District and Field number — many rows here share a single row there.

has fourteen months of allocation factors

The FLD-MONTH group of the gas field record. All 5,000 sampled fields carry all fourteen months.

gas-ledger.district = gas-ledger-field-months.district AND gas-ledger.field_no = gas-ledger-field-months.field_no

Where this comes from

Published by

Texas Railroad Commission — the original page

Original format

EBCDIC IBM mainframe encoding (cp037). Opening it as text gives you nonsense; it has to be transcoded first.

RRC publishes

Updated once a month (Monthly, with the gas ledger.)

RRC download link

GoAnywhere MFT

Record layout manual

GSA020K — Gas Ledger — Record Layout

Our table

texas.gas_ledger_field_month

EZRRC is an independent mirror of public-domain data published by the Texas Railroad Commission. It is not affiliated with or endorsed by the RRC. For any legal or regulatory purpose, verify against the official RRC release.