WELL · 42-041-32576 · DISTRICT 3

Ehh CP #5

N

Brazos County  · Vertical

Ehh CP #5 (API 42-041-32576) is a permitted well in Brazos County filed by Magellan Operating Company, LLC; no completion report is on file yet.

The RRC has issued one drilling permit, issued July 1, 2019, permitted to 500 ft.

Operator of record

Magellan Operating Company, LLC

Tulsa, OK · P-5 Y, filed Nov 4, 2025 · 3 permits on file · (800) 562-5879

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitMagellan Operating Company, LLCJul 1, 2019
500
total depth, ft
1
permits on file
Jul 1, 2019
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

30.707019, -96.316512

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Brazos 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
854449-99DrillMagellan Operating Company, LLCJun 21, 2019Jul 1, 2019—500

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 →

Goanna42-041-32532

1.2 KM · Hawkwood Energy Operating, LLC · Section with this well →

Sparta2,840-2,496
Wilcox3,610-3,266
Navarro5,685-5,341
Austin Chalk8,347-8,003
Eagle Ford8,702-8,358
Edwards—
Woodbine—
Georgetown—

9 TOPS · FIRST 8

Goanna42-041-32531

1.2 KM · Hawkwood Energy Operating, LLC · Section with this well →

Sparta2,840-2,496
Wilcox3,610-3,266
Navarro5,683-5,339
Austin Chalk8,332-7,988
Eagle Ford8,694-8,350
Edwards—
Woodbine—
Georgetown—

9 TOPS · FIRST 8

Thorny Devil42-041-32477

1.2 KM · Hawkwood Energy Operating, LLC · Section with this well →

Sparta3,059-2,709
Wilcox3,812-3,462
Navarro6,288-5,938
Austin Chalk8,310-7,960
Eagle Ford8,686-8,336
Edwards—
Buda—
Woodbine—

9 TOPS · FIRST 8

Thorny Devil42-041-32476

1.2 KM · Hawkwood Energy Operating, LLC · Section with this well →

Sparta3,079-2,729
Wilcox3,806-3,456
Navarro6,287-5,937
Austin Chalk8,314-7,964
Eagle Ford8,687-8,337
Edwards—
Woodbine—
Buda—

9 TOPS · FIRST 8

Stonefish42-041-32571

1.8 KM · Hawkwood Energy Operating, LLC · Section with this well →

Sparta2,840-2,528
Wilcox3,610-3,298
Navarro5,597-5,285
Austin Chalk8,281-7,969
Eagle Ford8,645-8,333
Georgetown—
Woodbine—
Buda—

9 TOPS · FIRST 8

Stonefish42-041-32570

1.8 KM · Hawkwood Energy Operating, LLC · Section with this well →

Sparta2,840-2,528
Wilcox3,610-3,298
Navarro5,606-5,294
Austin Chalk8,293-7,981
Eagle Ford8,631-8,319
Edwards—
Buda—
Woodbine—

9 TOPS · FIRST 8

Marlin42-041-32574

1.8 KM · Hawkwood Energy Operating, LLC · Section with this well →

Sparta2,840-2,530
Wilcox3,610-3,300
Navarro5,616-5,306
Austin Chalk8,258-7,948
Eagle Ford8,648-8,338
Woodbine—
Buda—
Edwards—

9 TOPS · FIRST 8

Manta42-041-32507

1.9 KM · Hawkwood Energy Operating, LLC · Section with this well →

Sparta2,840-2,529
Wilcox3,610-3,299
Navarro5,604-5,293
Austin Chalk8,288-7,977
Eagle Ford8,638-8,327
Woodbine—
Georgetown—
Edwards—

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