WELL · 42-179-32483 · DISTRICT 10

Huggins #304

Y

Gray County · Panhandle East field · Producing  · Vertical

Huggins #304 (API 42-179-32483) is a well in Gray County operated by Bce-Mach Iii LLC, completed July 22, 2004 and listed as producing on the RRC schedule.

The RRC has issued one drilling permit, issued May 20, 2004, permitted to 3,900 ft.

It was permitted by Chesapeake Operating, Inc. and has since transferred to Bce-Mach Iii LLC on the wellbore schedule.

Completion filings report one formation top, including Brown Dolomite.

No lease production has been reported under this well’s leases.

Operator of record

Bce-Mach III LLC

Permitted by Chesapeake Operating, Inc.; the EWA schedule now lists a different operator.

Oklahoma City, OK · P-5 Y, filed Mar 4, 2026 · 10 permits on file · (833) 831-2164

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore scheduleBce-Mach III LLC
Production reportsBce-Mach III LLCthrough Apr 2026
Latest permitChesapeake Operating, Inc.May 20, 2004

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

3,900
total depth, ft
1
permits on file
May 20, 2004
last permit issued
Jul 22, 2004
completed
0
cumulative oil, bbl
164K
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS · Jul 2004 THROUGH Jul 2026

Regulatory status · RRC wellbore file

Schedule
ON SCHEDULE
Completed
Jul 22, 2004
Shut in
—
Plugged
—

Operator's P-5 on the schedule: X

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
Huggins G-14-204021Panhandle, EastBce-Mach III LLC10164KJul 2004 – Jul 2026

Gas, mcf lease total

Last 12 months 3,919 · prior 12 3,539(+11%)

0200400202420252026

Chain of custody

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

  1. 1Chesapeake Operating, Inc.Jul 2004 → Oct 2014
  2. 2Chesapeake Operating, L.L.C.Nov 2014 → Jun 2016
  3. 34P Energy Texas, LLCJul 2016 → Oct 2016
  4. 4Scout Energy Management LLCJan 2018 → Jun 2022
  5. 5Bce-Mach III LLCAug 2022 → Apr 2026

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
545942-99DrillChesapeake Operating, Inc.May 20, 2004May 20, 2004Jun 25, 20043,900

Completions

CompletedLeaseFieldOperatorStatusDepth
—— G-14-204021————

Formation tops

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

FormationMD ftSubsea
Brown Dolomite2,276577

Perforations

Perforated and open-hole intervals.

FromToType
2,2392,448Perforated

Casing

Strings as reported, shallowest first.

Casing inSet atHole inCement
9.62534412.25235 S
72,2398.75110 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 27, 2004Sep 28, 2004Yes
00Nov 4, 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/17932483, documented in the API reference.