WELL · 42-399-30453 · DISTRICT 7

Chisum #2

Plugged

Runnels County · Wildcat field  · Vertical

Chisum #2 (API 42-399-30453) is a plugged well in Runnels County, plugged November 6, 1975, last operated by Campana Petroleum Company.

The RRC has issued one drilling permit, issued July 25, 2024, permitted to 5,000 ft.

It was permitted by Mcdonald Energy, Inc. and has since transferred to Campana Petroleum Company on the wellbore schedule.

Operator of record

Campana Petroleum Company

Permitted by McDonald Energy, Inc.; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitMcDonald Energy, Inc.Jul 25, 2024

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

5,000
total depth, ft
1
permits on file
Jul 25, 2024
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
Nov 6, 1975

Surface location

32.022163, -100.044767

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Runnels 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
901424-99ReenterMcDonald Energy, Inc.Jul 18, 2024Jul 25, 2024—5,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 →

Yates42-399-35605

3.3 KM · Cedar Oil Company · Section with this well →

King2,859-901
Cisco3,010-1,052
Canyon3,290-1,332
Strawn—
Cambrian—
Coleman Junction—
Problem Zone - 5 Mile Radius Aro—

Gray42-399-35590

3.9 KM · Cedar Oil Company · Section with this well →

King2,050-94
Canyon3,465-1,509
Cisco3,670-1,714
Strawn4,220-2,264
Problem Zone - 5 Mile Radius Aro—
Coleman Junction—
Cambrian—

Hannah42-399-35566

4.1 KM · Golden Oil and Ranch, LLC · Section with this well →

Coleman Junction1,786201
King3,048-1,061
Cisco3,352-1,365
Canyon3,615-1,628
Strawn4,345-2,358
Cambrian—
Problem Zone - 5 Mile Radius Aro—

Francisca42-399-35586

4.8 KM · Cedar Oil Company · Section with this well →

King2,000-51
Canyon3,400-1,451
Cisco3,600-1,651
Strawn4,200-2,251
Goen4,399-2,450
Cambrian—
Coleman Junction—
Problem Zone - 5 Mile Radius Aro—

Francisca42-399-35584

4.9 KM · Cedar Oil Company · Section with this well →

King2,000-67
Canyon3,400-1,467
Cisco3,600-1,667
Strawn4,192-2,259
Problem Zone - 5 Mile Radius Aro—
Coleman Junction—
Cambrian—

Saam42-399-35581

5.2 KM · Cedar Oil Company · Section with this well →

King2,000-66
Canyon3,400-1,466
Cisco3,600-1,666
Strawn4,196-2,262
Coleman Junction—
Problem Zone - 5 Mile Radius Aro—
Cambrian—

Saam B42-399-35589

5.3 KM · Cedar Oil Company · Section with this well →

King2,000-60
Canyon3,400-1,460
Cisco3,600-1,660
Strawn4,150-2,210
Cambrian—
Coleman Junction—
Problem Zone - 5 Mile Radius Aro—

Shirley42-399-35583

5.5 KM · Cedar Oil Company · Section with this well →

King2,000-65
Canyon3,400-1,465
Cisco3,600-1,665
Strawn4,192-2,257
Coleman Junction—
Cambrian—
Problem Zone - 5 Mile Radius Aro—

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