WELL · 42-317-45243 · DISTRICT 10

Broken Spoke W Unit C #2LS

N

Martin County  · Horizontal

Broken Spoke W Unit C #2LS (API 42-317-45243) is a permitted horizontal well in Martin County filed by Petrolegacy Energy II, LLC; no completion report is on file yet.

The RRC has issued one drilling permit, issued May 5, 2023, permitted to 10,500 ft.

Operator of record

Petrolegacy Energy II, LLC

Denver, CO · P-5 Y, filed Dec 4, 2025 · 240 permits on file · (877) 386-2200

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitPetrolegacy Energy II, LLCMay 5, 2023
10,500
total depth, ft
1
permits on file
May 5, 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.422724, -101.929429

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Martin 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
890249-99DrillPetrolegacy Energy II, LLCMay 1, 2023May 5, 2023—10,500

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 →

Broken Spoke W 17B42-317-46414

0.0 KM · Ovintiv USA Inc. · Section with this well →

Yates2,510223
San Andres3,968-1,235
Spraberry7,555-4,822
Cisco—
Pennsylvanian—
Grayburg—
Dean—
Wolfcamp—

10 TOPS · FIRST 8

Broken Spoke W 17C42-317-46415

0.0 KM · Ovintiv USA Inc. · Section with this well →

Yates2,510223
San Andres3,968-1,235
Spraberry7,555-4,822
Pennsylvanian—
Queen—
Santa Rosa—
Wolfcamp—
Cisco—

10 TOPS · FIRST 8

Broken Spoke W 17B42-317-46413

0.0 KM · Ovintiv USA Inc. · Section with this well →

Yates2,510223
San Andres3,968-1,235
Spraberry7,555-4,822
Dean8,906-6,173
Wolfcamp—
Grayburg—
Pennsylvanian—
Queen—

10 TOPS · FIRST 8

Broken Spoke W 17C42-317-46416

0.0 KM · Ovintiv USA Inc. · Section with this well →

Yates2,510223
San Andres3,968-1,235
Clear Fork6,044-3,311
Spraberry7,555-4,822
Dean8,906-6,173
Grayburg—
Santa Rosa—
Wolfcamp—

10 TOPS · FIRST 8

Broken Spoke W 17A42-317-46412

0.0 KM · Ovintiv USA Inc. · Section with this well →

Yates2,510222
San Andres3,698-966
Spraberry7,555-4,823
Cisco—
Dean—
Grayburg—
Pennsylvanian—
Queen—

10 TOPS · FIRST 8

Broken Spoke W 17A42-317-46417

0.3 KM · Ovintiv USA Inc. · Section with this well →

Yates2,521219
San Andres3,979-1,239
Clear Fork6,055-3,315
Spraberry7,566-4,826
Dean8,917-6,177
Wolfcamp9,166-6,426
Santa Rosa—
Cisco—

10 TOPS · FIRST 8

Jamie Salinas 17A42-317-46396

0.3 KM · Ovintiv USA Inc. · Section with this well →

Yates2,521219
San Andres3,979-1,239
Clear Fork6,055-3,315
Spraberry7,566-4,826
Dean8,917-6,177
Wolfcamp9,166-6,426
Cisco—
Santa Rosa—

10 TOPS · FIRST 8

Broken Spoke W 17CC42-317-46418

0.3 KM · Ovintiv USA Inc. · Section with this well →

Yates2,521219
San Andres3,979-1,239
Clear Fork6,055-3,315
Spraberry7,566-4,826
Dean8,917-6,177
Wolfcamp9,166-6,426
Cisco—
Santa Rosa—

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