Get the data

Heads up on Original: the Commission does not publish this table on its own. It publishes Production Data Query Dump, 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

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.

78,000 operators with their P-5 status code, last P-5 filing date, tax certification flag and e-filing status.

It overlaps the P-5 organization file but is cut from the production system, so the two can disagree by a filing cycle.

What you can do with it

Resolve operator numbers to names inside the production data without leaving it, and check whether an operator's P-5 was current.

Gotchas

This is the production system's copy. The P-5 organization dataset is the authoritative operator record and carries the address and organisation type.

Record layout

15 columns.

`pdq_og_operator_dw` 15 columns

Record layout for `pdq_og_operator_dw` — 15 columns
#	Column	Type	RRC name	Meaning	Lookup
1	`operator_no` key 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.	—
2	`operator_name`	text	—	Operator name as carried in this file. Names drift between filings — join on the operator number, never on the name.	—
3	`p5_status_code`	text	—	P5 status code	—
4	`p5_last_filed_dt`	text	—	P5 last filed date	—
5	`operator_tax_cert_flag`	text	—	Operator tax cert flag	—
6	`operator_sb639_flag`	text	—	Operator sb639 flag	—
7	`fa_option_code`	text	—	Fa option code	—
8	`record_status_code`	text	—	Record status code	—
9	`efile_status_code`	text	—	Efile status code	—
10	`efile_effective_dt`	date	—	Efile effective date	—
11	`create_by`	text	—	User or process that created the row in RRC's system.	—
12	`create_dt`	date	—	When the row was created in RRC's system.	—
13	`modify_by`	text	—	User or process that last changed the row in RRC's system.	—
14	`modify_dt`	date	—	When the row was last changed in RRC's system.	—
15	`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.	—

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 Operator Directory joins to PDQ Lease Production by Cycle on Operator number — one row here matches many rows there.

reported by

The operator that filed the production report for that month, resolved through the production system's own operator directory.

pdq-lease-cycle.operator_no = pdq-operator-directory.operator_no

PDQ Operator Directory joins to PDQ Operator Production by Cycle on Operator number — one row here matches many rows there.

totals the operator

Operator number to name and P-5 status.

pdq-operator-cycle.operator_no = pdq-operator-directory.operator_no

Where this comes from

Published by

Texas Railroad Commission — the original page

Original format

CSV Comma-separated text.

RRC publishes

Updated once a month (Last Saturday each month, with the PDQ dump.)

RRC download link

GoAnywhere MFT

Record layout manual

Production Data Query Dump — User Manual

Our table

texas.pdq_og_operator_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.