WELL · 42-505-33127 · DISTRICT 4

Yzaguirre J. #12

Y

Zapata County · Bob West (L-12 13 14 15) field · Temp Abandoned  · Directional

Yzaguirre J. #12 (API 42-505-33127) is a well in Zapata County operated by Beehive Operating LLC, completed July 23, 1994 and listed as temp abandoned on the RRC schedule.

The RRC has issued one drilling permit, issued December 1, 1993, permitted to 14,000 ft.

It was permitted by Enercorp Resources, Inc. and has since transferred to Beehive Operating LLC on the wellbore schedule.

Completion filings report 5 formation tops, including Queen, Wilcox, U. Zapata, L. Zapata.

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

Operator of record

Beehive Operating LLC

Permitted by Enercorp Resources, Inc.; the EWA schedule now lists a different operator.

Graham, TX · P-5 Y, filed May 4, 2026 · (877) 682-1308

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBeehive Operating LLC
Production reportsKCS Resources, Inc.through Sep 1995
Latest permitEnercorp Resources, Inc.Dec 1, 1993

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

14,000
total depth, ft
1
permits on file
Dec 1, 1993
last permit issued
Jul 23, 1994
completed
0
cumulative oil, bbl
9.75K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 1994 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 23, 1994
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Delinquent

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
Yzaguirre, J. G-4-151022Bob West (L-15)Beehive Operating, LLC109.75KJul 1994 – 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. 1KCS Resources, Inc.Jul 1994 → Sep 1995

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
418826-99DrillEnercorp Resources, Inc.Dec 1, 1993Dec 1, 1993Dec 5, 199314,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-151022————

Formation tops

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

FormationMD ftSubsea
QueenBASE OF QUEEN3,650-3,339
WilcoxTOP OF WILCOX5,575-5,264
U. Zapata6,200-5,889
L. Zapata6,570-6,259
Lopeno 1 Sand7,865-7,554

Perforations

Perforated and open-hole intervals.

FromToType
9,9309,936Perforated
9,9409,942Perforated
10,21210,226Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3751,50517.5635 S
9.6257,75412.252,200 S
5.510,6258.5755 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
00Oct 31, 1994Aug 11, 1994Yes
00Sep 29, 1994——

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