WELL · 42-501-33859 · DISTRICT 8

Winfrey 602 #2

N

Yoakum County  · Directional

Winfrey 602 #2 (API 42-501-33859) is a permitted well in Yoakum County filed by Blue Ridge Resources, LLC; no completion report is on file yet.

The RRC has issued 2 drilling permits between 1993 and 2014, permitted to 12,000 ft.

Completion filings report 8 formation tops, including San Andres, Tubb, L. Clearfork, Wolfcamp.

Its lease has reported 252K barrels of oil and 20.1K mcf of gas since November 1993, last reporting in July 2026. The lease carries 3 wells, so these are lease totals, not this well alone.

Operator of record

Blue Ridge Resources, LLC

Midland, TX · P-5 Y, filed Jun 2, 2017 · 30 permits on file · (432) 699-8903

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsBlue Ridge Resources, LLCthrough Jan 2014
Latest permitBlue Ridge Resources, LLCSep 18, 2014
12,000
total depth, ft
2
permits on file
Sep 18, 2014
last permit issued
—
completed
252K
cumulative oil, bbl
20.1K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Nov 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
—

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Winfrey 602 O-11-67180Platang, NE. (Devonian)Burk Royalty Co., Ltd.3252K20.1KNov 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. 1Hunt Oil CompanyNov 1993 → Dec 1996
  2. 2Atasca Resources, Inc.Jan 1997 → Jan 2004
  3. 3Blue Ridge Resources, LLCFeb 2004 → Jan 2014
  4. 4Benchmark Production, LLCSep 2004 → Mar 2006

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
794197-99RecompletionBlue Ridge Resources, LLCAug 14, 2014Sep 18, 2014—12,000
414188-99DrillHunt Oil CompanyJul 23, 1993Jul 29, 1993Sep 2, 199311,600

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-11-67180————

Formation tops

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

FormationMD ftSubsea
San Andres4,510-822
San AndresSAN ANDRES POROSITY5,140-1,452
Tubb7,110-3,422
L. Clearfork7,203-3,515
Wolfcamp8,970-5,282
PennsylvanianPENN CLASTICS10,584-6,896
MississippianMISS LM10,704-7,016
WoodfordWOODFORD SH11,308-7,620
Dev.11,366-7,678

Perforations

Perforated and open-hole intervals.

FromToType
11,43411,437Perforated
11,43911,442Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37540517.5425 S
9.6254,72512.252,100 S
5.511,4878.751,575 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
00Dec 27, 1993Nov 30, 1993Yes
00Dec 10, 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). 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/50133859, documented in the API reference.