WELL · 42-105-36974 · DISTRICT 7

Hoover Laura Estate 7C #6

Plugged

Crockett County · Ozona (Canyon Sand) field  · Vertical

Hoover Laura Estate 7c #6 (API 42-105-36974) is a plugged well in Crockett County, plugged June 16, 2021, last operated by Epic Permian Operating LLC.

The RRC has issued one drilling permit, issued October 4, 1995, permitted to 7,900 ft.

It was permitted by Union Pacific Resources Company and has since transferred to Epic Permian Operating LLC on the wellbore schedule.

Completion filings report one formation top, including Canyon.

Operator of record

Epic Permian Operating LLC

Permitted by Union Pacific Resources Company; the EWA schedule now lists a different operator.

Arvada, CO · P-5 Y, filed Apr 4, 2025 · 5 permits on file · (432) 687-6200

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEpic Permian Operating LLC
Production reportsEpic Permian Operating, LLCthrough Jul 2018
Latest permitUnion Pacific Resources CompanyOct 4, 1995

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

7,900
total depth, ft
1
permits on file
Oct 4, 1995
last permit issued
Dec 19, 1995
completed
0
cumulative oil, bbl
313K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 1995 THROUGH Jun 2021

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 19, 1995
Shut in
—
Plugged
Jun 16, 2021

Surface location

No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Hoover, Laura Estate "7C" G-9-157101Ozona (Canyon Sand)Epic Permian Operating, LLC10313KDec 1995 – Jun 2021

No volumes reported on these leases in the last three years.

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Union Pacific Resources CompanyDec 1995 → Jan 2001
  2. 2Rme Petroleum CompanyFeb 2001 → Nov 2002
  3. 3Anadarko E&P Company LPDec 2002 → Dec 2012
  4. 4Anadarko E&P Onshore LLCJan 2013 → Aug 2016
  5. 5Epic Permian Operating, LLCSep 2016 → Jul 2018

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
437321-99DrillUnion Pacific Resources CompanyJun 27, 1995Oct 4, 1995Nov 9, 19957,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-9-157101————

Formation tops

As filed on W-2/G-1. Subsea from 2,397 ft elevation.Download CSV →

FormationMD ftSubsea
Canyon5,990-3,593

Perforations

Perforated and open-hole intervals.

FromToType
6,6447,384Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,01411375 S
2.8757,5497.875590 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Mar 28, 1996Jan 22, 1996Yes
00Mar 11, 1996——

The source documents

Petrora holds the structured record. The scanned filings live at the RRC; these links open its search already filled in for this API.

Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward) and the University Lands library. then paste it into their search.

About this data

Permits from the RRC OGA049M master and daily daf420 files; wellbore and operator of record from the EWA schedule, weekly; completions, formation tops, casing, and perforations from the dbf900 wellbore file; production from PDQ lease reports, which lag two to three months; injection from UIC permits, H-10 reports, and TexNet daily volumes; earthquakes from the TexNet catalog.

New to these records? How to read a well page · API numbers · completion reports and tops · why production is by lease

Developers: this page as JSON is GET /v1/data/wells/10536974, documented in the API reference.