TEXAS · WELLS · HOCKLEY COUNTY · SLAUGHTER CONSOLIDATED LEASE · API 42-219-36773 · DISTRICT 7B

Slaughter Consolidated #430

On schedule

Hockley County · Tstar (Abo) field · Injection  · Vertical

Slaughter Consolidated #430 (API 42-219-36773) is a well in Hockley County operated by Hilcorp Energy Company, completed December 8, 2015 and listed as injection on the RRC schedule.

The RRC has issued one drilling permit, issued January 21, 2005, permitted to 8,100 ft.

It was permitted by Occidental Permian Ltd. and has since transferred to Hilcorp Energy Company on the wellbore schedule.

Completion filings report 11 formation tops, including Yates, Seven Rivers, Queen, Grayburg.

Its lease has reported 19M barrels of oil and 17M mcf of gas since January 1999, last reporting volume in April 2026. The lease carries 106 wells, so these are lease totals, not this well alone.

It holds an active disposal or injection permit, with 21K barrels injected in the 12 months reported through March 2026.

Operator of record

Hilcorp Energy Company

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,458
Phone
(713) 209-2400

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHilcorp Energy Company
Production reportsHilcorp Energy Companythrough Apr 2026
Latest permitOccidental Permian Ltd.Jan 21, 2005

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
Jan 21, 2005
last permit issued
Dec 8, 2015
completed
19M
cumulative oil, bbl
17M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · JAN 1999 THROUGH APR 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Dec 8, 2015
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.

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 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 →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Slaughter Consolidated O-11-68016Tstar (Abo)Hilcorp Energy Company10619M17MJan 1999 – Apr 2026

Oil, barrels lease total

Last 12 months 346,211 · prior 12 399,029(-13%)

020K40K60K202420252026

Gas, mcf lease total

Last 12 months 1,437,396 · prior 12 269,365

0200K400K202420252026

Wells named Slaughter Consolidated

Hilcorp Energy Company'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 wells

Chain of custody

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

  1. 1Altura Energy Ltd.Jan 1999 → Apr 2000
  2. 2Occidental Permian Ltd.May 2000 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
556363-99DrillOccidental Permian Ltd.Jan 18, 2005Jan 21, 2005Apr 13, 20058,300

Completions

CompletedLeaseFieldOperatorStatusDepth
Dec 8, 2015Slaughter Consolidated O-11-68016Tstar (Abo)Hilcorp Energy CompanyInjection8,100

Formation tops

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

FormationMD ftSubsea
Yates2,884625
Seven Rivers3,092417
Queen3,667-158
Grayburg3,948-439
San Andres4,133-624
San Andres4,136-627
Glorieta5,612-2,103
Tubb6,908-3,399
Clear ForkLOWER CLEARFORK7,028-3,519
L. Clearfork7,148-3,639
Abo7,703-4,194
Wichita-Albany8,383-4,874

Perforations

Perforated and open-hole intervals.

FromToType
7,7087,806Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6252,27312.25820 S
5.58,0937.875500 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
00Dec 1, 2025Nov 7, 2025—
00Dec 21, 2005Jul 5, 2005Yes
00Oct 17, 2005——

Well logs

The RRC's map lists this well among those with logs online. Its monthly inventories loaded here, which start in July 2006, list none for it, so none are itemized.

Open the RRC's log search for this well ↗

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.

Beyond the permit record

RRC UIC permits · H-10 reported volumes

Injection

21K
bbl, last 12 reported months
48.6K
bbl, all reported
Mar 2026
reported through
UICKindStatusPermitted bbl/dMax psiZone ft
000094953H-1 InjectionActive5,0003,5507,100–8,600

MONTHLY INJECTED, BBL · H-10 · LAST 24 REPORTED MONTHS

Last 12 months 21,024 · prior 12 0

05K10K20252026

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/21936773, documented in the API reference.