OPERATORS · TEXAS · P-5 NUMBER 385125 · CALLAHAN COUNTY

Hicks, Bill Co. in Callahan County

One operator, one county: its permits, wells of record, formations, and leases here, with the rest of the county and the rest of the operator one click away.

Hicks, Bill Co. has 27 drilling permits on file in Callahan County, the first issued in 1978 and the latest on April 16, 1980.

None were issued in the last twelve months.

It is operator of record on 2 wells in the county: 0 producing, 0 shut in, 0 injection.

0
permits, 12 months
27
permits, all time since 1978
—
horizontal, 12 months
—
ft average depth, 12 months
2
wells of record
0
producing · 0 shut in · 0 injection

Permits issued by month

LAST FIVE YEARS · CALLAHAN ONLY

Last 12 months 0 · prior 12 0

0120222023202420252026

Latest permits here

IssuedLease / wellTypeDepth
Apr 16, 1980Hatchett "C" #10 78417Other350
Apr 16, 1980Hatchett "C" #18 78416Other350
Apr 16, 1980Hatchett "C" #19 78415Other350
Apr 16, 1980Hatchett "C" #20 78414Other350
Apr 16, 1980Hatchett "C" #21 78413Other350
Jul 16, 1979Hatchett "C" #5W 52934Other400
Jun 25, 1979Hatchett "C" #7 51562Other350
Jun 25, 1979Hatchett '"C" #9 51559Other350
May 28, 1979Hatchett "A" #2 49550Drill400
May 28, 1979Hatchett "A" #4 49549Drill400

All 27 permits in Callahan County, searchable → ·  Wells of record here →

Permit types and formations

Permit types

Other
0 / 16
Drill
0 / 11

12 MONTHS / ALL TIME

Formations reported

No completion tops on file for its wells here.

Leases it reports here

No leases with wells completed in this county carry this operator's production reports.

All leases it reports → ·  Other operators in Callahan County →

About this data

Permits from the RRC OGA049M master and daily daf420 files; wells of record and status from the EWA wellbore schedule, weekly; formations from the dbf900 wellbore file; leases from PDQ lease reports, placed in the county by the wells completed on them.

Developers: this page as JSON is GET /v1/data/operators/tx/385125/counties/callahan, documented in the API reference.