WELL · 42-301-35201 · DISTRICT 8

Lindsay 3-10B-55-1 #332H

Y

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

Lindsay 3-10b-55-1 #332H (API 42-301-35201) is a horizontal well in Loving County operated by Wpx Energy Permian LLC, completed October 20, 2021 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued October 1, 2020, permitted to 16,000 ft.

Completion filings report 10 formation tops, including Bell Canyon, Cherry Canyon, Brushy Canyon, Bone Spring.

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

Operator of record

WPX Energy Permian LLC

Oklahoma City, OK · P-5 Y, filed Sep 4, 2025 · 956 permits on file · (800) 465-8314

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleWPX Energy Permian LLC
Production reportsWPX Energy Permian, LLCthrough Mar 2026
Latest permitWPX Energy Permian, LLCOct 1, 2020
16,000
total depth, ft
1
permits on file
Oct 1, 2020
last permit issued
Oct 20, 2021
completed
0
cumulative oil, bbl
2.01M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Dec 2020 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Oct 20, 2021
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

Surface location

31.999526, -103.744782

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
Lindsay 3-10B-55-1 G-10-290457Sandbar (Bone Spring)WPX Energy Permian, LLC102.01MDec 2020 – Jul 2026

Gas, mcf lease total

Last 12 months 165,658 · prior 12 261,774(-37%)

020K40K202420252026

Chain of custody

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

  1. 1WPX Energy Permian, LLCJul 2021 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
865323-99DrillWPX Energy Permian, LLCSep 30, 2020Oct 1, 2020May 22, 202116,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-10-290457————

Formation tops

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

FormationMD ftSubsea
Bell Canyon4,100-972
Cherry Canyon5,179-2,051
Brushy Canyon6,439-3,311
Bone Spring8,092-4,964
AtokaATOKA - HIGH PRESSURE——
Delaware——
Pennsylvanian——
Red Bluff——
Strawn——
Wolfcamp——

Perforations

Perforated and open-hole intervals.

FromToType
10,90318,372Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3751,44117.5944 S
9.6254,53012.25805 S
710,8918.75682 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
00Oct 4, 2022Aug 2, 2022Yes
00Oct 20, 2021Sep 29, 2021—
00Mar 24, 2021Mar 10, 2021Yes

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 →

Lindsay 3-10C-55-142-301-35202

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

Bell Canyon4,090-962
Cherry Canyon5,141-2,013
Brushy Canyon6,437-3,309
Bone Spring8,087-4,959
Delaware—
Atoka—
Wolfcamp—
Strawn—

10 TOPS · FIRST 8

Lindsay 3-10D-55-142-301-35203

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

Bell Canyon4,038-910
Cherry Canyon5,146-2,018
Brushy Canyon6,404-3,276
Bone Spring8,068-4,940
Red Bluff—
Strawn—
Pennsylvanian—
Atoka—

10 TOPS · FIRST 8

Lindsay 3-10E-55-142-301-35204

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

Bell Canyon3,991-863
Cherry Canyon5,126-1,998
Brushy Canyon6,395-3,267
Bone Spring8,053-4,925
Atoka—
Delaware—
Wolfcamp—
Strawn—

10 TOPS · FIRST 8

Lindsay 10-3F42-301-33649

0.1 KM · RKI Exploration & Production LLC · Section with this well →

Bell Canyon4,037-936
Cherry Canyon5,157-2,056
Brushy Canyon6,349-3,248
Bone Spring8,036-4,935
Wolfcamp11,217-8,116
Delaware—
Pennsylvanian—
Red Bluff—

10 TOPS · FIRST 8

Lindsay 10-3E42-301-33648

0.1 KM · RKI Exploration & Production LLC · Section with this well →

Bell Canyon4,024-922
Cherry Canyon5,151-2,049
Brushy Canyon6,345-3,243
Bone Spring8,031-4,929
Wolfcamp11,214-8,112
Atoka—
Delaware—
Pennsylvanian—

10 TOPS · FIRST 8

Lindsay 10-3I42-301-33812

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

Cherry Canyon5,155-2,052
Brushy Canyon6,350-3,247
Bone Spring8,037-4,934
Wolfcamp11,224-8,121
Red Bluff—
Fusselman—
Ellenburger—
Devonian—

14 TOPS · FIRST 8

Lindsay 10-3G42-301-33650

0.1 KM · RKI Exploration & Production LLC · Section with this well →

Bell Canyon4,039-938
Cherry Canyon5,153-2,052
Brushy Canyon6,347-3,246
Bone Spring8,035-4,934
Wolfcamp11,222-8,121
Pennsylvanian—
Strawn—
Red Bluff—

10 TOPS · FIRST 8

Lindsay 10-3B42-301-33645

0.1 KM · RKI Exploration & Production LLC · Section with this well →

Atoka—
Wolfcamp—
Strawn—
Red Bluff—
Pennsylvanian—
Delaware—
Cherry Canyon—
Brushy Canyon—

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