Air Force missile launch crew fell asleep

The probe found that the missile launch codes were outdated and remained secure at all times. But the July 12 incident comes on the heels of a series of missteps by the Air Force that had already put the service under intense scrutiny.

"This was just a procedural violation that we investigated," said Air Force Col. Dewey Ford, a spokesman at Peterson Air Force Base in Colorado Springs, Colo. "We determined that there was no compromise."

The lapse, which involved a crew based at Minot Air Force Base, was serious enough, however, to prompt an investigation by the 91st Missile Wing, in conjunction with codes experts at the 20th Air Force, U.S. Strategic Command and the National Security Agency.

And it delivers another blow to the beleaguered Air Force.

Last month, Defense Secretary Robert Gates announced a sweeping shake-up of the Air Force leadership, blaming them for failing to fully address a series of nuclear-related mishaps.

At the time, Gates said his decisions to sack the Air Force secretary and chief of staff were based mainly on the blistering conclusions of an internal report on the mistaken shipment to Taiwan of four Air Force fusing devices for ballistic missile nuclear warheads.

He also linked the underlying causes of that slip-up to the August incident in which a B-52 bomber was mistakenly armed with six nuclear warheads and flown from Minot Air Force Base to Barksdale Air Force Base in Louisiana.

No one has been punished yet in the latest Minot incident involving sleeping crew members. A continuing review by Minot commanders will determine what, if any, actions will be taken against them.

Ford and other Air Force officials said the Minot-based crew had code devices that were no longer usable, since new codes had been installed in the missiles.