TEXAS · WELLS · WEBB COUNTY · JACKSON VESTAL LEASE · API 42-479-41443 · DISTRICT 04

Jackson Vestal #2H

Y

Webb County · Owen (Olmos) field · Producing  · Horizontal

Jackson Vestal #2H (API 42-479-41443) is a horizontal well in Webb County operated by Lewis Petro Properties Inc., completed January 2, 2012 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued August 17, 2011, permitted to 5,119 ft.

Completion filings report 2 formation tops, including Escondido, Shale Marker.

Its lease has reported 3.29K barrels of oil and 1.32M mcf of gas since January 2012, 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.Aug 17, 2011
5,119
total depth, ft
1
permits on file
Aug 17, 2011
last permit issued
Jan 2, 2012
completed
3.29K
cumulative oil, bbl
1.32M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2012 THROUGH Apr 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jan 2, 2012
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
Jackson Vestal G-4-266483Owen (Olmos)Lewis Petro Properties, Inc.13.29K1.32MJan 2012 – Apr 2026

Gas, mcf lease total

Last 12 months 22,281 · prior 12 22,677(-2%)

01K2K3K202420252026

Chain of custody

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

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

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
722333-99DrillLewis Petro Properties, Inc.Aug 15, 2011Aug 17, 2011Aug 24, 201112,500

Completions

CompletedLeaseFieldOperatorStatusDepth
Jan 2, 2012Jackson Vestal G-4-266483Owen (Olmos)Lewis Petro Properties Inc.Producing5,119

Formation tops

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

FormationMD ftSubsea
Escondido1ST ESCONDIDO5,022-4,420
Escondido2ND ESCONDIDO5,170-4,568
Shale Marker5,230-4,628

Perforations

Perforated and open-hole intervals.

FromToType
5,4329,772Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
7.6252,2559.875366 S
4.59,8006.75752 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 11, 2013Jul 31, 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 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/47941443, documented in the API reference.