WELL · 42-175-33896 · DISTRICT 2

Lucas #3

Plugged

Goliad County · Berclair East (Yegua) field  · Vertical

Lucas #3 (API 42-175-33896) is a plugged well in Goliad County, plugged July 27, 2010, last operated by Alta Mesa Services LP.

The RRC has issued one drilling permit, issued March 7, 2006, permitted to 6,000 ft.

It was permitted by Aransas Resources, LP and has since transferred to Alta Mesa Services LP on the wellbore schedule.

Completion filings report 3 formation tops, including Frio, Vicksburg, Yegua.

Operator of record

Alta Mesa Services LP

Permitted by Aransas Resources, LP; the EWA schedule now lists a different operator.

Houston, TX · P-5 Y, filed Dec 4, 2025 · 140 permits on file · (866) 223-9968

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleAlta Mesa Services LP
Production reportsAlta Mesa Services, LPthrough Feb 2008
Latest permitAransas Resources, LPMar 7, 2006

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

6,000
total depth, ft
1
permits on file
Mar 7, 2006
last permit issued
Jan 21, 2010
completed
0
cumulative oil, bbl
320K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Apr 2006 THROUGH Jul 2010

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jan 21, 2010
Shut in
—
Plugged
Jul 27, 2010

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
Lucas G-2-220586Berclair, East (Yegua)Alta Mesa Services, LP10320KApr 2006 – Jul 2010

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. 1Aransas Resources, LPApr 2006 → Oct 2006
  2. 2Alta Mesa Services, LPNov 2006 → Feb 2008

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
615380-99DrillAransas Resources, LPMar 7, 2006Mar 7, 2006Mar 11, 20066,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-2-220586————

Formation tops

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

FormationMD ftSubsea
Frio2,295-2,095
Frio2,600-2,400
Frio2,800-2,600
Vicksburg3,715-3,515
Yegua5,600-5,400

Perforations

Perforated and open-hole intervals.

FromToType
2,6052,609Perforated
2,7972,801Perforated
5,6285,634Perforated
5,7305,782Perforated
5,7565,759Perforated
5,7635,766Perforated
5,7805,782Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
10.751,02314.75612 S
7.6254,4049.875720 S
4.55,9006.75350 S
—5,9006.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. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Jul 21, 2010Apr 29, 2010—
00May 10, 2010Jan 11, 2010—
00Mar 6, 2007May 19, 2006Yes
00Oct 31, 2006May 19, 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/17533896, documented in the API reference.