WELL · 42-155-30819 · DISTRICT 9

Hughston Unit #1

Plugged

Foard County · Wildcat field  · Vertical

Hughston Unit #1 (API 42-155-30819) is a plugged well in Foard County, plugged April 28, 2022, last operated by 3-T Exploration Inc..

The RRC has issued one drilling permit, issued March 14, 2022, permitted to 5,500 ft.

It was permitted by 3-T Exploration, Inc. and has since transferred to 3-T Exploration Inc. on the wellbore schedule.

Operator of record

3-T Exploration Inc.

Permitted by 3-T Exploration, Inc.; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permit3-T Exploration, Inc.Mar 14, 2022

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

5,500
total depth, ft
1
permits on file
Mar 14, 2022
last permit issued
—
completed
—
cumulative oil, bbl
—
cumulative gas, mcf

PRODUCTION FROM PDQ LEASE REPORTS

Regulatory status · RRC wellbore file

Schedule
OFF SCHEDULE
Completed
—
Shut in
—
Plugged
Apr 28, 2022

Surface location

33.934215, -99.868012

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Foard County.

Only the permit record exists for this well so far, here and in the RRC's wellbore query. Completion reports, formation tops, lease production, and the scanned filings appear once the operator files a completion report, typically months after drilling. Petrora refreshes the wellbore file weekly, so a filing from the last few days may reach the RRC before it shows here. How long each source takes →

Permits

PermitTypeOperatorReceivedIssuedSpudDepth
876963-99Drill3-T Exploration, Inc.Feb 10, 2022Mar 14, 2022Apr 18, 20225,500

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.

Nearby wells and their tops

NEAREST 7 LOCATED WELLS WITH TOPS · WITHIN 16 KM

Draw a cross-section

This well has no tops filed, so it cannot anchor a section; its neighbours can.

Section of the neighbours →

Rasberry /6100 Caddo/ Unit42-155-00152

11.2 KM · Falcon Production LLC · Section with this well →

Caddo6,112-4,331

Drabek42-155-30800

13.6 KM · Modern Exploration, Inc. · Section with this well →

Canyon5,011-3,560
Palo Pinto5,320-3,869
Caddo6,160-4,709
Atoka6,572-5,121
Chester7,452-6,001
Strawn—
Cisco—
Coleman Junction—

10 TOPS · FIRST 8

Jones Unit42-275-32357

15.3 KM · Expro Engineering, Inc. · Section with this well →

Coleman Junction1,856-446
Saddle Creek2,577-1,167
Cisco2,825-1,415
Home Creek3,873-2,463
Canyon4,087-2,677
Strawn4,597-3,187
Caddo5,700-4,290
Bend5,952-4,542

10 TOPS · FIRST 8

Christopher42-155-30814

15.4 KM · Delfin Operating, LLC · Section with this well →

Coleman Junction2,946-1,503
Tannehill3,514-2,071
Gunsite3,565-2,122
Cisco3,804-2,361
Canyon4,950-3,507
Palo Pinto5,262-3,819
Strawn5,680-4,237
Raspberry6,110-4,667

10 TOPS · FIRST 8

Brown, Williams et AL42-275-32390

15.6 KM · Double M Petroproperties, Inc. · Section with this well →

Coleman Junction1,850-392
Saddle Creek2,575-1,117
Cisco2,825-1,367
Home Creek3,870-2,412
Canyon4,085-2,627
Strawn4,592-3,134
Caddo5,750-4,292
Bend5,977-4,519

10 TOPS · FIRST 8

Jones Unit42-275-32352

15.6 KM · Expro Engineering, Inc. · Section with this well →

Coleman Junction1,856-405
Saddle Creek2,577-1,126
Cisco2,825-1,374
Home Creek3,873-2,422
Canyon4,087-2,636
Strawn4,597-3,146
Caddo5,753-4,302
Bend5,952-4,501

10 TOPS · FIRST 8

Johnson, L. K.42-155-30815

15.7 KM · NWG Operating LLC · Section with this well →

Coleman Junction1,967-347
Tannehill2,457-837
Gunsite3,325-1,705
Cisco3,629-2,009
Canyon3,730-2,110
Raspberry—
Caddo—
Bend—

10 TOPS · FIRST 8

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