WELL · 42-301-35812 · DISTRICT 8

TXL 41/44 #H302CN

Y

Loving County · Sandbar (Bone Spring) field · Producing  · Horizontal

Txl 41/44 #H302CN (API 42-301-35812) is a horizontal well in Loving County operated by Mewbourne Oil Company, completed January 11, 2023 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued February 25, 2022, permitted to 9,731 ft.

Completion filings report 8 formation tops, including Delaware, Bell Canyon, Cherry Canyon, Brushy Canyon.

No lease production has been reported under this well’s leases.

Operator of record

Mewbourne Oil Company

Tyler, TX · P-5 Y, filed May 4, 2026 · 2,061 permits on file · (903) 561-2900

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleMewbourne Oil Company
Production reportsMewbourne Oil Companythrough Apr 2026
Latest permitMewbourne Oil CompanyFeb 25, 2022
9,731
total depth, ft
1
permits on file
Feb 25, 2022
last permit issued
Jan 11, 2023
completed
0
cumulative oil, bbl
1.6M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2023 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jan 11, 2023
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

31.912021, -103.878441

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Loving 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
TXL 41/44 G-10-294828Sandbar (Bone Spring)Mewbourne Oil Company101.6MJan 2023 – Jul 2026

Gas, mcf lease total

Last 12 months 303,485 · prior 12 509,216(-40%)

050K100K202420252026

Chain of custody

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

  1. 1Mewbourne Oil CompanyJan 2023 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
877213-99DrillMewbourne Oil CompanyFeb 17, 2022Feb 25, 2022Aug 10, 20229,731

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-10-294828————

Formation tops

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

FormationMD ftSubsea
Delaware3,180-307
Bell Canyon3,206-333
Cherry Canyon4,127-1,254
Brushy Canyon5,259-2,386
Bone Spring7,001-4,128
Bone Spring1ST BONE SPRING7,932-5,059
Bone Spring2ND BONE SPRING8,566-5,693
Pennsylvanian——
Red Bluff——
Wolfcamp——

Perforations

Perforated and open-hole intervals.

FromToType
9,67919,875Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37581517.5600 S
9.6253,13012.25800 S
79,0678.75850 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
00Jun 23, 2023Apr 4, 2023Yes

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) and the University Lands library. 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 →

TXL 41/4442-301-35811

0.0 KM · Mewbourne Oil Company · Section with this well →

Delaware3,188-313
Bell Canyon3,210-335
Cherry Canyon4,128-1,253
Brushy Canyon5,261-2,386
Bone Spring7,009-4,134
Atoka—
Wolfcamp—
Strawn—

10 TOPS · FIRST 8

TXL 41/4442-301-35809

0.0 KM · Mewbourne Oil Company · Section with this well →

Delaware3,166-289
Bell Canyon3,195-318
Cherry Canyon4,107-1,230
Brushy Canyon5,227-2,350
Bone Spring7,026-4,149
Wolfcamp—
Strawn—
Atoka—

10 TOPS · FIRST 8

TXL 41/4442-301-35805

0.0 KM · Mewbourne Oil Company · Section with this well →

Delaware3,210-332
Bell Canyon3,234-356
Cherry Canyon4,136-1,258
Brushy Canyon5,281-2,403
Bone Spring7,036-4,158
Bone Spring7,982-5,104
Bone Spring8,581-5,703
Pennsylvanian—

10 TOPS · FIRST 8

CBR 41-44K-56-142-301-34338

0.3 KM · WPX Energy Permian, LLC · Section with this well →

Bell Canyon3,198-287
Delaware3,198-287
Cherry Canyon4,276-1,365
Brushy Canyon5,437-2,526
Bone Spring7,031-4,120
Wolfcamp10,162-7,251
Atoka—
Pennsylvanian—

10 TOPS · FIRST 8

CBR 41-44J-56-142-301-34330

0.3 KM · WPX Energy Permian, LLC · Section with this well →

Bell Canyon3,203-293
Delaware3,203-293
Cherry Canyon4,295-1,385
Brushy Canyon5,435-2,525
Bone Spring7,029-4,119
Wolfcamp10,161-7,251
Atoka—
Strawn—

10 TOPS · FIRST 8

CY 4142-301-34329

0.3 KM · WPX Energy Permian, LLC · Section with this well →

Delaware3,203-294
Bell Canyon3,203-294
Cherry Canyon4,274-1,365
Brushy Canyon5,439-2,530
Bone Spring7,028-4,119
Wolfcamp10,159-7,250
Atoka—
Strawn—

10 TOPS · FIRST 8

CY 4142-301-34326

0.3 KM · WPX Energy Permian, LLC · Section with this well →

Bell Canyon3,210-301
Delaware3,210-301
Cherry Canyon4,269-1,360
Brushy Canyon5,440-2,531
Bone Spring7,023-4,114
Wolfcamp10,157-7,248
Atoka—
Pennsylvanian—

10 TOPS · FIRST 8

CBR 41-44I-56-142-301-34320

0.3 KM · WPX Energy Permian, LLC · Section with this well →

Delaware3,202-293
Bell Canyon3,202-293
Cherry Canyon4,267-1,358
Brushy Canyon5,433-2,524
Bone Spring7,017-4,108
Wolfcamp10,151-7,242
Pennsylvanian—
Red Bluff—

10 TOPS · FIRST 8

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