Get the data

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

One of the sixteen delimited tables inside the monthly Production Data Query dump. RRC publishes the dump as a single archive; EZRRC publishes each table inside it separately so you can take the one you need instead of a 3.6 GB zip.

547,000 leases. This is the table that makes production data legible: it maps the oil/gas code, district and lease number key to the lease name, the operating company, the field and the well number, and flags leases that are off schedule or severed.

What you can do with it

Turn a lease key into a name, a field and an operator.

Find every lease an operator holds, and find leases that have been severed — the Commission's enforcement action for delinquent filings.

Gotchas

The severance flag means the lease has been severed for a compliance failure and cannot legally sell product. It is one of the most consequential columns in the catalog and it is a single character.

A lease number is only unique with the oil/gas code and the district in it. Oil lease 027587 in District 08 and gas lease 027587 in District 08 are different leases; so is oil lease 027587 in District 09.

Record layout

13 columns.

pdq_og_regulatory_lease_dw 13 columns

# Column Type RRC name Meaning Lookup
1 oil_gas_code key join text Whether the lease is carried on the oil schedule or the gas schedule. Oil or gas schedule
2 district_no key join text RRC's INTERNAL district number, 01 to 14 plus 20 for statewide. This is not the district name the industry uses: internal 07 is District 6E, 08 is 7B, 09 is 7C, 10 is District 08, 11 is 8A, 13 is 09 and 14 is District 10. Join to the district directory rather than reading it as a label. RRC district (internal number)
3 lease_no key join text RRC lease number. Unique only within a district and a schedule, so a lease key is district + oil/gas code + lease number.
4 district_name text RRC district as the industry writes it, e.g. 7B, 8A, 6E.
5 lease_name text Lease name as filed.
6 operator_no join text The operator's six-digit RRC P-5 organization number. Join to the P-5 Organization dataset for the company's name, address and P-5 status.
7 operator_name text Operator name as carried in this file. Names drift between filings — join on the operator number, never on the name.
8 field_no join text The eight-digit RRC field number. The field's name is not in most files; join to the field directory to get it.
9 field_name text Field name.
10 well_no text Well number within the lease, as the operator designates it.
11 lease_off_sched_flag text A flag that denotes if the lease is off the schedule for the cycle.
12 lease_severance_flag text Flag noting if a P-4 Severance was issued and is in effect.
13 ingested_at timestamptz When the upstream pipeline last wrote this row. Not an RRC field — it is EZRRC's provenance stamp, and it is what the freshness badge is measured against.

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 (internal number) 14 values

Read by district_no

RRC's internal sequential district numbering, 01 to 14 plus 20 for statewide. The production data, the UIC database and the high-cost gas certifications all use this. Internal 07 is District 6E, 08 is 7B, 09 is 7C, 10 is District 08, 11 is 8A, 13 is 09 and 14 is District 10. There is no internal 12.

CodeMeans
01 District 01 — San Antonio (internal 01) Internal district number 01, which RRC prints as District 01 and administers from San Antonio.
02 District 02 — San Antonio (internal 02) Internal district number 02, which RRC prints as District 02 and administers from San Antonio.
03 District 03 — Houston (internal 03) Internal district number 03, which RRC prints as District 03 and administers from Houston.
04 District 04 — Corpus Christi (internal 04) Internal district number 04, which RRC prints as District 04 and administers from Corpus Christi.
05 District 05 — Kilgore (internal 05) Internal district number 05, which RRC prints as District 05 and administers from Kilgore.
06 District 06 — Kilgore (internal 06) Internal district number 06, which RRC prints as District 06 and administers from Kilgore.
07 District 6E — Kilgore (internal 07) Internal district number 07, which RRC prints as District 6E and administers from Kilgore.
08 District 7B — Abilene (internal 08) Internal district number 08, which RRC prints as District 7B and administers from Abilene.
09 District 7C — San Angelo (internal 09) Internal district number 09, which RRC prints as District 7C and administers from San Angelo.
10 District 08 — Midland (internal 10) Internal district number 10, which RRC prints as District 08 and administers from Midland.
11 District 8A — Midland (internal 11) Internal district number 11, which RRC prints as District 8A and administers from Midland.
13 District 09 — Wichita Falls (internal 13) Internal district number 13, which RRC prints as District 09 and administers from Wichita Falls.
14 District 10 — Pampa (internal 14) Internal district number 14, which RRC prints as District 10 and administers from Pampa.
20 District 20 — State Wide (internal 20) Internal district number 20, which RRC prints as District 20 and administers from State Wide.

Source: Generated from texas.pdq_gp_district.district_no

Oil or gas schedule 2 values

Read by oil_gas_code

Which schedule a lease is carried on. This is not decoration: an oil lease number and a gas lease number can be the same digits and mean different leases, so a lease key is only unique with this code and the district in it.

CodeMeans
O Oil Carried on the oil proration schedule; lease numbers are oil lease numbers.
G Gas Carried on the gas proration schedule; lease numbers are gas well IDs.

Source: PDQ Dump user manual; values confirmed as the complete distinct set in texas.pdq_og_lease_cycle.oil_gas_code

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.

PDQ Regulatory Lease Directory joins to PDQ Well Completion Directory on Oil gas code and District number and Lease number — one row here matches many rows there.

is produced by the wells

The wells that make up a lease. Texas reports oil production by lease, so this is as close as the production data gets to a well — it tells you which wells are on the lease, not what each one made.

pdq-regulatory-lease-directory.oil_gas_code = pdq-well-completion.oil_gas_code AND pdq-regulatory-lease-directory.district_no = pdq-well-completion.district_no AND pdq-regulatory-lease-directory.lease_no = pdq-well-completion.lease_no

PDQ Regulatory Lease Directory joins to PDQ Lease Production by Cycle on Oil gas code and District number and Lease number — one row here matches many rows there.

produced from the lease

Production rows carry a lease key and nothing else identifying. The regulatory lease directory is what turns that key into a lease name, an operator, a field number and a well number, and it is where the severance flag lives. Exact on all 5,000 sampled rows. The key is three columns, not one: the oil/gas code, the district and the lease number. Any two of them alone are ambiguous.

pdq-lease-cycle.oil_gas_code = pdq-regulatory-lease-directory.oil_gas_code AND pdq-lease-cycle.district_no = pdq-regulatory-lease-directory.district_no AND pdq-lease-cycle.lease_no = pdq-regulatory-lease-directory.lease_no

PDQ Regulatory Lease Directory joins to High Cost Gas on District number = District and Lease number = Lease number — one row here matches many rows there.

certifies the lease

The certification file and the production system agree on the district (both use the internal numbering) and on the zero-padded lease number, so those two columns join exactly — 4,998 of 5,000 sampled certifications find their lease. They do not agree on the oil/gas code: the certification file writes 'GAS' and the production system writes 'G', which is why that column is not part of the join. Every row here is gas. This is also the route to the field: the certification carries no field number, but the lease directory it lands on does.

high-cost-gas.district = pdq-regulatory-lease-directory.district_no AND high-cost-gas.lease_number = pdq-regulatory-lease-directory.lease_no

PDQ Regulatory Lease Directory joins to PDQ Lease Disposition by Cycle on Oil gas code and District number and Lease number — one row here matches many rows there.

disposed of production from the lease

The lease key resolved to a name, operator and field.

pdq-lease-disposition-cycle.oil_gas_code = pdq-regulatory-lease-directory.oil_gas_code AND pdq-lease-disposition-cycle.district_no = pdq-regulatory-lease-directory.district_no AND pdq-lease-disposition-cycle.lease_no = pdq-regulatory-lease-directory.lease_no

PDQ Regulatory Lease Directory joins to PDQ Onshore Lease Summary on Oil gas code and District number and Lease number — one row here matches many rows there.

summarises the lease

The onshore lease summary's key, resolved to the lease directory.

pdq-onshore-lease-summary.oil_gas_code = pdq-regulatory-lease-directory.oil_gas_code AND pdq-onshore-lease-summary.district_no = pdq-regulatory-lease-directory.district_no AND pdq-onshore-lease-summary.lease_no = pdq-regulatory-lease-directory.lease_no

Where this comes from

Published by
Texas Railroad Commission — the original page
Original format
CSV Comma-separated text.
Update cadence
Updated once a month (Last Saturday each month, with the PDQ dump.)
RRC download link
GoAnywhere MFT
Record layout manual
Our table
texas.pdq_og_regulatory_lease_dw

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.