WELL · 42-383-34196 · DISTRICT 7

Vaughn Account 25 #3 R

Y

Reagan County · Texon S (Grayburg) field · Shut IN  · Vertical

Vaughn Account 25 #3 R (API 42-383-34196) is a well in Reagan County operated by Energy Production Corporation, completed November 14, 1992 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit (amended twice), issued November 5, 1992, permitted to 3,300 ft.

Completion filings report 4 formation tops, including Yates, Seven Rivers, Queen, Grayburg.

Its lease has reported 339K barrels of oil and 147 mcf of gas since January 1993, last reporting in July 2026. The lease carries 7 wells, so these are lease totals, not this well alone.

Operator of record

Energy Production Corporation

Kilgore, TX · P-5 Delinquent, filed Apr 22, 2024 · 202 permits on file · (903) 984-3443

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEnergy Production Corporation
Production reportsEnergy Production Corporationthrough Dec 2020
Latest permitEnergy Production CorporationNov 5, 1992
3,300
total depth, ft
3
permits on file
Nov 5, 1992
last permit issued
Nov 14, 1992
completed
339K
cumulative oil, bbl
147
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Nov 14, 1992
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Delinquent

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; they carry 7 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Vaughn Account 25 O-9-5473Texon, S (Grayburg)Energy Production Corporation7339K147Jan 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. 1Energy Production CorporationJan 1993 → Dec 2020
  2. 2Energy Management CompanyJun 2011 → Apr 2020

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
405742-97DrillEnergy Production CorporationDec 8, 1992Nov 5, 1992—3,300
405742-98DrillEnergy Production CorporationDec 8, 1992Nov 5, 1992—3,300
405742-99DrillEnergy Production CorporationNov 5, 1992Nov 5, 1992Nov 6, 19923,200

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-9-5473————

Formation tops

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

FormationMD ftSubsea
Yates2,064863
Seven Rivers2,220707
Queen2,694233
Grayburg3,186-259

Perforations

Perforated and open-hole intervals.

FromToType
3,3213,289Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62578012.25280 S
73,2318.75440 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 15, 1993Jan 11, 1993Yes
00Feb 22, 1993——

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