WELL · 42-311-34076 · DISTRICT 1

Henry #1

N

McMullen County · Wildcat field  · Vertical

Henry #1 (API 42-311-34076) is a well in Mcmullen County operated by Escondido Resources II LLC, completed December 16, 2008.

The RRC has issued one drilling permit (amended once), issued July 21, 2008, permitted to 13,000 ft.

Completion filings report 4 formation tops, including Escondido, Olmos, Austin Chalk, Edwards.

Its 2 leases have reported 1.41K barrels of oil since December 2008, last reporting in July 2026. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Escondido Resources II LLC

Houston, TX · P-5 Inactive, filed Nov 17, 2016 · 198 permits on file · (713) 662-0332

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleEscondido Resources II LLC
Production reportsRoyko Oil Companythrough Nov 2012
Latest permitEscondido Resources II, LLCNov 15, 2008

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

13,000
total depth, ft
2
permits on file
Nov 15, 2008
last permit issued
Dec 16, 2008
completed
1.41K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 2008 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 16, 2008
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 2 leases this well is completed on; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Henry O-1-15109A.W.P. (Olmos)Royko Oil Company11.41K0Aug 2009 – Jul 2026
Henry G-1-252813WildcatEscondido Resources II, LLC100Dec 2008 – Jan 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. 1Escondido Resources II, LLCSep 2009 → Dec 2009
  2. 2Royko Oil CompanyFeb 2010 → Nov 2012

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
665668-98DrillEscondido Resources II, LLCNov 11, 2008Nov 15, 2008Oct 25, 200813,000
665668-99DrillEscondido Resources II, LLCJun 30, 2008Jul 21, 2008Oct 25, 200812,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-1-252813————
—— O-1-15109————

Formation tops

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

FormationMD ftSubsea
Escondido8,380-8,016
Olmos9,249-8,885
Austin Chalk10,905-10,541
Edwards11,531-11,167

Perforations

Perforated and open-hole intervals.

FromToType
9,3319,369Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,88012.25545 S
5.511,5538.752,445 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 8, 2010Oct 7, 2009Yes
00Jan 8, 2010Jul 20, 2009Yes
00Dec 30, 2009——
00Nov 20, 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/31134076, documented in the API reference.