WELL · 42-479-35625 · DISTRICT 4

Garner Ranch 1057 #2

Plugged

Webb County · Tom Walsh (Olmos) field  · Vertical

Garner Ranch 1057 #2 (API 42-479-35625) is a plugged well in Webb County, plugged May 23, 2018, last operated by Lewis Petro Properties Inc..

The RRC has issued one drilling permit (amended once), issued October 8, 1992, permitted to 10,000 ft.

It was permitted by Texaco E & P Inc. and has since transferred to Lewis Petro Properties Inc. on the wellbore schedule.

Completion filings report 2 formation tops, including Wilcox, Carrizo.

Operator of record

Lewis Petro Properties Inc.

Permitted by Texaco E & P Inc.; the EWA schedule now lists a different operator.

Based in
San Antonio, TX
P-5 status
Active (A)
P-5 last filed
Jan 28, 2026
Permits on file
3,007
Phone
(210) 384-3200

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleLewis Petro Properties Inc.
Production reportsLewis Petro Properties, Inc.through Aug 2015
Latest permitTexaco E & P Inc.Oct 8, 1992

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

10,000
total depth, ft
2
permits on file
Oct 8, 1992
last permit issued
Dec 24, 1992
completed
0
cumulative oil, bbl
63.8K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH May 2018

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 24, 1992
Shut in
—
Plugged
May 23, 2018

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
Garner Ranch 1057 G-4-143565Tom Walsh (Olmos)Lewis Petro Properties, Inc.1063.8KJan 1993 – May 2018

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. 1Texaco E & P Inc.Jan 1993 → Nov 1994
  2. 2Petro-Hunt CorporationDec 1994 → May 1996
  3. 3Lewis Petro Properties, Inc.Jan 1998 → Aug 2015

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
404399-98DrillTexaco E & P Inc.Nov 3, 1992Oct 8, 1992Nov 9, 199210,000
404399-99DrillTexaco E & P Inc.Oct 7, 1992Oct 8, 1992—10,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-4-143565————

Formation tops

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

FormationMD ftSubsea
Wilcox1,870-1,163
Carrizo4,190-3,483

Perforations

Perforated and open-hole intervals.

FromToType
6,6276,629Perforated
6,6406,642Perforated
6,6966,700Perforated
6,7036,705Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62576414390 S
4.56,7857.875475 S
4.5—7.875500 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
00Feb 22, 1993Jan 14, 1993Yes
00Jan 26, 1993——

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