WELL · 42-089-00571 · DISTRICT 3

Sheridan Gas Unit #47

N

Colorado County · Sheridan (Wilcox) field  · Vertical

Sheridan Gas Unit #47 (API 42-089-00571) is a permitted well in Colorado County filed by Hilcorp Energy Company; no completion report is on file yet.

The RRC has issued 2 drilling permits between 1978 and 2000, permitted to 10,430 ft.

It was permitted by Hilcorp Energy Company and has since transferred to Shell Oil Company on the wellbore schedule.

Operator of record

Shell Oil Company

Permitted by Hilcorp Energy Company; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Jul 4, 2026 · 1,401 permits on file · (281) 787-6834

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleShell Oil Company
Production reportsRemora Management, LLCthrough Apr 2026
Latest permitHilcorp Energy CompanyDec 6, 2000

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

10,430
total depth, ft
2
permits on file
Dec 6, 2000
last permit issued
—
completed
0
cumulative oil, bbl
588K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Sheridan Gas Unit G-3-181533Sheridan (Wilcox Consolidated)Remora Management, LLC10465KFeb 2001 – Jul 2026
Sheridan Gas Unit G-3-78221Sheridan (Wilcox -H-)Hilcorp Energy Company10123KJan 1993 – Feb 2001

Gas, mcf lease total

Last 12 months 25,315 · prior 12 1,936(+1208%)

02K4K6K202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Shell Western E&P Inc.Feb 1993 → Dec 1995
  2. 2Hilcorp Energy CompanyFeb 2001 → Dec 2002
  3. 3Dominion Expl. & Prod., Inc.Jan 2003 → Jul 2007
  4. 4XTO Energy Inc.Aug 2007 → Sep 2024
  5. 5Remora Management, LLCOct 2024 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
502728-99RecompletionHilcorp Energy CompanyDec 6, 2000Dec 6, 2000Dec 6, 20009,072
22226-99RecompletionShell Oil CompanyApr 14, 1978Apr 14, 1978—10,430

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-78221————
—— G-3-181533————

Perforations

Perforated and open-hole intervals.

FromToType
9,0059,014Perforated
9,0739,086Perforated
10,16010,352Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.753,026——
510,100——
710,424——

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
00Jun 13, 2006Feb 6, 2006—
00Jan 10, 2005Nov 4, 2004—
00May 24, 2001Mar 21, 2001Yes
00Apr 3, 2001——
00Jan 12, 1984——

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