TEXAS · WELLS · PANOLA COUNTY · MOORE, C.E. UNIT LEASE · API 42-365-34697 · DISTRICT 06

Moore C.E. Unit #7

Plugged

Panola County · Carthage (Cotton Valley) field  · Vertical

Moore C.E. Unit #7 (API 42-365-34697) is a plugged well in Panola County, plugged December 20, 2015, last operated by Anadarko E&P Onshore LLC.

The RRC has issued one drilling permit, issued June 7, 2001, permitted to 11,000 ft.

It was permitted by Rme Petroleum Company and has since transferred to Anadarko E&P Onshore LLC on the wellbore schedule.

Completion filings report 4 formation tops, including Austin Chalk, Paluxy, Gloyd, Pettit.

Operator of record

Anadarko E&P Onshore LLC

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

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Oct 22, 2025
Permits on file
4,575
Phone
(713) 215-7000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleAnadarko E&P Onshore LLC
Production reportsAnadarko E&P Company LPthrough Jul 2010
Latest permitRme Petroleum CompanyJun 7, 2001

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

11,000
total depth, ft
1
permits on file
Jun 7, 2001
last permit issued
Mar 6, 2003
completed
0
cumulative oil, bbl
639K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Mar 2003 THROUGH Dec 2015

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 6, 2003
Shut in
—
Plugged
Dec 20, 2015

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
Moore, C.E. Unit G-6-194856Carthage (Cotton Valley)Anadarko E&P Onshore LLC10639KMar 2003 – Dec 2015

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. 1Anadarko E&P Company LPMar 2003 → Jul 2010

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
509784-99DrillRme Petroleum CompanyJun 4, 2001Jun 7, 2001Jan 12, 200311,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Mar 6, 2003Moore C.E. Unit G-6-194856Carthage (Cotton Valley)Anadarko E&P Onshore LLCPlugged—

Formation tops

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

FormationMD ftSubsea
Austin Chalk2,448-2,210
Paluxy2,893-2,655
Gloyd5,018-4,780
Pettit5,678-5,440

Perforations

Perforated and open-hole intervals.

FromToType
8,3128,880Perforated
9,1069,196Perforated
9,5429,552Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,06512.25380 S
5.59,5987.875830 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
00Jun 20, 2003Jun 3, 2003Yes
00Jun 12, 2003——

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