WELL · 42-001-30641 · DISTRICT 6

Todd -A- #9

N

Anderson County · Boggy Creek field  · Vertical

Todd -A- #9 (API 42-001-30641) is a well in Anderson County operated by Hopewell Operating Inc., completed October 18, 1996.

The RRC has issued one drilling permit, issued August 9, 2016, permitted to 3,806 ft.

Completion filings report 3 formation tops, including Pecan Gap, Subclarksville, Woodbine.

Its 2 leases have reported 47.9K barrels of oil and 42 mcf of gas since January 1993, last reporting in July 2026. The leases carry 8 wells, so these are lease totals, not this well alone.

Operator of record

Hopewell Operating Inc.

Shreveport, LA · P-5 Y, filed Oct 4, 2025 · 118 permits on file · (800) 256-2390

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHopewell Operating Inc.
Production reportsWTR Operating LLCthrough Mar 2026
Latest permitHopewell Operating, Inc.Aug 9, 2016

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

3,806
total depth, ft
1
permits on file
Aug 9, 2016
last permit issued
Oct 18, 1996
completed
47.9K
cumulative oil, bbl
42
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jan 1993 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Oct 18, 1996
Shut in
—
Plugged
—

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 2 leases this well is completed on; they carry 8 wells in total, so volumes are shared.Why →

LeaseFieldReporting operatorWellsOil, bblGas, mcfReported
Todd Estate O-6-5870Boggy Creek (Wilcox)WTR Operating LLC515.8K21Jan 1993 – Jul 2026
Todd -A- O-6-4984Boggy CreekHopewell Operating, Inc.332.1K21Jan 1993 – Feb 2018

Oil, barrels lease total

Last 12 months 769 · prior 12 981(-22%)

0200400202420252026

Chain of custody

Every operator that reported production on this well's lease, in order.

  1. 1Shelby, Michael H.Jan 1993 → Jan 1994
  2. 2Hopewell Operating, Inc.Feb 1994 → Nov 2024
  3. 3WTR Operating LLCDec 2024 → Mar 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
814143-99RecompletionHopewell Operating, Inc.Mar 1, 2016Aug 9, 2016—3,806

Completions

CompletedLeaseFieldOperatorStatusDepth
—— O-6-4984————
—— O-6-5870————

Formation tops

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

FormationMD ftSubsea
Pecan Gap2,660-2,185
Subclarksville3,144-2,669
Woodbine3,593-3,118

Perforations

Perforated and open-hole intervals.

FromToType
1,5241,536Perforated
3,6913,706Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.62524712.25200 S
8.625247——
4.53,8037.875120 S
4.53,803——

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, 2018Sep 28, 2016—
00Apr 21, 1997Nov 18, 1996—
00Jan 12, 1984Dec 16, 1977—

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