WELL · 42-413-31800 · DISTRICT 7

Sheen #2

Plugged

Schleicher County · Webster (Canyon) field  · Vertical

Sheen #2 (API 42-413-31800) is a plugged well in Schleicher County, plugged March 24, 2009, last operated by Ozark Exploration Inc..

The RRC has issued one drilling permit (amended once), issued July 20, 1992, permitted to 4,700 ft.

Completion filings report 7 formation tops, including B/Cisco, T/Adams Branch, T/Palo Pinto, T/U. Canyon.

Its 2 leases have reported 8.53K barrels of oil and 85.5K mcf of gas since January 1993, last reporting in May 2009. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Ozark Exploration Inc.

Based in
Dallas, TX
P-5 status
Active (A)
P-5 last filed
Mar 6, 2026
Permits on file
99
Phone
(214) 526-6270

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleOzark Exploration Inc.
Production reportsOzark Exploration, Inc.through Jul 2001
Latest permitOzark Exploration, Inc.Jul 20, 1992
4,700
total depth, ft
2
permits on file
Jul 20, 1992
last permit issued
Sep 26, 1992
completed
8.53K
cumulative oil, bbl
85.5K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH May 2009

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 26, 1992
Shut in
—
Plugged
Mar 24, 2009

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
Sheen O-9-13518Webster (Canyon)Ozark Exploration, Inc.18.53K64.6KOct 1993 – May 2009
Sheen G-9-142724Webster (Canyon)Ozark Exploration, Inc.1020.9KJan 1993 – Jan 1994

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. 1Ozark Exploration, Inc.Jan 1993 → Jul 2001

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
401449-98DrillOzark Exploration, Inc.Oct 13, 1992Jul 20, 1992Jul 22, 19924,700
401449-99DrillOzark Exploration, Inc.Jul 20, 1992Jul 20, 1992—4,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-9-142724————
—— O-9-13518————

Formation tops

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

FormationMD ftSubsea
B/Cisco2,482-169
T/Adams Branch3,845-1,532
T/Palo Pinto4,026-1,713
T/U. Canyon4,078-1,765
T/L. Canyon4,130-1,817
T/Strawn4,218-1,905
T/Strawn Lime4,218-1,905

Perforations

Perforated and open-hole intervals.

FromToType
4,0824,087Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62549511256 S
4.54,3457.875740 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
00Dec 15, 1993Oct 13, 1993—
00Oct 27, 1993——
00Dec 18, 1992Oct 12, 1992Yes
00Nov 2, 1992——

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) and the University Lands library. 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/41331800, documented in the API reference.