WELL · 42-025-33986 · DISTRICT 2

Brown #25

Plugged

Bee County · Wildcat field  · Vertical

Brown #25 (API 42-025-33986) is a plugged well in Bee County, plugged July 12, 2021, last operated by Headwaters Energy Partners LLC.

The RRC has issued 2 drilling permits between 2018 and 2021, permitted to 6,000 ft.

It was permitted by Headwaters Energy Partners, LLC and has since transferred to Headwaters Energy Partners LLC on the wellbore schedule.

Operator of record

Headwaters Energy Partners LLC

Permitted by Headwaters Energy Partners, LLC; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitHeadwaters Energy Partners, LLCMay 27, 2021

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

6,000
total depth, ft
2
permits on file
May 27, 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
Jul 12, 2021

Surface location

28.457658, -97.787322

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Bee 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
870034-99DrillHeadwaters Energy Partners, LLCMay 24, 2021May 27, 2021—6,000
845642-99DrillEnco Exploration CompanyOct 11, 2018Oct 12, 2018—6,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 →

Brown42-025-33987

2.4 KM · Enco Exploration Company · Section with this well →

Frio2,813-2,518
Vicksburg3,005-2,710
Catahoula—
Reklaw—
Queen City—
Olmos—
Jackson—
Edwards—

10 TOPS · FIRST 8

Brown42-025-33994

2.7 KM · Headwaters Energy Partners, LLC · Section with this well →

Frio3,096-2,821
Vicksburg3,348-3,073
Olmos—
Wilcox—
Reklaw—
Catahoula—
Eagle Ford—
Edwards—

10 TOPS · FIRST 8

Toogood42-025-34013

2.8 KM · Headwaters Energy Partners, LLC · Section with this well →

Frio3,111-2,784
Vicksburg3,265-2,938
Eagle Ford—
Catahoula—
Wilcox—
Reklaw—
Queen City—
Jackson—

10 TOPS · FIRST 8

Toogood42-025-34001

2.8 KM · Enco Exploration Company · Section with this well →

Frio3,087-2,759
Vicksburg3,312-2,984
Jackson3,657-3,329
Eagle Ford—
Edwards—
Wilcox—
Catahoula—
Olmos—

10 TOPS · FIRST 8

Whiddon42-025-33904

3.5 KM · Enco Exploration Company · Section with this well →

Catahoula700-442
Frio2,500-2,242
Vicksburg3,300-3,042
Jackson—
Eagle Ford—
Edwards—
Olmos—
Queen City—

10 TOPS · FIRST 8

Malone42-025-33633

3.6 KM · Enco Exploration Company · Section with this well →

Frio2,710-2,403
Vicksburg3,000-2,693
Hockley3,600-3,293

Collier42-025-33309

4.7 KM · Enco Exploration Company · Section with this well →

Catahoula2,217-1,932

Braly-Dugat42-025-34019

5.9 KM · Headwaters Energy Partners, LLC · Section with this well →

Frio2,954-2,638
Vicksburg3,142-2,826
Edwards—
Catahoula—
Jackson—
Olmos—
Queen City—
Reklaw—

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