WELL · 42-327-31253 · DISTRICT 7

Russell #78

Plugged

Menard County · Danny Mae (Lower Cisco a ) field  · Vertical

Russell #78 (API 42-327-31253) is a plugged well in Menard County, plugged September 7, 2022, last operated by Harvest Petroleum Inc..

The RRC has issued one drilling permit, issued July 21, 2022, permitted to 4,000 ft.

It was permitted by Harvest Petroleum Inc. and has since transferred to Harvest Petroleum Inc. on the wellbore schedule.

Operator of record

Harvest Petroleum Inc.

Permitted by Harvest Petroleum Inc.; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitHarvest Petroleum Inc.Jul 21, 2022

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

4,000
total depth, ft
1
permits on file
Jul 21, 2022
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
Sep 7, 2022

Surface location

30.940871, -100.054210

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Menard 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
882304-99DrillHarvest Petroleum Inc.Jul 21, 2022Jul 21, 2022Aug 10, 20224,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). 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 →

McGregor Unit42-413-32747

11.6 KM · Telesis Operating Co., Inc. · Section with this well →

Gunsight2,651-361
Adams Branch3,792-1,502
Palo Pinto4,227-1,937

McGregor Unit42-413-32981

11.7 KM · Boaz Energy II Operating, LLC · Section with this well →

Coleman Junction1,2001,114
Wolfcamp1,974340
Canyon3,750-1,436
Lime 41503,952-1,638
Strawn4,408-2,094
Ellenburger4,796-2,482
Cambrian5,540-3,226
San Angelo—

9 TOPS · FIRST 8

E.M. Clancy42-413-32934

13.4 KM · Boaz Energy II Operating, LLC · Section with this well →

Canyon—
Ellenburger—
San Angelo—
Strawn—
Wolfcamp—
Coleman Junction—
Clear Fork—

E.M. Clancy42-413-32935

13.7 KM · Boaz Energy II Operating, LLC · Section with this well →

Coleman Junction1,680
Wolfcamp2,650
Canyon3,950
Strawn4,490
Ellenburger—
San Angelo—
Clear Fork—
Coleman Junction—

9 TOPS · FIRST 8

Powell 'A'42-413-33001

13.8 KM · VX Operating, LLC · Section with this well →

Coleman Junction1,2501,063
Canyon3,931-1,618
Strawn4,256-1,943
Wolfcamp—
San Angelo—
Ellenburger—
Clear Fork—

Thornburg 2742-413-32999

13.9 KM · Boaz Energy II Operating, LLC · Section with this well →

Coleman Junction1,422
Wolfcamp2,058
Canyon3,926
Strawn4,302
Clear Fork—
Ellenburger—
San Angelo—

Thornburg 2742-413-32989

13.9 KM · Boaz Energy II Operating, LLC · Section with this well →

Coleman Junction1,570658
Wolfcamp2,042186
Canyon3,618-1,390
Strawn3,908-1,680
San Angelo—
Ellenburger—
Clear Fork—

Powell42-413-33007

14.0 KM · VX Operating, LLC · Section with this well →

Coleman Junction1,2001,118
Canyon3,881-1,563
Strawn4,002-1,684
Clear Fork—
Ellenburger—
San Angelo—
Wolfcamp—

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