WELL · 42-487-33210 · DISTRICT 9

Waggoner #5213

Plugged

Wilbarger County · Wilbarger County Regular field  · Vertical

Waggoner #5213 (API 42-487-33210) is a plugged well in Wilbarger County, plugged October 24, 2020, last operated by Dry Fork Production CO. LLC.

The RRC has issued one drilling permit, issued September 30, 2020, permitted to 2,050 ft.

It was permitted by Dry Fork Production CO., LLC and has since transferred to Dry Fork Production CO. LLC on the wellbore schedule.

Operator of record

Dry Fork Production Co. LLC

Permitted by Dry Fork Production Co., LLC; the EWA schedule now lists a different operator.

SOURCE · RRC EWA WELLBORE SCHEDULE

What each RRC source says

Wellbore schedulenone
Production reportsnone
Latest permitDry Fork Production Co., LLCSep 30, 2020

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

2,050
total depth, ft
1
permits on file
Sep 30, 2020
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 24, 2020

Surface location

34.027234, -99.075826

OpenStreetMap → ·  Google Maps →

Permit surface location from the RRC GIS record, in Wilbarger 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
865296-99DrillDry Fork Production Co., LLCSep 28, 2020Sep 30, 2020—2,050

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 →

Waggoner42-487-33163

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

Coleman Junction940253
Strawn—
Palo Pinto—
Milham Sand—
KMA—
King—
Dyson Sand—
Canyon—

10 TOPS · FIRST 8

Waggoner42-487-33142

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

Coleman Junction1,13053
King1,610-427
Strawn—
Palo Pinto—
Milham Sand—
Caddo—
Canyon—
Cisco—

10 TOPS · FIRST 8

Waggoner42-487-33209

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

Coleman Junction500693
Castlebury Lime1,713-520
Dyson Sand1,870-677
Palo Pinto—
Milham Sand—
KMA—
King—
Cisco—

10 TOPS · FIRST 8

Waggoner42-487-33164

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

Coleman Junction990202
King—
Caddo—
Canyon—
Cisco—
Dyson Sand—
KMA—
Milham Sand—

10 TOPS · FIRST 8

Waggoner-Epco42-487-33220

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

Canyon2,920-1,721
Caddo3,830-2,631
Strawn—
Milham Sand—
Palo Pinto—
Cisco—
Coleman Junction—
Dyson Sand—

10 TOPS · FIRST 8

Waggoner42-487-33089

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

Coleman Junction1,10094
Cisco1,738-544

Waggoner42-487-33274

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

Dyson Sand1,994-797
Gunsight2,306-1,109
Noble Lime2,434-1,237
Castlebury Lime2,611-1,414
Palo Pinto—
Canyon—
Cisco—
Coleman Junction—

10 TOPS · FIRST 8

Waggoner42-487-33263

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

Dyson Sand1,990-818
Breckenridge Lime2,069-897
Gunsight2,283-1,111
Noble Lime2,430-1,258
Milham Sand2,537-1,365
Canyon2,799-1,627
Palo Pinto—
Coleman Junction—

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