TEXAS · WELLS · REAGAN COUNTY · SHERROD UNIT LEASE · API 42-383-35803 · DISTRICT 6E

Sherrod Unit #709

Shut in

Reagan County · Spraberry (Trend Area) field · Shut In  · Vertical

Sherrod Unit #709 (API 42-383-35803) is a well in Reagan County operated by Pioneer Natural Res. USA Inc., completed July 11, 2025 and listed as shut in on the RRC schedule, shut in February 1, 2020.

The RRC has issued one drilling permit, issued June 22, 2006, permitted to 8,640 ft.

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

Its lease has reported 5.26M barrels of oil and 12.1M mcf of gas since the record begins in January 1993, last reporting volume in August 2026. The lease carries 172 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,633
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 Aug 2026
Latest permitPioneer Natural Res. USA, Inc.Jun 22, 2006
8,640
total depth, ft
1
permits on file
Jun 22, 2006
last permit issued
Jul 11, 2025
completed
5.26M
cumulative oil, bbl
12.1M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · ON RECORD FROM JAN 1993, THE RECORD'S FIRST MONTH, THROUGH AUG 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 11, 2025
Shut in
Feb 1, 2020
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.

Wells nearby

Every well with a location on file around this well, in any state, nearest first.

Loading the map…

Open the full map →

Texas locations come from drilling permits, so most older Texas wells have none and are not listed.

Lease production

PDQ LEASE REPORTS · REPORTED THROUGH AUG 2026

Texas reports oil by lease, not by well. These are the lease this well is completed on; they carry 172 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Sherrod Unit O-9-4947Spraberry (Trend Area)Pioneer Natural Res. USA, Inc.1725.26M12.1Mby Jan 1993 – Aug 2026

Oil, barrels lease total

Last 12 months 8,289 · prior 12 24,548(-66%)

02K4K6K202420252026

Gas, mcf lease total

Last 12 months 2,589 · prior 12 12,175(-79%)

01K2K3K202420252026

Wells named Sherrod Unit

Pioneer Natural Res. USA Inc.'s other wells filed under this lease name in Reagan County, newest permit first. The RRC gives a gas well its own lease number, so the name is what joins the wells of a unit.

Loading the lease's wells

Chain of custody

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

  1. 1Exxon Corp.Jan 1993 → Mar 2000
  2. 2Exxon Mobil CorporationApr 2000 → Jul 2005
  3. 3Pioneer Natural Res. USA, Inc.Aug 2005 → Aug 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
621466-99DrillPioneer Natural Res. USA, Inc.Jun 22, 2006Jun 22, 2006Jul 14, 20068,600

Completions

CompletedLeaseFieldOperatorStatusDepth
Jul 11, 2025Sherrod Unit O-9-4947Spraberry (Trend Area)Pioneer Natural Res. USA Inc.Shut In · shut in Feb 1, 20208,640

Formation tops

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

FormationMD ftSubsea
SpraberryTOP UPPER SPRABERRY6,812-4,128
SpraberryTOP LOWER SPRABERRY7,387-4,703
DeanTOP DEAN8,134-5,450
DeanBASE DEAN8,412-5,728

Perforations

Perforated and open-hole intervals.

FromToType
6,8196,997Perforated
7,6447,779Perforated
8,2758,404Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62551311300 S
4.58,6407.875630 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. The record date is the RRC's own date on the record, not the day the report was filed: 462,034 of the state's filings carry 1984-01-12. About these reports →

SuffixRRC record dateW-2 / G-1 dateLogs referenced
00Aug 15, 2025Aug 6, 2025—
00Mar 7, 2007Nov 2, 2006Yes
00Nov 14, 2006——

Well logs

1 log loaded from the RRC's log index, the latest received Mar 15, 2007. Cased hole, Gamma ray, Neutron. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.

Open the RRC's log search for this well ↗
Logas describedFiles Intervalft, as filedDatereceivedSizeMB
Neutron PorosityCOMPENSATED NEUTRON GAMMA RAY CCL LOGSpans Spraberry, DeanTIFF3,300 to 8,606Mar 15, 2007run Jul 31, 2006—

"Spans" is by this well's own filed formation tops: a formation runs from its top to the next deeper top filed, and the deepest runs to the bottom of the log. Depths are measured along the wellbore, so on a horizontal the lateral counts in the formation it was landed in.

Find logs withinmiles of this well:List →Map →

Search the well logs loaded into Petrora →

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.

The logs loaded for this well are under Well logs, with the RRC's log search for it. The University Lands library has no per-well link: then paste it into its 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/38335803, documented in the API reference.