Bourbon County Coffee 2015 - Gusher?

Discussion in 'Beer Talk' started by siege06nd, Dec 5, 2015.

Thread Status:
Not open for further replies.
  1. PA-Michigander

    PA-Michigander Grand Pooh-Bah (3,372) Nov 10, 2013 Pennsylvania
    Pooh-Bah Trader

    Or next year's King Henry?!?!?!
     
    FarmerTed and siege06nd like this.
  2. lester619

    lester619 Initiate (0) Apr 17, 2009 Wisconsin

    I haven't read this whole thing, is there some talk about refunds at least? I know I would want my money back. That definitely sucks, but Cheers anyway!
     
    Adrena1ine likes this.
  3. siege06nd

    siege06nd Pooh-Bah (2,027) Dec 29, 2009 Virginia
    Pooh-Bah

    I'm starting to wonder if these all aren't infected. Not to do the reverse of "it's not infection, it's just the coffee flavor" argument to those who are saying theirs taste fine, but I think refrigeration could be the hero here staving off the off flavors from taking hold.

    Like I said, I had one within a few days of purchase straight out of the cellar (wasn't fridged) and while it gushed, it tasted solid. Had another one that had been fridged that tasted ok too about three weeks later and it didnt gush. This last one was from the cellar and gushed and tasted pretty bad.

    Storage and serving temp seems to have an effect. But is it possible all of these bottles are infected, some have just been slowed and it's not showing as much yet?
     
  4. M_D_S

    M_D_S Aspirant (205) Jun 19, 2015 Delaware

    Typically non-returnable bottles are just rinsed. The risk of picking up something from them, assuming they've been stored correctly (i.e dry, away from things like malt dust), is extremely low. They don't exactly present a hospitable environment for things that will spoil beer. They're dry and they have no food source. More likely is a dirty filler or organisms brought in from earlier in the process.
     
    Fat_Maul and drtth like this.
  5. pagriley

    pagriley Pooh-Bah (2,382) Oct 27, 2014 Illinois
    Pooh-Bah Trader

    Just guessing here, but I assume Goose has a bottling machine that has many nozzles so it fills multiple bottles at once? That would certainly explain the randomness of having some bottles with the same time stamp as fine vs infected...
     
    FarmerTed likes this.
  6. M_D_S

    M_D_S Aspirant (205) Jun 19, 2015 Delaware

    That can. Also, if the microbiological loading is low and/or variable, you can have some level of bugs in every bottle. Some may spoil sooner, others may spoil later. It becomes a matter of building up a population of organisms large enough to create sufficient byproducts to be detectable to the drinker. Some may bloom rather quickly and be immediately noticeable. Some may take time. Some may crap out and do nothing.
     
    Fat_Maul, drtth and pagriley like this.
  7. AndyEdgar

    AndyEdgar Initiate (0) Feb 2, 2014 Illinois

    17/ sep 1226 no issues. Bought at binny's south loop on christmas eve
     
  8. wcu80

    wcu80 Pundit (967) Feb 2, 2005 Georgia
    Trader

    Add me to the list. Saw this thread a couple days ago and didn't really think much about it. My curiosity got the best of me and I cracked a bottle tonight that was undrinkable. Cracked another and it was nearly as bad. Bummer but the epitome of a 1st world problem.
     
    PsilohsaiBiN and siege06nd like this.
  9. croush

    croush Pooh-Bah (2,407) Mar 20, 2015 Illinois
    Pooh-Bah Trader

    Maybe FW sent that tweet out to help ease the minds of some of their customers that may just be worried about infection in general. I obviously have no idea what they were thinking (and I'm assuming nobody on here does either), but perhaps with the climate of one of the most sought after BA beers on the market having issues, they want to make sure there is some clarity that they are doing their due diligence (and I'm not implying that GI didn't do theirs).

    Back to this thread, I think I'm going to pop one of my bottles open by this weekend, regardless of whether GI gives a response or not.
     
    siege06nd likes this.
  10. Ajenkins626

    Ajenkins626 Devotee (388) Jun 14, 2014 Texas
    Trader

    17/SEP/15 1858. Cracked it out of curiosity and it tastes pretty darn good. Roasty, coffee, touch of sweetness, although not very much bourbon heat.
     
  11. SMH_NWI

    SMH_NWI Maven (1,468) Jan 8, 2015 Texas
    Trader

    Time stamps still going strong on page 10
    :grinning:
     
    jRocco2021 and jrnyc like this.
  12. PsilohsaiBiN

    PsilohsaiBiN Maven (1,473) Aug 10, 2010 New York

    So I guess I'm posting this here because this is the more popular thread of the two...but I have some questions/observations that others have raised that haven't been fully addressed that I think are important.

    1. Could it be possible that regular BCBS and variants released this year all have bottles that are/will be infected?
    2. If so, does that exclude this iteration of Rare...or not? (I'd like to hope that since this Rare used those old HH barrels and that it was '14 instead of '15 Cook County/BCBS what have you that there will be no infection there.
    3. That being said, I haven't heard of any complaints yet of '15 standard BCBS, Regal, Prop or Rare being infected but if anyone has in fact experienced this...PLEASE POST IT HERE!
    4. Could a genius mad scientist disgruntled employee have sabotaged '15 BCBS by infecting stuff deliberately? Ok, I'm gonna end it at 4. Feel free to add your own numbers. Cheers.
     
    dphalpin likes this.
  13. Adrena1ine

    Adrena1ine Zealot (748) Nov 22, 2014 Pennsylvania
    Trader

    Well for me at least... I can still fall back on Regal, Rare, and Regular... so unless the rest are infected im not that angry.
     
  14. Coldstorage

    Coldstorage Initiate (0) Oct 1, 2014 California

    tbh I'm not quite sure why @Highbrow is so agroor anyone else is so upset about it. So users are conflating a date stamp (basically a serial number) with a batch number... where is the harm? I guarantee you GI has batch data and the only way they can trace it back is specifics INCLUDING the time stamp. All data is helpful at this time. Infighting about correct terminology is not.
     
    hunninghake likes this.
  15. Highbrow

    Highbrow Pooh-Bah (1,770) Jan 7, 2011 California
    Pooh-Bah Trader

    i'm not sure why you're taking time to blast my user name for trying to make sure that the data is understood & viewed correctly? do you work for GI? what is your "guarantee" based upon? i can get behind your belief that this misinformation might be understood & useful to GI staff but why do you guys that want to defend or minimize this, speak as if this group is "GI"? it's not.

    besides for fun, & the comrade concept, would you disagree that a big portion of why we are here is to learn & share the best information & ideas possible? if you do agree that's a living concept of this meeting place, then why would you try to make a case of : bad/incorrect information that could be helpful to GI is somehow GOOD INCORRECT information for us?

    furthermore, what's wrong with trying to help people not sound ridiculous in case they do contact GI? obviously whoever answers the phone is not going to laugh (while the line is active), but what's wrong with pre-educating *us* so that if we do call or write, we don't sound like we think Goose Island actually bottled 12,000 "batches" of BCBS & variants? is this really a case of : The Truth Hurts? i think we have to simply agree to disagree there.

    and for the record i'm not *agroor* (unless that means bemused) nor am i upset. instead i am amazed so many can read a misconception, repeat & further it but all seem to miss or ignore the multiple corrections of said misconception.
     
  16. Coldstorage

    Coldstorage Initiate (0) Oct 1, 2014 California

    Sorry it should have said "agro, or why" in place of "agroor". I think you are over reacting in your corrections. I think you are over reacting in your above post as well. I don't think people listen or learn when they are being berated. You aren't reading as "bemused", it's coming off as churlish and condescending. I can see into the future and tell we will probably not see eye to eye on this.

    I don't work for GI I'm in public accounting. I used to work at an olive oil bottling plant. Based on my experience, there should be logs on GIs end with data. I highly doubt any customer service reps are hanging up the phone saying "hey Linda, another idiot called it a batch number. You know where this on gets filed... Har har" as she slides it into the trash can.
     
  17. cavedave

    cavedave Grand Pooh-Bah (4,157) Mar 12, 2009 New York
    In Memoriam Pooh-Bah Trader

    You missed the window, ABI said you needed to contact them by yesterday, and they are offering refunds as well as all expense paid trips to Disneyland.

    JK, nothing has been mentioned yet, but there will definitely be info aplenty here and everywhere when it happens:slight_smile:
     
  18. cavedave

    cavedave Grand Pooh-Bah (4,157) Mar 12, 2009 New York
    In Memoriam Pooh-Bah Trader

    The reason is if it is a batch number some folks might only take down that number, thinking it is the only important info needed to record.

    Since it isn't a batch number, but a time stamp, folks will understand all the numbers need to be observed and noted when they are made aware.

    Okay?
     
    drtth likes this.
  19. Drucifer

    Drucifer Initiate (0) Apr 16, 2012 Illinois

    Surprised it hasn't been mentioned, but FW's brewmaster is a former Goose brewmaster. Definitely a pot shot and it's hilarious.
     
    Beer4B, LakerLeith, m34josh and 6 others like this.
  20. pagriley

    pagriley Pooh-Bah (2,382) Oct 27, 2014 Illinois
    Pooh-Bah Trader

    We are talking about real people though. Actual human beings who poured their efforts into making something as good as it could be, and now they are finding out that it is infected... They probably feel pretty shitty already. Piling on / rubbing it into their faces is just rude. I don't give a crap about the company that owns GI, I am talking about the people who work there.
     
Thread Status:
Not open for further replies.