Long time ago Risk Digest had an article where the latest and greatest air craft carrier failed left drifting in the water when the operating system (NT) had a divide by zero error.
Doing a global search the best I could come across was this one article.
The article describes an incident where, apparently, a test of the US Navy's
new Electro-Magnetic Aircraft Launch System (EMALS) failed because it
unexpectedly went in reverse, destroying 'important equipment' and delaying
the program by several months. The failure has been blamed on a software
Given that such a device only has two possible ways to move - forwards or
backwards - one wonders just how it happened. However, I'm sure that it is
far more complicated than I realise.
What is most risky is the attitude of EMALS programme chief Captain Randy
Mahr who says, "The things that are delaying me right now are software
integration issues, which can be fine-tuned after the equipment is installed
in the ship."
I think most RISKS readers will agree that on-board ship will be the worst
place to finish the software. (However it will be the best place in order to
claim to your paymasters that the project is complete and operational - bar
a minor software glitch that may not happen again. And even if it does, it
may not kill or injure anyone as long as we remember to tell everyone to
stand well away from the back of the machine as well as the front.)"
a lot had to be removed due to "junk charters"