WELL · 42-363-31263 · DISTRICT 9

Clayton B #1

Y

Palo Pinto County · Perrin SW (Congl 4850) field · Shut IN  · Vertical

Clayton B #1 (API 42-363-31263) is a well in Palo Pinto County operated by North Texas Plugging LLC, completed April 19, 2008 and listed as shut in on the RRC schedule.

The RRC has issued one drilling permit, issued January 29, 2008, permitted to 5,000 ft.

It was permitted by Cumming Company, Inc. The and has since transferred to North Texas Plugging LLC on the wellbore schedule.

Completion filings report 4 formation tops, including Strawn, Pregnant Shale, Conglomerate, Marble Falls.

Its lease has reported 14K barrels of oil and 89.3K mcf of gas since April 2008, last reporting in July 2026.

Operator of record

North Texas Plugging LLC

Permitted by Cumming Company, Inc. The; the EWA schedule now lists a different operator.

Denton, TX · P-5 Y, filed Jul 4, 2026 · (214) 407-4525

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleNorth Texas Plugging LLC
Production reportsCumming Company, Inc. Thethrough Feb 2017
Latest permitCumming Company, Inc. TheJan 29, 2008

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

5,000
total depth, ft
1
permits on file
Jan 29, 2008
last permit issued
Apr 19, 2008
completed
14K
cumulative oil, bbl
89.3K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2008 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 19, 2008
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Delinquent

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
Clayton "B" O-13-30992Perrin, SW (Congl 4850)North Texas Plugging, LLC114K89.3KApr 2008 – Jul 2026

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. 1Cumming Company, Inc. TheApr 2008 → Nov 2016

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
653203-99ReenterCumming Company, Inc. TheJan 15, 2008Jan 29, 2008Feb 13, 20085,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-30992————

Formation tops

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

FormationMD ftSubsea
Strawn2,400-1,445
Pregnant Shale3,890-2,935
Conglomerate4,138-3,183
Marble Falls4,650-3,695

Perforations

Perforated and open-hole intervals.

FromToType
4,5584,634Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.625308——
4.54,7027.875210 S
4.5—7.875140 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
00Oct 3, 2008Jun 5, 2008Yes
00Sep 19, 2008——

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