TEXAS · WELLS · ZAPATA COUNTY · ALEXANDER "A" LEASE · API 42-505-35151 · DISTRICT 04

Alexander A #2

Plugged

Zapata County · Wildcat field  · Vertical

Fields on the latest permit · any of 2
Cisco-Benavides (Lobo Cons.) · Exsun (Lobo)
Not one formation; the well must be completed in one of them, and no target formation is stated. The district's wildcat field is also on the permit.

Alexander A #2 (API 42-505-35151) is a plugged well in Zapata County, plugged March 19, 2007, last operated by Chesapeake Operating Inc..

The RRC has issued one drilling permit, issued November 29, 2004, permitted to 11,500 ft.

It was permitted by Laredo Energy and has since transferred to Chesapeake Operating Inc. on the wellbore schedule.

Operator of record

Chesapeake Operating Inc.

Permitted by Laredo Energy; the EWA schedule now lists a different operator.

Based in
Oklahoma City, OK
P-5 status
Delinquent (D)
P-5 last filed
Dec 10, 2024
Permits on file
13,061
Phone
(405) 935-3100

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleChesapeake Operating Inc.
Production reportsnone
Latest permitLaredo EnergyNov 29, 2004

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

11,500
total depth, ft
1
permits on file
Nov 29, 2004
last permit issued
Jan 5, 2005
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2005 THROUGH —

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 5, 2005
Shut in
—
Plugged
Mar 19, 2007

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 "A" G-4-208271WildcatChesapeake Operating, Inc.100Jan 2005 – —

No volumes reported on these leases in the last three years.

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
554171-99DrillLaredo EnergyNov 29, 2004Nov 29, 2004Dec 4, 200411,500

Completions

CompletedLeaseFieldOperatorStatusDepth
Jan 5, 2005Alexander A G-4-208271WildcatChesapeake Operating Inc.Plugged—

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62576012.25355 S
76,5968.75350 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Jul 20, 2005Feb 15, 2005Yes
00May 19, 2005——

Well logs

1 log loaded from the RRC's log index, the latest received Aug 8, 2008. Density, Neutron, Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.

Open the RRC's log search for this well ↗
Logas describedFiles Intervalft, as filedDatereceivedSizeMB
COMBINATION: RESISTIVITY/NEUTRON/DENSITY POROSITYTIFF6,596 to 10,762Aug 8, 2008run Dec 31, 20040.46

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

The logs loaded for this well are under Well logs, with the RRC's log search for it.

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