WELL · 42-329-35462 · DISTRICT 8

Brooks B #2

Y

Midland County · Spraberry (Trend Area) field · Producing  · Vertical

Brooks B #2 (API 42-329-35462) is a well in Midland County operated by Pioneer Natural Res. USA Inc., completed March 25, 2006 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued February 8, 2006, permitted to 9,900 ft.

Completion filings report 2 formation tops, including Spraberry, Dean.

Its lease has reported 250K barrels of oil and 684K mcf of gas since January 2005, last reporting in July 2026. The lease carries 5 wells, so these are lease totals, not this well alone.

Operator of record

Pioneer Natural Res. USA Inc.

Based in
Spring, TX
P-5 status
Active (A)
P-5 last filed
Jul 8, 2026
Permits on file
15,628
Phone
(972) 444-4001

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulePioneer Natural Res. USA Inc.
Production reportsPioneer Natural Res. USA, Inc.through Apr 2026
Latest permitPioneer Natural Res. USA, Inc.Feb 8, 2006
9,900
total depth, ft
1
permits on file
Feb 8, 2006
last permit issued
Mar 25, 2006
completed
250K
cumulative oil, bbl
684K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 2005 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Mar 25, 2006
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active (A)

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; they carry 5 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Brooks "B" O-10-37473Spraberry (Trend Area)Pioneer Natural Res. USA, Inc.5250K684KJan 2005 – Jul 2026

Oil, barrels lease total

Last 12 months 5,760 · prior 12 6,002(-4%)

05001K1.5K202420252026

Gas, mcf lease total

Last 12 months 13,771 · prior 12 22,734(-39%)

01K2K3K202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Pioneer Natural Res. USA, Inc.Jan 2005 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
613804-99DrillPioneer Natural Res. USA, Inc.Feb 8, 2006Feb 8, 2006Feb 15, 20069,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-37473————

Formation tops

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

FormationMD ftSubsea
SpraberryTOP UPPER SPRABERRY7,583-4,850
SpraberryTOP LOWER SPRABERRY8,124-5,391
DeanTOP DEAN8,806-6,073
DeanBASE DEAN9,146-6,413

Perforations

Perforated and open-hole intervals.

FromToType
7,5867,781Perforated
8,3528,465Perforated
9,1069,183Perforated
9,2709,699Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62532711175 S
4.59,8947.875950 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
00Oct 17, 2006May 2, 2006Yes
00Jun 30, 2006——

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.

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