Field Oil Information
Queryable EBCDIC
The oil half of a field's master record: discovery, testing county, schedule headings and cumulative oil and casinghead gas.
Get the data
Heads up on Original: the Commission does not publish this table on its own. It publishes Statewide Field Data, 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.
What this is
The 19 OILSEG segment of the statewide field tape, one row for each of the 33,939 fields carried on the oil schedule. It holds the field's oil discovery date, county and depth, the county whose W-10 cycle it tests on, its offshore code, the heading code that says what the oil proration schedule prints for it, and sixteen cumulative totals of oil and casinghead gas and their allowables in the same four eras the gas segment uses.
What you can do with it
Rank oil fields by cumulative production since 1970, or by the last 24 months.
Find the oil fields discovered in a county or a decade, the ones in the bays and state waters, and the ones exempt from the ending-balance calculation.
Read what the proration schedule shows for a field — potential, acres, GOR, bottom-hole pressure — from its heading code, which is the closest thing the file has to naming the field's allocation basis.
Gotchas
original_oil_in_place is zero in every row: the manual says the item is no longer used.
The earliest schedule_start_date reads 1800-01-01, which is a placeholder rather than a date.
depth_1st_well is 99999 where the depth was never recorded.
As in the gas segment, the conversion, off-file, on-file and year-to-date cumulative totals cover different periods and must not be added together.
County codes are SMALLINTs, so pad before joining them to a county list.
Record layout
34 columns. Byte positions are 1-based and come from the RRC record layout, so you can check our decoding against the original file yourself.
fl_oil_field
34 columns
| # | Column | Type | Bytes | RRC name | Meaning | Lookup |
|---|---|---|---|---|---|---|
| 1 |
district_no
key
join
|
text | — | FL-DISTRICT |
RRC district as the FL tape stores it, 01 to 14 — the INTERNAL number, not the designation the industry prints. 07 is District 6E, 08 is 7B, 09 is 7C, 10 is District 08, 11 is 8A, 13 is District 09 and 14 is District 10. This is the same numbering PDQ calls district_no, so the two join directly; the printed form is on fl_field.district_name. Code 12 (District 8B) is reserved and no field carries it. e.g. 09 | RRC district (internal number) |
| 2 |
field_no
key
join
|
integer | — | FL-NUMBER |
The eight-digit RRC field number: five digits of field, then three of reservoir. Stored as an INTEGER, so the leading zeros are gone — 6,529 of the 65,826 fields have one. Pad it back before joining to PDQ or the Oracle field rules, which key on it as eight characters: lpad(field_no::text, 8, '0'). Padded, all 65,826 fields resolve to the PDQ field directory; unpadded, 59,297 do. e.g. 85279200 | — |
| 3 |
disc_date
|
date | 4-11 | FL-OIL-DISC-DATE-1ST-WELL |
Discovery date of the field's first oil well, CCYYMMDD. Filled on 31,856 of the 33,939 oil fields and running from 1896. | — |
| 4 |
disc_county_code
|
smallint | 12-14 | FL-OIL-DISC-COUNTY-CODE |
Three-digit RRC county code the field was discovered in, as a SMALLINT. Zero where none was recorded. e.g. 173 | — |
| 5 |
depth_1st_well
|
integer measured in ft | 15-19 | FL-OIL-DEPTH-1ST-WELL |
Depth in feet at which the discovery well was perforated. 99999 is the mainframe's 'not known'. e.g. 6785 | — |
| 6 |
testing_county
|
smallint | 20-22 | FL-OIL-TESTING-COUNTY |
County whose W-10 testing cycle the field tests on, as a three-digit code. | — |
| 7 |
first_alter_test_month
|
smallint | 23-24 | FL-OIL-1ST-ALTER-TEST-MONTH |
Alternate first testing month, 01-12, where the field does not test with its test county. Zero means it does. | — |
| 8 |
second_alter_test_month
|
smallint | 25-26 | FL-OIL-2ND-ALTER-TEST-MONTH |
Alternate second testing month, 01-12. Zero means none. | — |
| 9 |
offshore_code
|
text | 27-28 | FL-OIL-OFFSHORE-CODE |
Where the field's discovery well sits: 'L' land (33,507 fields), 'B' bays and estuaries, 'SO' state offshore, 'LB' land and bays, 'BO' bays and offshore. e.g. L | — |
| 10 |
schedule_column_hdg_cd
|
text | 29 | FL-OIL-SCHEDULE-COLUMN-HDG-CD |
Which set of column headings the oil proration schedule prints for this field, 'A' to 'Q' — the manual lists them at appendix D. It says what the schedule shows (potential, acres, GOR, bottom-hole pressure, acre-feet) and so, indirectly, what the field's allowable turns on. RRC-internal. e.g. B | — |
| 11 |
cum_oil_prod_to_conv
|
bigint measured in bbl | 30-36 | FL-CUM-OIL-PRODUCTION-TO-CONV |
Cumulative oil produced from 1970 to December 1982, in barrels: the lump sum the old tapes carried into the FL system at conversion. It does NOT include retro P-1 reports filed twelve months or more late. e.g. 234016542 | — |
| 12 |
cum_cshd_prod_to_conv
|
bigint measured in MCF | 37-43 | FL-CUM-CSHD-PRODUCTION-TO-CONV |
Cumulative casinghead gas produced from 1970 to December 1982, in MCF: the lump sum the old tapes carried into the FL system at conversion. It does NOT include retro P-1 reports filed twelve months or more late. | — |
| 13 |
cum_oil_allow_to_conv
|
bigint measured in bbl | 44-50 | FL-CUM-OIL-ALLOWABLE-TO-CONV |
Cumulative oil allowable from 1970 to December 1982, in barrels: the lump sum the old tapes carried into the FL system at conversion. It does NOT include retro P-1 reports filed twelve months or more late. | — |
| 14 |
cum_cshd_allow_to_conv
|
bigint measured in MCF | 51-57 | FL-CUM-CSHD-ALLOWABLE-TO-CONV |
Cumulative casinghead gas allowable from 1970 to December 1982, in MCF: the lump sum the old tapes carried into the FL system at conversion. It does NOT include retro P-1 reports filed twelve months or more late. | — |
| 15 |
off_file_cum_oil_allow
|
bigint measured in bbl | 58-64 | FL-OFF-FILE-CUM-OIL-ALLOWABLE |
Cumulative oil allowable in barrels from January 1983 up to the months still on the tape. Anything earlier is in the conversion total. | — |
| 16 |
off_file_cum_cshd_allow
|
bigint measured in MCF | 65-71 | FL-OFF-FILE-CUM-CSHD-ALLOWABLE |
Cumulative casinghead gas allowable in MCF from January 1983 up to the months still on the tape. Anything earlier is in the conversion total. | — |
| 17 |
off_file_cum_oil_prod
|
bigint measured in bbl | 72-78 | FL-OFF-FILE-CUM-OIL-PROD |
Cumulative oil production in barrels from January 1983 up to the months still on the tape. Anything earlier is in the conversion total. Includes every retro P-1 filed, which is why it is kept apart from the conversion total. | — |
| 18 |
off_file_cum_cshd_prod
|
bigint measured in MCF | 79-85 | FL-OFF-FILE-CUM-CSHD-PROD |
Cumulative casinghead gas production in MCF from January 1983 up to the months still on the tape. Anything earlier is in the conversion total. Includes retro P-1 reports. | — |
| 19 |
on_file_cum_oil_allow
|
bigint measured in bbl | 86-92 | FL-ON-FILE-CUM-OIL-ALLOWABLE |
The latest 24 months of oil allowable, in barrels. Production reporting lags allowable assignment by about two months, so this total stops two months short and can be compared directly with its opposite number. | — |
| 20 |
on_file_cum_cshd_allow
|
bigint measured in MCF | 93-99 | FL-ON-FILE-CUM-CSHD-ALLOWABLE |
The latest 24 months of casinghead gas allowable, in MCF. Production reporting lags allowable assignment by about two months, so this total stops two months short and can be compared directly with its opposite number. | — |
| 21 |
on_file_cum_oil_prod
|
bigint measured in bbl | 100-106 | FL-ON-FILE-CUM-OIL-PROD |
The latest 24 months of reported oil production, in barrels. Production reporting lags allowable assignment by about two months, so this total stops two months short and can be compared directly with its opposite number. e.g. 302927882 | — |
| 22 |
on_file_cum_cshd_prod
|
bigint measured in MCF | 107-113 | FL-ON-FILE-CUM-CSHD-PROD |
The latest 24 months of reported casinghead gas production, in MCF. Production reporting lags allowable assignment by about two months, so this total stops two months short and can be compared directly with its opposite number. | — |
| 23 |
ytd_cum_oil_allow
|
bigint measured in bbl | 114-120 | FL-YR-TO-DT-CUM-OIL-ALLOWABLE |
Oil allowable so far this calendar year, in barrels. The latest two months are not in it, for the same reporting lag. | — |
| 24 |
ytd_cum_cshd_allow
|
bigint measured in MCF | 121-127 | FL-YR-TO-DT-CUM-CSHD-ALLOWABLE |
Casinghead gas allowable so far this calendar year, in MCF. The latest two months are not in it, for the same reporting lag. | — |
| 25 |
ytd_cum_oil_prod
|
bigint measured in bbl | 128-134 | FL-YR-TO-DT-CUM-OIL-PROD |
Reported oil production so far this calendar year, in barrels. The latest two months are not in it, for the same reporting lag. | — |
| 26 |
ytd_cum_cshd_prod
|
bigint measured in MCF | 135-141 | FL-YR-TO-DT-CUM-CSHD-PROD |
Reported casinghead gas production so far this calendar year, in MCF. The latest two months are not in it, for the same reporting lag. | — |
| 27 |
ledger_month
|
smallint | 142-143 | FL-OIL-LEDGER-MONTH |
The most recent month RRC has oil production reports for. A property of the tape, not the field: every row says 6. | — |
| 28 |
schedule_lines_counter
|
smallint | 144-145 | FL-OIL-SCHEDULE-LINES-COUNTER |
How many remark lines RRC prints for this field on the oil proration schedule. Internal to the mainframe's printing. | — |
| 29 |
annual_lines_counter
|
smallint | 146-147 | FL-OIL-ANNUAL-LINES-COUNTER |
How many remark lines print on the annual report. Internal. | — |
| 30 |
original_oil_in_place
|
integer measured in bbl | 148-155 | FL-ORIGINAL-OIL-IN-PLACE |
Reserves in the field before production began, used by one allocation formula. The manual says it is no longer used and every row is zero. | — |
| 31 |
eb_exempt_flag
|
text | 156 | FL-OIL-FLD-EB-EXEMPT-FLAG |
'Y' where the field is exempt from the ending-balance calculation, which applies to fields limited by production. Two fields carry it. e.g. N | — |
| 32 |
schedule_start_date
|
date | 157-164 | FL-OIL-SCHEDULE-START-DATE |
When the field first appeared on the oil proration schedule, CCYYMMDD. Filled on 32,663 fields; the earliest reads 1800-01-01, which is a placeholder rather than a date. | — |
| 33 |
new_field_approval_date
|
date | 165-172 | FL-NEW-FLD-APPRVL-CCYRMODA |
Date the Commission approved the field as a new oil field. Filled on 2,764 fields. | — |
| 34 |
consolidated_field_flag
|
text | 173 | FL-OIL-CONSOLIDATED-FIELD-FLAG |
'Y' where this field is a consolidation of earlier ones. 2,518 fields. | — |
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.
| 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
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.
Field Oil Information joins to Statewide Field Data on District number and Field number — one row here matches one row there.
is the oil segment of
The oil half of a field's master record, back to the root. All 33,939 oil segments resolve, and no field has two. A field classified 'B' has both an oil and a gas segment.
statewide-field-oil-information.district_no = statewide-field-data.district_no AND statewide-field-oil-information.field_no = statewide-field-data.field_no
Where this comes from
- Published by
- Texas Railroad Commission — the original page
- Original format
- EBCDIC IBM mainframe encoding (cp037). Opening it as text gives you nonsense; it has to be transcoded first.
- RRC publishes
- Updated once a month (Monthly. Available by the 27th.)
- RRC download link
- GoAnywhere MFT
- Record layout manual
- Our table
texas.fl_oil_field
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.