WELL · 42-505-36218 · DISTRICT 4

Guerra Avelino #8A

Y

Zapata County · Lopeno (Consolidated) field · Producing  · Directional

Guerra Avelino #8A (API 42-505-36218) is a well in Zapata County operated by Vantage Operating II LLC, completed March 7, 2009 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued July 10, 2008, permitted to 14,000 ft.

It was permitted by Xto Energy Inc. and has since transferred to Vantage Operating II LLC on the wellbore schedule.

Completion filings report one formation top, including Wilcox.

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

Operator of record

Vantage Operating II LLC

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

San Antonio, TX · P-5 Y, filed May 4, 2026 · (210) 827-1151

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleVantage Operating II LLC
Production reportsVantage Operating II, LLCthrough Apr 2026
Latest permitXTO Energy Inc.Jul 10, 2008

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
Jul 10, 2008
last permit issued
Mar 7, 2009
completed
0
cumulative oil, bbl
1.52M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 2008 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Mar 7, 2009
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
Guerra, Avelino G-4-251689Lopeno (Consolidated)Vantage Operating II, LLC101.52MOct 2008 – Jul 2026

Gas, mcf lease total

Last 12 months 10,441 · prior 12 15,990(-35%)

02K4K202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1XTO Energy Inc.Oct 2008 → Jun 2021
  2. 2Vantage Operating II, LLCJul 2021 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
664914-99DrillXTO Energy Inc.Jun 19, 2008Jul 10, 2008Aug 18, 200814,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-251689————

Formation tops

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

FormationMD ftSubsea
WilcoxWILCOX G-110,295-9,925
WilcoxWILCOX J10,895-10,525
WilcoxWILCOX K11,165-10,795

Perforations

Perforated and open-hole intervals.

FromToType
11,07011,090Perforated
11,36011,380Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37559817.5532 S
9.6255,47012.25596 S
4.511,4508.51,000 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
00Nov 5, 2009Aug 27, 2009—
00Oct 21, 2009Nov 26, 2008Yes
00Oct 14, 2009——

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