OPERATORS · TEXAS · P-5 NUMBER 341362 · OCHILTREE COUNTY

H & L Operating Co., L.L.P. in Ochiltree 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.

H & L Operating Co., L.L.P. has 3 drilling permits on file in Ochiltree County, the first issued in 1999 and the latest on October 20, 2008.

None were issued in the last twelve months.

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

Its completed wells here most often report Brown Dolomite, Douglas, Marmaton.

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

Permits issued by month

LAST FIVE YEARS · OCHILTREE ONLY

Last 12 months 0 · prior 12 0

0120222023202420252026

Latest permits here

IssuedLease / wellTypeDepth
Oct 20, 2008Brillhart A #1 671840Recompletion8,080
Jul 20, 2006Pshigoda #5 622923Drill5,850
Jul 20, 2006Pshigoda #5 622923Drill5,850
Feb 19, 1999Pshigoda #4752 482679Drill7,150
Jun 18, 1984Schoenhals #1937 242264Drill9,000
Dec 19, 1980Doerrie, Vergil #1 102792Drill9,500
Aug 23, 1979Brillhart #1 56344Drill8,500

All 3 permits in Ochiltree County, searchable → ·  Wells of record here →

Permit types and formations

Permit types

Drill
0 / 2
Recompletion
0 / 1

12 MONTHS / ALL TIME

Leases it reports here

LeaseWellsOil, bblLast reported
Brillhart "A"12.37KOct 2008
Pshigoda10Apr 2007
Schoenhals16.5KDec 2005
Brillhart16.77KAug 2003
Doerrie, Virgil11.05KOct 1998

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