WELL · 42-105-42455 · DISTRICT 7

Bean Consolidated #F 9

Plugged

Crockett County · Pure-Bean South field  · Vertical

Bean Consolidated #F 9 (API 42-105-42455) is a plugged well in Crockett County, plugged September 20, 2018, last operated by Fenix Petroleum Group LLC.

The RRC has issued one drilling permit, issued July 18, 2018, permitted to 1,700 ft.

It was permitted by Fenix Petroleum Group LLC and has since transferred to Fenix Petroleum Group LLC on the wellbore schedule.

Operator of record

Fenix Petroleum Group LLC

Permitted by Fenix Petroleum Group LLC; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitFenix Petroleum Group LLCJul 18, 2018

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

1,700
total depth, ft
1
permits on file
Jul 18, 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
Sep 20, 2018

Surface location

30.806476, -101.291692

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Crockett 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
841763-99DrillFenix Petroleum Group LLCJun 27, 2018Jul 18, 2018Sep 17, 20181,700

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) and the University Lands library. 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 →

Bean Consolidated42-105-42465

0.0 KM · Fenix Petroleum Group LLC · Section with this well →

Queen8901,724
San Andres1,2471,367
Wolfcamp—
Canyon—
Strawn—
Leonard—
Ellenburger—
Devonian—

Bean Consolidated42-105-42457

1.0 KM · Fenix Petroleum Group LLC · Section with this well →

Queen8801,726
San Andres1,2511,355
Devonian—
Wolfcamp—
Strawn—
Leonard—
Ellenburger—
Canyon—

Bean Consolidated42-105-42339

1.1 KM · Remuda Operating Company · Section with this well →

Queen8721,746
San Andres1,2471,371
Wolfcamp—
Canyon—
Devonian—
Ellenburger—
Leonard—
Strawn—

Vaughan, R. L.42-105-42456

4.8 KM · Fenix Petroleum Group LLC · Section with this well →

Queen8861,730
San Andres1,2131,403
Gray Burg1,2621,354
Ellenburger—
Canyon—
Devonian—
Leonard—
Strawn—

9 TOPS · FIRST 8

Hagelstein42-105-34004

10.8 KM · Thompson, J. Cleo · Section with this well →

Wolfcamp5,928-3,517
Canyon6,774-4,363
Canyon6,922-4,511

Baker B42-105-42280

11.7 KM · Approach Operating LLC · Section with this well →

Queen1,0481,541
San Andres1,5751,014
Leonard4,181-1,592
Wolfcamp5,464-2,875
Ellenburger—
Strawn—
Devonian—
Canyon—

Baker B42-105-42279

11.7 KM · Approach Operating LLC · Section with this well →

Queen1,0481,541
San Andres1,5741,015
Leonard4,186-1,597
Wolfcamp5,473-2,884
Strawn—
Canyon—
Devonian—
Ellenburger—

Baker B42-105-42404

12.2 KM · Approach Operating LLC · Section with this well →

Queen1,0481,553
San Andres1,5431,058
Leonard4,173-1,572
Wolfcamp5,464-2,863
Canyon—
Devonian—
Ellenburger—
Strawn—

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