TEXAS · WELLS · JASPER COUNTY · TEMPLE-INDUSTRIES 4-H LEASE · API 42-241-30586 · DISTRICT 06

Temple-Industries 4-H #4 H

Plugged

Jasper County · Brookeland (Austin Chalk 8800) field  · Horizontal

Temple-Industries 4-H #4 H (API 42-241-30586) is a plugged horizontal well in Jasper County, plugged February 9, 2000, last operated by Anadarko E&P Company LP.

The RRC has issued one drilling permit (amended twice), issued September 22, 1994, permitted to 13,000 ft.

It was permitted by Torch Operating Company and has since transferred to Anadarko E&P Company LP on the wellbore schedule.

Operator of record

Anadarko E&P Company LP

Permitted by Torch Operating Company; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Inactive (I)
P-5 last filed
Sep 27, 2012
Permits on file
2,635
Phone
(832) 636-3130

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleAnadarko E&P Company LP
Production reportsUnion Pacific Resources Companythrough Oct 1999
Latest permitTorch Operating CompanySep 22, 1994

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

13,000
total depth, ft
3
permits on file
Sep 22, 1994
last permit issued
Feb 7, 1995
completed
0
cumulative oil, bbl
1M
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1995 THROUGH Mar 2007

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Feb 7, 1995
Shut in
—
Plugged
Feb 9, 2000

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
Temple-Industries 4-H G-6-154864Brookeland (Austin Chalk, 8800)Anadarko E&P Company LP101MJan 1995 – Mar 2007

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. 1Torch Operating CompanyJan 1995 → Jun 1996
  2. 2Union Pacific Resources CompanyJul 1996 → Oct 1999

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
428102-97DrillTorch Operating CompanyJul 25, 1995Sep 22, 1994—13,000
428102-98DrillTorch Operating CompanyApr 20, 1995Sep 22, 1994—13,000
428102-99DrillTorch Operating CompanySep 16, 1994Sep 22, 1994Nov 29, 199411,500

Completions

CompletedLeaseFieldOperatorStatusDepth
Feb 7, 1995Temple-Industries 4-H G-6-154864Brookeland (Austin Chalk 8800)Anadarko E&P Company LPPlugged—

Perforations

Perforated and open-hole intervals.

FromToType
9,53612,650Open hole
9,53613,000Open hole

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
1667——
10.752,06814.75919 S
7.6259,5369.875297 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
00Sep 28, 1995Mar 3, 1995Yes
00Aug 3, 1995——

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