WELL · 42-227-39905 · DISTRICT 10

Chalk, G. O. #42CF

N

Howard County  · Vertical

Chalk, G. O. #42CF (API 42-227-39905) is a permitted well in Howard County filed by Rover Petroleum Operating, LLC; no completion report is on file yet.

The RRC has issued one drilling permit, issued December 10, 2018, permitted to 4,200 ft.

Operator of record

Rover Petroleum Operating, LLC

Fort Worth, TX · P-5 Y, filed Jan 13, 2025 · 69 permits on file · (940) 440-2044

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitRover Petroleum Operating, LLCDec 10, 2018
4,200
total depth, ft
1
permits on file
Dec 10, 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
—

Surface location

32.126113, -101.246367

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Howard 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
846777-99DrillRover Petroleum Operating, LLCNov 13, 2018Dec 10, 2018—4,200

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). 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 →

Chalk, G. O.42-227-39903

0.1 KM · Rover Petroleum Operating, LLC · Section with this well →

Yates1,2331,223
Seven Rivers1,3201,136
San Andres2,100356
Glorieta2,691-235
Clear Fork2,942-486
Dean—
Coleman Junction—
Wolfcamp—

10 TOPS · FIRST 8

Chalk, G. O.42-227-39867

0.2 KM · Rover Petroleum Operating, LLC · Section with this well →

Seven Rivers1,3011,129
San Andres2,062368
Glorieta2,650-220
Clear Fork2,929-499
Wolfcamp—
Spraberry—
Leonard—
Dean—

10 TOPS · FIRST 8

Chalk, G. O.42-227-39679

0.2 KM · Rover Petroleum Operating, LLC · Section with this well →

Atoka—
Canyon—
Cisco—
Dean—
Leonard—
Mississippian—
Pennsylvanian—
Spraberry—

10 TOPS · FIRST 8

Chalk, G. O.42-227-39674

0.2 KM · Rover Petroleum Operating, LLC · Section with this well →

Atoka—
Canyon—
Cisco—
Dean—
Ellenburger—
Leonard—
Mississippian—
Pennsylvanian—

10 TOPS · FIRST 8

Chalk, G. O.42-227-39678

0.3 KM · Rover Petroleum Operating, LLC · Section with this well →

Yates1,1681,257
Seven Rivers1,2541,171
San Andres2,052373
Glorieta2,634-209
Clear Fork2,902-477
Wolfcamp—
Coleman Junction—
Dean—

10 TOPS · FIRST 8

Chalk, G. O.42-227-39777

0.3 KM · Rover Petroleum Operating, LLC · Section with this well →

Yates1,2561,199
Seven Rivers1,3401,115
San Andres2,108347
Glorieta2,702-247
Clear Fork2,957-502
Dean—
Spraberry—
Coleman Junction—

10 TOPS · FIRST 8

Chalk, G. O.42-227-39812

0.4 KM · Rover Petroleum Operating, LLC · Section with this well →

Seven Rivers1,3701,088
San Andres2,113345
Glorieta2,742-284
Clear Fork3,524-1,066
Coleman Junction—
Yates—
Wolfcamp—
Spraberry—

10 TOPS · FIRST 8

Chalk, G. O.42-227-39813

0.5 KM · Rover Petroleum Operating, LLC · Section with this well →

Yates1,2551,210
Seven Rivers1,3461,119
San Andres2,137328
Glorieta2,727-262
Clear Fork2,976-511
Coleman Junction—
Dean—
Spraberry—

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