WELL · 42-479-40398 · DISTRICT 4

Moore #1

Y

Webb County · Vaquillas Ranch (Lobo Cons.) field · Producing  · Vertical

Moore #1 (API 42-479-40398) is a well in Webb County operated by Lucky Lad Energy LLC, completed January 28, 2009 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued October 8, 2008, permitted to 12,500 ft.

It was permitted by Laredo Energy and has since transferred to Lucky Lad Energy LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Wilcox, Lobo Unconformity, Wills Point.

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

Operator of record

Lucky Lad Energy LLC

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

Magnolia, TX · P-5 Y, filed Jun 4, 2026 · (832) 390-1060

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleLucky Lad Energy LLC
Production reportsEncina Resources, LLCthrough Oct 2025
Latest permitLaredo EnergyOct 8, 2008

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

12,500
total depth, ft
1
permits on file
Oct 8, 2008
last permit issued
Jan 28, 2009
completed
0
cumulative oil, bbl
469K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2009 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jan 28, 2009
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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
Moore G-4-249559Vaquillas Ranch (Lobo Cons.)Lucky Lad Energy, LLC10469KJan 2009 – Jul 2026

Gas, mcf lease total

Last 12 months 28 · prior 12 120(-77%)

0204060202420252026

Chain of custody

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

  1. 1Laredo EnergyJan 2009 → Apr 2014
  2. 2Laredo Energy Operating, LLCMay 2014 → Oct 2014
  3. 3Encina Resources, LLCNov 2014 → Oct 2025

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
672058-99DrillLaredo EnergySep 29, 2008Oct 8, 2008Nov 2, 200812,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-249559————

Formation tops

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

FormationMD ftSubsea
WilcoxLOWER WILCOX8,200-7,575
Lobo Unconformity9,750-9,125
Wills Point11,100-10,475

Perforations

Perforated and open-hole intervals.

FromToType
10,66410,832Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6252,68012.25834 S
78,1178.75400 S
4.511,2006.125342 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 31, 2009—
00Sep 11, 2009Apr 3, 2009Yes
00Jul 27, 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/47940398, documented in the API reference.