WELL · 42-237-37572 · DISTRICT 9

Nowak-Brown Unit #1

Plugged

Jack County · Jack County Regular field  · Vertical

Nowak-Brown Unit #1 (API 42-237-37572) is a plugged well in Jack County, plugged July 3, 2020, last operated by Xplore Operating LLC.

The RRC has issued one drilling permit, issued December 2, 1988, permitted to 2,600 ft.

It was permitted by Corpening, Joe F. and has since transferred to Xplore Operating LLC on the wellbore schedule.

Completion filings report 2 formation tops, including Palo Pinto, Strawn.

Operator of record

Xplore Operating LLC

Permitted by Corpening, Joe F.; the EWA schedule now lists a different operator.

Based in
Arlington, TX
P-5 status
Active (A)
P-5 last filed
Oct 6, 2025
Permits on file
56
Phone
(817) 810-1244

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleXplore Operating LLC
Production reportsnone
Latest permitCorpening, Joe F.Dec 2, 1988

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

2,600
total depth, ft
1
permits on file
Dec 2, 1988
last permit issued
Mar 20, 1994
completed
0
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Nov 2020

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Mar 20, 1994
Shut in
—
Plugged
Jul 3, 2020

Surface location

No coordinates on the permit record yet. The RRC's GIS record usually lands within days of issuance; historical master-file permits never carry one.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH APR 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; this well is the only one on it.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Nowak-Brown Unit O-13-27275Jack County RegularXplore Operating, LLC100Jan 1993 – Nov 2020

No volumes reported on these leases in the last three years.

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
353658-99DrillCorpening, Joe F.Nov 28, 1988Dec 2, 1988—2,600

Completions

CompletedLeaseFieldOperatorStatusDepth
Mar 20, 1994Nowak-Brown Unit O-13-27275Jack County RegularXplore Operating LLCPlugged—

Formation tops

As filed on W-2/G-1. Subsea from 1,074 ft elevation.Download CSV →

FormationMD ftSubsea
Palo Pinto600474
Strawn2,500-1,426

Perforations

Perforated and open-hole intervals.

FromToType
2,2342,238Perforated
2,2382,242Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62515511100 S
5.52,4997.875150 S

Completion filings

W-2 and G-1 reports on record in the RRC wellbore file, newest first. The suffix identifies the wellbore or completion event. About these reports →

SuffixFiledW-2 / G-1 dateLogs referenced
00Jun 24, 1994Apr 11, 1994—
00Feb 17, 1989Feb 3, 1989Yes
00Feb 15, 1989——

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.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

0
bbl, last 12 reported months
156K
bbl, all reported
Oct 2021
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000080605H-1 InjectionPlugged Jul 20, 20205007502,238–2,242

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 0 · prior 12 0

0120202021

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