WELL · 42-239-33579 · DISTRICT 2

Peters Cole #1

Y

Jackson County · EL Toro Max (AY-3) field · Temp Abandoned  · Directional

Peters Cole #1 (API 42-239-33579) is a well in Jackson County operated by Atlas Operating LLC, completed May 30, 2013 and listed as temp abandoned on the RRC schedule.

The RRC has issued one drilling permit, issued March 22, 2012, permitted to 12,500 ft.

It was permitted by Alta Mesa Services, LP and has since transferred to Atlas Operating LLC on the wellbore schedule.

Completion filings report 2 formation tops, including El Toro Max (Ay-3), Yegua.

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

Operator of record

Atlas Operating LLC

Permitted by Alta Mesa Services, LP; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Oct 4, 2025 · 78 permits on file · (281) 893-9400

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleAtlas Operating LLC
Production reportsGaither Petroleum Corporationthrough Sep 2017
Latest permitAlta Mesa Services, LPMar 22, 2012

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

12,500
total depth, ft
1
permits on file
Mar 22, 2012
last permit issued
May 30, 2013
completed
0
cumulative oil, bbl
1.69M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Aug 2012 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 30, 2013
Shut in
—
Plugged
—

Operator's P-5 on the schedule: H

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
Peters Cole G-2-268204EL Toro Max (AY-3)Atlas Operating LLC101.69MAug 2012 – 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. 1Alta Mesa Services, LPSep 2012 → Dec 2015
  2. 2Gaither Petroleum CorporationJan 2016 → Sep 2017

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
734705-99DrillAlta Mesa Services, LPFeb 24, 2012Mar 22, 2012May 15, 201212,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-2-268204————

Formation tops

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

FormationMD ftSubsea
EL Toro Max (AY-3)10,450-10,375
Yegua——

Perforations

Perforated and open-hole intervals.

FromToType
10,57910,589Perforated
10,73010,740Perforated
10,93010,940Perforated
10,93010,940Open hole

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.752,48014.751,250 S
7.6256,7009.875345 S
4.511,4146.5350 S
4.514,4146.5350 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
00Sep 20, 2013Jun 13, 2013—
00Sep 18, 2013May 17, 2013—
00Jun 13, 2013Nov 1, 2012Yes

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