TEXAS · WELLS · SHACKELFORD COUNTY · STASNEY'S COOK RANCH "57" LEASE · API 42-417-38976 · DISTRICT 6E

Stasney S Cook Ranch 57 #138

Plugged

Shackelford County · Shackelford County Regular field  · Vertical

Stasney S Cook Ranch 57 #138 (API 42-417-38976) is a plugged well in Shackelford County, plugged April 9, 2024, last operated by Stasney Well Service LLC.

The RRC has issued one drilling permit, issued March 30, 2009, permitted to 2,000 ft.

It was permitted by Stasney, H. R. & Sons, Ltd. and has since transferred to Stasney Well Service LLC on the wellbore schedule.

Completion filings report 6 formation tops, including Coleman Junction, Sedwick Ls, Dothan Ls, Noodle Creek Ls.

Its lease has reported 44.9K barrels of oil since August 2007, last reporting volume in April 2026. The lease carries 19 wells, so these are lease totals, not this well alone.

Operator of record

Stasney Well Service LLC

Permitted by Stasney, H. R. & Sons, Ltd.; the EWA schedule now lists a different operator.

Based in
Albany, TX
P-5 status
Active (A)
P-5 last filed
Jan 22, 2026
Permits on file
305
Phone
(325) 762-3311

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleStasney Well Service LLC
Production reportsStasney Well Service, LLCthrough Apr 2026
Latest permitStasney, H. R. & Sons, Ltd.Mar 30, 2009

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
Mar 30, 2009
last permit issued
Jul 10, 2013
completed
44.9K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 2007 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jul 10, 2013
Shut in
—
Plugged
Apr 9, 2024

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

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Stasney's Cook Ranch "57" O-8-29973Shackelford County RegularStasney Well Service, LLC1944.9K0Aug 2007 – Apr 2026

Oil, barrels lease total

Last 12 months 295 · prior 12 362(-19%)

050100202420252026

Chain of custody

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

  1. 1Stasney, H. R. & Sons, Ltd.Sep 2007 → Jul 2010
  2. 2Stasney Well Service, LLCAug 2010 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
679731-99DrillStasney, H. R. & Sons, Ltd.Mar 23, 2009Mar 30, 2009Mar 31, 20092,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Jul 10, 2013Stasney S Cook Ranch 57 O-8-29973Shackelford County RegularStasney Well Service LLCPlugged—

Formation tops

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

FormationMD ftSubsea
Coleman JunctionCOLEMAN JUNCTION LS4281,145
Sedwick LS581992
Dothan LS746827
Noodle Creek LS810763
Frye SS900673
TannehillTANNEHILL LS970603

Perforations

Perforated and open-hole intervals.

FromToType
1,0011,007Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.625771160 S
4.51,0746.75180 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
00Sep 6, 2013Jul 15, 2013—
00Dec 15, 2009May 21, 2009Yes
00Jun 4, 2009——

Well logs

2 logs loaded from the RRC's log index, the latest received Sep 27, 2010. Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.

Open the RRC's log search for this well ↗
Logas describedFiles Intervalft, as filedDatereceivedSizeMB
RESISTIVITYSpans Coleman Junction, Sedwick Ls, Dothan Ls, Noodle Creek Ls, Frye Ss, TannehillTIFF100 to 1,088Sep 27, 2010run Apr 3, 20090.38
RESISTIVITYSpans Coleman Junction, Sedwick Ls, Dothan Ls, Noodle Creek Ls, Frye Ss, TannehillTIFF100 to 1,088Dec 28, 2009run Apr 3, 20090.44

"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

The logs loaded for this well are under Well logs, with the RRC's log search for it.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

135
bbl, last 12 reported months
49.1K
bbl, all reported
Jul 2023
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000107837H-1 InjectionPlugged Apr 10, 20244005001,001–1,007

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 135 · prior 12 293(-54%)

05010020222023

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