WELL · 42-023-31817 · DISTRICT 9

Waggoner KWF #841KW

Plugged

Baylor County · Baylor County Regular field  · Vertical

Waggoner Kwf #841KW (API 42-023-31817) is a plugged well in Baylor County, plugged September 24, 2024, last operated by W.T. Waggoner Estate Inc..

The RRC has issued one drilling permit, issued September 5, 2024, permitted to 9,000 ft.

It was permitted by W.T. Waggoner Estate, Inc. and has since transferred to W.T. Waggoner Estate Inc. on the wellbore schedule.

Operator of record

W.T. Waggoner Estate Inc.

Permitted by W.T. Waggoner Estate, Inc.; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitW.T. Waggoner Estate, Inc.Sep 5, 2024

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

9,000
total depth, ft
1
permits on file
Sep 5, 2024
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
Sep 24, 2024

Surface location

33.694254, -99.339681

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Baylor 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
902438-99DrillW.T. Waggoner Estate, Inc.Sep 4, 2024Sep 5, 2024Sep 15, 20249,000

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 5 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 →

Waggoner Swea42-023-31780

6.2 KM · W.T. Waggoner Estate, Inc. · Section with this well →

Coleman Junction976219
Saddle Creek—
Palo Pinto—
Home Creek—
Strawn—
Cisco—
Thomas Sand—
Tannehill—

10 TOPS · FIRST 8

Waggoner Sweb42-023-31779

7.6 KM · W.T. Waggoner Estate, Inc. · Section with this well →

Coleman Junction1,17716
Saddle Creek1,801-608
Tannehill1,970-777
Thomas Sand—
Canyon—
Cisco—
Gunsight—
Home Creek—

10 TOPS · FIRST 8

Griffin42-023-31760

10.8 KM · LMH Energy · Section with this well →

Strawn5,083-3,782
Thomas Sand—
Tannehill—
Canyon—
Saddle Creek—
Palo Pinto—
Home Creek—
Gunsight—

10 TOPS · FIRST 8

Waggoner Kef42-023-31818

12.5 KM · W.T. Waggoner Estate, Inc. · Section with this well →

Dyson Lime1,975-787
Dyson Sand1,987-799
Breckenridge Lime2,052-864
Gunsight2,397-1,209
Milham Lime2,656-1,468
Castlebury Lime2,676-1,488
Canyon3,106-1,918
KMA4,426-3,238

10 TOPS · FIRST 8

Waggoner Swwb42-275-32379

15.1 KM · W.T. Waggoner Estate, Inc. · Section with this well →

Coleman Junction1,394-151
Dothan Lime1,662-419
Saddle Creek2,003-760
Dyson Lime2,385-1,142
Dyson Snad2,416-1,173
Dyson Sand2,416-1,173
Noble Lime3,078-1,835
Canyon3,445-2,202

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