TEXAS · WELLS · WHEELER COUNTY · STILES RANCH 5 LEASE · API 42-483-31884 · DISTRICT 08

Stiles Ranch 5 #3

Plugged

Wheeler County · Stiles Ranch (Granite Wash Cons) field  · Vertical

Stiles Ranch 5 #3 (API 42-483-31884) is a plugged well in Wheeler County, plugged May 26, 2009, last operated by Chesapeake Operating Inc..

The RRC has issued one drilling permit, issued May 25, 2005, permitted to 16,000 ft.

Completion filings report 4 formation tops, including B. Heebner, Tonkawa, Missourian, Des Moines.

Its lease has reported 8.32K barrels of oil and 157K mcf of gas since September 2005, with no volume in the three years through April 2026.

Operator of record

Chesapeake Operating Inc.

Based in
Oklahoma City, OK
P-5 status
Delinquent (D)
P-5 last filed
Dec 10, 2024
Permits on file
13,061
Phone
(405) 935-3100

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleChesapeake Operating Inc.
Production reportsChesapeake Operating, Inc.through Jun 2008
Latest permitChesapeake Operating, Inc.May 25, 2005
16,000
total depth, ft
1
permits on file
May 25, 2005
last permit issued
Feb 15, 2008
completed
8.32K
cumulative oil, bbl
157K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 2005 THROUGH Jun 2008

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 15, 2008
Shut in
—
Plugged
May 26, 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 lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Stiles Ranch 5 G-14-213559Stiles Ranch (Granite Wash Cons)Chesapeake Operating, Inc.18.32K157KSep 2005 – Jun 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. 1Chesapeake Operating, Inc.Sep 2005 → Jun 2008

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
601225-99DrillChesapeake Operating, Inc.May 25, 2005May 25, 2005Aug 10, 200516,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Feb 15, 2008Stiles Ranch 5 G-14-213559Stiles Ranch (Granite Wash Cons)Chesapeake Operating Inc.Plugged—

Formation tops

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

FormationMD ftSubsea
B. Heebner9,033-6,776
Tonkawa9,912-7,655
Missourian10,440-8,183
Des Moines12,401-10,144

Perforations

Perforated and open-hole intervals.

FromToType
12,55314,014Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62590711610 S
4.514,1097.875630 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00May 7, 2008Feb 22, 2008—
00May 4, 2006Jan 13, 2006Yes
00Feb 1, 2006——

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