WELL · 42-485-40232 · DISTRICT 9

Sheldon #5

Plugged

Wichita County · Wichita County Regular field  · Vertical

Sheldon #5 (API 42-485-40232) is a plugged well in Wichita County, plugged April 7, 2005, last operated by H & W Oil.

The RRC has issued one drilling permit, issued January 11, 1985, permitted to 2,000 ft.

It was permitted by Schalk, Thomas S. and has since transferred to H & W Oil on the wellbore schedule.

Completion filings report one formation top, including Cisco.

Its lease has reported 4.28K barrels of oil and 71 mcf of gas since January 1993, last reporting in March 2008. The lease carries 6 wells, so these are lease totals, not this well alone.

Operator of record

H & W Oil

Permitted by Schalk, Thomas S.; the EWA schedule now lists a different operator.

Electra, TX · P-5 Y, filed Sep 3, 2004

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleH & W Oil
Production reportsH & W Oilthrough Oct 1999
Latest permitSchalk, Thomas S.Jan 11, 1985

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

2,000
total depth, ft
1
permits on file
Jan 11, 1985
last permit issued
Feb 15, 1985
completed
4.28K
cumulative oil, bbl
71
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Mar 2008

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 15, 1985
Shut in
—
Plugged
Apr 7, 2005

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Sheldon O-13-22686Wichita County RegularH & W Oil64.28K71Jan 1993 – Mar 2008

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. 1Schalk, Thomas S.Jan 1993 → Aug 1995
  2. 2Prickett Operating CompanySep 1995 → Jan 1997
  3. 3H & W OilMay 1997 → Oct 1999

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
264021-99DrillSchalk, Thomas S.Jan 9, 1985Jan 11, 1985Jan 17, 19852,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-22686————

Formation tops

As filed on W-2/G-1. Download CSV →

FormationMD ft
Cisco1,532

Perforations

Perforated and open-hole intervals.

FromToType
1,5321,544Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
4.51,9827.875387 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
00Mar 27, 1985Mar 15, 1985—
00Mar 26, 1985——

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.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

0
bbl, last 12 reported months
0
bbl, all reported
—
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000067603UIC PermitCanceled Nov 3, 198935400850–860

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