WELL · 42-115-33835 · DISTRICT 10

Big Bend Unit #J 2H

N

Dawson County  · Horizontal

Big Bend Unit #J 2H (API 42-115-33835) is a permitted horizontal well in Dawson County filed by Cgs Operating, LLC; no completion report is on file yet.

The RRC has issued one drilling permit, issued May 18, 2021, permitted to 10,000 ft.

Operator of record

CGS Operating, LLC

Kilgore, TX · P-5 Y, filed Jul 3, 2024 · 45 permits on file · (903) 571-5845

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitCGS Operating, LLCMay 18, 2021
10,000
total depth, ft
1
permits on file
May 18, 2021
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.627188, -101.955630

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
869888-99DrillCGS Operating, LLCMay 14, 2021May 18, 2021—10,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 →

Big Bend Unit42-115-33834

0.0 KM · CGS Operating, LLC · Section with this well →

Yates3,148-213
San Andres3,997-1,062
Spraberry7,668-4,733
Precambrian (Undifferentiated)—
Silurian (undifferentiated)—
Wolfcamp—
Canyon—
Dean—

13 TOPS · FIRST 8

Overton Unit42-115-33828

1.2 KM · CGS Operating, LLC · Section with this well →

Yates2,601319
San Andres4,160-1,240
Clear Fork5,740-2,820
Spraberry7,677-4,757
Dean9,063-6,143
Devonian—
Mississippian—
Pennsylvanian—

10 TOPS · FIRST 8

Overton Unit42-115-33826

1.2 KM · CGS Operating, LLC · Section with this well →

Yates2,90614
San Andres4,131-1,211
Spraberry7,684-4,764
Dean9,063-6,143
Canyon—
Devonian—
Mississippian—
Pennsylvanian—

10 TOPS · FIRST 8

Arod 2-11-1442-115-33871

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

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

10 TOPS · FIRST 8

Arod 2-11-1442-115-33870

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

Yates2,480422
San Andres4,039-1,137
Spraberry7,532-4,630
Dean8,935-6,033
Silurian (undifferentiated)—
Devonian—
Canyon—
Pennsylvanian—

10 TOPS · FIRST 8

Overton a Unit42-115-34048

2.4 KM · EOG Resources, Inc. · Section with this well →

Yates2,636287
San Andres4,148-1,225
Clear Fork5,655-2,732
Spraberry7,631-4,708
Dean9,037-6,114
Canyon—
Devonian—
Mississippian—

10 TOPS · FIRST 8

Overton B Unit42-115-34049

2.4 KM · EOG Resources, Inc. · Section with this well →

Yates2,635291
San Andres4,142-1,216
Clear Fork5,639-2,713
Spraberry7,611-4,685
Dean9,030-6,104
Pennsylvanian—
Wolfcamp—
Canyon—

10 TOPS · FIRST 8

JB Books42-115-33994

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

Yates2,503400
San Andres4,263-1,360
Spraberry7,555-4,652
Dean8,961-6,058
Wolfcamp—
Canyon—
Silurian (undifferentiated)—
Devonian—

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