WELL · 42-197-31770 · DISTRICT 13

Kempf Ferguson #1RE

Plugged

Hardeman County  · Vertical

Kempf Ferguson #1RE (API 42-197-31770) is a plugged well in Hardeman County, plugged October 9, 2019, last operated by Dry Fork Production CO., LLC.

The RRC has issued 2 drilling permits in 2019, permitted to 8,900 ft.

Operator of record

Dry Fork Production Co., LLC

Wichita Falls, TX · P-5 Y, filed Feb 4, 2026 · 207 permits on file · (940) 704-7200

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitDry Fork Production Co., LLCAug 16, 2019
8,900
total depth, ft
2
permits on file
Aug 16, 2019
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
Oct 9, 2019

Surface location

34.146514, -99.487358

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Hardeman 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
856255-99ReenterDry Fork Production Co., LLCAug 14, 2019Aug 16, 2019Aug 30, 20197,550
854259-99DrillTrio Consulting & Management,llcJun 17, 2019Jun 18, 2019Jul 8, 20198,900

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 →

Ward42-197-31787

0.1 KM · Interstate Explorations LLC · Section with this well →

Palo Pinto5,109-3,749
Barnett7,834-6,474
Meramec Shale7,978-6,618
Cisco—
Canyon—
Holmes Sand—
Conglomerates—
Coleman Junction—

10 TOPS · FIRST 8

Abloc42-197-31796

0.7 KM · Interstate Explorations LLC · Section with this well →

Palo Pinto5,131
Conglomerates7,200
Barnett7,838
Strawn—
Canyon—
Cisco—
Permian (undifferentiated)—
Holmes Sand—

10 TOPS · FIRST 8

Cuda42-197-31791

0.9 KM · Interstate Explorations LLC · Section with this well →

Palo Pinto5,093-3,751
Conglomerates7,315-5,973
Barnett7,860-6,518
Canyon—
Strawn—
Permian (undifferentiated)—
Meramec Shale—
Holmes Sand—

10 TOPS · FIRST 8

Boucher42-197-31274

0.9 KM · Ozark Exploration, Inc. · Section with this well →

Conglomerates7,235-5,849
Mississippian7,573-6,187
Chester7,832-6,446
Meramec Shale7,940-6,554
Ellenburger8,352-6,966

Ferguson42-197-31753

1.0 KM · Interstate Explorations LLC · Section with this well →

Canyon5,079
Conglomerates7,206
Barnett7,813
Meramec Shale7,880
Coleman Junction—
Cisco—
Holmes Sand—
Palo Pinto—

10 TOPS · FIRST 8

Baustert Unit42-197-31754

1.1 KM · Interstate Explorations LLC · Section with this well →

Canyon5,100
Conglomerates7,112
Barnett7,748
Meramec Shale7,904
Holmes Sand—
Palo Pinto—
Coleman Junction—
Cisco—

10 TOPS · FIRST 8

Pechacek42-197-30732

1.8 KM · Ferguson, S. M. Jr., Inc. · Section with this well →

Palo Pinto4,694-3,293
Conglomerates6,452-5,051
Holmes Sand7,790-6,389
Barnett7,815-6,414
Canyon—
Strawn—
Permian (undifferentiated)—
Meramec Shale—

10 TOPS · FIRST 8

Thompson42-197-31740

2.2 KM · Trio Consulting & Management,llc · Section with this well →

Coleman Junction1,960-540
Strawn2,670-1,250
Cisco2,670-1,250
Canyon2,750-1,330
Permian (undifferentiated)3,310-1,890
Palo Pinto4,540-3,120
Holmes Sand7,325-5,905
Conglomerates7,458-6,038

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