WELL · 42-327-30908 · DISTRICT 7

Lizzy B #3

Y

Menard County · Celery (Gunsight) field · Producing  · Vertical

Lizzy B #3 (API 42-327-30908) is a well in Menard County operated by Otex LLC, completed April 11, 2001 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued January 26, 2001, permitted to 2,350 ft.

It was permitted by Morrow Resources, Inc. and has since transferred to Otex LLC on the wellbore schedule.

Completion filings report 2 formation tops, including King, Gunsight.

Its lease has reported 6.77K barrels of oil and 46 mcf of gas since February 2000, last reporting in July 2026. The lease carries 2 wells, so these are lease totals, not this well alone.

Operator of record

Otex LLC

Permitted by Morrow Resources, Inc.; the EWA schedule now lists a different operator.

Santa Anna, TX · P-5 Y, filed Oct 4, 2025 · (325) 977-1600

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleOtex LLC
Production reportsOtex LLCthrough Apr 2026
Latest permitMorrow Resources, Inc.Jan 26, 2001

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

2,350
total depth, ft
1
permits on file
Jan 26, 2001
last permit issued
Apr 11, 2001
completed
6.77K
cumulative oil, bbl
46
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2000 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Apr 11, 2001
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; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Lizzy "B" O-9-14965Celery (Gunsight)Otex LLC26.77K46Feb 2000 – Jul 2026

Oil, barrels lease total

Last 12 months 7 · prior 12 5(+40%)

012202420252026

Chain of custody

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

  1. 1Morrow Resources, Inc.Feb 2000 → May 2004
  2. 2Subsurface Production, Inc.Jun 2004 → Jun 2011
  3. 3Pentergy Operating, LLCJul 2011 → Jul 2015
  4. 4Otex LLCOct 2019 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
504292-99DrillMorrow Resources, Inc.Jan 19, 2001Jan 26, 2001Feb 3, 20012,350

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-9-14965————

Formation tops

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

FormationMD ftSubsea
King1,540654
Gunsight1,811383

Perforations

Perforated and open-hole intervals.

FromToType
1,8121,816Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62537411145 S
4.51,8656.7575 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 13, 2002Jan 14, 2002Yes
00Feb 21, 2002——

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