WELL · 42-329-34155 · DISTRICT 8

Spinks #1H

Plugged

Midland County · Azalea (Devonian) field  · Horizontal

Spinks #1H (API 42-329-34155) is a plugged horizontal well in Midland County, plugged April 12, 2016, last operated by Burleson Petroleum Inc..

The RRC has issued one drilling permit, issued February 11, 1999, permitted to 12,000 ft.

It was permitted by Union Pacific Resources Company and has since transferred to Burleson Petroleum Inc. on the wellbore schedule.

Completion filings report 2 formation tops, including Strawn, Devonian.

Its lease has reported 8.36K barrels of oil and 599K mcf of gas since May 1999, last reporting in April 2016.

Operator of record

Burleson Petroleum Inc.

Permitted by Union Pacific Resources Company; the EWA schedule now lists a different operator.

Midland, TX · P-5 Y, filed Nov 4, 2025 · 85 permits on file · (432) 683-4747

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBurleson Petroleum Inc.
Production reportsConocophillips Companythrough Sep 2009
Latest permitUnion Pacific Resources CompanyFeb 11, 1999

The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.

12,000
total depth, ft
1
permits on file
Feb 11, 1999
last permit issued
May 8, 1999
completed
8.36K
cumulative oil, bbl
599K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 1999 THROUGH Apr 2016

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
May 8, 1999
Shut in
—
Plugged
Apr 12, 2016

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 →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Spinks O-10-36109Azalea (Devonian)Burleson Petroleum, Inc.18.36K599KMay 1999 – Apr 2016

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.

  1. 1Union Pacific Resources CompanyMay 1999 → Sep 1999
  2. 2Phillips Petroleum CompanyOct 1999 → Dec 2002
  3. 3Conocophillips CompanyJan 2003 → Sep 2009

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
482609-99DrillUnion Pacific Resources CompanyFeb 8, 1999Feb 11, 1999Feb 18, 199912,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-10-36109————

Formation tops

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

FormationMD ftSubsea
Strawn10,285-7,574
Devonian11,370-8,659

Perforations

Perforated and open-hole intervals.

FromToType
12,39015,010Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.37535517.5350 S
9.6255,02012.251,540 S
7.62511,3828.5500 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 →

SuffixFiledW-2 / G-1 dateLogs referenced
00Dec 17, 1999Aug 2, 1999Yes
00Dec 2, 1999——

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.

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