TEXAS · WELLS · HOCKLEY COUNTY · TEXACO SLAUGHTER ESTATE LEASE · API 42-219-36617 · DISTRICT 7B
Texaco Slaughter Estate #16
Hockley County · Tstar (Abo) field · Shut In · Vertical
Texaco Slaughter Estate #16 (API 42-219-36617) is a well in Hockley County operated by Bce-Mach Iii LLC, completed December 18, 2019 and listed as shut in on the RRC schedule, shut in September 1, 2021.
The RRC has issued one drilling permit, issued August 2, 2001, permitted to 8,100 ft.
It was permitted by Texaco E & P Inc. and has since transferred to Bce-Mach Iii LLC on the wellbore schedule.
Completion filings report 2 formation tops, including Yates, Abo.
Its lease has reported 3.48M barrels of oil and 970K mcf of gas since April 1996, last reporting volume in August 2026. The lease carries 25 wells, so these are lease totals, not this well alone.
It holds an active disposal or injection permit.
Operator of record
Permitted by Texaco E & P Inc.; the EWA schedule now lists a different operator.
- Based in
- Oklahoma City, OK
- P-5 status
- Active (A)
- P-5 last filed
- May 18, 2026
- Permits on file
- 10
- Phone
- (405) 252-8100
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Bce-Mach III LLC |
| Production reports | Bce-Mach III LLCthrough Aug 2026 |
| Latest permit | Texaco E & P Inc.Aug 2, 2001 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 8,100
- total depth, ft
- 1
- permits on file
- Aug 2, 2001
- last permit issued
- Dec 18, 2019
- completed
- 3.48M
- cumulative oil, bbl
- 970K
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · APR 1996 THROUGH AUG 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Dec 18, 2019
- Shut in
- Sep 1, 2021
- 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.
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 25 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Texaco Slaughter Estate O-11-67566 | Tstar (Abo) | Bce-Mach III LLC | 25 | 3.48M | 970K | Apr 1996 – Aug 2026 |
Oil, barrels lease total
Last 12 months 54,613 · prior 12 61,123(-11%)
Gas, mcf lease total
Last 12 months 25,368 · prior 12 23,530(+8%)
Wells named Texaco Slaughter Estate
Bce-Mach III LLC's other wells filed under this lease name in Hockley 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 wellsChain of custody
Every operator that reported production on this well's lease, in order.
- 1Texaco E & P Inc.Apr 1996 → May 2002
- 2Chevron U. S. A. Inc.Jun 2002 → Sep 2017
- 3Sabinal Energy Operating, LLCOct 2017 → Aug 2025
- 4Bce-Mach III LLCSep 2025 → Aug 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 512161-99 | Drill | Texaco E & P Inc. | Aug 2, 2001 | Aug 2, 2001 | Nov 11, 2001 | 8,100 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| Dec 18, 2019 | Texaco Slaughter Estate O-11-67566 | Tstar (Abo) | Bce-Mach III LLC | Shut In · shut in Sep 1, 2021 | 8,100 |
Formation tops
As filed on W-2/G-1. Subsea from 3,522 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 7,626 | 7,675 | Perforated |
| 7,626 | 7,841 | Perforated |
| 7,725 | 7,774 | Perforated |
| 7,787 | 7,841 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 2,235 | 12.25 | 1,300 S |
| 5.5 | 8,100 | 7.875 | 1,700 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 | Nov 6, 2024 | Sep 17, 2024 | — |
| 00 | Apr 1, 2013 | Aug 9, 2012 | — |
| 00 | Aug 15, 2002 | Jan 24, 2002 | Yes |
| 00 | Jul 9, 2002 | — | — |
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-219-36617 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-219-36617 → scanned completion filings
Log images filed since 2004 open from the RRC's log search for this well; none are loaded here for it.
Beyond the permit record
RRC UIC permits · H-10 reported volumes
Injection
- 0
- bbl, last 12 reported months
- 938K
- bbl, all reported
- Mar 2026
- reported through
| UIC | Kind | Status | Permitted bbl/d | Max psi | Zone ft |
|---|---|---|---|---|---|
| 000091800 | H-1 Injection | Active | 2,200 | 2,500 | 7,100–8,600 |
MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS
Last 12 months 0 · prior 12 0
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/21936617, documented in the API reference.