WELL · 42-505-34614 · DISTRICT 4

Guerra Avelino #6A

N

Zapata County · Lopeno (Consolidated) field  · Directional

Guerra Avelino #6A (API 42-505-34614) is a well in Zapata County operated by Dominion Expl. & Prod. Inc., completed December 18, 2002.

The RRC has issued one drilling permit, issued September 25, 2002, permitted to 12,000 ft.

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

Operator of record

Dominion Expl. & Prod. Inc.

Houston, TX · P-5 Y, filed Dec 5, 2008 · 271 permits on file

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleDominion Expl. & Prod. Inc.
Production reportsXTO Energy Inc.through Nov 2016
Latest permitDominion Expl. & Prod., Inc.Sep 25, 2002

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

12,000
total depth, ft
1
permits on file
Sep 25, 2002
last permit issued
Dec 18, 2002
completed
0
cumulative oil, bbl
3.3M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Nov 2002 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 18, 2002
Shut in
—
Plugged
—

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 4 leases this well is completed on; they carry 4 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Guerra, Avelino G-4-201377Lopeno (Wilcox I)Vantage Operating II, LLC103.3MNov 2002 – Jul 2026
Guerra, Avelino G-4-201405Lopeno (Wilcox G)Dominion Expl. & Prod., Inc.100Dec 2002 – Jun 2005
Guerra, Avelino G-4-201406Lopeno (Wilcox J)Dominion Expl. & Prod., Inc.100Nov 2002 – Jun 2005
Guerra, Avelino G-4-201407Lopeno (Wilcox 10,200)Dominion Expl. & Prod., Inc.100Dec 2002 – Jun 2005

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. 1Dominion Expl. & Prod., Inc.Dec 2002 → Jul 2007
  2. 2XTO Energy Inc.Aug 2007 → Nov 2016

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
524007-99DrillDominion Expl. & Prod., Inc.Sep 24, 2002Sep 25, 2002Dec 5, 200212,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-201377————
—— G-4-201405————
—— G-4-201406————
—— G-4-201407————

Perforations

Perforated and open-hole intervals.

FromToType
10,22010,232Perforated
10,22010,290Perforated
10,27810,290Perforated
10,52510,545Perforated
10,52510,868Perforated
10,84810,868Perforated
11,06011,080Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37561517.5715 S
9.6255,50612.25573 S
3.511,5054.75535 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 11, 2007Dec 22, 2006—
00Oct 26, 2004Sep 1, 2004—
00Aug 16, 2004Jan 28, 2003—
00Jul 20, 2004Dec 19, 2002Yes
00Jun 8, 2004——
00Jun 4, 2004——

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