WELL · 42-009-31902 · DISTRICT 9

LMH Energy O Donohoe #2

Y

Archer County · Archer County Regular field · Producing  · Vertical

Lmh Energy O Donohoe #2 (API 42-009-31902) is a well in Archer County operated by Lmh Energy, completed January 26, 2025 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued December 4, 2024, permitted to 4,100 ft.

Completion filings report 10 formation tops, including Thomas Sand, Gunsight, Canyon, Strawn.

Its lease has reported 406 barrels of oil since June 2024, last reporting in July 2026. The lease carries 2 wells, so these are lease totals, not this well alone.

It holds an active disposal or injection permit; TexNet located 0 M2+ earthquakes within 10 km over the last two years.

Operator of record

LMH Energy

Wichita Falls, TX · P-5 Y, filed Feb 4, 2026 · 59 permits on file · (940) 642-8280

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleLMH Energy
Production reportsLMH Energythrough Feb 2026
Latest permitLMH EnergyDec 4, 2024
4,100
total depth, ft
1
permits on file
Dec 4, 2024
last permit issued
Jan 26, 2025
completed
406
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jun 2024 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jan 26, 2025
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

33.681470, -98.739292

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Archer 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; they carry 2 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
LMH Energy O'Donohoe O-13-34309Archer County RegularLMH Energy24060Jun 2024 – Jul 2026

Oil, barrels lease total

Last 12 months 36 · prior 12 370(-90%)

0200400202420252026

Chain of custody

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

  1. 1LMH EnergyOct 2024 → Feb 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
902667-99ReenterLMH EnergySep 13, 2024Dec 4, 2024Jan 26, 20254,100

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-13-34309————

Formation tops

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

FormationMD ftSubsea
Thomas Sand1,185-193
Gunsight1,470-478
Canyon2,265-1,273
StrawnSTRAWN SAND3,770-2,778
BrysonBRYSON SAND——
Cisco——
Davidson——
Delmar——
Megargel——
Ward Sand——

Perforations

Perforated and open-hole intervals.

FromToType
3,8803,884Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62511112.25125 S
4.53,9177.875400 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
00Apr 2, 2025Mar 19, 2025—
00Mar 12, 2025Feb 20, 2025Yes

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 →

LMH Energy O'Donohoe42-009-05039

0.5 KM · LMH Energy · Section with this well →

Thomas Sand1,200-209
Gunsight1,400-409
Delmar2,000-1,009
Strawn—
Canyon—
Davidson—
Megargel—
Bryson—

10 TOPS · FIRST 8

Luig-O'Donohoe Unit42-009-43353

0.5 KM · LMH Energy · Section with this well →

Gunsight1,485-492
Canyon2,100-1,107
Thomas Sand—
Bryson—
Cisco—
Davidson—
Delmar—
Megargel—

10 TOPS · FIRST 8

Cowan McKinney Unit42-009-01776

2.9 KM · LMH Energy · Section with this well →

Thomas Sand1,228
Gunsight1,300
Canyon2,526
Strawn3,700
Bryson—
Delmar—
Davidson—
Ward Sand—

10 TOPS · FIRST 8

Cowan-McKinney Unit42-009-43338

3.0 KM · LMH Energy · Section with this well →

Cadoo4,795-3,760
Conglomerate5,066-4,031
Ellenburger5,143-4,108
Thomas Sand—
Bryson—
Ward Sand—
Strawn—
Megargel—

13 TOPS · FIRST 8

Cowan McKinney Unit42-009-43361

3.4 KM · LMH Energy · Section with this well →

Gunsight1,490-1,333
Ward Sand—
Bryson—
Canyon—
Cisco—
Davidson—
Delmar—
Megargel—

10 TOPS · FIRST 8

Cowan-McKinney Unit42-009-43337

3.4 KM · LMH Energy · Section with this well →

Canyon—
Bryson—
Thomas Sand—
Ward Sand—
Strawn—
Megargel—
Gunsight—
Delmar—

10 TOPS · FIRST 8

Cowan-McKinney Unit42-009-43360

3.5 KM · LMH Energy · Section with this well →

Gunsight1,490-437
Ward Sand—
Thomas Sand—
Strawn—
Megargel—
Davidson—
Delmar—
Bryson—

10 TOPS · FIRST 8

Cowan-McKinney42-009-40813

4.1 KM · LMH Energy · Section with this well →

Thomas Sand1,270-240
Gunsight1,452-422
Gunsight1,470-440
Canyon2,350-1,320
Kma LM3,265-2,235
Capps LM4,066-3,036
Smithwick4,783-3,753
Caddo4,831-3,801

17 TOPS · FIRST 8

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

0
bbl, last 12 reported months
0
bbl, all reported
—
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000126903H-1 InjectionActive5001,9503,900–4,040

TexNet catalog via USGS

Seismicity near this well

0
M2+ events within 10 km, last 2 years
—
largest

A proximity count, not an attribution. How to read it →

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