Disclaimer: in a long note like this there will be factual and typographical errors. If this is important to you go to the source.
There is nothing new to learn about the Bakken in this note; there is nothing new here. I was struck by the jump in production of #17271 and was interested in why that occurred.
**********************************
Background
This is pretty cool. Note the production profile of this well during this period of time, back in early 2015:
- 17271, 312, BR, Copper Draw 34-34H, t6/08, middle Bakken; cum 422K 11/17; original frack in June, 2008, open hole, 1 million lbs of sand; re-frack 7/13 - 11/22/2014; Bakken/Three Forks, 30 stage frack; slickwater, about 4 - 5 million lbs proppant,
BAKKEN | 1-2016 | 24 | 7295 | 7811 | 3526 | 15364 | 15305 | 0 |
BAKKEN | 12-2015 | 31 | 10429 | 10008 | 2174 | 21181 | 21104 | 0 |
BAKKEN | 11-2015 | 30 | 10063 | 10315 | 2030 | 17052 | 16978 | 0 |
BAKKEN | 10-2015 | 31 | 12087 | 12169 | 2417 | 23390 | 23313 | 0 |
BAKKEN | 9-2015 | 30 | 12493 | 12284 | 2501 | 13239 | 13164 | 0 |
BAKKEN | 8-2015 | 30 | 12423 | 12428 | 2383 | 13595 | 11742 | 1779 |
BAKKEN | 7-2015 | 31 | 13838 | 14072 | 2355 | 12443 | 9812 | 2554 |
BAKKEN | 6-2015 | 30 | 18548 | 18302 | 2686 | 14753 | 14678 | 0 |
BAKKEN | 5-2015 | 31 | 23387 | 23333 | 3389 | 18147 | 15488 | 2582 |
BAKKEN | 4-2015 | 30 | 19811 | 19790 | 3087 | 23925 | 16089 | 7762 |
BAKKEN | 3-2015 | 31 | 21210 | 21361 | 5133 | 9793 | 9716 | 0 |
BAKKEN | 2-2015 | 28 | 21007 | 21024 | 7106 | 10359 | 10289 | 0 |
BAKKEN | 1-2015 | 16 | 11840 | 11442 | 4779 | 40 | 0 | 0 |
BAKKEN | 12-2014 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
BAKKEN | 11-2014 | 3 | 5341 | 5341 | 4443 | 6819 | 449 | 6363 |
BAKKEN | 10-2014 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
BAKKEN | 9-2014 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
BAKKEN | 8-2014 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
BAKKEN | 7-2014 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
BAKKEN | 6-2014 | 2 | 282 | 855 | 18 | 435 | 430 | 0 |
BAKKEN | 5-2014 | 31 | 2936 | 2678 | 644 | 4080 | 4003 | 0 |
BAKKEN | 4-2014 | 8 | 1378 | 1239 | 182 | 864 | 769 | 76 |
The jump in production was due to a re-frack.
Looking at the graphic:
#23646 was fracked in early-to-mid 2013 so was not a factor. [However, #23646 might have showed a small bump in production in this same time period, but certainly not as significant:
- 23646, 2,325, BR, Copper Draw 24-22TFH 2SH, Johnson Corner, t7/13; cum 257K 11/17;
BAKKEN | 10-2015 | 31 | 4699 | 4761 | 1625 | 6616 | 6596 | 0 |
BAKKEN | 9-2015 | 30 | 5008 | 4935 | 1513 | 6149 | 5153 | 978 |
BAKKEN | 8-2015 | 31 | 5321 | 5142 | 1969 | 6933 | 1892 | 5021 |
BAKKEN | 7-2015 | 25 | 90 | 385 | 2024 | 6524 | 2752 | 3752 |
BAKKEN | 6-2015 | 30 | 6590 | 6569 | 2871 | 9620 | 235 | 9361 |
BAKKEN | 5-2015 | 30 | 7485 | 7472 | 3485 | 7996 | 4289 | 3683 |
BAKKEN | 4-2015 | 30 | 9277 | 9491 | 5383 | 10962 | 9432 | 1509 |
BAKKEN | 3-2015 | 13 | 6457 | 5976 | 2119 | 6704 | 0 | 6695 |
BAKKEN | 2-2015 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
BAKKEN | 1-2015 | 0 | 0 | 7 | 0 | 0 | 0 | 0 |
BAKKEN | 12-2014 | 1 | 23 | 17 | 1 | 13 | 0 | 11 |
BAKKEN | 11-2014 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
BAKKEN | 10-2014 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
BAKKEN | 9-2014 | 1 | 0 | 129 | 0 | 0 | 0 | 0 |
BAKKEN | 8-2014 | 8 | 2040 | 2082 | 206 | 1647 | 23 | 1624 |
BAKKEN | 7-2014 | 26 | 6501 | 6535 | 1134 | 7551 | 0 | 7551 |
BAKKEN | 6-2014 | 30 | 7475 | 7575 | 0 | 4330 | 64 |
But then we look at #28348. See production profile below. It was clearly fracked about that time frame under discussion. It had to have been fracked before 3/15. It turns out that #28348 was fracked 11/14 - 1/15.
- 28348, 1,920, BR, Copper Draw 41-27TFH, Johnson Corner, Three Forks, 35 stages, 4.1 million lbs, t3/15; cum 234K 11/17;
|
I initially thought #17271 jump in production was due to a neighboring well being fracked. But I was wrong. FracFocus showed that it had been fracked and sundry forms also confirmed it has been re-fracked.
Bottom line: not much to see here. Nothing new. Simply, it appears, an older well re-worked/re-fracked about the same time a neighboring well was fracked for the first time.
No big deal.
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.