WELL · 42-083-35472 · DISTRICT 7

James #4

Plugged

Coleman County · Coleman County Regular field  · Vertical

James #4 (API 42-083-35472) is a plugged well in Coleman County, plugged January 4, 2017, last operated by Blanton Oil LLC.

The RRC has issued one drilling permit, issued March 8, 1996, permitted to 2,000 ft.

It was permitted by Scranton Exploration and has since transferred to Blanton Oil LLC on the wellbore schedule.

Completion filings report one formation top, including Cross Cut Sand.

Its lease has reported 7.66K barrels of oil since September 1994, last reporting in July 2026. The lease carries 4 wells, so these are lease totals, not this well alone.

Operator of record

Blanton Oil LLC

Permitted by Scranton Exploration; the EWA schedule now lists a different operator.

Allen, TX · P-5 Y, filed Jun 2, 2017 · (325) 370-0879

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBlanton Oil LLC
Production reportsBlanton Oil, LLCthrough Apr 2015
Latest permitScranton ExplorationMar 8, 1996

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

2,000
total depth, ft
1
permits on file
Mar 8, 1996
last permit issued
May 16, 1996
completed
7.66K
cumulative oil, bbl
0
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Sep 1994 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
May 16, 1996
Shut in
—
Plugged
Jan 4, 2017

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; they carry 4 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
James O-8-27296Coleman County RegularBlanton Oil, LLC47.66K0Sep 1994 – Jul 2026

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. 1Guidance Oil Developers, Inc.Sep 1994 → May 1995
  2. 2B-W OilJul 1995 → Aug 1995
  3. 3Scranton ExplorationSep 1995 → Mar 2004
  4. 4Ledbetter, Jerald D. Oil CompanyApr 2004 → Jan 2007
  5. 5Ledbetter, Jerald D. Estate OFFeb 2007 → Jun 2013
  6. 6US. Fuels, Inc.Jul 2013 → Oct 2014
  7. 7Blanton Oil, LLCNov 2014 → Apr 2015

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
445734-99DrillScranton ExplorationMar 8, 1996Mar 8, 1996Mar 15, 19962,000

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-8-27296————

Formation tops

As filed on W-2/G-1. Download CSV →

FormationMD ft
Cross Cut Sand1,726

Perforations

Perforated and open-hole intervals.

FromToType
1,7261,728Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
4.51,7687.875350 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
00Jul 26, 1996May 28, 1996Yes
00Jun 3, 1996——

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