TEXAS · WELLS · GLASSCOCK COUNTY · API 42-173-38050 · DISTRICT 08

Brunson 42-6-F #4212H

N

Glasscock County  · Horizontal

Brunson 42-6-F #4212H (API 42-173-38050) is a permitted horizontal well in Glasscock County filed by Parsley Energy Operations, LLC; no completion report is on file yet.

The RRC has issued one drilling permit, issued December 3, 2018, permitted to 8,800 ft.

Operator of record

Parsley Energy Operations, LLC

Based in
Irving, TX
P-5 status
Inactive (I)
P-5 last filed
Jul 21, 2022
Permits on file
2,477
Phone
(972) 969-4051

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitParsley Energy Operations, LLCDec 3, 2018
8,800
total depth, ft
1
permits on file
Dec 3, 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
—

Surface location

31.866147, -101.667487

Google Maps ↗

Permit surface location from the RRC GIS record, in Glasscock 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
847366-99DrillParsley Energy Operations, LLCDec 3, 2018Dec 3, 2018—8,800

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 neighbors can.

Section of the neighbors →

Brunson 42-6-G42-173-38048

0.0 KM · Parsley Energy Operations, LLC · Section with this well →

San Andres3,552-855
Clear Fork5,891-3,194
Spraberry6,618-3,921
Seven Rivers—
Yates—
Wichita-Albany—
Glorieta—
Santa Rosa—

10 TOPS · FIRST 8

Brunson 42-6-G42-173-38051

0.0 KM · Parsley Energy Operations, LLC · Section with this well →

San Andres3,545-848
Clear Fork5,871-3,174
Spraberry6,609-3,912
Glorieta—
Wichita-Albany—
Yates—
Seven Rivers—
Santa Rosa—

10 TOPS · FIRST 8

Brunson 42-6-E42-173-37851

0.7 KM · Parsley Energy Operations, LLC · Section with this well →

San Andres3,229-531
Clear Fork5,902-3,204
Spraberry6,618-3,920
Queen—
Wichita-Albany—
Seven Rivers—
Yates—
Santa Rosa—

10 TOPS · FIRST 8

Brunson 42-6-E42-173-37843

0.7 KM · Parsley Energy Operations, LLC · Section with this well →

San Andres3,220-522
Clear Fork5,914-3,216
Spraberry6,639-3,941
Seven Rivers—
Santa Rosa—
Queen—
Grayburg—
Glorieta—

10 TOPS · FIRST 8

Currie 41-29-E42-173-38167

1.4 KM · Parsley Energy Operations, LLC · Section with this well →

Fusselman—
Atoka—
Wichita-Albany—
Yates—
Seven Rivers—
Santa Rosa—
Queen—
Pennsylvanian—

10 TOPS · FIRST 8

Currie 41-29-F42-173-38166

1.4 KM · Parsley Energy Operations, LLC · Section with this well →

San Andres3,447-750
Clear Fork5,784-3,087
Spraberry6,534-3,837
Queen—
Glorieta—
Santa Rosa—
Seven Rivers—
Wichita-Albany—

10 TOPS · FIRST 8

Currie 41-29-E42-173-38168

1.4 KM · Parsley Energy Operations, LLC · Section with this well →

San Andres3,403-706
Clear Fork5,812-3,115
Spraberry6,548-3,851
Yates—
Glorieta—
Grayburg—
Queen—
Santa Rosa—

10 TOPS · FIRST 8

Currie 41-44-F42-173-37835

1.4 KM · Parsley Energy Operations, LLC · Section with this well →

San Andres3,442-764
Clear Fork5,779-3,101
Spraberry6,519-3,841
Glorieta—
Santa Rosa—
Seven Rivers—
Wichita-Albany—
Yates—

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