TEXAS · WELLS · PANOLA COUNTY · BOREN UNIT 1 LEASE · API 42-365-37070 · DISTRICT 06

Boren Unit 1 #8H

Plugged

Panola County · Carthage (Cotton Valley) field  · Horizontal

Boren Unit 1 #8H (API 42-365-37070) is a plugged horizontal well in Panola County, plugged January 30, 2015, last operated by Anadarko E&P Onshore LLC.

The RRC has issued one drilling permit, issued April 14, 2008, permitted to 12,000 ft.

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

Completion filings report 5 formation tops, including A Sand, B Sand, C Sand, Vaughn.

Operator of record

Anadarko E&P Onshore LLC

Permitted by Anadarko E&P Company LP; the EWA schedule now lists a different operator.

Based in
Houston, TX
P-5 status
Active (A)
P-5 last filed
Oct 22, 2025
Permits on file
4,575
Phone
(713) 215-7000

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleAnadarko E&P Onshore LLC
Production reportsAnadarko E&P Company LPthrough Nov 2008
Latest permitAnadarko E&P Company LPApr 14, 2008

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
Apr 14, 2008
last permit issued
Sep 25, 2008
completed
0
cumulative oil, bbl
18.4K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 2008 THROUGH Jan 2015

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Sep 25, 2008
Shut in
—
Plugged
Jan 30, 2015

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
Boren Unit 1 G-6-245096Carthage (Cotton Valley)Anadarko E&P Onshore LLC1018.4KSep 2008 – Jan 2015

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. 1Anadarko E&P Company LPSep 2008 → Nov 2008

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
658626-99DrillAnadarko E&P Company LPApr 2, 2008Apr 14, 2008Jul 4, 200812,000

Completions

CompletedLeaseFieldOperatorStatusDepth
Sep 25, 2008Boren Unit 1 G-6-245096Carthage (Cotton Valley)Anadarko E&P Onshore LLCPlugged—

Formation tops

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

FormationMD ftSubsea
A Sand8,414-8,221
B Sand8,534-8,341
C Sand8,586-8,393
Vaughn8,790-8,597
Davis9,089-8,896

Perforations

Perforated and open-hole intervals.

FromToType
8,42811,746Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
13.3751,03517.5908 S
9.6256,20512.251,597 S
79,1658.75720 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
00Mar 6, 2009Jan 30, 2009Yes
00Feb 23, 2009——

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