TEXAS · WELLS · MARTIN COUNTY · SALE RANCH 23G LEASE · API 42-317-40548 · DISTRICT 7B
Sale Ranch 23G #7H
Martin County · Spraberry (Trend Area) field · Producing · Horizontal
Sale Ranch 23g #7H (API 42-317-40548) is a horizontal well in Martin County operated by Pioneer Natural Res. USA Inc., completed June 30, 2017 and listed as producing on the RRC schedule.
The RRC has issued one drilling permit, issued September 16, 2016, permitted to 9,174 ft.
Completion filings report 10 formation tops, including Santa Rosa, Yates, Queen, Grayburg.
Its lease has reported 463K barrels of oil and 1.8M mcf of gas since June 2017, last reporting volume in April 2026.
Operator of record
- 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 schedule | Pioneer Natural Res. USA Inc. |
| Production reports | Pioneer Natural Res. USA, Inc.through Apr 2026 |
| Latest permit | Pioneer Natural Res. USA, Inc.Sep 16, 2016 |
- 9,174
- total depth, ft
- 1
- permits on file
- Sep 16, 2016
- last permit issued
- Jun 30, 2017
- completed
- 463K
- cumulative oil, bbl
- 1.8M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jun 2017 THROUGH Apr 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Jun 30, 2017
- 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; this well is the only one on it.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Sale Ranch 23G O-10-48977 | Spraberry (Trend Area) | Pioneer Natural Res. USA, Inc. | 1 | 463K | 1.8M | Jun 2017 – Apr 2026 |
Gas, mcf lease total
Last 12 months 173,798 · prior 12 188,944(-8%)
Oil, barrels lease total
Last 12 months 11,339 · prior 12 12,777(-11%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Pioneer Natural Res. USA, Inc.Jun 2017 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 818296-99 | Drill | Pioneer Natural Res. USA, Inc. | Sep 7, 2016 | Sep 16, 2016 | Nov 10, 2016 | 11,000 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Jun 30, 2017 | Sale Ranch 23G O-10-48977 | Spraberry (Trend Area) | Pioneer Natural Res. USA Inc. | Producing | 9,174 |
Formation tops
As filed on W-2/G-1. Subsea from 2,825 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Santa Rosa | 1,187 | 1,638 |
| Santa Rosa | 1,277 | 1,548 |
| Yates | 2,609 | 216 |
| Queen | 3,492 | -667 |
| Grayburg | 3,951 | -1,126 |
| San AndresSAN ANDRES - ACTIVE CO2 FLOOD; H | 4,188 | -1,363 |
| Spraberry | 7,532 | -4,707 |
| Dean | 8,843 | -6,018 |
| Wolfcamp | 9,050 | -6,225 |
| Cisco | — | — |
| Pennsylvanian | — | — |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 9,568 | 19,815 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 1,669 | 17.5 | 1,468 S |
| 9.625 | 5,823 | 12.25 | 790 S |
| 5.5 | 19,799 | 8.5 | 665 S |
| 4.5 | 19,924 | 8.5 | 665 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 →
| Suffix | RRC record date | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Jan 31, 2018 | Oct 31, 2017 | Yes |
| 00 | Nov 20, 2017 | Aug 1, 2017 | — |
Well logs
2 logs loaded from the RRC's log index, the latest received Nov 1, 2017. Gamma ray. 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 described | Files | Intervalft, as filed | Datereceived | SizeMB |
|---|---|---|---|---|
| Gamma RaySpans Santa Rosa, Yates, Queen, Grayburg, San Andres, Spraberry, Dean, Wolfcamp | TIFF | 0 to 9,480 | Nov 1, 2017 | 12.7 |
| Gamma RaySpans Santa Rosa, Yates, Queen, Grayburg, San Andres, Spraberry, Dean, Wolfcamp | TIFF | 0 to 9,480 | Oct 23, 2017 | 12.7 |
"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.
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.
- Wellbore filings for 42-317-40548 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-317-40548 → scanned completion filings
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/31740548, documented in the API reference.