WELL · 42-505-32018 · DISTRICT 4

Alexander #1

Plugged

Zapata County · Roleta (7483) field  · Vertical

Alexander #1 (API 42-505-32018) is a plugged well in Zapata County, plugged March 7, 2012, last operated by Chesapeake Operating Inc..

The RRC has issued one drilling permit, issued January 29, 1985, permitted to 9,500 ft.

It was permitted by Spg Exploration, Corp. and has since transferred to Chesapeake Operating Inc. on the wellbore schedule.

Completion filings report 3 formation tops, including Queen City, Reklaw, Wilcox.

Operator of record

Chesapeake Operating Inc.

Permitted by SPG Exploration, Corp.; the EWA schedule now lists a different operator.

Oklahoma City, OK · P-5 Y, filed Jul 4, 2026 · 13,061 permits on file · (405) 935-7500

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleChesapeake Operating Inc.
Production reportsChesapeake Operating, Inc.through Mar 2009
Latest permitSPG Exploration, Corp.Jan 29, 1985

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

9,500
total depth, ft
1
permits on file
Jan 29, 1985
last permit issued
Mar 22, 1985
completed
0
cumulative oil, bbl
560K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Mar 2012

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 22, 1985
Shut in
—
Plugged
Mar 7, 2012

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
Alexander G-4-115699Roleta (7483)Chesapeake Operating, Inc.10560KJan 1993 – Mar 2012

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. 1Amax Oil & Gas Inc.Jan 1993 → Mar 1994
  2. 2Union Pacific Resources CompanyApr 1994 → Jan 2001
  3. 3Rme Petroleum CompanyFeb 2001 → Apr 2002
  4. 4Legend Natural Gas, LPMay 2002 → Dec 2002
  5. 5Chesapeake Operating, Inc.Jun 2005 → Mar 2009

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
265413-99DrillSPG Exploration, Corp.Jan 29, 1985Jan 29, 1985Feb 6, 19859,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-115699————

Formation tops

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

FormationMD ftSubsea
Queen City2,183-1,807
Reklaw4,333-3,957
WilcoxUPPER WILCOX5,110-4,734
WilcoxMIDDLE WILCOX5,540-5,164
WilcoxLOWER WILCOX6,517-6,141

Perforations

Perforated and open-hole intervals.

FromToType
7,5827,716Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.7553314.75375 S
7.6257,0509.875700 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
00Apr 18, 1985Apr 2, 1985—
00Apr 11, 1985——

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