WELL · 42-421-30959 · DISTRICT 10

Todd #1

Plugged

Sherman County · Texas Hugoton field  · Vertical

Todd #1 (API 42-421-30959) is a plugged well in Sherman County, plugged June 7, 2019, last operated by Hrf Exploration & Production LLC.

The RRC has issued one drilling permit, issued April 28, 2003, permitted to 3,500 ft.

It was permitted by Hrf Exploration & Production,Inc and has since transferred to Hrf Exploration & Production LLC on the wellbore schedule.

Completion filings report 7 formation tops, including Tubb, Panhandle Lime, Winfield, Council Grove.

Operator of record

HRF Exploration & Production LLC

Permitted by HRF Exploration & Production,inc; the EWA schedule now lists a different operator.

P-5 Y, filed Jun 4, 2026 · 3 permits on file · (989) 732-6950

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleHRF Exploration & Production LLC
Production reportsHRF Exploration & Production,llcthrough Jun 2016
Latest permitHRF Exploration & Production,incApr 28, 2003

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

3,500
total depth, ft
1
permits on file
Apr 28, 2003
last permit issued
Jul 31, 2003
completed
0
cumulative oil, bbl
422K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2003 THROUGH Jun 2019

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
Jul 31, 2003
Shut in
—
Plugged
Jun 7, 2019

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
Todd G-14-199362Texas HugotonHRF Exploration & Production,llc10422KJul 2003 – Jun 2019

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. 1HRF Exploration & Production,incJul 2003 → Dec 2004
  2. 2HRF Exploration & Production,llcJan 2005 → Jun 2016

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
529674-99DrillHRF Exploration & Production,incMar 17, 2003Apr 28, 2003May 25, 20033,500

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-14-199362————

Formation tops

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

FormationMD ftSubsea
Tubb1,7651,761
Panhandle Lime2,531995
Winfield2,873653
Council Grove3,078448
Texas Hugoton3,078448
Neva3,284242
Admire3,316210

Perforations

Perforated and open-hole intervals.

FromToType
3,3043,316Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
8.6251,65712.25845 S
5.53,5557.875245 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 18, 2018Nov 1, 2018—
00Mar 26, 2004Oct 15, 2003—
00Mar 22, 2004Sep 16, 2003Yes
00Feb 27, 2004——

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