Command and Control

About the book

Eric Schlosser builds Command and Control around a single night in September 1980, when a maintenance worker dropped a socket wrench in a Titan II silo near Damascus, Arkansas. The tool punctured the missile's fuel tank, and the resulting explosion threw a nuclear warhead out of the silo. Schlosser treats that event as a case study in how a system behaves when something goes wrong.

He widens the frame to the Strategic Air Command, the 308th Strategic Missile Wing, and the long effort to keep nuclear weapons safe while keeping them ready to launch. Declassified documents, accident reports, and interviews carry the account. Command systems, safety rules, and human judgment meet under pressure, and the book follows the people and machinery that carried policy out.

The narrative alternates between the Arkansas crisis and the broader record of near misses, design compromises, and organizational strain across the Cold War. Technical material stays grounded in concrete decisions and their consequences.

How to read it

Approach the book as reported history with a strong narrative spine. The Damascus sequence gives the technical chapters momentum. Readers who prefer story over policy can follow that thread first and return to the institutional material afterward.

The subject is demanding. Missile systems, fuel chemistry, and chain-of-command procedures require attention. Schlosser explains terms in context, but the density rewards slow reading. Track roles rather than memorizing names to keep the cast of officials and officers straight.

Who it suits

Readers drawn to Cold War history, military technology, or the history of government safety regulation will find a concrete account of how nuclear weapons were handled. Journalists and policy students can study the reporting method: documents, interviews, and a single incident used to illuminate a system. Anyone curious about the gap between official assurance and operational reality will get a detailed case.

Reading considerations

The book is long, and its alternating structure can feel digressive when the Arkansas narrative pauses for institutional background. The events described center on the Cold War and the 1980 accident. Readers should treat the book as history and reporting, not as current technical or policy guidance.