WELL · 42-239-31672 · DISTRICT 2

Powell Sam #1

Plugged

Jackson County · EL Toro S.W. (6506) field  · Vertical

Powell Sam #1 (API 42-239-31672) is a plugged well in Jackson County, plugged December 8, 1995, last operated by Carter Exploration Company.

The RRC has issued 4 drilling permits between 1981 and 1987, permitted to 6,912 ft.

Completion filings report 4 formation tops, including Oakville, Catahoula, Discorbis, Het.

Operator of record

Carter Exploration Company

Based in
Corpus Christ, TX
P-5 status
Inactive (I)
P-5 last filed
Feb 19, 2015
Permits on file
215
Phone
(361) 991-4362

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCarter Exploration Company
Production reportsCarter Exploration Companythrough Jun 1994
Latest permitCarter Exploration CompanyMar 5, 1987
6,912
total depth, ft
4
permits on file
Mar 5, 1987
last permit issued
Sep 7, 1981
completed
0
cumulative oil, bbl
76.8K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Dec 1995

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 7, 1981
Shut in
—
Plugged
Dec 8, 1995

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; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Powell, Sam G-2-123495EL Toro, SW. (5450)Carter Exploration Company1076.8KJan 1993 – Dec 1995
— O-2-6209——000—

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. 1Carter Exploration CompanyJan 1993 → Jun 1994

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
327101-99RecompletionCarter Exploration CompanyFeb 26, 1987Mar 5, 1987—6,912
177824-99RecompletionCarter Exploration CompanyNov 22, 1982Nov 22, 1982—6,912
170653-99RecompletionCarter Exploration CompanySep 1, 1982Sep 1, 1982—6,912
130080-99DrillCarter Exploration CompanyAug 13, 1981Aug 13, 1981—6,912

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-2-123495————
—— O-2-6209————

Formation tops

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

FormationMD ftSubsea
OakvilleBASE OF OAKVILLE2,001-1,945
Catahoula3,440-3,384
Discorbis4,520-4,464
Het4,760-4,704

Perforations

Perforated and open-hole intervals.

FromToType
5,2495,253Perforated
5,4635,465Perforated
5,8535,856Perforated
6,5066,508Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62573213.5435 S
2.3755,237——
2.3755,732——
2.3756,454——
4.56,8558.51,360 S
4.56,8557.8751,400 S
4.5—7.8751,360 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
00Feb 27, 1992Jan 10, 1992—
00Mar 27, 1987Feb 25, 1987Yes
00Mar 14, 1987—Yes
00Jan 12, 1984Oct 20, 1982—
00Jan 12, 1984Jul 23, 1982—
00Jan 12, 1984Oct 7, 1981—

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