TEXAS · WELLS · SUTTON COUNTY · SHANNON 52 LEASE · API 42-435-31971 · DISTRICT 6E

Shannon 52 #4

Plugged

Sutton County · Sawyer (Canyon) field  · Vertical

Shannon 52 #4 (API 42-435-31971) is a plugged well in Sutton County, plugged May 7, 2008, last operated by Smith Pipe Of Abilene.

The RRC has issued one drilling permit, issued September 1, 1977, permitted to 7,250 ft.

It was permitted by Hng Oil Company and has since transferred to Smith Pipe Of Abilene on the wellbore schedule.

Its lease has reported 239 barrels of oil and 39.4K mcf of gas since January 1993, with no volume in the three years through April 2026.

Operator of record

Smith Pipe of Abilene

Permitted by HNG Oil Company; the EWA schedule now lists a different operator.

Based in
Abilene, TX
P-5 status
Inactive (I)
P-5 last filed
Aug 29, 2014
Phone
(325) 692-3903

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSmith Pipe of Abilene
Production reportsSmith Pipe of Abilenethrough Jan 2008
Latest permitHNG Oil CompanySep 1, 1977

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

7,250
total depth, ft
1
permits on file
Sep 1, 1977
last permit issued
Jul 5, 1979
completed
239
cumulative oil, bbl
39.4K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jan 2008

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jul 5, 1979
Shut in
—
Plugged
May 7, 2008

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
Shannon 52 G-9-83439Sawyer (Canyon)Smith Pipe of Abilene123939.4KJan 1993 – Jan 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. 1American Exploration CompanyJan 1993 → Jul 1995
  2. 2Dreyfus, Louis Natural Gas CorpAug 1995 → Mar 1999
  3. 3Dominion Oklahoma Texas E&P, IncApr 2003 → Dec 2007
  4. 4Smith Pipe of AbileneJan 2008 → Jan 2008

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
6696-99DrillHNG Oil CompanySep 1, 1977Sep 1, 1977Jul 5, 19787,250

Completions

CompletedLeaseFieldOperatorStatusDepth
Jul 5, 1979Shannon 52 G-9-83439Sawyer (Canyon)Smith Pipe of AbilenePlugged—

Perforations

Perforated and open-hole intervals.

FromToType
6,5606,970Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
71,0668.75215 S
1.56,984——
4.57,1966.125145 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
00Jan 12, 1984Aug 6, 1979—

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