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.

Preview the first 100 rows

What this is

OGA090, the FL database tape. Every field on the Texas proration schedules — 65,826 of them — with everything the Commission keeps about it: what the field is and how it is classified, when and where it was discovered, the spacing and density rules it is under, the formula its allowable is split by, the counties it lies in, and month after month of allowables and production.

This is the only public source of FIELD-LEVEL MONTHLY ALLOWABLES AND PRODUCTION. The 17 FLDMO segment carries 4,015,934 field-months — gas, oil, condensate and casinghead allowables beside the P-1 and P-2 production actually reported, back to September 1992 for the fields RRC kept history on. Nothing else RRC publishes has it: PDQ's field cycle table has production and no allowables, and the oil and gas annual field tables have one row a year.

It is also the only source of the MAINFRAME FIELD RULES: 13,951 gas rules and 8,565 oil rules with their spacing, density, casing, diagonal and docket, the optional unit sizes beneath them, and the weighted allocation formula each one is worked with. The Oracle field-rules export published separately here is the modern system's view of the same fields; this is what the IMS database has been carrying since the 1980s, and it goes back further.

The original is one 240-byte-record EBCDIC tape holding thirty record types in IMS hierarchical order: a 01 FLDROOT field record, then everything beneath it — the gas segment and its market demand, cycles, rules, remarks, counties, allocation factors and A-sheets; the field's monthly statistics and 49(b) calculations; the oil segment and its own cycles, rules, remarks and factors. A child record does not repeat the field key, so the file can only be read forwards. Here it is thirty-one tables, every row carrying (district_no, field_no) and whatever identifies it under its parent, so it can be filtered, joined and exported.

Related, and worth reading beside it: the PDQ field directory and PDQ field cycle tables (the same 65,826 fields, district for district, with monthly production and no allowables), the oil and gas annual report field tables (one row per field per year, with well counts), and Oil & Gas Field Rules (the Oracle export).

What you can do with it

Read a field's whole regulatory record in one place: its class and H2S status, its gas-oil ratio rule, its discovery well and permit, the counties it spans, and the rules and formula that decide what its wells may produce.

Take field-level monthly allowables and production — the 4,015,934 rows of FLDMO published as Field Monthly Statistics below — and compare what the Commission allowed with what the operators reported, month by month.

Find every field under a given density rule: 80-acre units, 330-foot lease lines, corner-to-corner diagonals, rules rescinded in 2000, rules that came out of a particular docket.

Separate prorated gas fields from exempt and one-well ones, and follow a prorated field through its cycles, its allocation factors and (for 1986-1992) its A-sheets.

Join to PDQ on district and field number for lease-level production under the same field, and to the drilling permit datasets on the discovery well's permit number.

Gotchas

A download of THIS dataset is texas.fl_field, the 65,826-row field master. The other thirty tables are documented in the record layout below and five of them are published as datasets of their own — Field Monthly Statistics, Field Gas Information, Field Oil Information, and the gas and oil rules — which is where their rows are downloadable.

texas.fl_t3_root and texas.fl_t3 are EMPTY. The 15 and 16 T-3 nomination segments are in the manual and the August 2026 tape carries neither, so the two tables exist and hold nothing.

field_no is an INTEGER here and an eight-character string in PDQ and in the Oracle field rules. Pad it back before joining — lpad(field_no::text, 8, '0') — or the 6,529 fields whose numbers begin with a zero silently miss: padded, all 65,826 fields resolve to the PDQ field directory; unpadded, 59,297 do.

district_no is the tape's INTERNAL district number, 01-14, which is what PDQ calls district_no. 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. The printed form is in district_name, and that is the column to join the ledgers, the W-10 and the annual field tables on. District 6E holds exactly one field.

The cycle segments roll. GASCYCLE, OILCYCLE, GASAFACT and OILFTROT carry 26 cycles — 202407 to 202608 in the August 2026 file — and older ones fall off, so a history has to be accumulated by keeping snapshots. FLDMO is the exception: it keeps 26 months for most fields and all 408 months back to 1992-09 for 6,032 of them.

The A-sheet segments (13 and 14) stopped in July 1992 and the tape still carries them: 19,715 balancing periods and 94,946 monthly lines, all between 1986 and 1992. They are history, not current practice.

Columns the mainframe stopped writing are empty rather than missing: reservoir_name, formation_composition and net_gor_rule_code are null in all 65,826 rows, liquid_cond_allowable is zero in all 4,015,934 field-months, and original_oil_in_place is zero in every oil segment. The column descriptions say which.

Counts and flags carry the mainframe's zero-initialised values alongside the documented ones: '0' turns up in returned_to_pr_flag, permanent_gas_well_flag and siwh_exception_flag where the manual documents only 'Y' and 'N'.

Sentinel dates are everywhere: 0000-00-00, 00000000 and 1900-01-01 all mean "not recorded". The upstream loader turns the unparseable ones into NULL, but a 1900 date that parsed cleanly is still a placeholder, not a fact.

Record layout

434 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_field` 23 columns

This is the table you get when you download or query Statewide Field Data.

Record layout for `fl_field` — 23 columns, with byte positions
#	Column	Type	Bytes	RRC name	Meaning	Lookup
1	`district_no` key join	text	3-4	`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	5-12	`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	`district_name`	text	—	—	The same district written the way RRC prints it and the way the ledgers, the W-10 and PDQ's district_name write it: 01-06, 6E, 7B, 7C, 08, 8A, 09, 10. Derived on load from district_no by the table the manual prints at p. 2-3, so it is a label, not a code the tape carries. District 6E holds exactly one field. e.g. 7C	RRC district (printed designation)
4	`field_name`	text	13-44	`FL-NAME`	The field's name, up to 32 characters, as the Commission approved it: usually an operator's word, the stratigraphic interval and sometimes the depth, e.g. 'SPRABERRY (TREND AREA)'. 65,702 of the 65,826 names are distinct; 55 district-and-name pairs are carried by two different field numbers, so a name is not a key. e.g. SPRABERRY (TREND AREA)	—
5	`field_class`	text	45	`FL-FIELD-CLASS`	How the field is classified: 'G' gas (31,848 fields), 'O' oil (23,693) or 'B' both (10,285). A 'B' field has a gas segment and an oil segment under it and appears on both proration schedules. e.g. B	—
6	`reservoir_name`	text	46-75	`FL-RESERVOIR-NAME`	The reservoir the field produces from, up to 30 characters. EMPTY in every row of the tape — the mainframe stopped writing it — so the reservoir is only readable from the parenthesis in field_name.	—
7	`formation_composition`	text	76-77	`FL-FORMATION-COMPOSITION`	Rock type: SS sandstone, LS limestone, DO dolomite, AN anhydrite, CG conglomerate, GW granite wash, WG weathered granite, SP serpentine, DL dolomite-lime. The manual says the item is reserved for future use and it is EMPTY in every row.	—
8	`test_month_exception`	text	83	`FL-4-MONTH-TEST-EXCPT`	How long an operator has to file the well test that sets the allowable: '1', '3' or '4' months, four being an exception the Commission grants large gas fields. 45,476 fields carry '3', three carry '4' and the rest are blank. e.g. 3	—
9	`h2s_code`	text	85	`FL-HYDROGEN-SULFIDE-CD`	Hydrogen sulphide: 'N' none (62,750 fields), 'Y' present (2,950), 'E' present but exempt from filing the H-9 certificate (126). This is the field-level flag, not a well measurement. e.g. E	—
10	`gor_code`	text	86	`FL-GAS-OIL-RATIO-CODE`	How the field's gas-oil ratio limit is set: 'G' a ratio, 'L' a gas limit, 'K' a limit based on the top producing well. Null on the 31,882 fields with no GOR rule, which are gas fields. e.g. G	—
11	`gor_or_limit`	integer measured in cf/bbl	87-91	`FL-GAS-OIL-RATIO-OR-LIMIT`	The ratio or the limit itself, in cubic feet of gas per barrel of oil — read it with gor_code, which says which it is. 2,000 cf/bbl is the usual ratio; 99999 is the mainframe's 'unlimited'. e.g. 4000	—
12	`net_gor_rule_code`	text	92	`FL-NET-GOR-RULE-CODE`	Basis of the field's NET gas-oil ratio: 'R' regular, 'G' based on the GOR, 'L' a limited volume, 'U' unlimited. EMPTY in every row of the tape.	—
13	`net_gor_or_limit`	integer measured in cf/bbl	93-97	`FL-NET-GOR-RATIO-OR-LIMIT`	The net GOR ratio or limit. Zero in every row, which follows from net_gor_rule_code being empty.	—
14	`oil_disc_well_gravity`	numeric measured in API	98-100	`FL-OIL-DISC-WELL-GRAVITY`	Gravity of the oil in the field's discovery well, degrees API to one decimal. Stored on the tape as zoned-signed DISPLAY with the sign overpunched into the last byte ('{' is +0), which is why the 34,000-odd gas fields read 0.0 rather than null. e.g. 40.0	—
15	`assoc_oil_field_no`	integer	101-108	`FL-ASSOC-OIL-FIELD-NUMBER`	For a gas field associated with an oil field that carries a DIFFERENT field number, the oil field's eight-digit number. Filled on 39 fields; where the two share a number, field_class is 'B' and this is null.	—
16	`discovery_permit_no` join	integer	109-115	`FL-DISCOV-PERMIT-NUM`	Drilling permit number of the discovery well, on the 4,456 fields RRC recorded one for. Join it to the drilling permit datasets on permit_no.	—
17	`new_field_discov_flag`	text	116	`FL-NEW-FIELD-DISCOV-FLAG`	'Y' on the 4,704 fields flagged as a new-field discovery, 'N' on the rest. e.g. N	—
18	`new_field_discov_date`	date	117-124	`FL-NEW-FLD-DISCOV-SYS-CCYRMODA`	When the new-field discovery was recorded, CCYYMMDD. Filled on 4,702 fields and running 1995-01-03 to 2026-04-22, so its absence means the field predates the flag rather than that it was never discovered.	—
19	`returned_to_pr_flag`	text	125	`FL-RRC-RETURNED-TO-PR-FLAG`	'Y' on the 18 fields returned to the proration schedule by order. Most rows carry '0', which is the mainframe's zero-initialised 'no' rather than a documented value.	—
20	`returned_to_pr_yyyymm`	integer	126-131	`FL-RRC-RET-TO-PR-DATE`	Month the field was returned to the schedule, as yyyymm. The tape writes CCYYMM and the manual says the day defaults to the 1st. Filled on 18 fields.	—
21	`set_to_aof_flag`	text	132	`FL-SET-TO-AOF-BY-ORDER-FLAG`	'Y' on the 313 fields set to absolute open flow by Commission order — the whole field allowed to produce at capacity. Most rows carry '0'.	—
22	`set_to_aof_yyyymm`	integer	133-138	`FL-SET-TO-AOF-BY-ORDER-DATE`	Month the field was set to absolute open flow, as yyyymm, on the 313 fields that were. 1983-01 to 2016-02.	—
23	`manual_review_flag`	text	139	`FL-MANUAL-REVIEW-FLAG`	'Y' where the field's rules are complex enough that a person has to read them. Seven fields in the state carry it — the same seven the Oracle field-rules export flags. e.g. N	—

`fl_asheet` 16 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset.

Record layout for `fl_asheet` — 16 columns, with byte positions
#	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.	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.	—
3	`balancing_period_yyyymm` key	integer	3-8	`FL-AS-BALANCING-PERIOD-DATE`	The balancing period this A-sheet belongs to, as yyyymm. Gas cannot be stored, so wells may overproduce in a peak and make it up later; the periods run six months from each March and September. The whole segment was discontinued in July 1992 and the tape carries 198603 to 199209 — history, not current practice.	—
4	`user_updt_cur_6mo_flag`	text	9	`FL-AS-USER-UPDT-CUR-6MO-FLAG`	'Y' where an analyst overrode the calculated current six-month status. The manual says it is not used and every row agrees.	—
5	`user_updt_prior_6mo_flag`	text	10	`FL-AS-USER-UPDT-PRIOR-6MO-FLAG`	'Y' where an analyst overrode the prior six-month status. Not used.	—
6	`current_6mo_status`	integer measured in MCF	11-15	`FL-AS-CURRENT-6MO-STATUS`	How far the field was over or under its total reservoir allowable coming into the current balancing period, in MCF. Positive is overproduction, negative underproduction.	—
7	`prior_6mo_status`	integer measured in MCF	16-20	`FL-AS-PRIOR-6MO-STATUS`	The same figure coming into the PRIOR balancing period, in MCF.	—
8	`tot_prior_xtra_adj_amt`	integer measured in MCF	21-25	`FL-AS-TOT-PRIOR-XTRA-ADJ-AMT`	The calculated extra adjustment for the prior balancing period: three months of normal adjustment plus two of extra adjustment, subtracted from the prior six-month status.	—
9	`working_prior_amount`	integer measured in MCF	26-30	`FL-AS-WORKING-PRIOR-AMOUNT`	The working extra adjustment for the prior period — the same calculation with every month's extra adjustment in it, which is what an analyst was allowed to spend.	—
10	`active_inactive_flag`	text	31	`FL-AS-ACTIVE-INACTIVE-FLAG`	'A' active (16,514 rows), 'I' inactive (3,163), 'N' active but column 11 is not calculated. An inactive A-sheet means a prorated field with no wells, all shut in, or all on special allowables.	—
11	`calc_in_eff_yyyymm`	integer	32-37	`FL-AS-ASHEET-CALC-IN-EFF`	When the field became prorated, as yyyymm. Everything prorated on or before March 1986 carries 198603.	—
12	`prior_reinstated`	integer measured in MCF	38-42	`FL-AS-PRIOR-REINSTATED`	Underage cancelled and then reinstated for the prior balancing period, usually after a hearing.	—
13	`current_reinstated`	integer measured in MCF	43-47	`FL-AS-CURRENT-REINSTATED`	Underage cancelled and then reinstated for the current balancing period.	—
14	`page_number`	smallint	48-51	`FL-AS-PAGE-NUMBER`	Page this A-sheet printed on that month.	—
15	`update_flag`	text	52	`FL-AS-UPDATE-FLAG`	'Y' where the A-sheet was updated after its first calculation, in which case it was reprinted and sent to the analyst.	—
16	`extract_yyyymm`	integer	53-58	`FL-AS-EXTRACT-DATE`	The schedule month an A-sheet was last produced for, as yyyymm. RRC-internal.	—

`fl_asheet_month` 55 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset.

Record layout for `fl_asheet_month` — 55 columns, with byte positions
#	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.	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.	—
3	`balancing_period_yyyymm` key	integer	—	`FL-AS-BALANCING-PERIOD-DATE`	The balancing period this month belongs to, carried down from the parent A-sheet, as yyyymm.	—
4	`sched_yyyymm` key	integer	3-8	`FL-AS-SCHED-DATE`	The gas proration schedule month this A-sheet line was calculated for, as yyyymm. 198603 to 199206; the segment was discontinued in July 1992.	—
5	`recalc_alloc_fct_cnt`	smallint	9	`FL-AS-RECAL-ALLOC-FCT-CNT`	Not used, per the manual. Zero in every row.	—
6	`number_of_asheets`	smallint	10	`FL-AS-NUMBER-OF-ASHEETS`	How many times the A-sheet for this field-month was produced, counting the original.	—
7	`current_forecast`	integer measured in MCF	11-15	`FL-AS-CURRENT-FORECAST`	Column 1: the total adjusted T-3 amount for the field — how much gas purchasers nominated for it, in MCF.	—
8	`third_mo_prior_forecast`	integer measured in MCF	16-20	`FL-AS-3RD-MO-PRIOR-FORECAST`	Column 2: what column 1 said three months earlier.	—
9	`third_mo_prior_sup_chng`	integer measured in MCF	21-25	`FL-AS-3RD-MO-PRIOR-SUP-CHNG`	Column 3: adjustments to allowables from three months previous by gas well supplement. A supplement that cut allowables shows as a positive adjustment here.	—
10	`non_limited_prod`	integer measured in MCF	26-30	`FL-AS-NON-LIMITED-PROD`	Column 4: gas produced three months previous by the field's non-limited (top-allowable) wells, in MCF.	—
11	`gross_adjustment_amt`	integer measured in MCF	31-35	`FL-AS-GROSS-ADJUSTMENT-AMT`	Column 5: how far the field was over- or under-nominated three months previous. Column 2 + column 3 - column 4.	—
12	`limited_allowable`	integer measured in MCF	36-40	`FL-AS-LIMITED-ALLOWABLE`	Column 6: total allowable of the field's limited wells three months previous — the wells that cannot produce their formula share and are allowed what they can.	—
13	`limited_production`	integer measured in MCF	41-45	`FL-AS-LIMITED-PRODUCTION`	Column 7: what those limited wells actually produced three months previous.	—
14	`limited_adjustment`	integer measured in MCF	46-50	`FL-AS-LIMITED-ADJUSTMENT`	Column 8: the limited wells' underage, added back into the field for redistribution. Column 6 - column 7.	—
15	`normal_adjustment`	integer measured in MCF	51-55	`FL-AS-NORMAL-ADJUSTMENT`	Column 9: the difference between the total assigned reservoir allowable and the current forecast at the initial calculation.	—
16	`extra_adjustment`	integer measured in MCF	56-59	`FL-AS-EXTRA-ADJUSTMENT`	Column 10: the adjustment an analyst made by hand to balance the field's allowable against its production.	—
17	`total_assigned_res_amt`	integer measured in MCF	60-64	`FL-AS-TOTAL-ASSIGNED-RES-AMT`	Column 11: the total reservoir allowable the field was assigned. Column 1 - column 5 + column 8 + column 10, capped at maximum deliverability less 5 MCF.	—
18	`cancel_underage_amt`	integer measured in MCF	65-68	`FL-AS-CANCEL-UNDERAGE-AMT`	Cancelled underage added back into the field, printed in column 10 with a 'C' beside it.	—
19	`current_forecast_code`	text	69	`FL-AS-CURRENT-FORECAST-CODE`	Where column 1 came from: 'T' a T-3, 'Z' zero nominated, 'A' an average of past production, 'U' unspecified, 'G' a G-7 (only before September 1986).	—
20	`col_1_revised_code`	text	70	`FL-AS-COL-1-REVISED-CODE`	'R' where an analyst revised column 1, 'N' where not.	—
21	`third_mo_prior_frcst_code`	text	71	`FL-AS-3RD-MO-PRIOR-FRCST-CODE`	Where column 2 came from, on the same list as the current forecast code.	—
22	`col_2_revised_code`	text	72	`FL-AS-COL-2-REVISED-CODE`	'R' where an analyst revised column 2.	—
23	`col_3_revised_code`	text	73	`FL-AS-COL-3-REVISED-CODE`	'R' where an analyst revised column 3.	—
24	`col_4_revised_code`	text	74	`FL-AS-COL-4-REVISED-CODE`	'R' where an analyst revised column 4.	—
25	`col_5_revised_code`	text	75	`FL-AS-COL-5-REVISED-CODE`	'R' where an analyst revised column 5.	—
26	`col_6_revised_code`	text	76	`FL-AS-COL-6-REVISED-CODE`	'R' where an analyst revised column 6.	—
27	`col_7_revised_code`	text	77	`FL-AS-COL-7-REVISED-CODE`	'R' where an analyst revised column 7.	—
28	`col_8_revised_code`	text	78	`FL-AS-COL-8-REVISED-CODE`	'R' where an analyst revised column 8.	—
29	`col_10_revised_code`	text	79	`FL-AS-COL-10-REVISED-CODE`	'R' where an analyst revised the extra adjustment.	—
30	`tot_assign_res_amt_cd`	text	80	`FL-AS-TOT-ASSIGN-RES-AMT-CD`	What kind of allowable the field got: 'N' normal automatic calculation, 'M' cut to maximum deliverability less 5 MCF, '*' a zero-star allowable, 'A' an average of recent production, 'P' the third month previous production, 'U' unspecified.	—
31	`num_of_mons_avgd`	smallint	81-82	`FL-AS-NUM-OF-MONS-AVGD`	How many months the average past production was taken over. The manual says it is not used; every row is zero.	—
32	`col_11_revised_code`	text	83	`FL-AS-COL-11-REVISED-CODE`	'R' where an analyst revised the total reservoir allowable.	—
33	`user_upd_calc_eff_flag`	text	84	`FL-AS-USER-UPD-CALC-EFF-FLAG`	'Y' where an analyst updated the current month by hand, so the mainframe kept the entered figures instead of recalculating.	—
34	`cancel_underage_code`	text	85	`FL-AS-CANCEL-UNDERAGE-CODE`	'C' cancelled underage added back under normal conditions, 'Q' added into a field on a zero-star allowable, 'N' none.	—
35	`item_12_revised_code`	text	86	`FL-AS-ITEM-12-REVISED-CODE`	'R' where an analyst revised the cancelled underage.	—
36	`special_allowable_flag`	text	87	`FL-AS-SPECIAL-ALLOWABLE-FLAG`	'Y' where one or more wells in the field are on a special allowable.	—
37	`reduced_rate_flag`	text	88	`FL-AS-REDUCED-RATE-FLAG`	'Y' where one or more wells in the field are producing at a reduced rate.	—
38	`field_balanced_flag`	text	89	`FL-AS-FIELD-BALANCED-FLAG`	'Y' where the field's cumulative status is zero this month — it is exactly in balance.	—
39	`tot_calc_res_amount`	integer measured in MCF	90-94	`FL-AS-TOT-CALC-RES-AMOUNT`	The total reservoir allowable as calculated, which differs slightly from the assigned figure in column 11 because it cannot be divided evenly among the wells.	—
40	`intend_to_recalc_flag`	text	95	`FL-AS-INTEND-TO-RECALC-FLAG`	Not used, per the manual. One value in every row.	—
41	`gross_t3_total`	integer measured in MCF	96-100	`FL-AS-GROSS-T3-TOTAL`	Total gas nominated for the field on all its T-3 forms, in MCF, before any adjustment.	—
42	`adjusted_t3_total`	integer measured in MCF	101-105	`FL-AS-ADJUSTED-T3-TOTAL`	The same total after nominations were cut back to what the nominators' wells could deliver or were entitled to.	—
43	`gross_deliv`	integer measured in MCF	106-110	`FL-AS-GROSS-DELIV`	Not used, per the manual. Zero in every row.	—
44	`adjusted_deliv`	integer measured in MCF	111-115	`FL-AS-ADJUSTED-DELIV`	Not used, per the manual. Zero in every row.	—
45	`cor_3rd_mo_pri_sup_chg`	integer measured in MCF	116-120	`FL-AS-COR-3RD-MO-PRI-SUP-CHG`	Not used, per the manual. Zero in every row.	—
46	`tot_curr_xtra_adj_amt`	integer measured in MCF	121-125	`FL-AS-TOT-CURR-XTRA-ADJ-AMT`	The calculated extra adjustment for the current balancing period, worked out each May and November.	—
47	`working_cur_xtra_adj_amt`	integer measured in MCF	126-130	`FL-AS-WORKING-CUR-XTRA-ADJ-AMT`	The over- or underage in the current balancing period an analyst was allowed to spend adjusting the reservoir allowable.	—
48	`monthly_cumu_status`	integer measured in MCF	131-135	`FL-AS-MONTHLY-CUMU-STATUS`	How far the field is over (positive) or under (negative) its allowable, cumulatively, in MCF.	—
49	`projected_status`	integer measured in MCF	136-140	`FL-AS-PROJECTED-STATUS`	The projected cumulative status for the following month, from the average of the last three months' non-limited production.	—
50	`max_deliv`	integer measured in MCF	141-145	`FL-AS-MAX-DELIV`	Maximum deliverability of the field in MCF, from the G-10 tests. A total allowable above it is cut to it less 5 MCF.	—
51	`user_upd_max_del_flag`	text	146	`FL-AS-USER-UPD-MAX-DEL-FLAG`	'Y' where an analyst updated the maximum deliverability by hand.	—
52	`p_cur_alow_cur_frcst`	smallint measured in %	147-149	`FL-AS-P-CUR-ALOW-CUR-FRCST`	Column 11 as a percentage of column 1 — the allowable against what was nominated.	—
53	`p_cur_alow_6_mo_avg_prd`	smallint measured in %	150-152	`FL-AS-P-CUR-ALOW-6-MO-AVG-PRD`	Column 11 as a percentage of the last six months' average production.	—
54	`p_6_mo_avg_prd_6_mo_avg`	smallint measured in %	153-155	`FL-AS-P-6-MO-AVG-PRD-6-MO-AVG`	Not used, per the manual. Zero in every row.	—
55	`calc_asheet_date`	date	156-163	`FL-AS-CALC-ASHEET-DATE`	Date the total reservoir allowable was first calculated for the schedule month, CCYYMMDD. 1986 to 1992, when the segment stopped.	—

`fl_assoc_gas_field` 4 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset.

Record layout for `fl_assoc_gas_field` — 4 columns, with byte positions
#	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.	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.	—
3	`assoc_district_no` key join	text	3-4	`FL-ASSOC-GAS-FIELD-DIST`	Internal district number of a gas field associated with this oil field. Ninety-seven rows in the state: it is only written where the associated fields carry DIFFERENT field numbers, which is the exception.	—
4	`assoc_field_no` key join	integer	5-12	`FL-ASSOC-GAS-FIELD-NUMBER`	Eight-digit field number of the associated gas field. With assoc_district_no it is the key to that field's own root row.	—

`fl_calc_49b` 13 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset.

Record layout for `fl_calc_49b` — 13 columns, with byte positions
#	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.	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.	—
3	`seq` key	smallint	—	—	Which 49(b) calculation on this field, from 1. Position rather than date, because a field can carry two calculations with the same effective date and different pressures.	—
4	`allow_effective_date`	date	3-10	`FL-GAS-ALLOW-EFFECTIVE-DATE`	When this 49(b) allowable takes effect for the gas wells in an associated field, CCYYMMDD. 1966 to 2025.	—
5	`rrcid_determining_well`	integer	11-16	`FL-RRCID-DETERMINING-WELL`	RRC identification number of the well whose measured properties the calculation used.	—
6	`g1_gas_gravity`	numeric	19-21	`FL-G-1-GAS-GRAVITY`	Gas gravity of that well from its G-1, to three decimals (dimensionless, air = 1).	—
7	`avg_reservoir_bhp`	integer measured in psi	22-26	`FL-AVG-RESERVOIR-BHP`	Average reservoir bottom-hole pressure at the gas-oil contact, in PSI absolute.	—
8	`avg_reservoir_bh_temp`	smallint	27-29	`FL-AVG-RESERVOIR-BH-TEMP`	Average reservoir bottom-hole temperature at the gas-oil contact, in degrees Rankine.	—
9	`formation_volume_factor`	numeric	30-34	`FL-FORMATION-VOLUME-FACTOR`	Formation volume factor of the reservoir at average conditions, to four decimals. Dimensionless.	—
10	`solution_gas_oil_ratio`	numeric measured in cf/bbl	35-43	`FL-SOLUTION-GAS-OIL-RATIO`	Solution gas-oil ratio used in the 49(b) calculation, to four decimals.	—
11	`deviation_factor`	numeric	44-48	`FL-DEVIATION-FACTOR`	How far the gas departs from the ideal gas laws at average reservoir pressure and temperature, to four decimals. Dimensionless.	—
12	`top_daily_gas_allow_cu_ft`	bigint measured in cf/d	49-54	`FL-TOP-DAILY-GAS-ALLOW-CU-FT`	The resulting top daily gas allowable per well, in cubic feet.	—
13	`top_daily_gas_allow_mcf`	integer measured in MCF/d	55-58	`FL-TOP-DAILY-GAS-ALLOW-MCF`	The same allowable in MCF a day — the figure the schedule prints.	—

`fl_field_month` 18 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset — it is published separately as Field Monthly Statistics (Allowables and Production).

Record layout for `fl_field_month` — 18 columns, with byte positions
#	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	`prod_yyyymm` key	integer	3-8	`FL-PRODUCTION-DATE`	The production month this row is for, as yyyymm. 199209 through 202608 on the August 2026 tape. The manual promises 24 months and the file delivers more: 59,790 fields carry the last 26 months only, while 6,032 carry all 408 months back to September 1992. e.g. 202607	—
4	`gas_allowable`	bigint measured in MCF	11-17	`FL-GAS-ALLOWABLE`	Gas well gas the field was allowed to produce that month, in MCF. This is the field's total, assigned by the Commission and then prorated among its wells by the allocation formula. e.g. 185840	—
5	`liquid_cond_allowable`	integer measured in bbl	18-22	`FL-LIQUID-COND-ALLOWABLE`	The monthly condensate (liquid) allowable assigned to a gas field, in barrels. ZERO in all 4,015,934 rows of this tape: liquid limits are no longer set, which the gas segment's own on-file and year-to-date liquid totals confirm.	—
6	`oil_allowable`	integer measured in bbl	23-27	`FL-OIL-ALLOWABLE`	Oil the field was allowed to produce that month, in barrels — the field total that the yardstick and the field's allocation formula distribute among its wells. e.g. 28887062	—
7	`casinghead_gas_limit`	integer measured in MCF	28-32	`FL-CASINGHEAD-GAS-LIMIT`	MCF of casinghead gas — gas produced from an oil well — the field was allowed that month. 999999999 appears where the limit is the mainframe's 'no limit'; unlimited_casinghead_flag says so properly. e.g. 16864422	—
8	`p2_gas_production`	integer measured in MCF	33-37	`FL-P2-GAS-PRODUCTION`	Gas well gas the operators reported for the field that month on form P-2, in MCF. Reporting lags allowables by about two months, so the newest cycles read zero until the reports arrive.	—
9	`p2_condensate_production`	integer measured in bbl	38-42	`FL-P2-CONDENSATE-PRODUCTION`	Condensate reported on form P-2 for the field that month, in barrels.	—
10	`partial_gas_well_prod_cd`	text	43	`FL-PARTIAL-GAS-WELL-PROD-CD`	How complete the P-2 reporting is for the month: 'A' all reports in, 'S' some, 'N' none, 'I' no gas wells in the field. 'I' is the commonest value, on 1,856,462 rows, and 284,638 rows carry nothing at all. Anything other than 'A' means the production figures beside it are partial. e.g. N	—
11	`p1_oil_production`	integer measured in bbl	44-48	`FL-P1-OIL-PRODUCTION`	Oil the operators reported for the field that month on form P-1, in barrels.	—
12	`p1_casinghead_production`	integer measured in MCF	49-53	`FL-P1-CASINGHEAD-PRODUCTION`	Casinghead gas reported on form P-1 for the field that month, in MCF.	—
13	`partial_oil_well_prod_cd`	text	54	`FL-PARTIAL-OIL-WELL-PROD-CD`	How complete the P-1 reporting is: 'A' all reports in, 'S' some, 'N' none, 'I' no oil wells in the field. Read it before comparing one month with another. e.g. N	—
14	`date_last_updated`	date	55-62	`FL-DATE-LAST-UPDATED`	When the mainframe last wrote this row, CCYYMMDD. Filled on 2,849,023 of the rows, running 1994-10-17 to 2026-07-23; the older months carry none. e.g. 2026-07-23	—
15	`unlimited_casinghead_flag`	text	63	`FL-UNLIMITED-CASINGHEAD-FLAG`	'Y' where the field's casinghead gas is unlimited — it may produce to capacity. 4,754 rows. e.g. N	—
16	`include_drop_gas_stats_flag`	text	64	`FL-INCLUDE-DROP-GAS-STATS-FLAG`	RRC bookkeeping: 'Y' where gas well records for this field-month were dropped off the master production tapes and stored elsewhere. EMPTY in every row.	—
17	`include_drop_oil_stats_flag`	text	65	`FL-INCLUDE-DROP-OIL-STATS-FLAG`	The same for oil lease records. EMPTY in every row.	—
18	`total_calc_res_amount`	integer measured in MCF	66-70	`FL-TOTAL-CALC-RES-AMOUNT`	The total reservoir allowable as actually calculated, in MCF. It differs slightly from gas_allowable because the assigned total cannot always be divided evenly among the wells and the mainframe does not carry fractions. e.g. 185251	—

`fl_gas_alloc_factor` 4 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset.

Record layout for `fl_gas_alloc_factor` — 4 columns, with byte positions
#	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.	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.	—
3	`cycle_yyyymm` key	integer	3-6	`FL-GAS-FACTOR-CYCLE-KEY`	The allowable cycle this row is for, as yyyymm. The tape writes it as the ledgers' nines-complement key (9927 is January 1993, counting down), which upstream decodes. Twenty-six cycles are on the tape at a time: 202407 through 202608 in the August 2026 file. Older cycles fall off, so a history has to be accumulated from snapshots.	—
4	`zero_star_code`	text	57	`FL-ZERO-STAR-CODE`	Set where the field was given a zero-star (0*) allowable for the cycle — every well assigned zero so that all production counts as overproduction and the field's underproduction is worked off. 5,855 of the 1,094,929 rows carry it, and the tape writes '0' where the manual documents 'Y'.	—

`fl_gas_alloc_factor_item` 6 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset.

Record layout for `fl_gas_alloc_factor_item` — 6 columns, with byte positions
#	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.	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.	—
3	`cycle_yyyymm` key	integer	—	`FL-GAS-FACTOR-CYCLE-KEY`	The allowable cycle this row is for, as yyyymm. The tape writes it as the ledgers' nines-complement key (9927 is January 1993, counting down), which upstream decodes. Twenty-six cycles are on the tape at a time: 202407 through 202608 in the August 2026 file. Older cycles fall off, so a history has to be accumulated from snapshots.	—
4	`ordinal` key	smallint	—	—	Which of the five OCCURS slots this factor came out of, from 1. The slots are one 10-byte code-and-factor pair each, at bytes 7-56 of the record; empty slots are dropped rather than loaded as zeros, which is why only 4,018 rows exist against 1,094,929 parents. Two slots is the most any cycle uses.	—
5	`factor_code`	smallint	—	`FL-FACTOR-CODE`	What the factor measures, on the same list the gas allocation formula uses: 01 per cent deliverability, 02 acres, 03 per well, 06 deliverability, 17 acres x shut-in wellhead pressure, 20 the twelve-month peak.	—
6	`factor`	numeric	—	`FL-ALLOCATION-FACTOR`	The numeric factor the field's allowable calculation multiplies by, to seven decimal places (packed decimal on the tape).	—

`fl_gas_alloc_formula` 6 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset.

Record layout for `fl_gas_alloc_formula` — 6 columns, with byte positions
#	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.	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.	—
3	`rule_seq` key	smallint	—	—	Which rule under this field, counting from 1 in the order the tape carries them — newest first, the undated rule last. EZRRC's column, not RRC's: the tape keys a rule on 99999999 minus its effective date, and 7,496 of the 13,951 gas rules and 5,473 of the 8,565 oil rules carry the bare 99999999, meaning no effective date at all. A date missing from more than half the rows cannot be the key, so position is.	—
4	`seq` key	smallint	—	—	Position of this term in the formula, from 1. EZRRC's column: the terms are consecutive records on the tape with no key of their own. Three terms is the most any gas formula uses, two for oil.	—
5	`allow_percent_factor`	numeric	3-5	`FL-GAS-ALLOW-PERCENT-FACTR`	The weight this term carries in the formula, as a fraction: 0.50 is 50 per cent. The terms of a rule sum to 1.00 — on every gas rule but one and every oil rule but three, which come to 0.99 through rounding.	—
6	`allocation_factor_code`	smallint	6-7	`FL-GAS-ALLOCATION-FCTR-CD`	What the term measures: 01 per cent deliverability, 02 acres (5,483 terms), 03 per well, 04 acres x bottom-hole pressure, 05 acre feet, 06 deliverability, 07 bottom-hole pressure, 08 G-1 potential, 09 G-10 potential, 10 acres x calculated deliverability, 11 acres x rock pressure, 12 acre feet x bottom-hole pressure, 13 25% statewide, 14 49(b) associated, 15 acres x deliverability, 16 one well, 17 acres x shut-in wellhead pressure, 18 lease per cent reserves, 19 twelve-month peak.	—

`fl_gas_county` 3 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset.

Record layout for `fl_gas_county` — 3 columns, with byte positions
#	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.	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.	—
3	`county_code` key	smallint	3-5	`FL-GAS-COUNTY-CODE`	Three-digit RRC county code of a county this field lies in. The 254 onshore counties take the odd numbers 001-507; the 23 offshore and bay areas take 600-606 and 700-715. Stored as a SMALLINT, so it has lost its leading zeros: cast and pad before joining to a county code set or to a FIPS code.	—

`fl_gas_cycle` 20 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset.

Record layout for `fl_gas_cycle` — 20 columns, with byte positions
#	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.	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.	—
3	`cycle_yyyymm` key	integer	3-6	`FL-GAS-CYCLE-KEY`	The allowable cycle this row is for, as yyyymm. The tape writes it as the ledgers' nines-complement key (9927 is January 1993, counting down), which upstream decodes. Twenty-six cycles are on the tape at a time: 202407 through 202608 in the August 2026 file. Older cycles fall off, so a history has to be accumulated from snapshots.	—
4	`type_field_code`	text	7-8	`FL-GAS-TYPE-FIELD-CODE`	How the gas field was classified for that cycle, which decides how its allowable is worked out: 'ON' one-well (600,380 rows), 'EX' exempt (270,859), 'CA' capacity (150,498), '49' statewide rule 49(b) (57,738), 'PR' prorated (11,767), 'SV' salvage, 'ST' storage, 'CY' cycling. The manual also documents 'LQ' liquid limit and 'SP' special; neither appears on this tape.	—
5	`county_regular_indicator`	text	9	`FL-COUNTY-REGULAR-INDICATOR`	'Y' where an exempt field's wells are capped at 200 MCF a day times the days in the cycle. Every row of the tape carries the same value.	—
6	`limited_prod_allowable`	text	10-11	`FL-GAS-LIMITED-PROD-ALLOWABLE`	Which past-production rule limits the wells: '6M' the regular six-month figure, '3M' the highest of the last three cycles, '1M' the most recent cycle, '1D' that cycle as a daily figure, '3D' the highest daily of three cycles, 'NO' none. '3M' on 849,579 rows.	—
7	`balance_rule_code`	text	12	`FL-GAS-BALANCE-RULE-CODE`	Whether the field balances over- and underproduction: 'N' simple balancing, 'R' regular balancing (22,966 rows), 'C', 'S' and 'L' the variants the manual leaves undefined.	—
8	`no_past_production_flag`	text	13	`FL-GAS-NO-PAST-PRODUCTION-FLAG`	'N' blocks the past-production allowable for every well in the field. Check this before the well-level flag.	—
9	`no_highest_daily_flag`	text	14	`FL-GAS-NO-HIGHEST-DAILY-FLAG`	'N' blocks the twelve-month highest-daily-average allowable for every well in the field.	—
10	`highest_daily_cycles`	smallint	15	`FL-GAS-HIGHEST-DAILY-CYCLES`	How many cycles, including this one, the highest-daily block or exception amount still runs for. Zero in every row of this tape.	—
11	`except_high_day_amount`	integer measured in MCF	16-20	`FL-GAS-EXCEPT-HIGH-DAY-AMOUNT`	MCF to use instead of the twelve-month highest daily average. Zero in every row of this tape.	—
12	`past_production_cycles`	smallint	21	`FL-GAS-PAST-PRODUCTION-CYCLES`	How many cycles the past-production block or exception still runs for. Zero in every row of this tape.	—
13	`except_past_prod_amount`	integer measured in MCF	22-26	`FL-GAS-EXCEPT-PAST-PROD-AMOUNT`	MCF to use instead of the past-production amount. Zero in every row of this tape.	—
14	`wells_with_allowables`	integer	27-31	`FL-GAS-WELLS-WITH-ALLOWABLES`	How many wells in the field were given an allowable greater than zero that cycle. Up to 13,804.	—
15	`schedule_column_hdg_cd`	text	32	`FL-GAS-SCHEDULE-COLUMN-HDG-CD`	Which set of column headings the gas proration schedule prints, '1' to '9' — the manual lists them at appendix C. It says what the schedule shows: deliverability, wellhead or bottom-hole pressure, potential, acre-feet.	—
16	`limit_allow_hearing_flag`	text	33	`FL-GAS-LIMIT-ALLOW-HEARING-FLG`	'Y' where the past-production amount was set at a hearing and is calculated under the field's special orders.	—
17	`capability_review_flag`	text	34	`FL-GAS-CAPABILITY-REVIEW-FLAG`	'Y' where only one month of production is reviewed in working out a well's capability.	—
18	`eligible_250_spec_flag`	text	35	`FL-ELIGIBLE-FOR-250-SPEC-FLAG`	'Y' where the field has 0-250 MCF deliverability, no field rules and so needs no G-10. RRC's own screens show the same byte as 'special field rules exist' when it is 'N', which is the opposite reading of the same value.	—
19	`permanent_gas_well_flag`	text	36	`FL-PERMANENT-GAS-WELL-FLAG`	'Y' where the wells are permanently classified gas wells. Most rows carry '0', the mainframe's zero-initialised 'no'.	—
20	`siwh_exception_flag`	text	37	`FL-SIWH-EXCEPTION-FLAG`	'Y' where the field has an exception to the shut-in wellhead pressure requirement. Most rows carry '0'.	—

`fl_gas_field` 40 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset — it is published separately as Field Gas Information.

Record layout for `fl_gas_field` — 40 columns, with byte positions
#	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-GAS-DISC-DATE-1ST-WELL`	Discovery date of the field's first gas well, CCYYMMDD. Filled on 41,376 of the 42,133 gas fields. Eight of them decode to a year before 1900 — 0028, 0048, 0052 — which is what the tape's own digits say rather than a parse error: a two-digit year the mainframe never got a century for. Trim the tail before charting discoveries by year. e.g. 1904-12-31	—
4	`disc_county_code`	smallint	12-14	`FL-GAS-DISC-COUNTY-CODE`	Three-digit RRC county code the field was discovered in. Zero where the mainframe never recorded one. Stored as a SMALLINT, so pad it back to three digits before joining to a county list. e.g. 383	—
5	`perf_1st_well`	integer measured in ft	15-19	`FL-GAS-PERF-1ST-WELL`	Depth in feet at which the discovery well was perforated — the closest thing this file has to a field depth. e.g. 6785	—
6	`type_field_code`	text	20	`FL-TYPE-FIELD-CODE`	'A' associated with an oil field, 'N' non-associated. The manual says the item is no longer maintained; the tape still carries 34,600 N and 7,533 A. e.g. A	—
7	`testing_county`	smallint	29-31	`FL-GAS-TESTING-COUNTY`	County whose testing cycle this field tests on, as a three-digit code. Statewide rule 53 puts every field on a county's cycle, and it is not always the county the field is in.	—
8	`test_frequency`	text	32	`FL-GAS-TEST-FREQUENCY`	'A' annual or 'S' semi-annual G-10 testing. 39,374 fields test semi-annually. e.g. A	—
9	`pri_test_month`	smallint	33-34	`FL-GAS-PRI-ALTER-TEST-MONTH`	Alternate primary testing month, 01-12, where the field does not test with its test county's cycle. Zero means it does.	—
10	`sec_test_month`	smallint	35-36	`FL-GAS-SEC-ALTER-TEST-MONTH`	Alternate secondary testing month for a semi-annual field, 01-12. Zero means it tests with the county.	—
11	`pri_test_g10_required`	text	37	`FL-PRI-TEST-MON-G10-REQUIRE`	What the G-10 must report in the primary test month: 'B' deliverability, flowing and shut-in wellhead pressure; 'C' deliverability and flowing pressure; 'D' adds potential; 'E' adds bottom-hole pressure; 'F' both; 'G' deliverability only; 'J' annual testing; 'K' a commingling test. Every gas well reports gas gravity whatever the code. e.g. J	—
12	`sec_test_g10_required`	text	38	`FL-SEC-TEST-MON-G10-REQUIRE`	The same code list for the secondary test month. 'K' — the commingling test — is what an annually tested field carries here. e.g. K	—
13	`commingling_counter`	integer	41-45	`FL-GAS-COMMINGLING-COUNTER`	Number of wells commingled above ground in the field. The manual says it is not maintained, and 41,000 of the 42,133 rows are zero.	—
14	`exempt_min_gor`	text	46	`FL-GAS-EXEMPT-MINIMUM-GOR`	'Y' on the 151 fields exempt from the minimum gas-oil ratio, which may produce more than one barrel of condensate per 100,000 cubic feet of gas without being reclassified as oil wells.	—
15	`offshore_code`	text	47-48	`FL-OFFSHORE-CODE`	Where the field's discovery well sits: 'L' land (40,823 fields), 'B' bays and estuaries, 'SO' state offshore, 'LB' land and bays, 'BO' bays and offshore, 'AL' all three, 'SF' state and federal. e.g. L	—
16	`cum_gas_prod_to_conv`	bigint measured in MCF	50-56	`FL-CUM-GAS-PRODUCTION-TO-CONV`	Cumulative gas well 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-2 reports filed twelve months or more late. e.g. 1217098	—
17	`cum_cond_prod_to_conv`	bigint measured in bbl	57-62	`FL-CUM-COND-PRODUCTION-TO-CONV`	Cumulative condensate 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-2 reports filed twelve months or more late.	—
18	`cum_gas_allow_to_conv`	bigint measured in MCF	63-69	`FL-CUM-GAS-ALLOWABLE-TO-CONV`	Cumulative 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-2 reports filed twelve months or more late.	—
19	`cum_liq_allow_to_conv`	bigint measured in bbl	70-76	`FL-CUM-LIQ-ALLOWABLE-TO-CONV`	Cumulative liquid 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-2 reports filed twelve months or more late. Non-zero on seven fields only.	—
20	`off_file_cum_gas_allow`	bigint measured in MCF	77-83	`FL-OFF-FILE-CUM-GAS-ALLOWABLE`	Cumulative gas allowable in MCF from January 1983 up to the months still on the tape. Anything earlier is in the conversion total.	—
21	`off_file_cum_liq_allow`	bigint measured in bbl	84-90	`FL-OFF-FILE-CUM-LIQ-ALLOWABLE`	Cumulative liquid allowable in barrels from January 1983 up to the months still on the tape. Anything earlier is in the conversion total. Non-zero on six fields only.	—
22	`off_file_cum_gas_prod`	bigint measured in MCF	91-97	`FL-OFF-FILE-CUM-GAS-PROD`	Cumulative gas well gas production in MCF from January 1983 up to the months still on the tape. Anything earlier is in the conversion total. Kept apart from the conversion total because it DOES include every retro P-2 filed.	—
23	`off_file_cum_cond_prod`	bigint measured in bbl	98-103	`FL-OFF-FILE-CUM-COND-PROD`	Cumulative condensate production in barrels from January 1983 up to the months still on the tape. Anything earlier is in the conversion total. Includes retro P-2 reports.	—
24	`on_file_cum_gas_allow`	bigint measured in MCF	104-110	`FL-ON-FILE-CUM-GAS-ALLOWABLE`	The latest 24 months of 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.	—
25	`on_file_cum_liq_allow`	bigint measured in bbl	111-117	`FL-ON-FILE-CUM-LIQ-ALLOWABLE`	The latest 24 months of liquid 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. Zero in every row.	—
26	`on_file_cum_gas_prod`	bigint measured in MCF	118-124	`FL-ON-FILE-CUM-GAS-PROD`	The latest 24 months of reported gas well 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.	—
27	`on_file_cum_cond_prod`	bigint measured in bbl	125-130	`FL-ON-FILE-CUM-COND-PROD`	The latest 24 months of reported condensate 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.	—
28	`ytd_cum_gas_allow`	bigint measured in MCF	131-136	`FL-YR-TO-DT-CUM-GAS-ALLOWABLE`	Gas allowable so far this calendar year, in MCF. The latest two months are not in it, for the same reporting lag.	—
29	`ytd_cum_liq_allow`	bigint measured in bbl	137-142	`FL-YR-TO-DT-CUM-LIQ-ALLOWABLE`	Liquid allowable so far this calendar year, in barrels. The latest two months are not in it, for the same reporting lag. Zero in every row.	—
30	`ytd_cum_gas_prod`	bigint measured in MCF	143-148	`FL-YR-TO-DT-CUM-GAS-PROD`	Reported gas well gas production so far this calendar year, in MCF. The latest two months are not in it, for the same reporting lag.	—
31	`ytd_cum_cond_prod`	bigint measured in bbl	149-154	`FL-YR-TO-DT-CUM-COND-PROD`	Reported condensate production so far this calendar year, in barrels. The latest two months are not in it, for the same reporting lag.	—
32	`salt_dome_exemption`	text	155	`FL-SALT-DOME-EXEMPTION`	'Y' on the 69 gas fields classified as salt domes, which the statewide spacing rule does not apply to.	—
33	`county_regular_exemption`	text	156	`FL-COUNTY-REGULAR-EXEMPTION`	'Y' on the 3,333 fields exempt as county regular — the small shallow fields of Districts 7B and 09 and McCulloch County, which have their own spacing rules and allowable schedule.	—
34	`ledger_month`	smallint	157-158	`FL-LEDGER-MONTH`	The current ledger month: the most recent month RRC has production reports for. RRC-internal, and a property of the tape rather than of the field — every row of the August 2026 file says 6.	—
35	`new_gas_field_appr_date`	date	159-166	`FL-NEW-GAS-FLD-APPR-DATE`	Date the Commission approved the field as a new gas field, CCYYMMDD. Filled on 7,408 fields.	—
36	`cum_prod_prior_1970`	bigint measured in MCF	167-173	`FL-CUM-PROD-PRIOR-1970`	Everything the field produced before 1970, in MCF, as one lump sum. Zero or absent on the fields discovered since.	—
37	`schedule_start_date`	date	174-181	`FL-GAS-SCHEDULE-START-DATE`	When the field first appeared on the gas proration schedule, CCYYMMDD. Filled on 7,016 fields, 1945 onwards.	—
38	`consolidated_field_flag`	text	182	`FL-GAS-CONSOLIDATED-FIELD-FLAG`	'Y' where this field is a consolidation of earlier ones. 4,553 fields.	—
39	`correlative_interval_from`	integer measured in ft	183-187	`FL-GAS-CORRELATIVE-INTER-FROM`	Top of the correlative interval in feet — the depth window the field's rules apply to. Filled on 602 fields. e.g. 6865	—
40	`correlative_interval_to`	integer measured in ft	188-192	`FL-GAS-CORRELATIVE-INTER-TO`	Bottom of the correlative interval, in feet. Filled on the same 602 fields. e.g. 10605	—

`fl_gas_field_rule` 28 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset — it is published separately as Field Gas Rules (Mainframe).

Record layout for `fl_gas_field_rule` — 28 columns, with byte positions
#	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. 11	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. 53411426	—
3	`rule_seq` key	smallint	—	—	Which rule under this field, counting from 1 in the order the tape carries them — newest first, the undated rule last. EZRRC's column, not RRC's: the tape keys a rule on 99999999 minus its effective date, and 7,496 of the 13,951 gas rules and 5,473 of the 8,565 oil rules carry the bare 99999999, meaning no effective date at all. A date missing from more than half the rows cannot be the key, so position is. e.g. 1	—
4	`rule_effective_date`	date	3-10	`FL-GAS-RULE-EFFECTIVE-KEY`	When this gas rule took effect. The tape stores 99999999 minus the date, so the rules sort newest first; 7,496 of the 13,951 carry the bare 99999999 and decode to null, which is the standing rule with no order date behind it. The 2,148 dates present run from 1933 to 2066 — the far end is what the mainframe was given, not a rule that starts in forty years.	—
5	`proration_eff_date`	date	11-18	`FL-GAS-PRORATION-EFF-DATE`	Date the allocation formula took effect for this prorated field, CCYYMMDD on the tape. Null on the fields that were never prorated.	—
6	`proration_suspend_date`	date	19-26	`FL-GAS-PRORATION-SUSPEND-DATE`	When the allocation formula was suspended for the field. Filled on 2,992 rules.	—
7	`rules_rescinded_date`	date	27-34	`FL-GAS-RULES-RESCINDED-DATE`	When the field rules were rescinded and the field went back to statewide spacing. Filled on 1,180 rules, every one of them 2000-05-01 — a bulk rescission rather than 1,180 separate ones.	—
8	`docket_suffix`	text	35-37	`FL-GAS-DOCKET-SUFFIX`	Three characters categorising the docket the rule came from. EMPTY in every row; the docket number itself is in docket_number.	—
9	`spacing_to_lease_line`	smallint measured in ft	38-41	`FL-GAS-SPACING-TO-LEASE-LINE`	Feet a well must be from the nearest lease line under this field's rules. Statewide rule 37 says 467. Zero means the rule sets no lease-line distance, not zero feet. e.g. 440	—
10	`spacing_to_well`	smallint measured in ft	42-45	`FL-GAS-SPACING-TO-WELL`	Feet a well must be from the nearest other well under this field's rules. Statewide rule 37 says 1,200. Zero means unset. e.g. 880	—
11	`injection_credit`	text	46	`FL-GAS-INJECTION-CREDIT`	'Y' where gas injected back into the reservoir is credited against the field's production. 150 rules.	—
12	`acres_per_unit`	numeric measured in acres	47-52	`FL-GAS-ACRES-PER-UNIT`	Acres dedicated to one well — the minimum proration unit on which a well may be drilled. Statewide rule 37 says 40. Two decimal places. e.g. 42.50	—
13	`tolerance_acres`	numeric measured in acres	53-57	`FL-GAS-TOLERANCE-ACRES`	Acreage left over in a lease once every proration unit has been carved out, which the operator may ask to be spread among the other wells or given to the last well drilled. Two decimal places.	—
14	`casing_code`	text	58	`FL-GAS-CASING-CODE`	What sets the required casing depth: 'F' the field rules, 'W' the Texas Department of Water Resources (now the TCEQ). Null where the rule says nothing. e.g. W	—
15	`casing_depth`	integer measured in ft	59-63	`FL-GAS-CASING-DEPTH`	Depth in feet the casing of the discovery well was set to. Zero on the great majority — read it with casing_code, which usually says the water agency sets the depth rather than the field rule.	—
16	`casing_remarks`	text	64-95	`FL-GAS-CASING-REMARKS`	Free text a proration analyst wrote about the casing requirement, up to 32 characters ('TDWR LTR.', 'T. W. C.'). e.g. T. W. C.	—
17	`diagonal_code`	text	96-97	`FL-GAS-DIAGONAL-CODE`	How the diagonal is measured: 'CC' corner to corner, 'WC' well to corner. Null where no diagonal applies. e.g. CC	—
18	`diagonal`	integer measured in ft	98-102	`FL-GAS-DIAGONAL`	The diagonal of the proration unit in feet — the second half of a density rule, which stops a unit being a long thin strip. Zero means none; 99999 is the mainframe's 'no limit'.	—
19	`diagonal_remarks`	text	103-123	`FL-GAS-DIAGONAL-REMARKS`	Free text about the diagonal, up to 21 characters.	—
20	`field_allow_tolerance`	smallint measured in MCF	124-126	`FL-GAS-FIELD-ALLOW-TOLERANCE`	How far the allowables handed to the wells may add up short of the field total before the calculation stops, in MCF per well. The standard deviation is 1.5 MCF per well.	—
21	`field_transfer_allow`	text	127	`FL-GAS-FIELD-TRANSFER-ALLOW`	'Y' where allowable may be transferred from a poor well to one that can produce it. Rare, and RRC has to approve it: 66 rules. e.g. Y	—
22	`allowable_basis`	text	128	`FL-GAS-ALLOWABLE-BASIS`	'G' where the allowable comes from the G-7 and T-3 nomination process, 'A' where it is an average of past production. Every rule that carries a value carries 'G'. e.g. G	—
23	`no_months_averaged`	smallint	129-130	`FL-GAS-NO-MONTHS-AVERAGED`	How many months of past production were averaged to set the allowable. The manual says the process is not in use and every row is zero.	—
24	`field_text`	text	131-190	`FL-GAS-FIELD-TEXT`	Free text a proration analyst wrote about this rule, up to 60 characters. It carries the things the fixed columns cannot — optional unit sizes, what has to be filed with a plat, which older field a rule was inherited from. e.g. OIL FIELD CARRIED AS LEVELLAND FIELD/MULTI 49B	—
25	`old_allocation_code`	text	191	`FL-GAS-OLD-ALLOCATION-CODE`	The pre-1980s allocation-formula code, one character, listed at the manual's appendix C ('2' is 100% acres, '%' a percentage split on AP and NP fields). RRC-internal, and superseded by the allocation formula terms in fl_gas_alloc_formula.	—
26	`class_pending_code`	text	192-193	`FL-GAS-CLASS-PENDING-CODE`	The allowable type that takes effect when the allocation formula is suspended. One rule in the state carries it.	—
27	`docket_number`	text	194-203	`FL-GAS-DOCKET-NUMBER`	The Commission docket the rule came out of, written district-dash-number ('7C-0297471', '08-72572'). This is the number to look the order up under in the oil and gas docket dataset. e.g. 8A-84804	—
28	`rules_not_reliable_flag`	text	204	`FL-GAS-RULES-NOT-RELIABLE-FLAG`	'Y' when RRC does not stand behind the transcribed rule. Empty in every row of the August 2026 tape, gas and oil alike.	—

`fl_gas_market_demand` 17 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset.

Record layout for `fl_gas_market_demand` — 17 columns, with byte positions
#	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.	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.	—
3	`sched_yyyymm` key	integer	3-8	`FL-MKT-DEMAND-SCHED-DATE`	The schedule month this forecast is for, as yyyymm. 412 months are on the tape, and all but two of the 507,251 rows fall between 1983 and 2026-09; two rows decode to 1922-11, which is a corrupt key rather than a forecast from 1922.	—
4	`forecast`	integer measured in MCF	9-13	`FL-MKT-DEMAND-FORECAST`	The field's initial market demand forecast in MCF: the sum of the forecasts calculated for each operator in it. Prorated fields only, and based on the previous year's production.	—
5	`capability`	integer measured in MCF	14-18	`FL-MKT-DEMAND-CAPABILITY`	Total capability of all the wells in the field, in MCF — what the field could produce if the market took it.	—
6	`forecast_corr_adj`	integer measured in MCF	19-23	`FL-MKT-DMD-FORECAST-CORR-ADJ`	The forecast correction adjustment: current month production, less the third month previous adjusted forecast, plus the supplemental change and the commission adjustment, less special allowable underage.	—
7	`supp_chg_adj`	integer measured in MCF	24-28	`FL-MKT-DEMAND-SUPP-CHG-ADJ`	Net adjustment to allowables from three months previous, as set by the gas well supplements the Commission issued.	—
8	`commission_adj`	integer measured in MCF	29-33	`FL-MKT-DEMAND-COMMISSION-ADJ`	The Commission's own adjustment to the reservoir market demand, made to balance it against capability or to correct the initial figure.	—
9	`rev_forecast`	integer measured in MCF	34-38	`FL-MKT-DEMAND-REV-FORECAST`	The revised reservoir forecast: the sum of the operators' revised forecasts.	—
10	`adj_res_forecast`	integer measured in MCF	39-43	`FL-MKT-DMD-ADJ-RES-FORECAST`	The sum of the operator forecasts after each has been adjusted down to that operator's capability.	—
11	`calc_res_forecast`	integer measured in MCF	44-48	`FL-MKT-DMD-CALC-RES-FORECAST`	Calculated reservoir market demand: the adjusted forecast plus the correction and supplemental adjustments from three months previous.	—
12	`total_res_forecast`	integer measured in MCF	49-53	`FL-MKT-DMD-TOTAL-RES-FORECAST`	Total reservoir market demand after every adjustment — the calculated demand plus the Commission adjustment.	—
13	`hearing_spec_amt`	integer measured in MCF	54-58	`FL-MKT-DMD-HEARING-SPEC-AMT`	Total of the special well allowables set by hearing for the reservoir.	—
14	`third_month_previous`	integer measured in MCF	59-63	`FL-MKT-DMD-3RD-MONTH-PREVIOUS`	Gas well gas the field produced in the third month before the schedule month, in MCF. Production reporting lags allowables, so this is the newest complete month available when the demand is set.	—
15	`special_underage`	integer measured in MCF	64-72	`FL-MKT-DMD-SPECIAL-UNDERAGE`	Underage from special-allowable wells. Stored as zoned-signed DISPLAY rather than packed, so it is the one negative-only column here; from May 1994 it counts the current production month rather than the schedule month.	—
16	`precalc_allowable`	integer measured in MCF	73-77	`FL-MKT-DMD-PRECALC-ALLOWABLE`	Reservoir allowable calculations kept under a 1963 special order for the Fort Wilshire gas field alone. Zero in every row of this tape.	—
17	`twelve_month_peak`	integer measured in MCF	78-82	`FL-MKT-DMD-12-MONTH-PEAK`	The twelve-month peak amount, which the manual says is used for the Panhandle West field only. Filled on 211,965 rows; where the mainframe never wrote the packed field it holds EBCDIC zeros and loads as null rather than 0.	—

`fl_gas_market_demand_remark` 6 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset.

Record layout for `fl_gas_market_demand_remark` — 6 columns, with byte positions
#	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.	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.	—
3	`sched_yyyymm` key	integer	—	`FL-MKT-DEMAND-SCHED-DATE`	The schedule month of the parent market demand forecast, as yyyymm.	—
4	`line_no` key	smallint	—	—	Line within the schedule month and kind, from 1. EZRRC's column: the manual says the segment recurs with no key at all, so position on the tape is what tells two lines apart. Four lines is the most any month carries.	—
5	`remark_kind` key	text	—	—	Which of the two remark segments the line came from: 'C' the 05 commission-adjustment remark (115,052 lines), 'S' the 06 supplement-adjustment remark (17,260). The two share one 80-byte layout and one table; without this column they would be indistinguishable.	—
6	`remark_text`	text	3-82	—	The line itself, up to 80 characters — free text a proration analyst wrote about how the reservoir's market demand was worked out for that cycle. It prints on the allocation sheet.	—

`fl_gas_operator_market_demand` 19 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset.

Record layout for `fl_gas_operator_market_demand` — 19 columns, with byte positions
#	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.	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.	—
3	`sched_yyyymm` key	integer	—	`FL-MKT-DEMAND-SCHED-DATE`	The schedule month of the parent field forecast, as yyyymm, carried down from it.	—
4	`operator_no` key join	integer	3-8	`FL-OPERATOR-NUMBER`	The operator's six-digit P-5 organization number, and the only place this whole file names a company. 6,683 distinct operators appear and 6,682 of them are in the P-5 organization dataset, which keys on the same number as an integer, so the join needs no cast. It is not in the join graph because that joins one dataset's primary table to another's and this is a child table.	—
5	`forecast`	integer measured in MCF	9-13	`FL-OPR-MKT-DMD-FORECAST`	The operator's initial market demand forecast for the field, in MCF, based on the previous year's production.	—
6	`opt_forecast`	integer measured in MCF	14-18	`FL-OPR-MKT-DMD-OPT-FORECAST`	The optional forecast the operator filed for its own wells. It cannot exceed the wells' total capability.	—
7	`capability`	integer measured in MCF	19-23	`FL-OPR-CAPABILITY`	Total capability of the operator's wells in the reservoir: the highest six-month production, plus G-10 capability, plus GC-1 substitute capability.	—
8	`substitute_capability`	integer measured in MCF	24-28	`FL-OPR-SUBSTITUTE-CAPABILITY`	Substitute capability as filed on form GC-1 and used in the operator's forecast.	—
9	`adj_forecast`	integer measured in MCF	29-33	`FL-OPR-MKT-DMD-ADJ-FORECAST`	The forecast adjusted down to capability — the lesser of the operator's capability and its optional or revised forecast.	—
10	`rev_forecast`	integer measured in MCF	34-38	`FL-OPR-MKT-DMD-REV-FORECAST`	The forecast revised for new production information or for wells added to or removed from the reservoir.	—
11	`g10_total`	integer measured in MCF	39-43	`FL-OPR-MKT-DMD-G10-TOTAL`	Total G-10 capability counted towards this operator's forecast, in MCF.	—
12	`high_prod_total`	integer measured in MCF	44-48	`FL-OPR-MKT-DMD-HIGH-PROD-TOTAL`	Sum of the wells' highest six months of production, counted towards the forecast.	—
13	`high_prod_wells`	integer	49-51	`FL-OPR-MKT-DMD-HIGH-PROD-WELLS`	How many wells contributed to that highest-six-months figure.	—
14	`sub_cap_wells`	integer	52-54	`FL-OPR-MKT-DMD-SUB-CAP-WELLS`	How many wells contributed substitute capability.	—
15	`g10_wells`	integer	55-57	`FL-OPR-MKT-DMD-G10-WELLS`	How many wells contributed G-10 capability.	—
16	`delq_p2_wells`	integer	58-60	`FL-OPR-MKT-DMD-DELQ-P2-WELLS`	How many of the operator's wells in the reservoir have a delinquent form P-2.	—
17	`third_mo_prev`	integer measured in MCF	61-65	`FL-OPR-MKT-DMD-3RD-MO-PREV`	What the operator's wells in the reservoir produced three months before the schedule month, in MCF.	—
18	`md1_received_flag`	text	66	`FL-MD-1-RECEIVED-FLAG`	'Y' where the Commission has received the operator's form MD-1. The manual prints no position for this byte; it is at 66 on the tape, which pushes the twelve-month peak to 67 — read off the bytes rather than the manual.	—
19	`twelve_month_peak`	integer measured in MCF	67-71	`FL-OPR-MKT-DMD-12-MONTH-PEAK`	The operator's twelve-month peak amount, used for the Panhandle West field. Filled on 323,533 of the 776,522 rows; elsewhere the packed field holds EBCDIC zeros and loads as null.	—

`fl_gas_optional_rule` 11 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset.

Record layout for `fl_gas_optional_rule` — 11 columns, with byte positions
#	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.	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.	—
3	`rule_seq` key	smallint	—	—	Which rule under this field, counting from 1 in the order the tape carries them — newest first, the undated rule last. EZRRC's column, not RRC's: the tape keys a rule on 99999999 minus its effective date, and 7,496 of the 13,951 gas rules and 5,473 of the 8,565 oil rules carry the bare 99999999, meaning no effective date at all. A date missing from more than half the rows cannot be the key, so position is.	—
4	`opt_key` key	smallint	3-4	`FL-GAS-OPT-KEY`	Which optional rule under the parent rule, 1 to 4. RRC's own two-digit key for the segment.	—
5	`space_to_lease_line`	smallint measured in ft	5-8	`FL-GAS-OPT-SPACE-TO-LEASE-LINE`	Feet from the nearest lease line under this optional unit.	—
6	`space_to_well`	smallint measured in ft	9-12	`FL-GAS-OPT-SPACE-TO-WELL`	Feet from the nearest well under this optional unit.	—
7	`acres_per_unit`	numeric measured in acres	13-18	`FL-GAS-OPT-ACRES-PER-UNIT`	Acres per well under this optional unit, two decimal places.	—
8	`tolerance_acres`	numeric measured in acres	19-23	`FL-GAS-OPT-TOLERANCE-ACRES`	Tolerance acreage allowed on this optional unit.	—
9	`diagonal_code`	text	24-25	`FL-GAS-OPT-DIAGONAL-CODE`	'CC' corner to corner or 'WC' well to corner, as for the main rule.	—
10	`diagonal_feet`	integer measured in ft	26-30	`FL-GAS-OPT-DIAGONAL-FEET`	Diagonal of the optional proration unit, in feet.	—
11	`field_text`	text	31-77	`FL-GAS-OPT-FIELD-TEXT`	Free text about the optional rule, up to 47 characters. Filled on 100 of the 1,322 gas rows and 248 of the 1,121 oil ones.	—

`fl_gas_remark` 11 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset.

Record layout for `fl_gas_remark` — 11 columns, with byte positions
#	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.	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.	—
3	`remark_no` key	smallint	3-5	`FL-GAS-REMARK-NUMBER`	Which remark on this field, as RRC numbers them. With line_no it is the key; a remark of several lines repeats the number.	—
4	`line_no` key	smallint	6-8	`FL-GAS-REMARK-LINE-NO`	Line within the remark, from 1. A remark can run to 78 lines.	—
5	`print_annual_flag`	text	9	`FL-GAS-PRINT-ANNUAL-FLAG`	'Y' if this line prints on the annual report — the yearly production summary for the field.	—
6	`print_ledger_flag`	text	10	`FL-GAS-PRINT-LEDGER-FLAG`	'Y' if this line prints on the ledger report. The manual says the flag is not in use and the tape agrees: every row that carries a value at all carries the same one.	—
7	`print_schedule_flag`	text	11	`FL-GAS-PRINT-SCHEDULE-FLAG`	'Y' if this line prints on the monthly proration schedule, the document that tells an operator what each well may produce.	—
8	`print_on_line_flag`	text	12	`FL-GAS-PRINT-ON-LINE-FLAG`	'Y' if this line shows on RRC's own terminal screens.	—
9	`print_asheet_flag`	text	13	`FL-GAS-PRINT-ASHEET-FLAG`	'Y' if this line prints on the allocation sheet, the monthly worksheet RRC uses to set a prorated gas field's total allowable. The gas segment has this fifth print flag; the oil one does not.	—
10	`remark_date`	date	14-21	`FL-GAS-REMARK-DATE`	Date the remark was last written, CCYYMMDD. Null where the mainframe never stamped one.	—
11	`remark_text`	text	22-87	`FL-GAS-REMARK-TEXT`	The line itself, up to 66 characters as the tape wraps it.	—

`fl_map` 3 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset.

Record layout for `fl_map` — 3 columns, with byte positions
#	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.	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.	—
3	`map_number_index` key	text	3-8	`FL-MAP-NUMBER-INDEX`	The index RRC's Mapping and Graphics section gave the field map this field appears on, up to six characters. 767 distinct maps cover 3,854 of the 65,826 fields.	—

`fl_map_county` 5 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset.

Record layout for `fl_map_county` — 5 columns, with byte positions
#	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.	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.	—
3	`map_number_index` key	text	—	`FL-MAP-NUMBER-INDEX`	The parent map index this county belongs to.	—
4	`ordinal` key	smallint	—	—	Which of the six OCCURS county slots on the map record this came from, from 1. Zero slots are dropped rather than loaded, so a map with two counties has two rows.	—
5	`county_code`	smallint	—	`FL-MAP-COUNTY-CODE`	A county the field occupies on this map sheet, as a three-digit RRC county code held in a SMALLINT.	—

`fl_oil_alloc_factor` 6 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset.

Record layout for `fl_oil_alloc_factor` — 6 columns, with byte positions
#	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.	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.	—
3	`cycle_yyyymm` key	integer	—	`FL-OIL-FACTOR-CYCLE-KEY`	The allowable cycle this row is for, as yyyymm. The tape writes it as the ledgers' nines-complement key (9927 is January 1993, counting down), which upstream decodes. Twenty-six cycles are on the tape at a time: 202407 through 202608 in the August 2026 file. Older cycles fall off, so a history has to be accumulated from snapshots.	—
4	`seq` key	smallint	—	—	Position of this factor under the cycle's factor root, from 1. EZRRC's column: the factors are consecutive records with no key of their own. Three is the most any cycle carries.	—
5	`factor_code`	smallint	3-4	`FL-OIL-FACTOR-CODE`	What the factor measures: 01 per well (450,676 rows), 02 acres (177,282), 03 acre feet, 04 bottom-hole pressure, 05 original potential, 06 current potential.	—
6	`factor`	numeric	5-12	`FL-OIL-ALLOCATION-FACTOR`	The numeric factor used in calculating the field allowable, to seven decimal places.	—

`fl_oil_alloc_formula` 6 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset.

Record layout for `fl_oil_alloc_formula` — 6 columns, with byte positions
#	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.	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.	—
3	`rule_seq` key	smallint	—	—	Which rule under this field, counting from 1 in the order the tape carries them — newest first, the undated rule last. EZRRC's column, not RRC's: the tape keys a rule on 99999999 minus its effective date, and 7,496 of the 13,951 gas rules and 5,473 of the 8,565 oil rules carry the bare 99999999, meaning no effective date at all. A date missing from more than half the rows cannot be the key, so position is.	—
4	`seq` key	smallint	—	—	Position of this term in the formula, from 1. EZRRC's column: the terms are consecutive records on the tape with no key of their own. Three terms is the most any gas formula uses, two for oil.	—
5	`allow_percent_factor`	numeric	3-5	`FL-OIL-ALLOW-PERCENT-FACTOR`	The weight this term carries in the formula, as a fraction: 0.50 is 50 per cent. The terms of a rule sum to 1.00 — on every gas rule but one and every oil rule but three, which come to 0.99 through rounding.	—
6	`allocation_factor_code`	smallint	6-7	`FL-OIL-ALLOCATION-FCTR-CODE`	What the term measures: 01 per well (3,712 terms), 02 acres (7,456), 03 acre feet, 04 bottom-hole pressure, 05 original potential, 06 current potential, 07 acre pounds, 08 county regular, 09 the 1947 yardstick, 10 the 1965 yardstick, 11 rock pressure, 12 acre foot pounds.	—

`fl_oil_county` 3 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset.

Record layout for `fl_oil_county` — 3 columns, with byte positions
#	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.	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.	—
3	`county_code` key	smallint	3-5	`FL-OIL-COUNTY-CODE`	Three-digit RRC county code of a county this field lies in. The 254 onshore counties take the odd numbers 001-507; the 23 offshore and bay areas take 600-606 and 700-715. Stored as a SMALLINT, so it has lost its leading zeros: cast and pad before joining to a county code set or to a FIPS code.	—

`fl_oil_cycle` 10 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset.

Record layout for `fl_oil_cycle` — 10 columns, with byte positions
#	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.	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.	—
3	`cycle_yyyymm` key	integer	3-6	`FL-OIL-CYCLE-KEY`	The allowable cycle this row is for, as yyyymm. The tape writes it as the ledgers' nines-complement key (9927 is January 1993, counting down), which upstream decodes. Twenty-six cycles are on the tape at a time: 202407 through 202608 in the August 2026 file. Older cycles fall off, so a history has to be accumulated from snapshots.	—
4	`type_field_code`	text	7	`FL-OIL-TYPE-FIELD-CODE`	How the oil field was classified for that cycle: 'R' regular (864,936 rows), 'I' inactive, 'S' salt dome, 'C' county regular, 'M' reservoir maximum efficiency rate, 'N' new pool exempt.	—
5	`yardstick`	text	8	`FL-YARDSTICK`	Which yardstick schedule sets the top allowable per well: 'A' the 1947 yardstick, 'B' the 1965 one (443,868 rows), 'C' the offshore yardstick, 'N' a discovery allowable, 'X' none. A yardstick reads an allowable off the well's depth and its acreage.	—
6	`regular_allow_calc_flag`	text	9	`FL-REGULAR-ALLOW-CALC-FLAG`	'Y' where the regular allowable calculation runs for this field this cycle.	—
7	`top_allowable_cd`	text	10	`FL-OIL-TOP-ALLOWABLE-CD`	'R' where the field has a regular top allowable, 'M' where it has a maximum efficiency rate set at a hearing. 74,733 rows are 'M'.	—
8	`top_allowable_amt`	integer measured in bbl	11-14	`FL-OIL-TOP-ALLOWABLE-AMT`	The most a single well in the field is granted to produce, in barrels — the figure the yardstick or the hearing set, and the one the proration schedule prints against each well. The manual does not say whether it is a daily or a monthly figure, so this does not either.	—
9	`res_mer_amount`	integer measured in bbl	15-18	`FL-OIL-RES-MER-AMOUNT`	The reservoir's maximum efficiency rate in barrels, where one was set at a hearing, prorated among the wells.	—
10	`county_regular_flag`	text	19	`FL-OIL-COUNTY-REGULAR-FLAG`	'Y' where the field's allowable is calculated on the county regular schedule — the small shallow fields of Districts 7B and 09 and McCulloch County.	—

`fl_oil_factor_root` 8 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset.

Record layout for `fl_oil_factor_root` — 8 columns, with byte positions
#	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.	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.	—
3	`cycle_yyyymm` key	integer	3-6	`FL-OIL-FACTOR-CYCLE-KEY`	The allowable cycle this row is for, as yyyymm. The tape writes it as the ledgers' nines-complement key (9927 is January 1993, counting down), which upstream decodes. Twenty-six cycles are on the tape at a time: 202407 through 202608 in the August 2026 file. Older cycles fall off, so a history has to be accumulated from snapshots.	—
4	`prod_fact_exempt_flag`	text	7	`FL-OIL-PROD-FACT-EXEMPT-FLAG`	'Y' where the field is exempt from the statewide production factor, 'N' where it is subject to it.	—
5	`prod_factor`	numeric	8-15	`FL-OIL-PROD-FACTOR`	The statewide production factor set at the monthly demand hearing, to seven decimals — the fraction of the top allowable the state lets oil fields produce. 1.0000000 in every row of this tape, which is to say the factor has not cut allowables in any of the 26 cycles on it.	—
6	`split_prod_factor`	numeric	16-23	`FL-OIL-SPLIT-PROD-FACTOR`	A second production factor for the month, where a different one took effect part-way through. Zero in every row of this tape.	—
7	`split_prod_factor_date`	smallint	24-25	`FL-OIL-SPLIT-PROD-FACTOR-DATE`	Day of the month the second factor took effect. Zero in every row.	—
8	`unworkable_res_mer`	text	26	`FL-OIL-UNWORKABLE-RES-MER`	Marks an oil field that can no longer reach its maximum efficiency rate because the reservoir is depleted. 1,248 rows carry 'Y'; most carry 'N' or the mainframe's '0'.	—

`fl_oil_field` 34 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset — it is published separately as Field Oil Information.

Record layout for `fl_oil_field` — 34 columns, with byte positions
#	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.	—

`fl_oil_field_rule` 22 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset — it is published separately as Field Oil Rules (Mainframe).

Record layout for `fl_oil_field_rule` — 22 columns, with byte positions
#	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	`rule_seq` key	smallint	—	—	Which rule under this field, counting from 1 in the order the tape carries them — newest first, the undated rule last. EZRRC's column, not RRC's: the tape keys a rule on 99999999 minus its effective date, and 7,496 of the 13,951 gas rules and 5,473 of the 8,565 oil rules carry the bare 99999999, meaning no effective date at all. A date missing from more than half the rows cannot be the key, so position is. e.g. 1	—
4	`rule_effective_date`	date	3-10	`FL-OIL-RULE-EFFECTIVE-KEY`	When this oil rule took effect, decoded from the tape's 99999999 minus the date. Null on 5,473 of the 8,565 rules — the standing rule with no order date behind it. e.g. 2016-03-08	—
5	`proration_eff_date`	date	11-18	`FL-OIL-PRORATION-EFF-DATE`	Date the allocation formula took effect for this prorated field, CCYYMMDD on the tape. Null on the fields that were never prorated. e.g. 2016-03-01	—
6	`rule_suspend_date`	date	19-26	`FL-OIL-RULE-SUSPEND-DATE`	When the rule was suspended or rescinded and the field reverted to statewide spacing. Filled on 1,102 rules, and it is usually the effective date of the rule that replaced it.	—
7	`docket_suffix`	text	35-37	`FL-OIL-DOCKET-SUFFIX`	Three characters categorising the docket. EMPTY in every row.	—
8	`spacing_to_lease_line`	smallint measured in ft	38-41	`FL-OIL-SPACING-TO-LEASE-LINE`	Feet a well must be from the nearest lease line under this field's rules. Statewide rule 37 says 467. Zero means the rule sets no lease-line distance, not zero feet. e.g. 330	—
9	`spacing_to_well`	smallint measured in ft	42-45	`FL-OIL-SPACING-TO-WELL`	Feet a well must be from the nearest other well under this field's rules. Statewide rule 37 says 1,200. Zero means unset.	—
10	`acres_per_unit`	numeric measured in acres	46-51	`FL-OIL-ACRES-PER-UNIT`	Acres dedicated to one well — the minimum proration unit on which a well may be drilled. Statewide rule 37 says 40. Two decimal places. e.g. 80.00	—
11	`tolerance_acres_code`	text	52	`FL-OIL-TOLERANCE-ACRES-CODE`	Who gets the leftover acreage: 'L' the last well drilled (6,710 rules), 'E' each well in the lease (237). e.g. E	—
12	`tolerance_acres`	numeric measured in acres	53-57	`FL-OIL-TOLERANCE-ACRES`	Acreage left over in a lease once every proration unit has been carved out, which the operator may ask to be spread among the other wells or given to the last well drilled. Two decimal places. e.g. 80.00	—
13	`casing_code`	text	58	`FL-OIL-CASING-CODE`	What sets the required casing depth: 'F' the field rules, 'W' the Texas Department of Water Resources (now the TCEQ). Null where the rule says nothing. e.g. W	—
14	`casing_depth`	integer measured in ft	59-63	`FL-OIL-CASING-DEPTH`	Depth in feet the casing of the discovery well was set to. Zero on the great majority — read it with casing_code, which usually says the water agency sets the depth rather than the field rule.	—
15	`casing_remarks`	text	64-95	`FL-OIL-CASING-REMARKS`	Free text a proration analyst wrote about the casing requirement, up to 32 characters ('TDWR LTR.', 'T. W. C.').	—
16	`diagonal_code`	text	96-97	`FL-OIL-DIAGONAL-CODE`	How the diagonal is measured: 'CC' corner to corner, 'WC' well to corner. Null where no diagonal applies.	—
17	`diagonal`	integer measured in ft	98-102	`FL-OIL-DIAGONAL`	The diagonal of the proration unit in feet — the second half of a density rule, which stops a unit being a long thin strip. Zero means none; 99999 is the mainframe's 'no limit'.	—
18	`diagonal_remarks`	text	103-123	`FL-OIL-DIAGONAL-REMARKS`	Free text about the diagonal, up to 21 characters.	—
19	`allocation_code`	text	124	`FL-OIL-ALLOCATION-CODE`	The field's allocation formula in one character, from the manual's appendix D: 'B' acres (4,779 rules), 'C' acres and per well (2,635), 'A' per well (1,008), 'D' potential and per well, 'O' yardstick, and a dozen field-specific ones. The weighted terms are in fl_oil_alloc_formula. e.g. C	—
20	`field_text`	text	125-184	`FL-OIL-FIELD-TEXT`	Free text a proration analyst wrote about this rule, up to 60 characters. It carries the things the fixed columns cannot — optional unit sizes, what has to be filed with a plat, which older field a rule was inherited from. e.g. P16 & LEASE PLAT OR PRO PLAT	—
21	`docket_number`	text	185-194	`FL-OIL-DOCKET-NUMBER`	The Commission docket the rule came out of, written district-dash-number ('7C-0297471', '08-72572'). This is the number to look the order up under in the oil and gas docket dataset. e.g. 7C-0297471	—
22	`rules_not_reliable_flag`	text	195	`FL-OIL-RULES-NOT-RELIABLE-FLAG`	'Y' when RRC does not stand behind the transcribed rule. Empty in every row of the August 2026 tape, gas and oil alike.	—

`fl_oil_optional_rule` 11 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset.

Record layout for `fl_oil_optional_rule` — 11 columns, with byte positions
#	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.	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.	—
3	`rule_seq` key	smallint	—	—	Which rule under this field, counting from 1 in the order the tape carries them — newest first, the undated rule last. EZRRC's column, not RRC's: the tape keys a rule on 99999999 minus its effective date, and 7,496 of the 13,951 gas rules and 5,473 of the 8,565 oil rules carry the bare 99999999, meaning no effective date at all. A date missing from more than half the rows cannot be the key, so position is.	—
4	`opt_key` key	smallint	3-4	`FL-OIL-OPT-KEY`	Which optional rule under the parent rule, 1 to 4. RRC's own two-digit key for the segment.	—
5	`space_to_lease_line`	smallint measured in ft	5-8	`FL-OIL-OPT-SPACE-TO-LEASE-LINE`	Feet from the nearest lease line under this optional unit.	—
6	`space_to_well`	smallint measured in ft	9-12	`FL-OIL-OPT-SPACE-TO-WELL`	Feet from the nearest well under this optional unit.	—
7	`acres_per_unit`	numeric measured in acres	13-18	`FL-OIL-OPT-ACRES-PER-UNIT`	Acres per well under this optional unit, two decimal places.	—
8	`tolerance_acres`	numeric measured in acres	19-23	`FL-OIL-OPT-TOLERANCE-ACRES`	Tolerance acreage allowed on this optional unit.	—
9	`diagonal_code`	text	24-25	`FL-OIL-OPT-DIAGONAL-CODE`	'CC' corner to corner or 'WC' well to corner, as for the main rule.	—
10	`diagonal_feet`	integer measured in ft	26-30	`FL-OIL-OPT-DIAGONAL-FEET`	Diagonal of the optional proration unit, in feet.	—
11	`field_text`	text	31-77	`FL-OIL-OPT-FIELD-TEXT`	Free text about the optional rule, up to 47 characters. Filled on 100 of the 1,322 gas rows and 248 of the 1,121 oil ones.	—

`fl_oil_remark` 10 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset.

Record layout for `fl_oil_remark` — 10 columns, with byte positions
#	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.	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.	—
3	`remark_no` key	smallint	3-5	`FL-OIL-REMARK-NUMBER`	Which remark on this field, as RRC numbers them. With line_no it is the key; a remark of several lines repeats the number.	—
4	`line_no` key	smallint	6-8	`FL-OIL-REMARK-LINE-NO`	Line within the remark, from 1. A remark can run to 78 lines.	—
5	`print_annual_flag`	text	9	`FL-OIL-PRINT-ANNUAL-FLAG`	'Y' if this line prints on the annual report — the yearly production summary for the field.	—
6	`print_ledger_flag`	text	10	`FL-OIL-PRINT-LEDGER-FLAG`	'Y' if this line prints on the ledger report. The manual says the flag is not in use and the tape agrees: every row that carries a value at all carries the same one.	—
7	`print_schedule_flag`	text	11	`FL-OIL-PRINT-SCHEDULE-FLAG`	'Y' if this line prints on the monthly proration schedule, the document that tells an operator what each well may produce.	—
8	`print_on_line_flag`	text	12	`FL-OIL-PRINT-ON-LINE-FLAG`	'Y' if this line shows on RRC's own terminal screens.	—
9	`remark_date`	date	13-20	`FL-OIL-REMARK-DATE`	Date the remark was last written, CCYYMMDD. Null where the mainframe never stamped one.	—
10	`remark_text`	text	21-86	`FL-OIL-REMARK-TEXT`	The line itself, up to 66 characters as the tape wraps it.	—

`fl_t3` 12 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset.

Record layout for `fl_t3` — 12 columns, with byte positions
#	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.	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.	—
3	`nominator_no` key	integer	—	`FL-T3-NOMINATOR-NUMBER`	P-5 number of the nominator, from the parent T-3 root.	—
4	`system_no` key	smallint	—	`FL-T3-SYSTEM-NUMBER`	Pipeline and gathering system, from the parent T-3 root.	—
5	`seq` key	smallint	—	—	Position of this T-3 under its nominator, from 1. EZRRC's column.	—
6	`report_yyyymm`	integer	3-8	`FL-T3-REPORT-DATE`	The month the nomination applies to, as yyyymm. The tape stores it as 999999 minus the date.	—
7	`kind_of_gas`	text	9	`FL-T3-KIND-OF-GAS`	'C' casinghead gas or 'G' gas well gas. Casinghead gas takes first priority in nominations so that gas produced with oil is not vented.	—
8	`perc_fld_del`	numeric	10-12	`FL-T3-PERC-FLD-DEL`	What share of the gas the nominator had contracted for in this field it says it will take this month, as a fraction. The manual says the item is not yet in use.	—
9	`posting_date`	date	13-20	`FL-T3-POSTING-DATE`	Date the T-3 was entered into RRC's system, CCYYMMDD.	—
10	`corrected_report`	text	21	`FL-T3-CORRECTED-REPORT`	'Y' where this T-3 corrects an earlier one, 'N' where original.	—
11	`amount_of_gas`	integer measured in MCF	22-30	`FL-T3-AMOUNT-OF-GAS`	Gas the nominator wants to buy from the field, in MCF.	—
12	`batch_number`	smallint	31-33	`FL-T3-BATCH-NUMBER`	Which keypunch batch the form came in on. RRC-internal.	—

`fl_t3_root` 4 columns

Documented here because RRC ships it in the same file. It is not in a download of this dataset.

Record layout for `fl_t3_root` — 4 columns, with byte positions
#	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.	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.	—
3	`nominator_no` key	integer	3-8	`FL-T3-NOMINATOR-NUMBER`	P-5 number of the purchaser filing the T-3 nomination for this field. EMPTY: the tape carries no T-3 records.	—
4	`system_no` key	smallint	9-12	`FL-T3-SYSTEM-NUMBER`	The pipeline and gathering system the purchaser is nominating for. EMPTY: the tape carries no T-3 records.	—

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 (printed designation) 14 values

Read by district_name

The district as the Railroad Commission prints it: 01-06, 6E, 7B, 7C, 08, 8A, 09 and 10, plus 20 for statewide. This is what appears on permits, completions, ST-1 filings and inspection reports. It is not interchangeable with the internal district number. A column holding '11' means District 8A under the internal numbering and nothing at all under this one.

RRC district (printed designation) — 14 codes and their meanings
Code	Means
`01`	District 01 — San Antonio RRC District 01, administered from the San Antonio district office.
`02`	District 02 — San Antonio RRC District 02, administered from the San Antonio district office.
`03`	District 03 — Houston RRC District 03, administered from the Houston district office.
`04`	District 04 — Corpus Christi RRC District 04, administered from the Corpus Christi district office.
`05`	District 05 — Kilgore RRC District 05, administered from the Kilgore district office.
`06`	District 06 — Kilgore RRC District 06, administered from the Kilgore district office.
`6E`	District 6E — Kilgore RRC District 6E, administered from the Kilgore district office.
`7B`	District 7B — Abilene RRC District 7B, administered from the Abilene district office.
`7C`	District 7C — San Angelo RRC District 7C, administered from the San Angelo district office.
`08`	District 08 — Midland RRC District 08, administered from the Midland district office.
`8A`	District 8A — Midland RRC District 8A, administered from the Midland district office.
`09`	District 09 — Wichita Falls RRC District 09, administered from the Wichita Falls district office.
`10`	District 10 — Pampa RRC District 10, administered from the Pampa district office.
`20`	District 20 — State Wide RRC District 20, administered from the State Wide district office.

Source: Generated from texas.pdq_gp_district.district_name

RRC district (internal number) 14 values

Read by district_no, district_no, district_no, district_no, district_no, district_no, district_no, district_no, district_no, district_no, district_no, district_no, district_no, district_no, district_no, district_no, district_no, district_no, district_no, district_no, district_no, district_no, district_no, district_no, district_no, district_no, district_no, district_no, district_no, district_no, 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.

RRC district (internal number) — 14 codes and their meanings
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.

Statewide Field Data joins to PDQ Field Directory on District number and Field number — one row here matches one row there.

is the same field as

The FL tape's field master and PDQ's field directory are the same 65,826 fields, district for district: every fl_field row finds exactly one PDQ row and every PDQ row finds exactly one fl_field row. Both write the district as the internal number, so that half needs no translation. Worth having in both directions. PDQ carries the field name, the wildcat flag and the derived rule type; the FL tape carries the rules themselves, the allocation formula, the allowables and the monthly production. These two columns are different types — one is text, the other an integer — so a direct equality is rejected by Postgres. Cast the text side to integer, which also disposes of any leading zeros; casting the integer to text would not, because '000123' and 123 are not equal as text.

statewide-field-data.district_no = pdq-field-directory.district_no AND statewide-field-data.field_no = pdq-field-directory.field_no

Statewide Field Data joins to Oil & Gas Field Rules on Field number — one row here matches one row there.

is the same field as

The mainframe's field master and RRC's Oracle field-rules export, on the eight-digit field number. All 65,826 fields on the tape are in the export, which carries 65,836 -- ten fields the tape does not. The two describe the same fields from different systems and are worth reading together: the Oracle export has the derived rule type and the schedule remarks, the tape has the rule history, the allocation formulas and the allowables. These two columns are different types — one is text, the other an integer — so a direct equality is rejected by Postgres. Cast the text side to integer, which also disposes of any leading zeros; casting the integer to text would not, because '000123' and 123 are not equal as text.

statewide-field-data.field_no = oil-gas-field-rules.field_number

Statewide Field Data joins to PDQ Field Production by Cycle on District number and Field number — one row here matches many rows there.

has monthly production in

From the field master to PDQ's monthly production for the same field. 41,144 of the 65,826 fields have at least one PDQ cycle; the rest have never reported production under that field number. PDQ is the better source for production alone -- it reaches back to 1993 for every field -- and the FL tape is the only source of the allowable beside it. Field Monthly Statistics joins the two on the month as well. These two columns are different types — one is text, the other an integer — so a direct equality is rejected by Postgres. Cast the text side to integer, which also disposes of any leading zeros; casting the integer to text would not, because '000123' and 123 are not equal as text.

statewide-field-data.district_no = pdq-field-cycle.district_no AND statewide-field-data.field_no = pdq-field-cycle.field_no

Statewide Field Data joins to Drilling Permit Master on Discovery permit number = Permit number — many rows here share a single row there.

was discovered by the well permitted as

From a field to the drilling permit of its discovery well. 4,455 of the 4,456 fields that carry a discovery permit find it in the permit master -- the whole W-1 history since 1976 -- against 83 in the rolling daily extract, which only holds the last few years. Only 4,456 of the 65,826 fields carry one at all: the rest were discovered before RRC started recording it here.

statewide-field-data.discovery_permit_no = drilling-permit-master.permit_no

Statewide Field Data joins to Oil & Gas Field Name & Numbers on Field number — one row here matches one row there.

is the same field as

The published name list and the mainframe's field master (flf900) are the same 65,826 fields, one for one in both directions. Both hold the field number as an INTEGER, so this is the one field join in the catalogue that needs neither a cast nor a pad. The tape agrees with the published list on every row it can be compared on -- the field name is identical on all 65,826, and so is `fl_field.district_name`. The tape is the one to go to for the rules, the allowables, the monthly statistics and the discovery well; this is the one to go to for the county code, the multi-county flag and RRC's own oil/gas classification, which the tape records as a single character over different groupings.

oil-gas-field-names-numbers.field_no = statewide-field-data.field_no

Statewide Field Data joins to Field Monthly Statistics (Allowables and Production) on District number and Field number — one row here matches many rows there.

is a month of

Each field-month back to the field it belongs to, for the name, the class and the rules. Every one of 20,000 sampled rows resolves, as it must: the loader drops a child whose parent it never saw.

statewide-field-monthly-statistics.district_no = statewide-field-data.district_no AND statewide-field-monthly-statistics.field_no = statewide-field-data.field_no

Statewide Field Data joins to Field Gas Information on District number and Field number — one row here matches one row there.

is the gas segment of

The gas half of a field's master record, back to the root. All 42,133 gas segments resolve, and no field has two.

statewide-field-gas-information.district_no = statewide-field-data.district_no AND statewide-field-gas-information.field_no = statewide-field-data.field_no

Statewide Field Data joins to Field Oil Information 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

Statewide Field Data joins to Field Gas Rules (Mainframe) on District number and Field number — one row here matches many rows there.

is a gas rule for

All 13,951 gas rules resolve to a field, and 11,435 distinct fields carry one: a field can have up to twelve rules on the tape, newest first.

statewide-field-gas-rules.district_no = statewide-field-data.district_no AND statewide-field-gas-rules.field_no = statewide-field-data.field_no

Statewide Field Data joins to Field Oil Rules (Mainframe) on District number and Field number — one row here matches many rows there.

is an oil rule for

All 8,565 oil rules resolve to a field, over 7,829 distinct fields; the most any field carries is eight.

statewide-field-oil-rules.district_no = statewide-field-data.district_no AND statewide-field-oil-rules.field_no = statewide-field-data.field_no

Statewide Field Data joins to Gas Annual Report Field Table on District name = District and Field name = Field name — one row here matches many rows there.

is the field record for

From a field's annual gas production to its whole regulatory record. 4,999 of 5,000 sampled annual rows find a field, with no folding or padding on either side: both write the district as RRC prints it and the field name in RRC's own capitalisation. The symmetry is close to exact -- 42,138 annual rows against the 42,133 fields the tape carries on the gas schedule -- but a name is still not a key: 115 fields share a (district, name) pair with another field, so those come back twice. The field NUMBER would settle it and the annual file does not carry one.

gas-annual-report-field-table.district = statewide-field-data.district_name AND gas-annual-report-field-table.field_name = statewide-field-data.field_name

Statewide Field Data joins to Oil Annual Report Field Table on District name = District and Field name = Field name — one row here matches many rows there.

is the field record for

The same join on the oil side, and it works as well: 739 of the 741 rows currently loaded find their field. 741 rows is the whole oil annual table today, and every one of them is District 10 -- upstream loads one district part of that file and twelve of the gas one. When the other eleven arrive this join covers them without changing.

oil-annual-report-field-table.district = statewide-field-data.district_name AND oil-annual-report-field-table.field_name = statewide-field-data.field_name

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

OGA090 — Field Information — Record Layout

Our table

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

Get the data

What this is

What you can do with it

Gotchas

Record layout

fl_field 23 columns

fl_asheet 16 columns

fl_asheet_month 55 columns

fl_assoc_gas_field 4 columns

fl_calc_49b 13 columns

fl_field_month 18 columns

fl_gas_alloc_factor 4 columns

fl_gas_alloc_factor_item 6 columns

fl_gas_alloc_formula 6 columns

fl_gas_county 3 columns

fl_gas_cycle 20 columns

fl_gas_field 40 columns

fl_gas_field_rule 28 columns

fl_gas_market_demand 17 columns

fl_gas_market_demand_remark 6 columns

fl_gas_operator_market_demand 19 columns

fl_gas_optional_rule 11 columns

fl_gas_remark 11 columns

fl_map 3 columns

fl_map_county 5 columns

fl_oil_alloc_factor 6 columns

fl_oil_alloc_formula 6 columns

fl_oil_county 3 columns

fl_oil_cycle 10 columns

fl_oil_factor_root 8 columns

fl_oil_field 34 columns

fl_oil_field_rule 22 columns

fl_oil_optional_rule 11 columns

fl_oil_remark 10 columns

fl_t3 12 columns

fl_t3_root 4 columns

Code lookups used here

RRC district (printed designation) 14 values

RRC district (internal number) 14 values

What this joins to

Where this comes from

`fl_field` 23 columns

`fl_asheet` 16 columns

`fl_asheet_month` 55 columns

`fl_assoc_gas_field` 4 columns

`fl_calc_49b` 13 columns

`fl_field_month` 18 columns

`fl_gas_alloc_factor` 4 columns

`fl_gas_alloc_factor_item` 6 columns

`fl_gas_alloc_formula` 6 columns

`fl_gas_county` 3 columns

`fl_gas_cycle` 20 columns

`fl_gas_field` 40 columns

`fl_gas_field_rule` 28 columns

`fl_gas_market_demand` 17 columns

`fl_gas_market_demand_remark` 6 columns

`fl_gas_operator_market_demand` 19 columns

`fl_gas_optional_rule` 11 columns

`fl_gas_remark` 11 columns

`fl_map` 3 columns

`fl_map_county` 5 columns

`fl_oil_alloc_factor` 6 columns

`fl_oil_alloc_formula` 6 columns

`fl_oil_county` 3 columns

`fl_oil_cycle` 10 columns

`fl_oil_factor_root` 8 columns

`fl_oil_field` 34 columns

`fl_oil_field_rule` 22 columns

`fl_oil_optional_rule` 11 columns

`fl_oil_remark` 10 columns

`fl_t3` 12 columns

`fl_t3_root` 4 columns