WELL · 42-285-34093 · DISTRICT 2

Lyons #1

N

Lavaca County  · Vertical

Lyons #1 (API 42-285-34093) is a permitted well in Lavaca County filed by Texron Operating, LLC; no completion report is on file yet.

The RRC has issued one drilling permit, issued November 8, 2018, permitted to 12,500 ft.

Operator of record

Texron Operating, LLC

Bulverde, TX · P-5 Y, filed Nov 4, 2025 · 16 permits on file · (210) 213-7797

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitTexron Operating, LLCNov 8, 2018
12,500
total depth, ft
1
permits on file
Nov 8, 2018
last permit issued
—
completed
—
cumulative oil, bbl
—
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
—

Surface location

29.251200, -96.929930

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Lavaca County.

Only the permit record exists for this well so far, here and in the RRC's wellbore query. Completion reports, formation tops, lease production, and the scanned filings appear once the operator files a completion report, typically months after drilling. Petrora refreshes the wellbore file weekly, so a filing from the last few days may reach the RRC before it shows here. How long each source takes →

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
846560-99DrillTexron Operating, LLCNov 6, 2018Nov 8, 2018—12,500

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.

Nearby wells and their tops

NEAREST 8 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well has no tops filed, so it cannot anchor a section; its neighbours can.

Section of the neighbours →

Barnes42-285-32733

3.0 KM · Reo Operating LLC · Section with this well →

Wilcox11,832-11,626
Wilcox12,080-11,874

Gemelos 'B'42-285-34113

3.6 KM · Millennium Exploration Co. LLC · Section with this well →

Catahoula1,500-1,362
Frio2,393-2,255
Yegua7,500-7,362
Wilcox7,660-7,522
Edwards—
Eagle Ford—
Vicksburg—

Pope42-285-33386

7.1 KM · Suncoast Technical Services Inc · Section with this well →

Miocene (undifferentiated)1,200-1,033
Frio2,300-2,133
Hope (Frio)3,079-2,912
Hope (Frio)3,079-2,912
Vicksburg3,420-3,253
Hope (Frio 3079)—

Goodrich-Poindexter Unit42-285-33384

7.4 KM · Suncoast Technical Services Inc · Section with this well →

Brushy Creek, N. Frio2,750-2,604
Brushy Creek, Frio2,760-2,614
Hope (Frio)3,079-2,933
Hope (Miocene)3,300-3,154
Hope (Miocene 1500)—
Hope (Miocene 2730)—
Hope (Miocene 2780)—

Evans42-285-34083

7.4 KM · Trio Consulting & Management,llc · Section with this well →

Frio2,800-2,570
Yegua4,205-3,975
Wilcox6,850-6,620
Wilcox10,308-10,078
Vicksburg—
Catahoula—
Eagle Ford—
Edwards—

Klimitchek42-285-33427

8.5 KM · Dewbre Petroleum Corporation · Section with this well →

Catahoula2,310-2,155
Frio3,056-2,901
Yegua5,622-5,467
Wilcox8,020-7,865
8050' Wilcox8,020-7,865
Edwards—
Vicksburg—
Eagle Ford—

Cullen Trust42-285-33587

8.6 KM · Republic Resources, LLC. · Section with this well →

Wilcox—
Frio—
Yegua—

Fitzhenry42-285-32710

9.0 KM · XTO Energy Inc. · Section with this well →

Wilcox7,790-7,631
Johnson10,200-10,041
Sibley A13,890-13,731
RE-Frac Existing Perfs—

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