WELL · 42-291-32823 · DISTRICT 3

Henderson Ranch #2

Y

Liberty County · Willis Marsh (13200) field · Producing  · Directional

Henderson Ranch #2 (API 42-291-32823) is a well in Liberty County operated by White Stride LLC, completed October 30, 2010 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued September 3, 2010, permitted to 13,750 ft.

It was permitted by Choice Exploration, Inc. and has since transferred to White Stride LLC on the wellbore schedule.

Completion filings report 3 formation tops, including Het, Frio, Willis Marsh (11,900 Yegua).

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

Operator of record

White Stride LLC

Permitted by Choice Exploration, Inc.; the EWA schedule now lists a different operator.

Piedmont, OK · P-5 Y, filed Dec 4, 2025 · (580) 554-9554

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleWhite Stride LLC
Production reportsWhite Stride LLCthrough Mar 2026
Latest permitChoice Exploration, Inc.Sep 3, 2010

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

13,750
total depth, ft
1
permits on file
Sep 3, 2010
last permit issued
Oct 30, 2010
completed
0
cumulative oil, bbl
364K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Oct 2010 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Oct 30, 2010
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
Henderson Ranch G-3-260489Willis Marsh (13200)White Stride LLC10364KOct 2010 – Jul 2026

Gas, mcf lease total

Last 12 months 3,567 · prior 12 5,989(-40%)

05001K202420252026

Chain of custody

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

  1. 1Choice Exploration, Inc.Oct 2010 → Nov 2017
  2. 2Costa Energy, LLCDec 2017 → Nov 2025
  3. 3White Stride LLCDec 2025 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
701477-99DrillChoice Exploration, Inc.Aug 30, 2010Sep 3, 2010Sep 12, 201013,750

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-3-260489————

Formation tops

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

FormationMD ftSubsea
Het5,575-5,526
FrioBASE OF FRIO SANDS7,760-7,711
Willis Marsh (11,900 Yegua)11,795-11,746

Perforations

Perforated and open-hole intervals.

FromToType
12,99613,006Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3753,20017.51,920 S
9.6258,42912.5890 S
4.513,5606.5170 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
00Aug 11, 2011Dec 1, 2010Yes

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