PDQ Well Completion Directory
The wells that make up each lease, with API numbers and shut-in status.
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.
How it is laid out:
The Railroad Commission publishes this as CSV. Comma-separated text. We decode it into a table you can open anywhere. It has 17 columns and about 820.6K rows.
The columns you will most likely want:
-
oil_gas_codeWhether the lease is carried on the oil schedule or the gas schedule. -
district_noRRC's INTERNAL district number, 01 to 14 plus 20 for statewide. -
lease_noRRC lease number. -
well_noWell number within the lease, as the operator designates it. -
api_county_codeThe three-digit county part of the API number. -
api_unique_noThe five-digit unique part of the API number.
…and 11 more, all documented on the full page.
What we add:
Turn lease production into well-level context: which wells are on the lease, which are shut in, and which are subject to 14(b)(2). Join straight to the wellbore database on the API county and unique number — the two columns are already split the same way.
- Decoded out of the Commission's original format into something Excel opens.
- Filterable before you download, so you can take one county instead of the whole state.
- The Commission's single-letter codes translated into words.
Worth knowing before use:
Lease production cannot be allocated to individual wells from this table. It tells you which wells are on the lease, not what each one made. A lease number is only unique with the oil/gas code and the district in it.
The full page lists every trap in this dataset.