Video: San Diego fireworks accidentally went off all at once

Discuss

64 Responses to “Video: San Diego fireworks accidentally went off all at once”

  1. Xeni Jardin says:

    It happens to a lot of cities. San Diego shouldn’t feel ashamed. There are drugs that can help with this issue.

  2. royaltrux says:

    Surprisingly not much fun to watch – too much glare.

    • Iron Clad Burrito says:

      The camera doesn’t really do it justice.  As brief as it was, it was pretty awesome to watch.  :)

  3. Steve Merchant on fireworks (XFM days with RG and KP):  “I always thought, ‘if the guy organising it had wheeled out an ENORMOUS firework, climbed in, gone ‘last one to the moon’s a bender!’ then shot off, that I would have been, ‘yeah!”’ http://www.youtube.com/watch?v=NC0342–G4s

  4. There seem to be three displays (1 in foreground, 2 in background). Did they all go off at once?

    • chaopoiesis says:

      Multiple launch sites around San Diego Bay. Which implies some sort of synchronized remote launch system. Which in turn implies the potential for a hack. One wonders…

      BTW here’s a far better video of it:

      http://www.youtube.com/watch?v=4ifn8LJl5n0

      • morcheeba says:

        Nah, it would be much easier to use synchronized clocks than some sort of data link.

        • chaopoiesis says:

          … then for all the clocks to fail identically, the same setup error by the same tech crew.  Plausible.

          • nathanroberts says:

            That actually sounds fairly similar to the (supposed) origin of Murphy’s Law.  An experiment involving a series of force sensors returned no data; as it turns out, every single sensor had been systematically wired backwards.

      • royaltrux says:

         That is a much better video, thanks.

      • David Pescovitz says:

        Thanks! I updated the post with this better video!

      • Dolphin Bunnywolf says:

         So could the programmable controls powering the firing system be vulnerable to, say, a Stuxnet variant?

        • Dolphin Bunnywolf says:

           Or maybe they hired Beavis and Butthead to run their fireworks shows?

          Damn, I miss the little weinerheads.

        • chaopoiesis says:

          A recent article in the U-T San Diego quotes the owner of the fireworks company as claiming the problem was caused by a “rogue signal” sent by “a virus” in their computerized launch software. You can’t make this stuff up…

  5. technobach says:

    I personally think that all fireworks shows should be like this.

  6. Marcus Mendes says:

    This is why I ALWAYS read before pressing “Yes to all”

  7. angusm says:

    It reminds me of the end of “Quatermass and the Pit”. The scene in question scared the crap out of me when I was young and impressionable, because, well, huge glowing things in the sky are scary, that’s all there is to it.

  8. MrHarley says:

    Stay classy San Diego! This I like, however electing birther guy to judge, now that’s a technical glitch.

     http://www.utsandiego.com/news/2012/jun/19/gary-kreep-clinches-win-for-judge/

  9. Nadreck says:

    You’re supposed to hook the fuses up in *series* NOT *parallel*, dammit!

    • Sagodjur says:

       Completely off topic – I can’t find anything online about the hard-boiled story you referenced in a post nine months ago called The Deader They Die. You mind telling me who wrote it?

  10. eselqueso says:

    Who has time for a whole 15 minute show anymore, anyway? This should be fireworks protocol from now on!

  11. oldtaku says:

    I bet someone programmed all the delays in seconds when it needed to be hundredths of seconds or milliseconds (you enter what you think is 5 seconds to the next shell, but you just specified .05 seconds). There’s no way it was a physical problem with it happening on all three barges.

    • rekoil says:

      That theory makes a lot of sense, since it’s apparent from the video that there *was* some sort of sequencing going on (you can see charges firing sequentially), just at an extremely high fire rate.

  12. teapot says:

    Nothing says ‘merica like a BIG FUCKING EXPLOSION! I can not think of a more fitting way to celebrate US independence day.

  13. angusm says:

    I guess next year they won’t ask Michael Bay to organize the fireworks display.

  14. sqyntz says:

    contrary to the title,  they did *not* all go off at once!

    • Aeron says:

      Seriously, all at once would have meant three large holes in San Diego.

      • rekoil says:

        They launched sequentially but at an incredibly rapid rate (see oldtaku’s comment above). But they all launched as designed and exploded in the air, not on the platforms.

  15. RSDeuce says:

    We weren’t close, and got to watch another fireworks show (at Fiesta Island) that went off without a hitch. However, we could see all three locations and even from several miles that crap was LOUD. Pretty amazing at a distance. 

  16. Atvaark says:

    So, Mythbusters, what did it prove?

  17. oldtaku says:

    Found one even dumber – the town’s fireworks set off by a stray bullet: http://www.theregister.co.uk/2012/07/05/premature_detonation/

  18. Peter Swimm says:

    I hope they had a grindcore band playing the hits.

  19. semiotix says:

    We apologize for the brevity of the show and the technical difficulties

    PR fail. Here’s what you say.

    “You are welcome for the off-the-charts awesomeness of the show, which no other fireworks company would even dare to attempt.”

  20. ackpht says:

    They should consult with my lovely neighbors, who had no difficulty stretching out their pyrotechnic and acoustic displays over the entire day. Maybe the guys in San Diego were too sober.

  21. Aeron says:

    This was a really good sales pitch for whomever designed the launchers, huh? One hiccup and something terrible would have happened.

  22. ponzicar says:

     That’s not a glitch. That’s an improvement. It’s a lot more spectacular than watching them go off one at a time over a much larger period of time.

  23. Gemma says:

    Scotland was there before you! The same thing happened in Oban on bonfire night last year (November 2011).

    Video and news story.

  24. Paul Renault says:

    It looks the aftermath of finally defeating the last Boss on Diablo III.

    http://arstechnica.com/gaming/2012/07/blizzard-admits-diablo-iii-is-a-game-that-ends/

    • Michael Stratford says:

      Finally?  As though that took longer than 1 try, few hours of your time?

      • Paul Renault says:

         You have to include all the time spent on Diablo and Diablo II.

        (Actually, after fifteen or twenty levels of Diablo, I stopped playing it.  I’ve never understood the attraction.)

  25. Manny says:

    That was frickin’ AWESOME!

  26. lasermike026 says:

    I like it!  Fireworks for the twitter generation!

  27. crummett says:

    The plaintive beeping is kind of poignant. Poor computer. “Uh, excuse me. We seem to have some sort of problem here!”

  28. Daneel says:

    Something like this happened at a Guy Fawkes Night display I went to once. Caused by one firework exploding on the ground and setting all the others off, some were blown over and went off at strange angles.  Think a few people were nastily injured.

    http://news.bbc.co.uk/2/hi/uk_news/england/northamptonshire/4411776.stm

    I wonder if Kettering has ever been likened to San Diego before? Anyone else here ever been to both?

  29. wilmcdaniel says:

    I like sparklers using proximity to create BIG.

  30. Mike Fayer says:

    That’s not a bug that’s a feature.

  31. Subdrill says:

    I’ve had a bit of pyro experience, and with the disclaimer that this is speculation, it’s likely a rather unforgiving feature caused by user error. They were probably using FireOne choreography software and hardware, a really expensive, but very simple and easily scalable system for designing and performing pyro shows. Once you’ve built a database of all your products, you can drag and drop any shell or effect to burst at time “x” to line up with the music, and the software will automatically initiate the effect at time “x-y”, where “y” is the time that effect takes to go from launch until the actual burst. Once you’ve programmed the show, you can easily print out lists of where to hook up every single piece of product, from 1 to whatever; the loaders don’t have to deal with the timings of anything, and come performance time, the operator only has to hit the start button and the show runs automatically along a perfectly-synced timeline.
    Here’s the trouble though: when checking for continuity and connection right before the show, you can move that curser anywhere along the timeline to check when and where and how everything’s going to fire, and you can start and stop anywhere during the program’s timeline without resetting to the beginning every time. If after the continuity check, you don’t reset to the beginning, and you’re now live and ready to fire the real thing and hit start, the curser doesn’t just stop or reset to the beginning, it attempts to play from that spot. And then fires all product that is set to fire from that delay -or earlier-. The software effectively says “now’s the time to fire everything whose delay is less than time “x-y”, and for a time “x” at the end of the show, that’s everything. The operator hits start, the software sends the “fire everything” signal, and you get this. It’s happened a couple times before, it’s a terrible bug I’m surprised hasn’t been fixed, and the lead operator was almost definitely fired for this, that was probably at least $100,000 worth of product shot in 9 seconds. 

  32. BarBarSeven says:

    Fail? AGAIN! AGAIN!

  33. penguinchris says:

    I’m not sure how common these are, but at my local fireworks show they had some that directed all their energy not toward glowing burning stuff, but solely toward making the loudest bang possible. They were awesome… you could see them shooting up and then instead of the typical big explosion, it was just an enormous boom. The sound is my favorite part of fireworks shows and this one in San Diego must have been unbelievably great.

  34. xiangreek says:

    Boss:  “Hey Frank, this field’s value is in milliseconds, not seconds…”

    Frank: “Oh shi…”

Leave a Reply