WELL · 42-155-30821 · DISTRICT 13

Hord #1

Plugged

Foard County · Crowell N (Conglomerate) field  · Vertical

Hord #1 (API 42-155-30821) is a plugged well in Foard County, plugged January 13, 2023, last operated by Abb Oil CO. Inc..

The RRC has issued one drilling permit, issued December 13, 2022, permitted to 6,500 ft.

It was permitted by Abb Oil CO., Inc. and has since transferred to Abb Oil CO. Inc. on the wellbore schedule.

Operator of record

Abb Oil Co. Inc.

Permitted by Abb Oil Co., Inc.; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitAbb Oil Co., Inc.Dec 13, 2022

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

6,500
total depth, ft
1
permits on file
Dec 13, 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
Jan 13, 2023

Surface location

34.052000, -99.742200

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
886346-99DrillAbb Oil Co., Inc.Dec 8, 2022Dec 13, 2022Dec 21, 20226,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 8 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 →

Walser42-155-30827

2.0 KM · Abb Oil Co., Inc. · Section with this well →

Canyon4,500
Caddo5,780
Conglomerate6,000

Walser42-155-30823

2.3 KM · Abb Oil Co., Inc. · Section with this well →

Canyon4,630-3,200
Caddo5,698-4,268
Bend6,180-4,750
Cisco—
Tannehill—
Strawn—
Raspberry—
Palo Pinto—

10 TOPS · FIRST 8

Christopher42-155-30814

2.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

Welch, James A.42-155-30811

2.5 KM · Williams, A. Oil · Section with this well →

Coleman Junction2,015
Bend6,050
Raspberry—
Caddo—
Canyon—
Cisco—
Gunsite—
Palo Pinto—

10 TOPS · FIRST 8

Welch, J. A.42-155-30804

2.8 KM · Menasco, J. · Section with this well →

Coleman Junction1,965-528
Bend6,014-4,577
Caddo—
Tannehill—
Strawn—
Raspberry—
Palo Pinto—
Gunsite—

10 TOPS · FIRST 8

Thompson42-155-30816

2.9 KM · Abb Oil Co., Inc. · Section with this well →

Canyon4,500-3,061
Caddo5,700-4,261
Bend5,760-4,321
Palo Pinto—
Raspberry—
Strawn—
Tannehill—
Cisco—

10 TOPS · FIRST 8

Walser42-155-30806

3.0 KM · Dry Fork Production Co., LLC · Section with this well →

Coleman Junction1,965-537
Caddo5,624-4,196
Bend6,028-4,600
Raspberry—
Cisco—
Canyon—
Tannehill—
Gunsite—

10 TOPS · FIRST 8

Thompson42-155-30818

3.2 KM · Abb Oil Co., Inc. · Section with this well →

Canyon4,500-3,067
Caddo5,700-4,267
Bend5,900-4,467
Tannehill—
Strawn—
Raspberry—
Palo Pinto—
Gunsite—

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