WELL · 42-311-33046 · DISTRICT 1

Rhode D. W. 77 #1

Plugged

McMullen County · Dos Anos (Hockley) field  · Vertical

Rhode D. W. 77 #1 (API 42-311-33046) is a plugged well in Mcmullen County, plugged August 29, 2018, last operated by Wagner Oil Company.

The RRC has issued one drilling permit, issued November 30, 1994, permitted to 2,500 ft.

It was permitted by Parker & Parsley Development L.P and has since transferred to Wagner Oil Company on the wellbore schedule.

Completion filings report 2 formation tops, including Top Of Cole, Top Of Hockley.

Operator of record

Wagner Oil Company

Permitted by Parker & Parsley Development L.P; the EWA schedule now lists a different operator.

Fort Worth, TX · P-5 Y, filed Sep 4, 2025 · 278 permits on file · (800) 457-5332

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleWagner Oil Company
Production reportsCimarex Energy Co. of Coloradothrough Nov 2012
Latest permitParker & Parsley Development L.PNov 30, 1994

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

2,500
total depth, ft
1
permits on file
Nov 30, 1994
last permit issued
Dec 22, 1994
completed
0
cumulative oil, bbl
932K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 1994 THROUGH Aug 2018

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 22, 1994
Shut in
—
Plugged
Aug 29, 2018

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
Rhode, D. W. "77" G-1-153727Dos Anos (Hockley)Wagner Oil Company10932KDec 1994 – Aug 2018

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. 1Parker & Parsley Producing L.P.Feb 1995 → Oct 1997
  2. 2Pioneer Resources Producing, L.PNov 1997 → Jun 1999
  3. 3Prize Operating CompanyJul 1999 → Mar 2002
  4. 4Gruy Petroleum Management Co.Apr 2002 → Apr 2006
  5. 5Cimarex Energy Co. of ColoradoMay 2006 → Nov 2012

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
430448-99DrillParker & Parsley Development L.PNov 29, 1994Nov 30, 1994Dec 13, 19942,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-1-153727————

Formation tops

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

FormationMD ftSubsea
Top of Cole1,790-1,357
Top of Hockley2,170-1,737

Perforations

Perforated and open-hole intervals.

FromToType
2,1722,180Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
12.2541812.25170 S
5.52,4297.875270 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
00May 11, 1995Feb 17, 1995Yes
00May 2, 1995——

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