WELL · 42-291-32859 · DISTRICT 3

Pelican South #1

N

Liberty County  · Vertical

Pelican South #1 (API 42-291-32859) is a permitted well in Liberty County filed by Resaca Resources, L.L.C.; no completion report is on file yet.

The RRC has issued 3 drilling permits between 2011 and 2013, permitted to 9,800 ft.

Completion filings report 8 formation tops, including Yegua, Blanding, Mulepond, Glass.

Its 2 leases have reported 5.95K barrels of oil and 30.8K mcf of gas since February 2012, last reporting in July 2026. The leases carry 2 wells, so these are lease totals, not this well alone.

Operator of record

Resaca Resources, L.L.C.

Austin, TX · P-5 Y, filed Feb 4, 2026 · 130 permits on file · (512) 431-6050

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsResaca Resources, L.L.C.through Dec 2013
Latest permitResaca Resources, L.L.C.Oct 14, 2013
9,800
total depth, ft
3
permits on file
Oct 14, 2013
last permit issued
—
completed
5.95K
cumulative oil, bbl
30.8K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Feb 2012 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
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
Pelican South O-3-26179Lick Branch (8800 Sherwood)Resaca Resources, L.L.C.11.91K23KDec 2012 – Jul 2026
Pelican South O-3-25941PelicanResaca Resources, L.L.C.14.04K7.87KFeb 2012 – Feb 2014

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. 1Resaca Resources, L.L.C.Feb 2012 → Dec 2013

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
771131-99RecompletionResaca Resources, L.L.C.Oct 3, 2013Oct 14, 2013—9,650
753984-99RecompletionResaca Resources, L.L.C.Jan 3, 2013Jan 11, 2013Dec 6, 20129,800
727238-99DrillResaca Resources, L.L.C.Oct 28, 2011Nov 4, 2011Jan 12, 20129,800

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-25941————
—— O-3-26179————

Formation tops

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

FormationMD ftSubsea
Yegua5,359-5,196
Blanding5,525-5,362
Mulepond6,648-6,485
Glass6,789-6,626
P Nelson6,924-6,761
YeguaBASAL YEGUA6,996-6,833
Wilcox8,754-8,591
Wilcox8,764-8,601
Kirby8,830-8,667
Sherwood8,950-8,787

Perforations

Perforated and open-hole intervals.

FromToType
8,9688,979Perforated
9,0109,015Perforated
9,1999,203Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.6251,90312.25621 S
4.59,3558.75634 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 22, 2013Oct 3, 2013—
00Dec 14, 2012Jun 20, 2012Yes

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