WELL · 42-479-39322 · DISTRICT 4

EL Gato A #28

Y

Webb County · Big Cowboy (Lobo) field · Temp Abandoned  · Vertical

El Gato A #28 (API 42-479-39322) is a well in Webb County operated by Hilcorp Energy Company, completed December 10, 2005 and listed as temp abandoned on the RRC schedule.

The RRC has issued one drilling permit, issued October 26, 2005, permitted to 9,500 ft.

It was permitted by Axio Production Company, L.P. and has since transferred to Hilcorp Energy Company on the wellbore schedule.

Completion filings report 2 formation tops, including Wilcox, Lobo 3.

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

Operator of record

Hilcorp Energy Company

Permitted by Axio Production Company, L.P.; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Mar 26, 2026 · 3,453 permits on file · (713) 209-2411

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHilcorp Energy Company
Production reportsHilcorp Energy Companythrough Nov 2022
Latest permitAxio Production Company, L.P.Oct 26, 2005

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
Oct 26, 2005
last permit issued
Dec 10, 2005
completed
0
cumulative oil, bbl
1.09M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 2005 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Dec 10, 2005
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

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
EL Gato A G-4-215099Big Cowboy (Lobo)Hilcorp Energy Company101.09MDec 2005 – 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. 1Chesapeake Operating, Inc.Dec 2005 → Aug 2014
  2. 2Hilcorp Energy CompanySep 2014 → Nov 2022

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
608036-99DrillAxio Production Company, L.P.Oct 17, 2005Oct 26, 2005Nov 3, 20059,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-215099————

Formation tops

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

FormationMD ftSubsea
WilcoxWILCOX 16,692-6,211
WilcoxWILCOX 26,912-6,431
Lobo 38,076-7,595

Perforations

Perforated and open-hole intervals.

FromToType
8,0788,096Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62589912.25345 S
77,4738.75210 S
4.58,4366.125150 S
4.58,4366.25150 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
00Mar 16, 2007Sep 12, 2006—
00Aug 7, 2006Dec 20, 2005Yes
00Apr 7, 2006——

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