WELL · 42-137-30362 · DISTRICT 1

Rudasill #1

Plugged

Edwards County · Rudasill (Ellenberger) field  · Vertical

Rudasill #1 (API 42-137-30362) is a plugged well in Edwards County, plugged October 23, 2014, last operated by Chi Operating Inc..

The RRC has issued one drilling permit, issued February 1, 1991, permitted to 10,264 ft.

It was permitted by A A Production Inc. and has since transferred to Chi Operating Inc. on the wellbore schedule.

Completion filings report 4 formation tops, including Canyon, Holman, Strawn, Ellenburger.

Operator of record

Chi Operating Inc.

Permitted by A a Production Inc.; the EWA schedule now lists a different operator.

Midland, TX · P-5 Y, filed Apr 4, 2026 · 126 permits on file · (432) 557-8773

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleChi Operating Inc.
Production reportsChi Operating, Inc.through Jul 2012
Latest permitA a Production Inc.Feb 1, 1991

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

10,264
total depth, ft
1
permits on file
Feb 1, 1991
last permit issued
Mar 2, 1991
completed
0
cumulative oil, bbl
33.7K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Oct 2014

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 2, 1991
Shut in
—
Plugged
Oct 23, 2014

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
Rudasill G-1-141512Rudasill (Ellenberger)Chi Operating, Inc.1033.7KJan 1993 – Oct 2014

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. 1A a Production Inc.Jan 1993 → Oct 1996
  2. 2Brown, J. K. Inc.Nov 1996 → Apr 1999
  3. 3Whiting Petroleum CorporationMay 1999 → Dec 2001
  4. 4SDX Resources, Inc.Jan 2002 → Jul 2006
  5. 5Chi Operating, Inc.Aug 2006 → Jul 2012

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
384152-99ReenterA a Production Inc.Feb 1, 1991Feb 1, 1991Feb 10, 199110,264

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-1-141512————

Formation tops

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

FormationMD ftSubsea
CanyonCANYON SAND2,756-418
Holman7,300-4,962
Strawn9,253-6,915
Ellenburger9,363-7,025

Perforations

Perforated and open-hole intervals.

FromToType
9,6379,732Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.751,64613.375650 S
10.751,64614.75650 S
5.59,7518.75625 S
5.59,7517.875825 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
00Jul 16, 1992Oct 21, 1991—
00Jun 10, 1992——
00Jan 12, 1984May 11, 1977—

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