WELL · 42-365-34509 · DISTRICT 6

Carter #1

Plugged

Panola County · Pinehill SE (Pettit Upper) field  · Vertical

Carter #1 (API 42-365-34509) is a plugged well in Panola County, plugged April 21, 2017, last operated by AC Exploration LLC.

The RRC has issued one drilling permit (amended once), issued September 20, 2000, permitted to 7,600 ft.

It was permitted by Strand Energy, L.C. and has since transferred to AC Exploration LLC on the wellbore schedule.

Completion filings report 4 formation tops, including Tma, BMA, T/Pettet, T/Travis Peak.

Its lease has reported 4.84K barrels of oil and 47.5K mcf of gas since July 2001, last reporting in July 2017.

Operator of record

AC Exploration LLC

Permitted by Strand Energy, L.C.; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Jul 4, 2026 · 57 permits on file · (713) 467-5978

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleAC Exploration LLC
Production reportsAC Exploration, LLCthrough Feb 2017
Latest permitStrand Energy, L.C.Sep 20, 2000

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

7,600
total depth, ft
2
permits on file
Sep 20, 2000
last permit issued
Jul 2, 2001
completed
4.84K
cumulative oil, bbl
47.5K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2001 THROUGH Jul 2017

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jul 2, 2001
Shut in
—
Plugged
Apr 21, 2017

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
Carter O-6-14098Pinehill, SE (Pettit, Upper)AC Exploration, LLC14.84K47.5KJul 2001 – Jul 2017

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. 1Strand Energy, L.C.Jul 2001 → Nov 2001
  2. 2Odegard Energy, Inc.Dec 2001 → May 2005
  3. 3AC Exploration, LLCJun 2005 → Jan 2017

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
499853-98DrillStrand Energy, L.C.May 29, 2001Sep 20, 2000—7,600
499853-99DrillStrand Energy, L.C.Sep 20, 2000Sep 20, 2000Sep 25, 20007,600

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-6-14098————

Formation tops

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

FormationMD ftSubsea
Tma5,400-5,059
BMA5,615-5,274
T/Pettet6,345-6,004
T/Travis Peak6,740-6,399

Perforations

Perforated and open-hole intervals.

FromToType
6,4626,465Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,12511335 S
4.57,4007.875777 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
00Aug 23, 2001Jul 5, 2001Yes
00Jul 24, 2001——

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