OPERATORS · TEXAS · P-5 NUMBER 311500 · CLAY COUNTY

Goat Mayo Oil Company in Clay 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.

Goat Mayo Oil Company has 50 drilling permits on file in Clay County, the first issued in 1977 and the latest on April 2, 1987.

None were issued in the last twelve months.

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

Its completed wells here most often report Cisco, Canyon.

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

Permits issued by month

LAST FIVE YEARS · CLAY ONLY

Last 12 months 0 · prior 12 0

0120222023202420252026

Latest permits here

IssuedLease / wellTypeDepth
Apr 2, 1987Mayo, J. H. #21 328406Drill1,050
Nov 25, 1985Mayo, J. H. #21 290973Drill1,050
Feb 14, 1984Mayo, J. H. #20 229455Drill2,000
Nov 8, 1983Goat Mayo #8 220139Drill2,000
Nov 8, 1983Goat Mayo #7 220138Drill2,000
May 26, 1983Goat Mayo #6 197134Drill2,000
May 19, 1983Goat Mayo #5 196215Drill2,000
Nov 23, 1982Mayo, J. H. #19 177959Drill1,000
Oct 22, 1982Mayo, J. H. #18 176038Drill1,000
Feb 16, 1982Mayo, J.H. #17 155426Drill1,100

All 50 permits in Clay County, searchable → ·  Wells of record here →

Permit types and formations

Permit types

Drill
0 / 50

12 MONTHS / ALL TIME

Formations reported

Leases it reports here

LeaseWellsOil, bblLast reported
Mayo50Aug 2003
Mayo, Goat50Aug 2003
Householder Estate30May 1994

All leases it reports → ·  Other operators in Clay 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/311500/counties/clay, documented in the API reference.