PDQ Well Completion Directory
Queryable CSV
The wells that make up each lease, with API numbers and shut-in status.
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.
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.
282,000 rows tying a lease and well number to an API county and unique number, with the wellbore and well shut-in dates, the 14(b)(2) status and the wellbore location code.
It is the bridge from the lease-based production world to the API-numbered wellbore world.
What you can do with it
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.
Gotchas
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. 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
17 columns.
pdq_og_well_completion
17 columns
| # | Column | Type | RRC name | Meaning | Lookup |
|---|---|---|---|---|---|
| 1 |
oil_gas_code
join
|
text | — | Whether the lease is carried on the oil schedule or the gas schedule. | Oil or gas schedule |
| 2 |
district_no
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
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 |
well_no
|
text | — | Well number within the lease, as the operator designates it. | — |
| 5 |
api_county_code
key
join
|
text | — | The three-digit county part of the API number. | Texas county code |
| 6 |
api_unique_no
key
join
|
text | — | The five-digit unique part of the API number. | — |
| 7 |
onshore_assc_cnty
|
text | — | Onshore associated county. | — |
| 8 |
district_name
|
text | — | RRC district as the industry writes it, e.g. 7B, 8A, 6E. | — |
| 9 |
county_name
|
text | — | County name. | — |
| 10 |
oil_well_unit_no
|
text | — | This data item contains an alphabetic or numeric identifier; a numeric identifier usually represents waterflood groupings. If this data item contains high-values, the well is not in a unit. | — |
| 11 |
well_root_no
|
text | — | This data item contains a key for internal use by ADP. It is a number, which will never change, even if the well changes to a different lease. It is used to access the root segment in the Well Database. | — |
| 12 |
wellbore_shutin_dt
|
text | — | Indicates the wellbore shut-in date. | — |
| 13 |
well_shutin_dt
|
text | — | Indicates the well shut-in date. | — |
| 14 |
well_14b2_status_code
|
text | — | Indicates whether the well has a Statewide Rule 14(b)(2) extention/ status. Statewide Rule 14(b)(2) requires that all wells be plugged when they are no longer producing. | — |
| 15 |
well_subject_14b2_flag
|
text | — | Indicates inactive wells that are subject to Statewide Rule 14 (b) (2). | — |
| 16 |
wellbore_location_code
|
text | — | Indicates the location of the wellbore. The location code defines if it is Land (L), Offshore (O), Inland Waterway (I) and Bay/Estuary (B). | — |
| 17 |
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.
Texas county code 277 values
Read by api_county_code
The three-digit county code RRC uses, which is also the county's FIPS code. `canonical_value` carries the full five-digit state plus county FIPS, so a county joins straight to Census geography. There are 254 Texas counties and 277 codes; the extras are offshore areas and administrative entries.
Source: Generated from texas.pdq_gp_county
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.
| Code | Means |
|---|---|
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.
| Code | Means |
|---|---|
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 Well Completion Directory joins to Full Wellbore Database (ASCII) on API county code = API county and API unique number = API unique — many rows here share a single row there.
is the wellbore
Both files split the API number the same way, so this is an exact two-column join — 5,000 of 5,000 sampled rows. It is the bridge from lease-based production to the API-numbered wellbore world.
pdq-well-completion.api_county_code = full-wellbore-ascii.api_county AND pdq-well-completion.api_unique_no = full-wellbore-ascii.api_unique
PDQ Well Completion Directory joins to PDQ Regulatory Lease Directory on Oil gas code and District number and Lease number — many rows here share a single row 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
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_well_completion
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.