WELL · 42-041-32670 · DISTRICT 3

Lott-Lee a WB #2H

Y

Brazos County · Madisonville W. (Woodbine -A-) field · Producing  · Horizontal

Lott-Lee A WB #2H (API 42-041-32670) is a horizontal well in Brazos County operated by Wildfire Energy Operating LLC, completed February 1, 2026 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit (amended once), issued January 24, 2025, permitted to 8,400 ft.

Completion filings report 9 formation tops, including Pecan Gap, Austin Chalk, Woodbine, Buda.

Its lease has reported 23.7K barrels of oil and 11.3K mcf of gas since November 2025, last reporting in July 2026.

Operator of record

Wildfire Energy Operating LLC

Houston, TX · P-5 Y, filed Oct 4, 2025 · 171 permits on file · (713) 261-3871

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleWildfire Energy Operating LLC
Production reportsWildfire Energy Operating LLCthrough Mar 2026
Latest permitWildfire Energy Operating LLCJan 24, 2025
8,400
total depth, ft
2
permits on file
Jan 24, 2025
last permit issued
Feb 1, 2026
completed
23.7K
cumulative oil, bbl
11.3K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Nov 2025 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Feb 1, 2026
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

30.860504, -96.216923

OpenStreetMap → ·  Google Maps →

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

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
Lott-Lee a WB O-3-28264Madisonville, W. (Woodbine -A-)Wildfire Energy Operating LLC123.7K11.3KNov 2025 – Jul 2026

Oil, barrels lease total

Last 12 months 23,697 · prior 12 0

05K10K15K202420252026

Gas, mcf lease total

Last 12 months 11,338 · prior 12 0

05K10K202420252026

Chain of custody

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

  1. 1Wildfire Energy Operating LLCJan 2026 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
905386-98DrillWildfire Energy Operating LLCApr 21, 2026Jan 24, 2025Jan 9, 20268,400
905386-99DrillWildfire Energy Operating LLCJan 21, 2025Jan 24, 2025Nov 16, 20258,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-3-28264————

Formation tops

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

FormationMD ftSubsea
Pecan Gap6,953-6,652
Austin ChalkAUSTIN CHALK - LOST CIRCULATION7,781-7,480
Woodbine8,201-7,900
WoodbineWOODBINE - PRODUCTION8,201-7,900
BudaBUDA - PRODUCTION——
EdwardsEDWARDS - DISPOSAL——
GeorgetownGEORGETOWN - PRODUCTION——
NavarroNAVARRO - DISPOSAL——
SpartaSPARTA - DISPOSAL——
WilcoxWILCOX - DISPOSAL——
WoodbineWOODBINE - PRODUCTION——

Perforations

Perforated and open-hole intervals.

FromToType
8,52516,402Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6253,74712.252,180 S
5.516,4257.8751,940 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
00May 22, 2026Apr 13, 2026—
00Feb 9, 2026Jan 9, 2026Yes

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's tops beside its 5 nearest neighbours, subsea-aligned so they line up regardless of surface terrain.

Open the cross-section →

Lott-Lee WB Unit42-041-32671

0.0 KM · Wildfire Energy Operating LLC · Section with this well →

Pecan Gap7,080-6,779
Austin Chalk7,768-7,467
Woodbine8,184-7,883
Woodbine8,184-7,883
Sparta—
Georgetown—
Edwards—
Buda—

10 TOPS · FIRST 8

Wilson-Payne42-041-32368

0.6 KM · Vess Oil Corporation · Section with this well →

Navarro5,360-5,060
Austin Chalk7,794-7,494
Woodbine8,104-7,804
Wilcox—
Sparta—
Georgetown—
Edwards—
Buda—

Wilson-Payne42-041-32367

0.6 KM · Vess Oil Corporation · Section with this well →

Navarro5,356-5,055
Austin Chalk7,795-7,494
Woodbine8,104-7,803
Buda—
Edwards—
Georgetown—
Sparta—
Wilcox—

Mc.t (Allocation)42-041-32526

1.2 KM · MD America Energy, LLC · Section with this well →

Navarro5,458-5,159
Austin Chalk7,759-7,460
Woodbine8,152-7,853
Wilcox—
Buda—
Edwards—
Georgetown—
Sparta—

Wilson Odom (Allocation)42-041-32560

1.7 KM · MD America Energy, LLC · Section with this well →

Austin Chalk8,119-7,872
Woodbine8,238-7,991
Navarro8,714-8,467
Wilcox—
Edwards—
Buda—
Sparta—
Georgetown—

Clark (Allocation)42-041-32289

2.7 KM · Woodbine Acquisition LLC · Section with this well →

Midway4,580-4,318
Nacatoch5,963-5,701
Austin Chalk7,780-7,518
Ash Marker8,087-7,825
Ash Marker8,087-7,825
Austin Chalk8,120-7,858
Sub-Clarksville8,124-7,862
Woodbine8,620-8,358

16 TOPS · FIRST 8

Wilson Unit C42-041-32070

2.7 KM · Woodbine Acquisition Corporation · Section with this well →

Austin Chalk8,159-7,923
Sub-Clarkville8,164-7,928
Sub-Clarksville8,164-7,928
Woodbine8,268-8,032

Odom, Henry K. #142-041-30408

2.8 KM · Etx Energy, LLC · Section with this well →

Pecan Gap7,000-6,765
Austin Chalk7,750-7,515
Buda9,000-8,765

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