OPERATORS · TEXAS · P-5 NUMBER 220861 · DUVAL COUNTY

Discovery Petroleum, L.L.C. in Duval 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.

Discovery Petroleum, L.L.C. has 2 drilling permits on file in Duval County, the first issued in 2009 and the latest on August 12, 2009.

None were issued in the last twelve months.

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

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

Permits issued by month

LAST FIVE YEARS · DUVAL ONLY

Last 12 months 0 · prior 12 0

0120222023202420252026

Latest permits here

IssuedLease / wellTypeDepth
Aug 12, 2009Rossi Heirs #100 683744Drill5,600
Feb 17, 2009Mary Rossi West, Etal #A 6 678291Recompletion4,596
Oct 27, 1995Bahr, John W. #1 441341Drill4,400
Jun 27, 1983West, Mary Rossi et Al #A6 213627Drill5,400
Nov 30, 1979Blevins, George et Al #1 69586Other4,790
Mar 9, 1978Blunk, V. M. #2 19681Other5,346

All 2 permits in Duval County, searchable → ·  Wells of record here →

Permit types and formations

Permit types

Drill
0 / 1
Recompletion
0 / 1

12 MONTHS / ALL TIME

Formations reported

No completion tops on file for its wells here.

Leases it reports here

LeaseWellsOil, bblLast reported
Southland Life Ins.30Jul 2026
Southland Life Ins. Co.10Apr 2018
Bahr, John W.10Apr 2018
Blunk, V. M.10Mar 2018
Blevins, George10Mar 2018
West, Mary Rossi et Al10Mar 2018

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