What this is:

ODA037K. The Commission's docket: 223,000 cases with the full procedural calendar — filed, noticed, heard, decided, ordered, closed, reopened — plus the examiners, the witness and transcript counts, whether the case was protested, and whether it was granted or denied. Two child files hang off it: the parties named in each docket and the subject lines describing what it was about. EZRRC publishes both separately.

How it is laid out:

The Railroad Commission publishes this as Fixed-width ASCII. Columns are byte ranges with no separators, described only in a scanned record layout. We decode it into a table you can open anywhere. It has 57 columns and about 223.3K rows.

The columns you will most likely want:

  • record_type The two-byte record type from the original hierarchical file.
  • docket_number The docket number. Join the name and subject tables on this.
  • suffix Docket suffix, e.g. R37 for a Rule 37 spacing exception, A37 for an amendment.
  • div Division the docket sits with.
  • filed_date Date the application was filed.
  • notice_date Date notice was issued.

…and 51 more, all documented on the full page.

What we add:

Find every case an operator has been party to, measure how long the Commission takes from filing to decision, and count contested versus uncontested outcomes. Follow a rulemaking from proposal to completion, and find the docket that set a field's rules.

  • 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.

Worth knowing before use:

The original layout stores every date as four separate two-digit fields — century, year, month, day. Upstream reassembles them into real dates, which is why the warehouse columns look nothing like the manual. The docket number alone is not unique: a suffix and a division qualify it.

The full page lists every trap in this dataset.

Get it:

People who want this usually want: