WELL · 42-095-31970 · DISTRICT 7
S & H Livestock #1
Concho County · Paint Rock S. (Goen Lime) field · Vertical
S & H Livestock #1 (API 42-095-31970) is a plugged well in Concho County, plugged September 20, 2011, last operated by Concho Oilfield Serv & Oper CO..
The RRC has issued one drilling permit, issued January 7, 2001, permitted to 3,700 ft.
It was permitted by B-J Oil CO. and has since transferred to Concho Oilfield Serv & Oper CO. on the wellbore schedule.
Completion filings report 4 formation tops, including Tannehill, Crosscut Sand, Goen Lime, Strawn.
Operator of record
Concho Oilfield Serv & Oper Co.
Permitted by B-J Oil Co.; the EWA schedule now lists a different operator.
Eden, TX · P-5 Y, filed Feb 4, 2026 · 11 permits on file · (325) 456-0685
SOURCE · RRC EWA WELLBORE SCHEDULE
What each RRC source says
| Wellbore schedule | Concho Oilfield Serv & Oper Co. |
| Production reports | none |
| Latest permit | B-J Oil Co.Jan 7, 2001 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 3,700
- total depth, ft
- 1
- permits on file
- Jan 7, 2001
- last permit issued
- Oct 8, 2002
- completed
- 0
- cumulative oil, bbl
- 0
- cumulative gas, mcf
PRODUCTION FROM PDQ LEASE REPORTS · Oct 2002 THROUGH Jul 2026
Regulatory status · RRC wellbore file
- Schedule
- OFF SCHEDULE
- Completed
- Oct 8, 2002
- Shut in
- —
- Plugged
- Sep 20, 2011
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 |
|---|---|---|---|---|---|---|
| S & H Livestock O-9-15317 | Paint Rock, S. (Goen Lime) | Concho Oilfield Serv & Oper Co. | 1 | 0 | 0 | Oct 2002 – Jul 2026 |
No volumes reported on these leases in the last three years.
Permits
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 516434-99 | Drill | B-J Oil Co. | Dec 27, 2001 | Jan 7, 2001 | Apr 22, 2002 | 3,700 |
Completions
| Completed | Lease | Field | Operator | Status | Depth |
|---|---|---|---|---|---|
| — | — O-9-15317 | — | — | — | — |
Formation tops
As filed on W-2/G-1. Subsea from 1,697 ft elevation.Download CSV →
Perforations
Perforated and open-hole intervals.
| From | To | Type |
|---|---|---|
| 3,364 | 3,368 | Perforated |
Casing
Strings as reported, shallowest first.
| Casing in | Set at | Hole in | Cement |
|---|---|---|---|
| 8.625 | 121 | 11 | 290 S |
| 4.5 | 3,644 | 7.875 | 280 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 | Mar 5, 2003 | Dec 16, 2002 | Yes |
| 00 | Jan 14, 2003 | — | — |
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-095-31970 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-095-31970 → 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.
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/09531970, documented in the API reference.