FARK.com: (12537502) That time back in 1964 when the Air Force almost nuked South Dakota by accident Skip to content
Do you have adblock enabled?
 
If you can read this, either the style sheet didn't load or you have an older browser that doesn't support style sheets. Try clearing your browser cache and refreshing the page.

(9News (Australia))   That time back in 1964 when the Air Force almost nuked South Dakota by accident   (9news.com.au) divider line
    More: Scary, Nuclear fission, Explosive material, Missile, Nuclear weapon, Nuclear warfare, Minuteman Missile National Historic Site, Nuclear power, United States Air Force  
•       •       •

2515 clicks; posted to Main » on 31 Aug 2022 at 8:05 AM (14 weeks ago)   |   Favorite    |   share:  Share on Twitter share via Email Share on Facebook



59 Comments     (+0 »)
View Voting Results: Smartest and Funniest


Oldest | « | 1 | 2 | » | Newest | Show all

 
2022-08-31 7:35:55 AM  
How would you tell if they did or not? *gestures at SD*
 
2022-08-31 8:06:30 AM  
Well, there's one person happy about that...
thumbs.gfycat.comView Full Size


But as for the rest of us, we're still stuck with two Dakotas when we only need none.
 
2022-08-31 8:07:08 AM  

urger: How would you tell if they did or not? *gestures at SD*


oblig
supercultshow.files.wordpress.comView Full Size
 
2022-08-31 8:08:04 AM  
Sure..."accident". Got it.
 
2022-08-31 8:08:24 AM  
Eh, we could use two less Dakotas.
 
2022-08-31 8:10:44 AM  
Early in my career I worked with a few older technicians that came out of the Air Force missile silos, this incident was well known to them.  The way it was told to me was that a tech skipped some steps in the service procedures, and only de-powered certain circuits while doing maintenance.  A wrench was dropped, which bridged power to a place it shouldnt have been and explosive bolts fired, resulting in a displaced warhead.  It was all assholes and elbows from that point on.
 
2022-08-31 8:11:29 AM  
 
2022-08-31 8:12:20 AM  
They have a thing about trying to nuke anything with South in the name.
 
2022-08-31 8:16:09 AM  

eKonk: Well, there's one person happy about that...
[thumbs.gfycat.com image 200x150]

But as for the rest of us, we're still stuck with two Dakotas when we only need none.


How can I subscribe to your newsletter? You must know everything about how "Dakota Territory" became two States, much to the surprise of those pushing for statehood.

Hint: the railroads got involved.
 
2022-08-31 8:16:47 AM  

eKonk: But as for the rest of us, we're still stuck with two Dakotas when we only need none.


If you don't like them, I'll gladly take one. Your choice.
media1.popsugar-assets.comView Full Size
static.independent.co.ukView Full Size
 
2022-08-31 8:18:53 AM  
Better luck next time, airplane flying guy.
 
2022-08-31 8:19:50 AM  
And it would have caused millions in improvements
 
2022-08-31 8:23:28 AM  
So the warhead wasn't armed and all of the fail safes that were in the design ensured that it didn't go off  Hardly an "almost" scenario.
 
2022-08-31 8:25:02 AM  
1958 Mars Bluff Nuclear Bomb Incident
Youtube rzt2BRdEe6g
 
2022-08-31 8:29:56 AM  
Sure wished they'd say what happened to the wrench dropper.

Airman Freakstorm.  We still consider you a valued member of the U S Air Force but being around things that go boom, maybe not the best for you.   We see you in Security Forces, maybe.   How would you like to train Milkitary Working Dogs?  You know the ones with 250 pounds of biting pressure?  We'll get you one of those suits - eventually.  But for now, just wear these milk bones down around your crotchal area.
 
2022-08-31 8:30:04 AM  

EasilyDistracted: So the warhead wasn't armed and all of the fail safes that were in the design ensured that it didn't go off  Hardly an "almost" scenario.


According to TFA there was also a risk during the handling of the damaged warhead by Air Force personnel who were not qualified to do it.
 
2022-08-31 8:40:34 AM  

planes: eKonk: Well, there's one person happy about that...
[thumbs.gfycat.com image 200x150]

But as for the rest of us, we're still stuck with two Dakotas when we only need none.

How can I subscribe to your newsletter? You must know everything about how "Dakota Territory" became two States, much to the surprise of those pushing for statehood.

Hint: the railroads got involved.


Everything? That's too much to know. Yes, railroads got involved, there were different economic/communication hubs for each part, etc.  I know that one of the main motivations to make two separate states was to skew the senate towards rural states, which has highlighted a major flaw with the Senate and Electoral College.

I also know that, even today, the combined populations of both Dakotas, Wyoming, and Montana combined wouldn't crack the top half of US states in population (roughly the same population as Utah), yet combined (as of the 2023 Congressional session) will have one more vote than Utah and SIX more Senators.

We'd be better off with fewer Dakotas.
 
2022-08-31 8:42:53 AM  

eKonk: Well, there's one person happy about that...
[thumbs.gfycat.com image 200x150] [View Full Size image _x_]


Two....

Fark user imageView Full Size
 
2022-08-31 8:44:54 AM  

EasilyDistracted: So the warhead wasn't armed and all of the fail safes that were in the design ensured that it didn't go off  Hardly an "almost" scenario.


Those things are a LOT harder to set off than most people think.
 
2022-08-31 8:46:12 AM  
If you ever want to see an example of how the white man has farked things up, it's South Dakota
 
2022-08-31 8:48:11 AM  

cide1: It was all assholes and elbows from that point on.


They made hotdogs?
 
2022-08-31 8:49:16 AM  

EasilyDistracted: So the warhead wasn't armed and all of the fail safes that were in the design ensured that it didn't go off  Hardly an "almost" scenario.


When it comes to explosives, especially nukes, farking up to the extent they did qualifies as an almost.  Relying on a failsafe to save your ass is a very bad idea, so getting to the point you need them is a butthole clencher.
 
2022-08-31 8:55:13 AM  

cide1: Early in my career I worked with a few older technicians that came out of the Air Force missile silos, this incident was well known to them.  The way it was told to me was that a tech skipped some steps in the service procedures, and only de-powered certain circuits while doing maintenance.  A wrench was dropped, which bridged power to a place it shouldnt have been and explosive bolts fired, resulting in a displaced warhead.  It was all assholes and elbows from that point on.


That may have been a different incident than this one...can't remember off the top of my head.

But the "service procedures" is typically called "tech data".  And during weapon maintenance or anything related to weapon maintenance, there is tech data....like *tomes* of tech data.  Some is for reference that you *must* have on hand but anything you do will follow a specific procedure - *everything* is read aloud and checked off like a astronaut would do flying to the moon.  You don't have to check it off one at a time or read everything verbatim but it must be checked in order - if an inspector (USAF or DOE) comes up and says, "Let me see your tech data..." it better be checked to the step you are on.
 
2022-08-31 8:58:39 AM  

Netrngr: They have a thing about trying to nuke anything with South in the name.


sometimes they tried to nuke the places with 'north' in the name as well.

https://en.wikipedia.org/wiki/1961_Goldsboro_B-52_crash
 
2022-08-31 8:59:05 AM  
Tell me you have insomnia without telling me you have insomnia.

Fark user imageView Full Size
 
2022-08-31 8:59:33 AM  

Jairzinho: EasilyDistracted: So the warhead wasn't armed and all of the fail safes that were in the design ensured that it didn't go off  Hardly an "almost" scenario.

According to TFA there was also a risk during the handling of the damaged warhead by Air Force personnel who were not qualified to do it.


Fark user imageView Full Size
 
2022-08-31 9:01:33 AM  

Jairzinho: EasilyDistracted: So the warhead wasn't armed and all of the fail safes that were in the design ensured that it didn't go off  Hardly an "almost" scenario.

According to TFA there was also a risk during the handling of the damaged warhead by Air Force personnel who were not qualified to do it.


Which is incorrect because the article is sensationalizing.  Various members of the maintenance flight have design training.  They know what level of damage allows what level of response.  And if they didn't, the people at Sandia are a phone call away to give advice.  They didn't "rush out" to the site because they were concerned the USAF crew was farking up movement of a damaged weapon - they can come out any time they like and they sure as shiat would do so for this kind of damage.

The article is horribly exaggerating.  The could have left the weapon laying there, grabbed a couple of South Dakota hillbillies, handed them some sledge hammers, and let them have a day-long go at that warhead and they wouldn't have been able to do more than contaminate themselves and the immediate area.
 
2022-08-31 9:04:24 AM  

UberDave: cide1: Early in my career I worked with a few older technicians that came out of the Air Force missile silos, this incident was well known to them.  The way it was told to me was that a tech skipped some steps in the service procedures, and only de-powered certain circuits while doing maintenance.  A wrench was dropped, which bridged power to a place it shouldnt have been and explosive bolts fired, resulting in a displaced warhead.  It was all assholes and elbows from that point on.

That may have been a different incident than this one...can't remember off the top of my head.

But the "service procedures" is typically called "tech data".  And during weapon maintenance or anything related to weapon maintenance, there is tech data....like *tomes* of tech data.  Some is for reference that you *must* have on hand but anything you do will follow a specific procedure - *everything* is read aloud and checked off like a astronaut would do flying to the moon.  You don't have to check it off one at a time or read everything verbatim but it must be checked in order - if an inspector (USAF or DOE) comes up and says, "Let me see your tech data..." it better be checked to the step you are on.


We had PMS in the Navy, complete with reading that shiat aloud.  I had to do weekly inspections on maintenance and only failed people a couple times, most notably when some dude was cleaning toilets with that strong cleaning powder shiat without a respirator.

Maintenance is often boring as fark, but will fark you up if you don't do it right *Shrugs*.
 
2022-08-31 9:05:37 AM  

Theeng: EasilyDistracted: So the warhead wasn't armed and all of the fail safes that were in the design ensured that it didn't go off  Hardly an "almost" scenario.

When it comes to explosives, especially nukes, farking up to the extent they did qualifies as an almost.  Relying on a failsafe to save your ass is a very bad idea, so getting to the point you need them is a butthole clencher.


That warhead has a safe evacuation distance of 1000' (may be 500'...can't remember off the top of my head).  An Mk82, which is a common 500lb "dumb" bomb, has an evacuation safe distance of 5000'.  Just to give you an idea of the explosive hazard.

You could have lit a bonfire around that nuke and it would have done nothing but smolder.  When you consider all the things that have to be perfect for that thing to produce a nuclear yield, it was no where *near* "almost".
 
2022-08-31 9:08:30 AM  
Let's get a grip here. The only silos at the actual base were training silos. All the operational silos were 30 or more miles from the city (and the base).

In reality, some farmers might have had a really bad day, or we may remember Wall or Sturgis in a much different way, but the specific "everybody on east side of Rapid City would have been burned" line is nonsense. Now, they may all have two heads from the fallout, depending on which silo it was and which way the wind was blowing, but thermal burns unlikely.
 
2022-08-31 9:08:36 AM  

Theeng: Maintenance is often boring as fark, but will fark you up if you don't do it right *Shrugs*.


Call it "readiness" and it explains why the Russians are getting farked so hard in Ukraine.

Entropy is a remorseless biatch that never sleeps.
 
2022-08-31 9:11:21 AM  

scanman61: EasilyDistracted: So the warhead wasn't armed and all of the fail safes that were in the design ensured that it didn't go off  Hardly an "almost" scenario.

Those things are a LOT harder to set off than most people think.


Only one way to find out:
i.imgflip.comView Full Size

c.tenor.comView Full Size
 
2022-08-31 9:12:28 AM  

scanman61: Theeng: Maintenance is often boring as fark, but will fark you up if you don't do it right *Shrugs*.

Call it "readiness" and it explains why the Russians are getting farked so hard in Ukraine.

Entropy is a remorseless biatch that never sleeps.


Readiness is a big farking deal, as the Moskva demonstrated.

UberDave: Theeng: EasilyDistracted: So the warhead wasn't armed and all of the fail safes that were in the design ensured that it didn't go off  Hardly an "almost" scenario.

When it comes to explosives, especially nukes, farking up to the extent they did qualifies as an almost.  Relying on a failsafe to save your ass is a very bad idea, so getting to the point you need them is a butthole clencher.

That warhead has a safe evacuation distance of 1000' (may be 500'...can't remember off the top of my head).  An Mk82, which is a common 500lb "dumb" bomb, has an evacuation safe distance of 5000'.  Just to give you an idea of the explosive hazard.

You could have lit a bonfire around that nuke and it would have done nothing but smolder.  When you consider all the things that have to be perfect for that thing to produce a nuclear yield, it was no where *near* "almost".


I'm more than okay with overstating the risks of people farking up maintenance on a nuke.
 
2022-08-31 9:16:27 AM  

Sofa King Smart: Netrngr: They have a thing about trying to nuke anything with South in the name.

sometimes they tried to nuke the places with 'north' in the name as well.

https://en.wikipedia.org/wiki/1961_Goldsboro_B-52_crash


This one was probably the closest we ever came to an accidental detonation. I say probably because the government tends not to be too forthcoming about things like this, though the lack of detonations speaks for itself.
 
2022-08-31 9:16:54 AM  

eKonk: Well, there's one person happy about that...
[thumbs.gfycat.com image 200x150]

But as for the rest of us, we're still stuck with two Dakotas when we only need none.


Hell. All states should be the size of two and 3 quarters Rhode Islands'.
 
2022-08-31 9:17:43 AM  
c.tenor.comView Full Size
 
2022-08-31 9:21:46 AM  

Harry Freakstorm: Sure wished they'd say what happened to the wrench dropper.

Airman Freakstorm.  We still consider you a valued member of the U S Air Force but being around things that go boom, maybe not the best for you.   We see you in Security Forces, maybe.   How would you like to train Milkitary Working Dogs?  You know the ones with 250 pounds of biting pressure?  We'll get you one of those suits - eventually.  But for now, just wear these milk bones down around your crotchal area.


I remember watching a load crew fark up an ACM (AGM-129) by dropping a big-ass wrench from height.  It had a warhead (that was in no danger) and that missile had to be pulled.  If I hadn't seen it, those dudes would have send the entire load (6 missiles on a B52 pylon) back to the maintenance facility and blamed it on nuclear maintenance when it was found.

It's easy for crews to get complacent even though they are pretty much experts at what they are doing.  I was a trainer for a bit and when I got a new crew to train (both novice members and a crew chief...and this was months long), I would first find a bare warhead on a trailer or test stand and gather around it within arm's length and have a nice talk about what this relatively tiny thing means, represents, can do, and how they have a responsibility to *always* keep that in mind and be as meticulous and professional as possible while working with it.  The goal was to prevent complacency.
 
2022-08-31 9:27:59 AM  
Earlier that year they intentionally nuked Mississippi, which is understandable

Atomic Journeys: Mississippi segment
Youtube RIw0RU4JFOA
 
2022-08-31 9:29:46 AM  

cide1: Early in my career I worked with a few older technicians that came out of the Air Force missile silos, this incident was well known to them.  The way it was told to me was that a tech skipped some steps in the service procedures, and only de-powered certain circuits while doing maintenance.  A wrench was dropped, which bridged power to a place it shouldnt have been and explosive bolts fired, resulting in a displaced warhead.  It was all assholes and elbows from that point on.


Sometimes dropping a wrench in a missile silo has ... worse ... consequences.
 
2022-08-31 9:30:19 AM  
Silo L-02, so Vale. 35 miles away from Rapid.
 
2022-08-31 9:30:34 AM  

Adolf Oliver Nipples: Sofa King Smart: Netrngr: They have a thing about trying to nuke anything with South in the name.

sometimes they tried to nuke the places with 'north' in the name as well.

https://en.wikipedia.org/wiki/1961_Goldsboro_B-52_crash

This one was probably the closest we ever came to an accidental detonation. I say probably because the government tends not to be too forthcoming about things like this, though the lack of detonations speaks for itself.


I remember learning about this when it was still classified.  *Everyone* talked about it so ominously.  It was a big mistake for sure but the more I learned about the details, I think it was unlikely.  Personally, I think it had less than a 5% chance of producing a yield and if it had, it would have been small....noticeable, but small....and it would have been filthy (not "dirty"...but "filthy").
 
2022-08-31 9:51:52 AM  

Ambitwistor: cide1: Early in my career I worked with a few older technicians that came out of the Air Force missile silos, this incident was well known to them.  The way it was told to me was that a tech skipped some steps in the service procedures, and only de-powered certain circuits while doing maintenance.  A wrench was dropped, which bridged power to a place it shouldnt have been and explosive bolts fired, resulting in a displaced warhead.  It was all assholes and elbows from that point on.

Sometimes dropping a wrench in a missile silo has ... worse ... consequences.


was just gonna mention that


Fark user imageView Full Size

/ it's good reading
 
2022-08-31 9:56:42 AM  
So why does the article have an oh so unhelpful pic of a nuclear reactor. Not even farking close
 
2022-08-31 10:02:47 AM  

eKonk: planes: eKonk: Well, there's one person happy about that...
[thumbs.gfycat.com image 200x150]

But as for the rest of us, we're still stuck with two Dakotas when we only need none.

How can I subscribe to your newsletter? You must know everything about how "Dakota Territory" became two States, much to the surprise of those pushing for statehood.

Hint: the railroads got involved.

Everything? That's too much to know. Yes, railroads got involved, there were different economic/communication hubs for each part, etc.  I know that one of the main motivations to make two separate states was to skew the senate towards rural states, which has highlighted a major flaw with the Senate and Electoral College.

I also know that, even today, the combined populations of both Dakotas, Wyoming, and Montana combined wouldn't crack the top half of US states in population (roughly the same population as Utah), yet combined (as of the 2023 Congressional session) will have one more vote than Utah and SIX more Senators.

We'd be better off with fewer Dakotas.


Eminent domain all the private property in both dakotas, montana,and wyoming.

Kick everyone out and make it all a giant national park.

Add dc and Puerto Rico as states and go back to the 48 star flag.

Old glory ftw.
 
2022-08-31 10:04:42 AM  

Ambitwistor: Sometimes dropping a wrench in a missile silo has ... worse ... consequences.


Eric Schlosser's book on that incident (and many others) is a great read. PBS did a documentary on it as well.
 
2022-08-31 10:08:16 AM  
Funny thing is, they actually did nuke Ohio.
 
2022-08-31 10:13:18 AM  
Yeah, and those are the " who gives a shiat" secrets...
 
2022-08-31 10:19:50 AM  

Ambitwistor: cide1: Early in my career I worked with a few older technicians that came out of the Air Force missile silos, this incident was well known to them.  The way it was told to me was that a tech skipped some steps in the service procedures, and only de-powered certain circuits while doing maintenance.  A wrench was dropped, which bridged power to a place it shouldnt have been and explosive bolts fired, resulting in a displaced warhead.  It was all assholes and elbows from that point on.

Sometimes dropping a wrench in a missile silo has ... worse ... consequences.


There is a nice documentary, re-enacting this story and with interviews of some of the people involved. I watched it not long ago.
The Nuclear Warhead Explosion That Nearly Ended The World | Alive | Wonder
Youtube qLS0ho8gWPE
 
2022-08-31 10:24:01 AM  
All of these nuclear accidents happened back in the 50's and 60's, before we knew how dangerous nuclear weapons were. We are much more careful now.
 
2022-08-31 10:24:14 AM  

Ragin' Asian: Tell me you have insomnia without telling me you have insomnia.

[Fark user image 425x584]


I've seen that movie...
Fark user imageView Full Size
 
Displayed 50 of 59 comments


Oldest | « | 1 | 2 | » | Newest | Show all


View Voting Results: Smartest and Funniest

This thread is closed to new comments.

Continue Farking




On Twitter


  1. Links are submitted by members of the Fark community.

  2. When community members submit a link, they also write a custom headline for the story.

  3. Other Farkers comment on the links. This is the number of comments. Click here to read them.

  4. Click here to submit a link.