TEXAS · WELLS · DENTON COUNTY · JACKSON, H. B. LEASE · API 42-121-30516 · DISTRICT 7C

Jackson H. B. #2

Plugged

Denton County · Monteath (Atoka Upper) field  · Vertical

Jackson H. B. #2 (API 42-121-30516) is a plugged well in Denton County, plugged November 10, 2010, last operated by J-W Operating CO..

The RRC has issued one drilling permit, issued April 12, 1989, permitted to 6,500 ft.

It was permitted by Enre Corp. and has since transferred to J-W Operating CO. on the wellbore schedule.

Completion filings report 3 formation tops, including Caddo, Pregnant Shale, Atoka.

Operator of record

J-W Operating Co.

Permitted by Enre Corp.; the EWA schedule now lists a different operator.

Based in
Addison, TX
P-5 status
Delinquent (D)
P-5 last filed
Jul 30, 2019
Permits on file
350
Phone
(972) 233-8191

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleJ-W Operating Co.
Production reportsJ-W Operating Co.through Jun 2008
Latest permitEnre Corp.Apr 12, 1989

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

6,500
total depth, ft
1
permits on file
Apr 12, 1989
last permit issued
Aug 28, 1989
completed
0
cumulative oil, bbl
149K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Nov 2010

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Aug 28, 1989
Shut in
—
Plugged
Nov 10, 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
Jackson, H. B. G-13-132124Monteath (Atoka, Upper)J-W Operating Co.10149KJan 1993 – Nov 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. 1Enre Corp.Jan 1993 → Jan 2001
  2. 2Enre, L.P.Feb 2001 → Feb 2004
  3. 3J-W Operating Co.Mar 2004 → Jun 2008

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
357962-99DrillEnre Corp.Apr 10, 1989Apr 12, 1989—6,500

Completions

CompletedLeaseFieldOperatorStatusDepth
Aug 28, 1989Jackson H. B. G-13-132124Monteath (Atoka Upper)J-W Operating Co.Plugged—

Formation tops

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

FormationMD ftSubsea
Caddo4,332-3,653
CaddoCADDO-CONGLOMERATE4,764-4,085
Pregnant Shale5,448-4,769
AtokaATOKA CONGL.6,084-5,405

Perforations

Perforated and open-hole intervals.

FromToType
5,4505,456Perforated
5,4655,469Perforated
5,5035,507Perforated
5,5285,535Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62593712.25460 S
4.56,2237.875450 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 11, 1989Sep 29, 1989Yes
00Oct 30, 1989——

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