WELL · 42-483-30844 · DISTRICT 10

Conwell Gas Unit #1

Plugged

Wheeler County · Kelton NW. (Morrow) field  · Vertical

Conwell Gas Unit #1 (API 42-483-30844) is a plugged well in Wheeler County, plugged May 2, 2018, last operated by 4p Energy Texas LLC.

The RRC has issued 2 drilling permits between 1981 and 1997, permitted to 17,300 ft.

It was permitted by Rio Grande Drilling Company and has since transferred to 4p Energy Texas LLC on the wellbore schedule.

Operator of record

4P Energy Texas LLC

Permitted by Rio Grande Drilling Company; the EWA schedule now lists a different operator.

Denver, CO · P-5 Y, filed Dec 4, 2020 · 127 permits on file · (303) 478-4800

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedule4P Energy Texas LLC
Production reportsChesapeake Operating, Inc.through Apr 2013
Latest permitRio Grande Drilling CompanyOct 3, 1997

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

17,300
total depth, ft
2
permits on file
Oct 3, 1997
last permit issued
Oct 15, 1997
completed
0
cumulative oil, bbl
372K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH May 2018

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Oct 15, 1997
Shut in
—
Plugged
May 2, 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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Conwell Gas Unit G-14-166295Kelton, NW. (Morrow)4P Energy Texas, LLC10151KOct 1997 – May 2018
Conwell -GU- G-14-104893Kelton,nw (Hunton)Rio Grande Drilling Company10222KJan 1993 – Dec 1999

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. 1Exxon Corp.Jan 1993 → Mar 1996
  2. 2Rio Grande Drilling CompanyApr 1996 → Feb 1999
  3. 3Exco Resources, Inc.Mar 1999 → Aug 2005
  4. 4Chesapeake Operating, Inc.Sep 2005 → Apr 2013

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
467914-99RecompletionRio Grande Drilling CompanySep 22, 1997Oct 3, 1997Sep 24, 199717,300
111922-99DrillExxon Corp.Mar 12, 1981Mar 12, 1981May 6, 198117,300

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-14-104893————
—— G-14-166295————

Perforations

Perforated and open-hole intervals.

FromToType
14,46814,482Perforated
14,49514,506Perforated
16,34416,364Perforated
16,34416,932Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37529817.5588 S
10.755,56712.251,800 S
7.62514,3759.52,190 S
2.87516,050——
517,0116.5970 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
00Apr 27, 1998Nov 4, 1997Yes
00Feb 5, 1998——
00Jan 12, 1984Mar 4, 1983—

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