OPERATORS · TEXAS · P-5 NUMBER 559580 · MITCHELL COUNTY

Melton, Joe, Drlg. Co., Inc. in Mitchell 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.

Melton, Joe, Drlg. Co., INC. has 13 drilling permits on file in Mitchell County, the first issued in 1979 and the latest on February 18, 1981.

None were issued in the last twelve months.

It is not operator of record on any well in the county on the current wellbore schedule.

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

Permits issued by month

LAST FIVE YEARS · MITCHELL ONLY

Last 12 months 0 · prior 12 0

0120222023202420252026

Latest permits here

IssuedLease / wellTypeDepth
Feb 18, 1981Daniel, Elmo #4 117152Drill3,150
Feb 18, 1981Daniel, Elmo #4 113542Drill3,150
Jan 27, 1981Daniel, Elmo #5 111220Drill3,150
Oct 20, 1980Adams #4 96075Drill2,950
Oct 20, 1980Adams #3 96074Drill2,950
Apr 30, 1980Morrison #3 79778Drill3,150
Apr 30, 1980Morrison #4 79777Drill3,150
Jan 10, 1980Morrison #2 69182Drill3,150
Jan 10, 1980Daniel, Elmo #3 69181Drill3,150
Jan 10, 1980Adams #2 69180Drill3,150

All 13 permits in Mitchell County, searchable → ·  Wells of record here →

Permit types and formations

Permit types

Drill
0 / 13

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 Mitchell 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/559580/counties/mitchell, documented in the API reference.