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

Legado Midcon, LLC 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.

Legado Midcon, LLC has 9 drilling permits on file in Ochiltree County, the first issued in 2009 and the latest on February 22, 2010.

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
9
permits, all time since 2009
—
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 · OCHILTREE ONLY

Last 12 months 0 · prior 12 0

0120222023202420252026

Latest permits here

IssuedLease / wellTypeDepth
Feb 22, 2010BMB 1019 SWD #1 691657Reenter7,275
Dec 15, 2009Bechthold 35 #1H 688602DrillHZ9,000
Nov 13, 2009Bechthold B #1 687261Recompletion8,050
Nov 13, 2009Bechthold B #1 687261Recompletion8,050
Nov 9, 2009Winthrop 1108 #1H 687073DrillHZ8,200
Oct 7, 2009Daniels 1094 #1H 685875DrillHZ8,200
Oct 7, 2009Daniels 1094 #1H 685875DrillHZ8,200
Jul 15, 2009Stollings 38 #1H 683038DrillHZ9,000
Jul 15, 2009Stollings 38 #1H 683038DrillHZ9,000

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

Permit types and formations

Permit types

Drill
0 / 6
Recompletion
0 / 2
Reenter
0 / 1

12 MONTHS / ALL TIME

Formations reported

No completion tops on file for its wells here.

Leases it reports here

LeaseWellsOil, bblLast reported
Bechthold B10—

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/495447/counties/ochiltree, documented in the API reference.