TEXAS · WELLS · WEBB COUNTY · GARNER LEASE · API 42-479-35598 · DISTRICT 04

Garner #11

Y

Webb County · Tom Walsh (Olmos) field · Producing  · Vertical

Garner #11 (API 42-479-35598) is a well in Webb County operated by Lewis Petro Properties Inc., completed November 27, 1992 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued September 18, 1992, permitted to 6,830 ft.

Completion filings report one formation top, including Olmos.

Its lease has reported 4.65K barrels of oil and 896K mcf of gas since January 1993, last reporting volume in April 2026.

Operator of record

Lewis Petro Properties Inc.

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 Apr 2026
Latest permitLewis Petro Properties, Inc.Sep 18, 1992
6,830
total depth, ft
1
permits on file
Sep 18, 1992
last permit issued
Nov 27, 1992
completed
4.65K
cumulative oil, bbl
896K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Nov 27, 1992
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

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 G-4-143138Tom Walsh (Olmos)Lewis Petro Properties, Inc.14.65K896KJan 1993 – Apr 2026

Gas, mcf lease total

Last 12 months 2,265 · prior 12 2,360(-4%)

0100200300202420252026

Chain of custody

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

  1. 1Lewis Petro Properties, Inc.Jan 1993 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
403636-99DrillLewis Petro Properties, Inc.Sep 18, 1992Sep 18, 1992Oct 10, 19927,300

Completions

CompletedLeaseFieldOperatorStatusDepth
Nov 27, 1992Garner G-4-143138Tom Walsh (Olmos)Lewis Petro Properties Inc.Producing6,830

Formation tops

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

FormationMD ftSubsea
OlmosOLMOS "A"6,630-5,955
OlmosOLMOS "B"6,715-6,040

Perforations

Perforated and open-hole intervals.

FromToType
6,6256,650Perforated
6,7146,728Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62576412.25365 S
4.56,8457.875960 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Mar 26, 1993Mar 2, 1993—
00Feb 4, 1993Jan 11, 1993—
00Jan 22, 1993Dec 8, 1992Yes
00Dec 10, 1992——

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 filed since 2004 open from the RRC's log search for this well; none are loaded here for it.

Find logs withinmiles of this well:List →Map →

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