Showing posts with label Parent_Well_Uplift. Show all posts
Showing posts with label Parent_Well_Uplift. Show all posts

Saturday, October 12, 2019

Sorting Out A Mystery Of A BR Archer Well In Charlson Oil Field -- October 13, 2019

Disclaimer: in a long note like this there will be typographical and factual errors. There is at least one glaring error in an original source at the NDIC file report which I did not mention. I often see things that do not exist. I did not look at all wells in the immediate area of #26419. There may be other explanations for the huge jump in production in #26419. Regardless of the jump in production, the mom-and-pop mineral owners should be thrilled to see this huge jump in production (unless they hate paying more taxes to the IRS and the state of ND). It is very possible I made a very simple error/mistake that completely negates this entire post. I certainly could have mis-identified permit numbers, which I have done before. If so, that's fine; some reader will note it and bring it to my attention. I'm simply trying to better understand the Bakken. For all I know, it was simply a work-over rig or perhaps a small meteor strike.

Note: there's a similar mystery surrounding another Petro-Hunt in Charlson oil field, #26206. See this post.

The Original Post
Begun October 12, 2019
Completed October 13, 2019

Back on February 7, 2017, this post: "Possibly a record post-shut-in-production jump in the Bakken."

I was curious to see how these wells were doing two years later. Wow, what an adventure!

The well:
  • 26419, 2,904, BR, Archer 14-25TFH, Charlson, t2/14; cum 605K 8/19;
Note before going further:
  • this is one of several BR Archer wells
  • this BR Archer well was a Three Forks well drilled back in 2014; 
  • in five years, this well had produced over 600,000 bbls of oil
The first thing I noticed: the BR Archer wells were very, very good wells, but interestingly, some of the wells had been recently taken off line for a short period of time. That piqued my interest. I thought I was only going to be updating total production but immediately there was a puzzle. Why were these really good wells coming off line?

This was the biggest puzzle: the production profile of this well (#26419) did not make sense to me.

Look what happened to production between 3/18 and 9/18 (see portion of full production profile below). The huge jump in production meant that this well had to have been re-fracked.

But, neither FracFocus nor the NDIC file report showed any re-frack. Wow. I  had not seen this before. I had not seen such a huge jump in production in which there was not a re-frack. It just doesn't happen. Period. Dot.

Again, look at the jump in production -- an "old" well plateauing out to 5,000 bbls/month and then a huge jump in production -- as much as 26,000 bbls/month -- with no evidence of a re-frack. I had no idea what was going on. This did not make sense.

BAKKEN12-2018311878118778380219123190120
BAKKEN11-2018302115421181399122822227080
BAKKEN10-2018312579625830378130081299540
BAKKEN9-2018302385523388368627707275920
BAKKEN8-201812410638539605087499154
BAKKEN7-20180000000
BAKKEN6-20180000000
BAKKEN5-20180000000
BAKKEN4-2018002450000
BAKKEN3-20181827942749414502349530
BAKKEN2-20182845634463654310330230

That's a huge jump, from 3,000 in 3/18 (only 18 days) to 26,000 in 10/18. The only thing that could explain this was a re-frack and yet there was no re-frack.

So, we had this jump from 3,000 bbls/month to 26,000 bbls/month and no evidence of a re-frack.

Obviously there had to have been a neighboring well that had been re-fracked.

So, let's go to the map.

Wow, that turned out to be a bummer.

Note that there is no neighboring well to the well in question (#26419) -- yes, some relatively close wells but they were all the same age or older than the well in question and thus they could not have been related to that huge jump in production.

Nothing made sense.

I zoomed in on the map.


I expanded the area of the map.

 
Again, nothing jumped out at me, unless one looked at those #338XX wells to the north of the index well, #26419. If so, this is something I had never seen before (or don't recall seeing, or missed) and I Iook at literally every well that's been drilled in the Bakken since 2007.

I zoomed in on the #338XX wells. It turned out that #33817, a section line well, was closest to the index well. See map above.

I looked at the history of #33817.

Wow! Eureka! Paydirt!

#33817 was fracked just before the huge jump in production for #26419 in 10/18.

Wow. I had not seen this before. The "child" well did not parallel the "parent" well for the entire length of the horizontals. The "child" well and the "parent" well aligned for only half of the horizontal.

All wells under discussion are two-mile-long laterals, but the index well and the neighboring #338XX wells only exist side-by-side for half their lengths (I note this on the map below: a heavy red line where the wells parallel each other and a thinner red line where they do not). 


Interestingly enough, the frack for #33817 was a relatively moderate frack. Production profile and frack data for #33817 at this post.

Relationship between #33817 and the index well:
  • #33817 and #26419 are 0.11 mile (580 feet) apart (horizontally).  
  • but note this:
    • #33817 is a middle Bakken well;
    • #26419 is a Three Forks well;
The next 338XX series well to the west is #33814. Relationship of #33814 to the index well:
  • #33814 is a Three Forks well; awesome!
  • it is located 0.2 mile (1056 feet) to the west of the index well
  • it was a very, very small frack, only 5.1 million lbs of sand (51 stages)
  • production profile for this well is here;
Okay, so there you have it. Data points, facts, comments, opinions:
  • #26419 is a Three Forks, first bench well, based on the name of the well, the permit and the Weatherford geological well report;
  • the well was completed in February, 2014; was a great well and then showed the typical Bakken decline, plateauing at a very respectable 5,000 bbls/month by 8/17
  • in early 2018, it was taken off line for five months
  • when it came back on line, production jumped from 5,000 bbls/month to an astounding 26,000 bbls/month, minimally better than the original frack, but the anticipated decline occurred more quickly; but it maintained high production for several months; full production profile is posted elsewhere (see link above)
  • the huge jump in production all but suggested this well had been fracked
  • neither FracFocus nor the file report showed any data to suggest the well had been refracked
    • it's been more than a year; the paperwork is "not in the mail"
  • at first glance there were no obvious neighboring, recently-fracked wells that could account for the huge jump in production
  • far to the north, and paralleling only half of the #26419 horizontal were #338XX series wells on a single pad that might have played a part
  • the geographic location and timing of the fracks of the #338XX series wells would account for the jump in production of #26419
  • #26419 is a Three Forks (that in itself is unusual, so early in the Bakken, to see a Three Forks well)
  • closest to this Three Forks well was a middle Bakken well (#33817) -- about 500 feet west
  • then, 1,000 feet to the west was another Three Forks well
  • fracks for both the #33817 and the #33814 were moderate and small fracks, respectively
  • I have not seen moderate and small fracks result in a neighboring well to have such a huge jump in production as we see in #26419
  • there is a third #338XX well on that pad fracked at the same time as the others (actually there are four)
  • there is a research paper out there, which I have linked elsewhere, published very early in the Bakken boom that suggested that the "parent-child uplift" phenomenon existed but it required three neighboring wells to be fracked simultaneously to affect a "parent" well 
  • it's hard to believe that a small frack in the same formation one thousand feet away caused a huge production jump in #26419
  • if not, then it was a middle Bakken well only 500 feet away that was also additive
One more thing:
  • the index well, #26419, an Archer well, is a BR-operated well (Burlington Resources/COP)
  • the #338XX pad to the west is a Petro-Hunt pad
  • think about that, especially from BR's viewpoint
And:
  • these wells are in the Charlson oil field; that field is tracked here;
  • the Charlson oil field is one of the most interesting fields in the Bakken
  • it was "discovered" very early (see this post); it was this field that excited me as much as the Parshall oil field at the time;
  • the webmaster for a Bakken discussion group and another blogger first noted what an incredible field this was going to be
  • the Charlson is among the handful of early Bakken fields that stood out: Charlson, Parshall, Grail, Sanish
  • at one time, the Charlson had bragging rights to the most successful in the Bakken; I think that still holds true but do not quote me on that
  • since then there have been more record-setting wells in the Bakken
  • for how prolific this field seems to be, it is being drilled out very, very slowly, at least compared to a couple of other fields held by other operators
Disclaimer: in a long note like this there will be typographical and factual errors. There is at least one glaring error in an original source at the NDIC file report which I did not mention. I often see things that do not exist. I did not look at all wells in the immediate area of #26419. There may be other explanations for the huge jump in production. Regardless of the jump in production, the mom-and-pop mineral owners should be thrilled to see this huge jump in production (unless they hate paying more taxes to the IRS and the state of ND). It is very possible I made a very simple error/mistake that completely negates this entire post. I certainly could have mis-identified permit numbers, which I have done before. If so, that's fine; some reader will note it and bring it to my attention. I'm simply trying to better understand the Bakken. For all I know, it was simply a work-over rig or perhaps a small meteor strike.


Friday, October 11, 2019

Parent / Child Wells -- Random Note -- October 11, 2019

Well, look at this.

Regular readers of the blog know that I am inappropriately excited about the "halo" effect -- that jump in production seen in Bakken wells when they are brought back on line after being off line for a few weeks or a few months while neighboring wells are fracked. In some cases (rarely) the "parent" well is off-line for less than a month.

I tag posts discussing this phenomenon as "halo" or "jump in production." I noted the phenomenon almost a decade ago but had not seen validation from a credible source.

[The very first post that was tagged with the halo effect was dated August 19, 2010. Link here: http://themilliondollarway.blogspot.com/2010/08/another-first-for-north-dakota_19.html.]

I did receive a phone call from an analyst at the largest fracking company in the Bakken at that time about six years ago asking me about my observations. The analyst said his company was referring to these as "parent/child" wells. I did not post the specifics of that phone call at that time assuming that some of the information I had been told was proprietary.

[I was in Belmont, MA, when I received the phone call. I was last in Belmont, MA, in 2013: that's why I know that the phone call was at least six years ago.]

I continue to look for validation from credible sources. About a month ago, maybe two or three months ago, I started getting hints of validation from Whiting. I think I have posted some of that, but I can't recall for sure.

Break, break.

It's my observation that the parent / child interaction in the Bakken is "positive." Either there is no effect, a subtle effect, or a huge positive effect, but I have not seen any suggestion that the parent / child interaction is "bad news" in the Bakken.

On the other hand, however, there have been numerous stories in the popular press that this is not the case in other shale plays. There are concerns, particularly in the Permian, that new wells (or "children" wells) are having an adverse effect on older wells ("parent" wells).

Break, break.

Tonight, in the process of looking for something else, I ran across this slide in a recent Whiting presentation.

The link: https://event.webcasts.com/viewer/event.jsp?ei=1260399&tp_key=d761d52d8c.

Slide #9.

Screenshot:


Note: "Parent / child well activity [in the Bakken] is positive vs experience in other shale plays."

By the way, that one slide above has many, many other interesting data points. 

Wednesday, October 9, 2019

Random Look At Another Well With Jump In Production -- October 9, 2019

I'm ready to head to bed; it's 11:29 p.m. CT. I've just finished another episode of "Perry Mason" over at Amazon Prime.

But I want to see how long it takes to find another interesting story from the Bakken.

One year ago, "new wells reporting, 4Q18."

Wow, in half a minute, half a dozen wells I could have reported.

I'll post this one:
  • 32843, 45 (no typo), BR, Remington 4B MBH, Blue Buttes, t11/18; cum 220K 8/19; a huge well despite the IP (which is typical for BR):
PoolDateDaysBBLS OilRunsBBLS WaterMCF ProdMCF SoldVent/Flare
BAKKEN8-2019311704217145640440296349075249
BAKKEN7-2019312370323721803635149281826854
BAKKEN6-2019302764727558781736783332053462
BAKKEN5-2019313287733048975545178411463923
BAKKEN4-2019302813027979681635144319943063
BAKKEN3-2019312870228760753938842351403601
BAKKEN2-2019282253722640554328052279850
BAKKEN1-2019292343223231610325750163959343
BAKKEN12-2018311601415824302517975141433816
BAKKEN11-2018238138170501516765750

Tested 11/18.

220K by 8/19, less than a full year later.

Note the IP.

Neighboring well, #17118, Remington 14-11H, remains off line (8/19).

Note: it was tested 11/18.

Another neighboring well:

  • 23250, 2,806, BR, Lovaas 11-1MBH, Blue Buttes, t1212; cum 418K 8/19; prodution period of interest:

BAKKEN5-201931134521360019521771217096539
BAKKEN4-2019281474914402354847635694124
BAKKEN3-2019291177011626351542019863143
BAKKEN2-20192814113142953877605522633722
BAKKEN1-201931254142531770561055085991874
BAKKEN12-2018181426013561354716829167840
BAKKEN11-2018100030300
BAKKEN10-2018001900000
BAKKEN9-20181822382309428349734520

This well comes off the confidential list at the very same time a neighboring well is fracked.

After this well comes back on line its production jumps from 4,000 bbls/month (8/18) to an astounding 25,000 bbls/month (1/19). 

The Bakken never ceases to amaze me. It is now 11:39 p.m.

It took ten minutes to find this well and post it. 

Zavanna Completing Its George Wells in Stockyard Creek; Jump In Production Noted -- October 9, 2019

Updates

March 17, 2021: a Zavanna George well has just gone over 500K bbls crude oil. See this post.  

The Zavanna George pad:



The wells:

  • 22044, 700, Zavanna, George 19-20 1H, t10/12; cum 517K 1/20;
  • 35170, 306, Zavanna, George 19-25 2HXW, t4/19; cum 184K 1/20;
  • 29800, 301, Zavanna, George 19-30 3TFHXW, t4/19; cum 184K 1/20;
  • 29799, 301, Zavanna, George 19-30 4H, t4/19; cum 203K 1/20;
  • 35171, drl, Zavanna, George 19-30 5TFH, first production, t--; cum --;
  • 35172, 556, Zavanna, George 19-30 6H, t4/19; cum 217K 1/20;
  • 35173, 33 (no typo), Zavanna, George 19-30 7TFH, t4/19; cum 123K 1/21;

Original Pad 

These two wells (#29799, #29800) were permitted back on October 23, 2014:

  • 29799,  218, Zavanna, George 19-30 4H, Stockyard Creek, t4/19; cum 105K 8/19;
PoolDateDaysBBLS OilRunsBBLS WaterMCF ProdMCF SoldVent/Flare
BAKKEN8-20193120174191612747941121356984961
BAKKEN7-2019311859117016248982565724729466
BAKKEN6-20193029327271403652939205346604098
BAKKEN5-20192736681348854469548523481210
BAKKEN4-2019841221949565324130
  • 29800, 301, Zavanna, George 19-30 3TFHXW, Stockyard Creek, t4/19; cum 56K 8/19;
PoolDateDaysBBLS OilRunsBBLS WaterMCF ProdMCF SoldVent/Flare
BAKKEN8-20193156265344174841802287608800
BAKKEN7-20193191358361217661708316277344
BAKKEN6-20193021158195803811531619220549118
BAKKEN5-20191718314174173084025119248660
BAKKEN4-20195157983998157386630

This was was permitted even farther back, December 12, 2011:
  • 22044, 700, Zavanna, George 19-30 1H, Stockyard Creek, t10/12; cum 404K 8/19; no evidence this well was re-fracked: a) production jump did not exceed newly fracked offset wells; b) FracFocus: only frack was in 2012; c) no sundry form at NDIC to suggest a re-frack;
PoolDateDaysBBLS OilRunsBBLS WaterMCF ProdMCF SoldVent/Flare
BAKKEN8-20193113117124582314629601138442627
BAKKEN7-2019311049396042718419742117881416
BAKKEN6-2019306884637134181845063181685
BAKKEN5-20190000477450
BAKKEN4-201981638744411421736
BAKKEN3-20190000000
BAKKEN2-20190000000
BAKKEN1-20190000000
BAKKEN12-20180000000
BAKKEN11-20180000000
BAKKEN10-20180000000
BAKKEN9-20180000000
BAKKEN8-20180000000
BAKKEN7-20180000391239120
BAKKEN6-20182518922107158020411481187
BAKKEN5-2018313352320822834409391235

Permitted more recently:
  • 35170, 306, Zavanna, George 19-25 2HXW, Avoca, t4/19; cum 106K 8/19;
PoolDateDaysBBLS OilRunsBBLS WaterMCF ProdMCF SoldVent/Flare
BAKKEN8-20193119101181412445633433256877284
BAKKEN7-2019312308921133354623081929720637
BAKKEN6-20193028160260604290537026288327747
BAKKEN5-20192933908322485246641841418260
BAKKEN4-201961900101089827185990

Additional George wells are yet to be reported.

Monday, September 23, 2019

CLR Has Completed Angus Federal 6-16H2; Older Well Back On Status; Small Jump In Production

A neighboring well has just been completed and is producing:
  • 33965, SI/NC, CLR, Angus Federal 6-16H2, Elm Creek, 26,729 feet; producing as of 5/19; three Forks, second bench; t5/19; cum 568K 1/24;
The well:
  • 20804, 329, CLR, Angus 1-9H, 30 stages; 2.7 million lbs, t2/13; cum 310K 7/19; offline as of 12/18; still offline 4/19; back on line as of 5/19; a middle Bakken well; cum 401K 1/24;
Recent production; small jump in production:
PoolDateDaysBBLS OilRunsBBLS WaterMCF ProdMCF SoldVent/Flare
BAKKEN7-201931448241663802687236052877
BAKKEN6-201927353638403573555321153149
BAKKEN5-20199131580664072962628
BAKKEN4-20190000000
BAKKEN3-20190000000
BAKKEN2-20190000000
BAKKEN1-20191018722000
BAKKEN12-201825162516875484847443775
BAKKEN11-2018301952205466643603428538

Friday, September 20, 2019

This Is Absolutely, Positively, Not Happening InThe Bakken -- September 20, 2019

The note below is pretty much complete; there may be some fine tweaking but consider it done.

**************************
Off The Radar Scope: Rigs Do Matter 

This is interesting. I had not thought of this. Because there is so little national news regarding the Bakken and because the Permian is getting all the press, a lot of folks outside the region mistakenly think the Bakken has completely slowed down. An operator looking for capital among investors (east coast, west coast) were surprised to hear that the Bakken was still very, very active. Potential investors were surprised to hear that North Dakota was producing as much oil with 50 - 60 rigs as the state was producing (actually more) than when there were 200 rigs in the Bakken (lousy grammar on my part).

So: the number of rigs does matter when it comes to "demonstrating" activity (and perhaps investor interest). That driller, by the way, suggests that North Dakota would likely produce upwards of 2 million bopd in about three years. If the takeaway capacity was sufficient and the price "right," I think we could be at 2 million bopd now.

In addition, see first comment:
Regarding the linked articles below: Basic concept, not news. Poorly explained (some mistakes).

Also, despite the shift to closer spacing [in the Bakken?], we are still not seeing a dropoff in performance. Obviously there must be other aspects that are improving and the net result is okay, on average.
***********************************
The Note

The world's top oil basin is running out of space -- link here.
Permian "child" wells may cut oil recovery up to 20%, bank says -- Bloomberg.

I'm in a rush right now so I will have to come back to this, but this is so not happening in the Bakken.

First of all, it's an old story regarding the Permian, previously posted on the blog, but both Bloomberg and oilprice make it sound like something new.

From the linked articles:


But whatever. It's not happening in the Bakken.

I don't have the statistical analysis, but I have the anecdotal evidence to make that statement. But Whiting does. Exhibit A:


I don't know the Permian at all. I follow it a little bit and have noted a few things. Most important(ly): it appears unconventional / shale basins are not all alike.

I am inappropriately exuberant about the Bakken, so everything that follows, take with a grain of salt. This is my worldview of the Bakken vs other shale plays, particularly the Eagle Ford and the Permian.

First, I think the Bakken is still going to be the best of the three plays (Bakken, Permian, Eagle Ford) in these categories:
  • effect the Bakken will have on the state economy compared to that of the Permian/Eagle Ford and the Texas economy
  • the amount of money that will be returned to mom-and-pop mineral owners in North Dakota on a per capita basis compared to those in Texas
  • crude oil production per well
Now, with regard to the linked articles above, that "child" wells are a challenge in the Permian. It appears to be quite the opposite in the North Dakota Bakken (I can't speak to the Bakken in Montana and/or Saskatchewan).

It certainly appears the operators have figured out the "Goldilocks" density, although even that will change / improve over time.

It appears that in Tier 1, middle Bakken, six wells in 1280-acre spacing will be the norm.

It appears that in Tier 1, first bench Three Forks, six wells in 1280-acre spacing will also be the norm.

All other tiers and all other Bakken formations, the jury is still out.

To see examples of well density in the Bakken, click on the follow tags:
Years ago I noticed the positive impact that "child" wells had on their parents and on their sibs. I have blogged about that often. An analyst / research student working for Halliburton telephoned me years ago to discuss this with me (he called me; I didn't call him).

I devoted an entire site to these "wells of interest." At the index to that site, one can see all the examples of the positive impact of "child" wells. I think at one time they were called "daughter" wells, but I don't recall for sure. The list of wells has gotten so long, I've pretty much quit doing that. Whether I've "proved" the point or not to others bothers me not at all. I believe what I see.

The Bakken is a bit easier about which to generalize. For the most part, when we talking about the Bakken now (2014 - 2018) we are talking about one formation, about 20 to 40 feet thick, pretty much being fracked about the same by all operators.

I have no clue about the Permian but it's my understanding the unconventional target formations in the Permian are many and they are thick. So, when I see a Bloomberg article with so much generalization it makes me wonder. If I were following the Permian or interested in the Permian I would want to know a lot more specifics.

They used to talk about the Bakken development being like a baseball game and early on we were only in the first inning. No one makes that analogy any more but I would guess we might be in the third inning.

The Permian? Easily the first inning, maybe the bottom of the first inning. But that's it. Based on what little I know about the Permian it sounds like there is a lot to learn. My hunch is that the operators have gone after the absolutely easiest stuff to lift.

Oh, a random note: in the Bloomberg article they talked about "dry" wells in the Permian. That's interesting. Hitting a dry well in the Permian has to be concerning. There are no "dry" wells in the Bakken. We've talked about that before. Yes, some wells are reported as "dry" but that's because of a failure of the well itself, usually a failure in the cementing / casing process. But if the well is completed in the Bakken it will strike oil.

It may not be an "economic" well but we've discussed that also. But it won't be dry.

I have yet to see more than a handful of recent middle Bakken wells abandoned due to low oil production.

Thursday, August 29, 2019

Halo Effect -- Bakken Style -- August 29, 2018

Reporting today:
  • 34789, 3,051, WPX, Sweet Grass Woman 22-15HD, Spotted Horn, t7/19; cum --; (#22629 -- still too early to tell, #29445 -- huge jump in production, #34646)
Four Sweet Grass Woman wells fracked; completed; reporting.

A neighboring well:
PoolDateDaysBBLS OilRunsBBLS WaterMCF ProdMCF SoldVent/Flare
BAKKEN6-2019301081610596884015031134060
BAKKEN5-201931120161202895131624613778700
BAKKEN4-2019301284812942103081737114603926
BAKKEN3-20193114060139951180519009145712452
BAKKEN2-20192811256113211126515219117221862
BAKKEN1-20192391329036108811234738157125
BAKKEN12-20183118159181872944524550658615551
BAKKEN11-2018417981727224524311206726
BAKKEN10-201817304530892000411618861513
BAKKEN9-20181320092039116327171562604
BAKKEN8-201831500049392380676039841789
BAKKEN7-201831539354412053729245051738

Sunday, August 18, 2019

Follow-Up On A Nice WPX Wolf Well In Squaw Creek -- August 18, 2019

The well:
  • 19973, 141, WPX, Wolf 27-34H, Squaw Creek, t7/11; cum 265K 2/18; -- that was back on 2/18 -- cum of 265K; now, cum 346K 6/19;
Production back in 2018 when neighboring wells were fracked:
BAKKEN4-2018307989809146281387699252315
BAKKEN3-2018311026910546613717838126993417
BAKKEN2-201810266725611441463311643001
BAKKEN1-20181137243658185564806075352
BAKKEN12-2017316820660164171184852545231
BAKKEN11-2017306405644274521112457474080
BAKKEN10-2017318714870891571513679975574
BAKKEN9-20173085048631138021477176965553
BAKKEN8-2017203026290110314525627361948
BAKKEN7-20171201404
BAKKEN6-20172089195841715481013121
BAKKEN5-2017311376130763923891467151
BAKKEN4-2017301341133170823281350223

This page won't be updated. The Wolf / Rachel Wolf wells are tracked here.