Sunday, February 26, 2017

Idle Rambling Comparing Two Wells That Were Not All That Great Early On -- Then Their Production Diverged -- February 26, 2017

This is going to be a long note. It is likely to be confusing. It may not be worth the effort. In a long note, there will be factual and typographical errors. If this is important to you, go to the source.

These are two QEP wells very, very close to each other and drilled about the same time. They both had similar births. One died early; one is still alive.

The first QEP well; it may have been killed prematurely; it was never all that good to begin with; its production was about 1,000 bbls of oil/month when it was killed (PA). Monthly production data shortly before it was killed:

Monthly Production Data for well #1:

PoolDateDaysBBLS OilRunsBBLS WaterMCF ProdMCF SoldVent/Flare
BAKKEN10-20130000000
BAKKEN9-20130000000
BAKKEN8-20130000000
BAKKEN7-20130000000
BAKKEN6-20130000000
BAKKEN5-20130000000
BAKKEN4-20130000000
BAKKEN3-20130000000
BAKKEN2-20130000000
BAKKEN1-20130000000
BAKKEN12-201231000000
BAKKEN11-20120000000
BAKKEN10-20120000000
BAKKEN9-2012002140000
BAKKEN8-20120000000
BAKKEN7-20122580035035
BAKKEN6-20120000000
BAKKEN5-20123011471180187134313430
BAKKEN4-20123012211194180121512150
BAKKEN3-20123112651673167136313630
BAKKEN2-2012291159929110106610660
BAKKEN1-20123112901456145115111510
BAKKEN12-20113112901208150128212820

Notice: that well was killed in May, 2012.

The second well was drilled/completed/tested at almost the very same time, in early 2008.

This is well #2. This was its production between December, 2011, and May, 2012, to compare with the well above:
BAKKEN5-2012319409522577917910
BAKKEN4-20123092811542273673670
BAKKEN3-201231936695237127912790
BAKKEN2-20122910011177257132013200
BAKKEN1-20122912101196287155315530
BAKKEN12-2011319097021606806800

That well, well #2, was no better, producing about 1,000 bbls of crude oil / month.

But it was allowed to live.

Look at the production since October, 2015, and to the present. Going from around 1,000 bbls of crude oil / month, it jumped to over 8,000 bbls (extrapolated to full 31 days) in October, 2015:
PoolDateDaysBBLS OilRunsBBLS WaterMCF ProdMCF SoldVent/Flare
BAKKEN12-2016301475158014953278291796
BAKKEN11-201628159311701615410841080
BAKKEN10-2016231227113713582859274996
BAKKEN9-201630200320811965610861062
BAKKEN8-201631256129782413683368321
BAKKEN7-201614100168912781266125115
BAKKEN6-2016302596270321504183415825
BAKKEN5-2016313080320022223691351864
BAKKEN4-201630340233872554480844392
BAKKEN3-20169124811331141129912310
BAKKEN2-20169716658137780865954
BAKKEN1-20162846374567562558805459112
BAKKEN12-20150000000
BAKKEN11-20151933833435160744123924121
BAKKEN10-2015277947818737181080810445311

I do not know why well #1 was killed and why well #2 was allowed to live. That's unimportant now.

The question is whether well #1 could have come back as strong as #2 came back after it, too, looked like it was never going to do all that well.

The wells:
  • #1, killed: 16959, 971, QEP, Jones 16-14H, Blue Buttes, t6/08; cum 102K 5/12;
  • #2, kept alive: 16960, 768, QEP, Jones 4-23H, Blue Buttes, t4/08; cum 156K 12/16;
  • #3, in the graphic but not discussed in this post: 17266, 912, QEP, Jones 4-24H, Spotted horn, t1/09; cum 186K 12/16;
The graphic:


4 comments:

  1. Bruce, where do you get these graphics showing the well paths?

    ReplyDelete
    Replies
    1. The NDIC website (which, by the way, has the best site I've seen among the various states that have an oil and gas industry):

      https://www.dmr.nd.gov/OaGIMS/viewer.htm

      In addition, I wrote this up a long time ago; don't know how good it is any more:

      http://themilliondollarway.blogspot.com/2010/02/ndic-gis-map-server-hints-and-tips.html

      Delete
  2. Bruce, never mind..I found the maps. Love your blog

    ReplyDelete
  3. Thank you for your kind words. I wrote this up a long time ago to help with the map; not sure how much it will help:

    http://themilliondollarway.blogspot.com/2010/02/ndic-gis-map-server-hints-and-tips.html

    ReplyDelete