Monday, February 26, 2018

Random Look At Well Demonstrating An Unusual Bakken Phenomenon -- February 26, 2018

Five Petro-Hunt wells have been recently fracked; see graphic below. This is the "USA" well that came off the confidential list today:
  • 28464, 1,630, Petro-Hunt, USA 153-96-24C-13-5H, Keene, Bakken/Three Forks, t10/17; cum 45K 12/17; (#18356)

When these Petro-Hunt wells (DUCs) came off the confidential list, I was curious how an older well would do. This well was fracked back in 2010. I am hoping that someone can tell me this well was recently re-fracked. There is no sundry form in the well file suggesting it was re-fracked; and FracFocus has no data suggesting it was re-fraced:
  • 18356, 1,029, Petro-Hunt, USA 153-96-24D-13-1H, API - 33-053-03060, Keene, Bakken/Three Forks, t8/10; cum 323K 12/17, recent production:
PoolDateDaysBBLS OilRunsBBLS WaterMCF ProdMCF SoldVent/Flare
BAKKEN/THREE FORKS12-201731218102175713683520934850143
BAKKEN/THREE FORKS11-201730217392177511723307032511350
BAKKEN/THREE FORKS10-201710768775371295822308216
BAKKEN/THREE FORKS9-2017122370000
BAKKEN/THREE FORKS8-20172514411566503386103687
BAKKEN/THREE FORKS7-20172818231555740389303702
BAKKEN/THREE FORKS6-20173012481154612304202840
BAKKEN/THREE FORKS5-20173114921516532335703141
BAKKEN/THREE FORKS4-20173014761429522307402865

The production data after this well was originally fracked, back in 2010:

BAKKEN/THREE FORKS1-2011318862889996911598113810
BAKKEN/THREE FORKS12-201031972796909851322812784227
BAKKEN/THREE FORKS11-201030896589958451173197411780
BAKKEN/THREE FORKS10-20103110838109459161447255788677
BAKKEN/THREE FORKS9-2010309682961872115395264712538
BAKKEN/THREE FORKS8-2010281285512405327815402015185
BAKKEN/THREE FORKS7-20100000000


Again, there is no evidence that this well was re-fracked but the recent production data suggests that it was. It should be noted that the Charlson field is a particularly good field with some incredibly good wells, suggesting extensive natural fracturing.

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.