WELL · 42-115-33916 · DISTRICT 10

Dal Paso SWD #1

WaterN

Dawson County  · Vertical

Dal Paso Swd #1 (API 42-115-33916) is a permitted well in Dawson County filed by Bqh Operating, LLC; no completion report is on file yet.

The RRC has issued one drilling permit, issued July 25, 2023, permitted to 5,220 ft.

Operator of record

BQH Operating, LLC

Midland, TX · P-5 Y, filed Jul 4, 2025 · 6 permits on file · (432) 553-8452

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitBQH Operating, LLCJul 25, 2023
5,220
total depth, ft
1
permits on file
Jul 25, 2023
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

32.604396, -101.959869

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Dawson 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
892341-99DrillBQH Operating, LLCJul 24, 2023Jul 25, 2023—5,220

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 has no tops filed, so it cannot anchor a section; its neighbours can.

Section of the neighbours →

Cutter Cochise B42-115-34016

1.0 KM · SM Energy Company · Section with this well →

Yates2,591312
San Andres4,342-1,439
Clear Fork5,524-2,621
Spraberry7,672-4,769
Dean9,045-6,142
Canyon—
Devonian—
Mississippian—

10 TOPS · FIRST 8

Cutter A42-115-34015

1.0 KM · SM Energy Company · Section with this well →

Yates2,589314
San Andres4,385-1,482
Clear Fork5,553-2,650
Spraberry7,669-4,766
Devonian—
Canyon—
Dean—
Mississippian—

10 TOPS · FIRST 8

Blue Beauty A42-115-34013

1.1 KM · SM Energy Company · Section with this well →

Yates2,555341
San Andres4,333-1,437
Clear Fork5,509-2,613
Spraberry7,645-4,749
Dean9,029-6,133
Devonian—
Mississippian—
Pennsylvanian—

10 TOPS · FIRST 8

Blue Beauty B42-115-34014

1.1 KM · SM Energy Company · Section with this well →

Yates2,557339
San Andres4,329-1,433
Clear Fork5,501-2,605
Spraberry7,715-4,819
Dean9,021-6,125
Pennsylvanian—
Canyon—
Devonian—

11 TOPS · FIRST 8

Big Jake B42-115-34026

1.4 KM · SM Energy Company · Section with this well →

Yates2,621289
San Andres4,361-1,451
Clear Fork5,535-2,625
Spraberry7,686-4,776
Dean9,068-6,158
Mississippian—
Pennsylvanian—
Wolfcamp—

10 TOPS · FIRST 8

Big Jake A42-115-34025

1.4 KM · SM Energy Company · Section with this well →

Yates2,623287
San Andres4,400-1,490
Clear Fork5,483-2,573
Spraberry7,700-4,790
Dean9,078-6,168
Devonian—
Wolfcamp—
Silurian (undifferentiated)—

11 TOPS · FIRST 8

Blue Beauty 15-2242-115-33829

1.7 KM · Reliance Energy, Inc. · Section with this well →

Yates2,530375
San Andres4,750-1,845
Spraberry7,650-4,745
Dean9,022-6,117
Wolfcamp—
Devonian—
Mississippian—
Pennsylvanian—

10 TOPS · FIRST 8

Arod 2-11-1442-115-33871

2.1 KM · Reliance Energy, Inc. · Section with this well →

Yates2,595308
San Andres4,750-1,847
Spraberry7,522-4,619
Dean8,962-6,059
Pennsylvanian—
Mississippian—
Devonian—
Wolfcamp—

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