WELL · 42-497-33712 · DISTRICT 9

Vaught B. P. #6

Y

Wise County · Boonsville (Bend Congl. Gas) field · Temp Abandoned  · Vertical

Vaught B. P. #6 (API 42-497-33712) is a well in Wise County operated by Eagleridge Operating LLC, completed April 22, 1992 and listed as temp abandoned on the RRC schedule.

The RRC has issued one drilling permit, issued March 26, 1992, permitted to 6,000 ft.

It was permitted by EP Operating Company and has since transferred to Eagleridge Operating LLC on the wellbore schedule.

Completion filings report 2 formation tops, including Caddo, Atoka.

No lease production has been reported under this well’s leases.

Operator of record

Eagleridge Operating LLC

Permitted by EP Operating Company; the EWA schedule now lists a different operator.

Dallas, TX · P-5 Y, filed Jan 4, 2026 · 129 permits on file · (855) 820-6008

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEagleridge Operating LLC
Production reportsEagleridge Operating, LLCthrough Jan 2020
Latest permitEP Operating CompanyMar 26, 1992

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

6,000
total depth, ft
1
permits on file
Mar 26, 1992
last permit issued
Apr 22, 1992
completed
0
cumulative oil, bbl
522K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 22, 1992
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

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
Vaught, B. P. G-13-141247Boonsville (Bend Congl., Gas)Eagleridge Operating, LLC10522KJan 1993 – Jul 2026

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. 1EP Operating Limited PartnershipJan 1993 → Feb 1995
  2. 2Enserch Exploration, IncMar 1995 → Dec 1997
  3. 3Merit Energy CompanyJan 1998 → Sep 2019
  4. 4Eagleridge Operating, LLCOct 2019 → Jan 2020

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
397793-99DrillEP Operating CompanyMar 26, 1992Mar 26, 1992Mar 28, 19926,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-13-141247————

Formation tops

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

FormationMD ftSubsea
CaddoCADDO LIME4,240-3,248
AtokaATOKA A4,938-3,946

Perforations

Perforated and open-hole intervals.

FromToType
5,6655,691Perforated
5,7015,724Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62542812.25220 S
5.55,9007.875410 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
00Jun 29, 1992May 4, 1992Yes
00May 12, 1992——

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). 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/49733712, documented in the API reference.