WELL · 42-367-34356 · DISTRICT 9

King Unit #1H

Y

Parker County · Newark East (Barnett Shale) field · Producing  · Horizontal

King Unit #1H (API 42-367-34356) is a horizontal well in Parker County operated by Spindletop Oil & Gas Company, completed May 16, 2007 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued March 6, 2007, permitted to 9,300 ft.

It was permitted by Tanglewood Oil & Gas LLC and has since transferred to Spindletop Oil & Gas Company on the wellbore schedule.

Completion filings report one formation top, including Barnett.

No lease production has been reported under this well’s leases.

Operator of record

Spindletop Oil & Gas Company

Permitted by Tanglewood Oil & Gas LLC; the EWA schedule now lists a different operator.

Dallas, TX · P-5 Y, filed Aug 4, 2025 · 180 permits on file · (972) 644-2581

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleSpindletop Oil & Gas Company
Production reportsSpindletop Oil & Gas Companythrough Apr 2026
Latest permitTanglewood Oil & Gas LLCMar 6, 2007

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

9,300
total depth, ft
1
permits on file
Mar 6, 2007
last permit issued
May 16, 2007
completed
0
cumulative oil, bbl
1.45M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · May 2007 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
May 16, 2007
Shut in
—
Plugged
—

Operator's P-5 on the schedule: Active

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
King Unit G-13-231716Newark, East (Barnett Shale)Spindletop Oil & Gas Company101.45MMay 2007 – Jul 2026

Gas, mcf lease total

Last 12 months 38,853 · prior 12 41,188(-6%)

02K4K202420252026

Chain of custody

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

  1. 1Tanglewood Oil & Gas LLCJun 2007 → Oct 2017
  2. 2Spindletop Drilling Co.Nov 2017 → Dec 2021
  3. 3Spindletop Oil & Gas CompanyJan 2022 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
634460-99DrillTanglewood Oil & Gas LLCMar 1, 2007Mar 6, 2007Mar 6, 20079,300

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-13-231716————

Formation tops

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

FormationMD ftSubsea
BarnettBARNETT SHALE6,317-5,524

Perforations

Perforated and open-hole intervals.

FromToType
6,7918,315Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62597012.25465 S
5.58,3517.87559 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
00Jan 9, 2008Jun 27, 2007Yes
00Dec 20, 2007——

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