WELL · 42-219-36684 · DISTRICT 8
Slaughter Consolidated #109
Hockley County · Tstar (Abo) field · Injection · Horizontal
Slaughter Consolidated #109 (API 42-219-36684) is a horizontal well in Hockley County operated by Hilcorp Energy Company, completed June 9, 2025 and listed as injection on the RRC schedule.
The RRC has issued 2 drilling permits between 2002 and 2006, permitted to 8,300 ft.
It was permitted by Occidental Permian Ltd. and has since transferred to Hilcorp Energy Company on the wellbore schedule.
Completion filings report 9 formation tops, including Yates, Seven Rivers, Queen, Gryburg.
Its lease has reported 19M barrels of oil and 17M mcf of gas since January 1999, last reporting in July 2026. The lease carries 106 wells, so these are lease totals, not this well alone.
It holds an active disposal or injection permit, with 3.64K barrels injected in the 12 months reported through March 2026.
Operator of record
Permitted by Occidental Permian Ltd.; the EWA schedule now lists a different operator.
- Based in
- Houston, TX
- P-5 status
- Active – Extension (X)
- P-5 last filed
- Mar 27, 2026
- Permits on file
- 3,454
- Phone
- (713) 209-2400
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Hilcorp Energy Company |
| Production reports | Occidental Permian Ltd.through Apr 2026 |
| Latest permit | Occidental Permian Ltd.May 18, 2006 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 8,300
- total depth, ft
- 2
- permits on file
- May 18, 2006
- last permit issued
- Jun 9, 2025
- completed
- 19M
- cumulative oil, bbl
- 17M
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Jan 1999 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- ON SCHEDULE
- Completed
- Jun 9, 2025
- Shut in
- —
- Plugged
- —
Operator's P-5 on the schedule: Active – Extension (X)
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 106 wells in total, so volumes are shared.Why →
| Lease | Field | Reporting operator | Wells | Oil, bbl | Gas, mcf | Reported |
|---|---|---|---|---|---|---|
| Slaughter Consolidated O-11-68016 | Tstar (Abo) | Hilcorp Energy Company | 106 | 19M | 17M | Jan 1999 – Jul 2026 |
Oil, barrels lease total
Last 12 months 346,211 · prior 12 399,029(-13%)
Gas, mcf lease total
Last 12 months 1,437,396 · prior 12 269,365(+434%)
Chain of custody
Every operator that reported production on this well's lease, in order.
- 1Altura Energy Ltd.Jan 1999 → Apr 2000
- 2Occidental Permian Ltd.May 2000 → Apr 2026
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 619497-99 | Recompletion | Occidental Permian Ltd. | May 18, 2006 | May 18, 2006 | Jun 4, 2006 | 8,300 |
| 525996-99 | Drill | Occidental Permian Ltd. | Dec 2, 2002 | Dec 3, 2002 | Nov 10, 2003 | 8,300 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-11-68016 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 3,522 ft elevation.Download CSV →
| Formation | MD ft | Subsea |
|---|---|---|
| Yates | 2,828 | 694 |
| Yates | 2,837 | 685 |
| Seven Rivers | 3,030 | 492 |
| Queen | 3,632 | -110 |
| Gryburg | 3,900 | -378 |
| San Andres | 4,086 | -564 |
| Glorieta | 5,551 | -2,029 |
| Tubb | 6,700 | -3,178 |
| Lowr Clearfork | 6,986 | -3,464 |
| Wichita-AlbanyWICHITA | 7,275 | -3,753 |
| Wichita-AlbanyWICHITA ALBANY | 7,275 | -3,753 |
| Wichita-AlbanyWICHITA ALBANY | 7,276 | -3,754 |
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 7,245 | 9,646 | Perforated |
| 7,246 | 7,900 | Perforated |
| 7,246 | 9,645 | Open hole |
| 7,440 | 7,900 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 2,282 | 12.25 | 820 S |
| 5.5 | 8,102 | 7.875 | 500 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 →
| Suffix | Filed | W-2 / G-1 date | Logs referenced |
|---|---|---|---|
| 00 | Oct 30, 2025 | Aug 26, 2025 | — |
| 00 | May 9, 2024 | Jun 6, 2023 | — |
| 00 | Apr 12, 2017 | Mar 15, 2017 | — |
| 00 | Feb 7, 2008 | Apr 9, 2007 | — |
| 00 | Dec 28, 2005 | Jul 28, 2005 | — |
| 00 | Apr 7, 2004 | Jan 9, 2004 | Yes |
| 00 | Mar 31, 2004 | — | — |
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-36684 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-219-36684 → scanned completion filings
Log images are in archives with no per-well link: the RRC's Neubus archive (2004 onward). then paste it into their search.
Beyond the permit record
RRC UIC permits · H-10 reported volumes
Injection
- 3.64K
- bbl, last 12 reported months
- 17.2K
- bbl, all reported
- Mar 2026
- reported through
| UIC | Kind | Status | Permitted bbl/d | Max psi | Zone ft |
|---|---|---|---|---|---|
| 000095070 | H-1 Injection | Active | 5,000 | 3,000 | 7,100–8,600 |
MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS
Last 12 months 3,635 · 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/21936684, documented in the API reference.