WELL · 42-095-30939 · DISTRICT 7

Henderson 70 #1070

Plugged

Concho County · Henderson (3325) field  · Vertical

Henderson 70 #1070 (API 42-095-30939) is a plugged well in Concho County, plugged April 30, 2010, last operated by Concho Oilfield Serv & Oper CO..

The RRC has issued one drilling permit, issued November 5, 1987, permitted to 4,200 ft.

It was permitted by Edammer, Inc. and has since transferred to Concho Oilfield Serv & Oper CO. on the wellbore schedule.

Completion filings report 5 formation tops, including Palo Pinto, Cross Cut Sand, Harkey Sand, Capps Li.

Its lease has reported 5.99K barrels of oil and 96 mcf of gas since January 1993, last reporting in July 2010.

Operator of record

Concho Oilfield Serv & Oper Co.

Permitted by Edammer, Inc.; 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 scheduleConcho Oilfield Serv & Oper Co.
Production reportsConcho Oilfield Serv & Oper Co.through Jun 2006
Latest permitEdammer, Inc.Nov 5, 1987

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

4,200
total depth, ft
1
permits on file
Nov 5, 1987
last permit issued
Dec 17, 1987
completed
5.99K
cumulative oil, bbl
96
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2010

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Dec 17, 1987
Shut in
—
Plugged
Apr 30, 2010

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
Henderson "70" O-9-12365Henderson (3325)Concho Oilfield Serv & Oper Co.15.99K96Jan 1993 – Jul 2010

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. 1Cimarron Properties, Inc.Jan 1993 → Nov 1997
  2. 2Concho Oilfield Serv & Oper Co.Dec 1997 → Jun 2006

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
338204-99DrillEdammer, Inc.Nov 2, 1987Nov 5, 1987—4,200

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-9-12365————

Formation tops

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

FormationMD ftSubsea
Palo PintoBASE PALO PINTO LI3,294-1,148
Cross Cut Sand3,350-1,204
Harkey Sand3,422-1,276
Capps LI3,751-1,605
Goen LI3,870-1,724

Perforations

Perforated and open-hole intervals.

FromToType
3,3503,354Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62535212.25230 S
4.53,5297.875250 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 22, 1988Jan 11, 1988Yes
00Jan 16, 1988——

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