WELL · 42-365-33638 · DISTRICT 6

Beasley 3 Unit #8

Y

Panola County · Carthage (Cotton Valley) field · Temp Abandoned  · Vertical

Beasley 3 Unit #8 (API 42-365-33638) is a well in Panola County operated by Cr2 Energy LLC, completed September 21, 1997 and listed as temp abandoned on the RRC schedule.

The RRC has issued one drilling permit, issued April 22, 1997, permitted to 9,700 ft.

It was permitted by Phillips Petroleum Company and has since transferred to Cr2 Energy LLC on the wellbore schedule.

Completion filings report 4 formation tops, including Rodessa, Pettit, Travis Peak, Cotton Valley.

No lease production has been reported under this well’s leases.

Operator of record

CR2 Energy LLC

Permitted by Phillips Petroleum Company; the EWA schedule now lists a different operator.

Kemah, TX · P-5 Y, filed Jun 4, 2026 · (281) 636-2078

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleCR2 Energy LLC
Production reportsTanos Exploration II, LLCthrough Mar 2016
Latest permitPhillips Petroleum CompanyApr 22, 1997

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

9,700
total depth, ft
1
permits on file
Apr 22, 1997
last permit issued
Sep 21, 1997
completed
0
cumulative oil, bbl
1.45M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 1997 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Sep 21, 1997
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

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
Beasley 3 Unit G-6-164979Carthage (Cotton Valley)CR2 Energy LLC101.45MSep 1997 – 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. 1Phillips Petroleum CompanySep 1997 → Dec 2002
  2. 2Conocophillips CompanyJan 2003 → Dec 2015
  3. 3Tanos Exploration II, LLCJan 2016 → Mar 2016

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
460224-99DrillPhillips Petroleum CompanyMar 21, 1997Apr 22, 1997Aug 11, 19979,700

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-6-164979————

Formation tops

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

FormationMD ftSubsea
Rodessa5,033-4,772
Pettit5,811-5,550
Travis Peak6,283-6,022
Cotton Valley8,356-8,095

Perforations

Perforated and open-hole intervals.

FromToType
9,2069,226Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,00212.25380 S
2.8759,4917.8751,500 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
00Nov 14, 1997Oct 6, 1997Yes
00Oct 31, 1997——

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