WELL · 42-235-36254 · DISTRICT 7

Sugg 2 #17

Plugged

Irion County · Sugg Ranch (Canyon) field  · Directional

Sugg 2 #17 (API 42-235-36254) is a plugged well in Irion County, plugged May 1, 2018, last operated by Compass Energy Operating LLC.

The RRC has issued one drilling permit, issued April 9, 2018, permitted to 9,000 ft.

It was permitted by Compass Energy Operating, LLC and has since transferred to Compass Energy Operating LLC on the wellbore schedule.

Operator of record

Compass Energy Operating LLC

Permitted by Compass Energy Operating, LLC; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitCompass Energy Operating, LLCApr 9, 2018

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

9,000
total depth, ft
1
permits on file
Apr 9, 2018
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
May 1, 2018

Surface location

31.472974, -101.028825

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Irion 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
836916-99DrillCompass Energy Operating, LLCFeb 28, 2018Apr 9, 2018Apr 20, 20189,000

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 →

Sugg '41'42-235-33869

1.6 KM · TXP, Incorporated · Section with this well →

San Angelo1,0981,422
Clear Fork2,980-460
Wolfcamp5,290-2,770
T/Canyon Sand6,950-4,430
Canyon6,950-4,430

Sugg 7A-191042-235-36526

6.1 KM · Compass Energy Operating, LLC · Section with this well →

Grayburg1,3661,039
San Andres1,721684
Clear Fork2,681-276
Spraberry4,166-1,761
Wolfcamp5,934-3,529
Canyon—
Fusselman—

Sheen 8A-1142-235-36527

6.2 KM · Compass Energy Operating, LLC · Section with this well →

Grayburg1,1681,144
San Andres1,515797
Clear Fork2,579-267
Spraberry3,718-1,406
Wolfcamp5,616-3,304
Canyon—
Fusselman—

Sugg '7A'42-235-36253

6.8 KM · Compass Energy Operating, LLC · Section with this well →

Grayburg1,2461,056
San Andres1,588714
San Angelo2,200102
Clear Fork2,700-398
Spraberry3,200-898
Wolfcamp4,200-1,898
Canyon5,700-3,398
Fusselman—

Sugg 642-235-33426

8.1 KM · IP Petroleum Company, Inc. · Section with this well →

Wolfcamp5,564-3,204
Canyon6,781-4,421
Canyon7,060-4,700
Canyon7,365-5,005

Sugg Farmar '6'42-235-34864

9.2 KM · TXP, Incorporated · Section with this well →

Coleman Junction3,710-1,415
Dean5,370-3,075
Canyon6,510-4,215

Flying -B- Ranch42-451-32884

9.4 KM · Maverick Operating, LLC · Section with this well →

San Angelo4102,112
San Andres1,5001,022
Strawn—
Canyon—
Cisco—
Clear Fork—
Coleman Junction—

Flying -B- Ranch42-451-32868

9.4 KM · Maverick Operating, LLC · Section with this well →

Coleman Junction1,1001,420
San Andres1,3701,150
San Angelo2,330190
Canyon4,100-1,580
Clear Fork4,320-1,800
Cisco6,000-3,480
Strawn6,300-3,780

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