TEXAS · WELLS · WILBARGER COUNTY · API 42-487-33141 · DISTRICT 7C
Waggoner Beaver Creek B #B 15
Wilbarger County · Wilbarger County (Special) field · Vertical
Waggoner Beaver Creek B #B 15 (API 42-487-33141) is a plugged well in Wilbarger County, plugged October 9, 2017, last operated by W.T. Waggoner Estate Inc..
The RRC has issued one drilling permit, issued September 22, 2017, permitted to 2,100 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 schedule | none |
| Production reports | none |
| Latest permit | W.T. Waggoner Estate, Inc.Sep 22, 2017 |
The sources disagree, which usually means a transfer or a lease-level production filing by a different entity. Petrora goes with the schedule.
- 2,100
- total depth, ft
- 1
- permits on file
- Sep 22, 2017
- 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, 2017
Surface location
34.013461, -99.070762 NAD27, as filed
34.013552, -99.071113 WGS84
Permit surface location from the RRC GIS record, referenced to NAD27 as the RRC files it; the WGS84 pair is the same point through NOAA's NADCON grid, and the map link uses it, in Wilbarger County.
Wells nearby
Every well with a location on file around this one, in any state, nearest first.
Loading the wells nearby…
Texas locations come from drilling permits, so most older Texas wells have none and are not listed.
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
| Permit | Type | Operator | Received | Issued | Spud | Depth |
|---|---|---|---|---|---|---|
| 830946-99 | Drill | W.T. Waggoner Estate, Inc. | Sep 14, 2017 | Sep 22, 2017 | Sep 26, 2017 | 2,100 |
Well logs
1 log loaded from the RRC's log index, the latest received Feb 14, 2018. Resistivity. These are the logs loaded into Petrora from the Railroad Commission's inventories, not necessarily every log run on the well. The RRC holds the files; each opens from its log search for the well. The kind is the RRC's description of the log; the interval is the one filed for it.
Open the RRC's log search for this well ↗| Logas described | Files | Intervalft, as filed | Datereceived | SizeMB |
|---|---|---|---|---|
| RESISTIVITY | TIFF | 85 to 2,073 | Feb 14, 2018run Oct 4, 2017 | 2.60 |
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.
- Wellbore filings for 42-487-33141 → W-2, G-1, plugging reports, as PDFs
- Completion packets for 42-487-33141 → scanned completion filings
The logs loaded for this well are under Well logs, with the RRC's log search for it.
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 neighbors can.
Section of the neighbors →Waggoner42-487-33263
0.7 KM · Dry Fork Production Co., LLC · Section with this well →
| Dyson Sand | 1,990 | -818 |
| Breckenridge Lime | 2,069 | -897 |
| Gunsight | 2,283 | -1,111 |
| Noble Lime | 2,430 | -1,258 |
| Milham Sand | 2,537 | -1,365 |
| Canyon | 2,799 | -1,627 |
| Coleman Junction | — | |
| King | — |
10 TOPS · FIRST 8
Waggoner Bda42-487-33402
1.0 KM · W.T. Waggoner Estate, Inc. · Section with this well →
| Dyson Lime | 1,965 | -800 |
| Dyson Sand | 1,971 | -806 |
| Megargel Lime | 2,153 | -988 |
| Noble Lime | 2,421 | -1,256 |
| Milham Sand | 2,528 | -1,363 |
| Canyon | 2,786 | -1,621 |
| King | — | |
| Palo Pinto | — |
10 TOPS · FIRST 8
Waggoner42-487-33163
1.7 KM · Dry Fork Production Co., LLC · Section with this well →
| Coleman Junction | 940 | 253 |
| Canyon | — | |
| Caddo | — | |
| Dyson Sand | — | |
| King | — | |
| KMA | — | |
| Milham Sand | — | |
| Palo Pinto | — |
10 TOPS · FIRST 8
Waggoner42-487-33142
1.8 KM · Trio Consulting & Management,llc · Section with this well →
| Coleman Junction | 1,130 | 53 |
| King | 1,610 | -427 |
| Milham Sand | — | |
| Canyon | — | |
| Strawn | — | |
| Palo Pinto | — | |
| Caddo | — | |
| Cisco | — |
10 TOPS · FIRST 8
Waggoner42-487-33209
1.8 KM · Dry Fork Production Co., LLC · Section with this well →
| Coleman Junction | 500 | 693 |
| Castlebury Lime | 1,713 | -520 |
| Dyson Sand | 1,870 | -677 |
| Canyon | — | |
| Cisco | — | |
| King | — | |
| KMA | — | |
| Milham Sand | — |
10 TOPS · FIRST 8
Waggoner BDB42-487-33403
1.9 KM · W.T. Waggoner Estate, Inc. · Section with this well →
| Dyson Lime | 1,936 | -772 |
| Megargel Lime | 2,128 | -964 |
| Milham Sand | 2,471 | -1,307 |
| Castlebury Lime | 2,567 | -1,403 |
| Canyon | 2,768 | -1,604 |
| Palo Pinto | — | |
| King | — | |
| Dyson Sand | — |
10 TOPS · FIRST 8
Waggoner42-487-33164
1.9 KM · Dry Fork Production Co., LLC · Section with this well →
| Coleman Junction | 990 | 202 |
| Dyson Sand | — | |
| Strawn | — | |
| Palo Pinto | — | |
| Milham Sand | — | |
| KMA | — | |
| King | — | |
| Cisco | — |
10 TOPS · FIRST 8
Waggoner42-487-33274
2.0 KM · Dry Fork Production Co., LLC · Section with this well →
| Dyson Sand | 1,994 | -797 |
| Gunsight | 2,306 | -1,109 |
| Noble Lime | 2,434 | -1,237 |
| Castlebury Lime | 2,611 | -1,414 |
| King | — | |
| Milham Sand | — | |
| 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/48733141, documented in the API reference.