TEXAS · WELLS · MARTIN COUNTY · SLAUGHTER 29D LEASE · API 42-317-38867 · DISTRICT 7B
Slaughter 29D #1
Martin County · Spraberry (Trend Area) field · Shut In · Vertical
- Fields on the latest permit · any of 2
- Mon Bak (Strawn) · Spraberry (Trend Area)
- Not one formation; the well must be completed in one of them, and no target formation is stated.
Slaughter 29d #1 (API 42-317-38867) is a well in Martin County operated by Ovintiv USA Inc., completed January 8, 2014 and listed as shut in on the RRC schedule, shut in November 1, 2022.
The RRC has issued one drilling permit, issued August 22, 2013, permitted to 10,674 ft.
It was permitted by Pioneer Natural Res. USA, Inc. and has since transferred to Ovintiv USA Inc. on the wellbore schedule.
Completion filings report 5 formation tops, including Spraberry, Dean, Wolfcamp, Strawn.
Its lease has reported 51.1K barrels of oil and 35.7K mcf of gas since January 2014, with no volume in the three years through April 2026. The lease carries 2 wells, so these are lease totals, not this well alone.
Operator of record
Permitted by Pioneer Natural Res. USA, Inc.; the EWA schedule now lists a different operator.
- Based in
- Denver, CO
- P-5 status
- Active (A)
- P-5 last filed
- Dec 12, 2025
- Permits on file
- 1,391
- Phone
- (720) 876-5176
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Ovintiv USA Inc. |
| Production reports | Ovintiv USA Inc.through Feb 2023 |
| Latest permit | Pioneer Natural Res. USA, Inc.Aug 22, 2013 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 10,674
- total depth, ft
- 1
- permits on file
- Aug 22, 2013
- last permit issued
- Jan 8, 2014
- completed
- 51.1K
- cumulative oil, bbl
- 35.7K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 2014 THROUGH Feb 2023
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Jan 8, 2014
- Shut in
- Nov 1, 2022
- 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 2 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Slaughter 29D O-10-44956 | Spraberry (Trend Area) | Ovintiv USA Inc. | 2 | 51.1K | 35.7K | Jan 2014 – Feb 2023 |
No volumes reported on these leases in the last three years.
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Pioneer Natural Res. USA, Inc.Jan 2014 → May 2017
- 2Petrolegacy Energy II, LLCJun 2017 → Feb 2023
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 768584-99 | Drill | Pioneer Natural Res. USA, Inc. | Aug 20, 2013 | Aug 22, 2013 | Sep 23, 2013 | 11,100 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Jan 8, 2014 | Slaughter 29D O-10-44956 | Spraberry (Trend Area) | Ovintiv USA Inc. | Shut In · shut in Nov 1, 2022 | 10,674 |
Formation tops
As filed on W-2/G-1. Subsea from 2,694 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 8,352 | 10,532 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 13.375 | 410 | 17.5 | 500 S |
| 8.625 | 4,737 | 11 | 850 S |
| 4.5 | 10,674 | 7.875 | 1,130 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 | Aug 19, 2014 | Mar 7, 2014 | Yes |
Well logs
1 log loaded from the RRC's log index, the latest received Sep 22, 2014. 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 described | Files | Intervalft, as filed | Datereceived | SizeMB |
|---|---|---|---|---|
| NEUTRON POROSITYSpans Spraberry, Dean, Wolfcamp, Strawn, Atoka | TIFF | 3,767 to 10,640 | Sep 22, 2014run Oct 8, 2013 | 3.07 |
"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-38867 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-317-38867 → 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/31738867, documented in the API reference.