“Titan II” and “Titan 2” redirect here. For other uses, it seems humanity requires multiple interpretations of something designed for singular, rather drastic purpose. See Titan 2 (disambiguation) for the other shades of meaning.

LGM-25C Titan II

An LGM-25C Titan intercontinental ballistic missile , a veritable monument to kinetic energy, captured in its silo , poised for a launch that would undoubtedly alter the geopolitical landscape – or simply scorch a large portion of it.

Type

An Intercontinental ballistic missile , a rather euphemistic term for a device designed to deliver a catastrophic payload across continents. Its primary directive was, quite simply, global reach with unparalleled destructive capability.

Place of origin

United States. A product of the Cold War’s relentless pursuit of strategic advantage.

Service history

In service from a tense 1962 to a somewhat less tense, but still volatile, 1987. A quarter-century of global anxiety, neatly packaged in a series of colossal tubes.

Used by

The United States. Specifically, its strategic forces, tasked with the grim calculus of deterrence.

Production history

Manufacturer The Glenn L. Martin Company , a corporation that, for a time, specialized in crafting instruments of ultimate persuasion.

Specifications

• Mass 155,000 kg (342,000 lb). A truly impressive piece of existential dread, weighing more than a hundred average cars.
• Length 31.394 m (103.00 ft). Taller than an eight-story building, designed to stand vertically in its subterranean lair before its brief, fiery ascent.
• Diameter 3.05 m (10.0 ft). A substantial cylinder of barely contained power.
• Warhead The infamous W-53 9 Mt thermonuclear warhead. Nine megatons. Just ponder that for a moment. It was the largest single warhead ever deployed on an American intercontinental ballistic missile , a blunt instrument of truly terrifying power.
• Detonation mechanism Air-burst or contact (surface). Because one needs options when obliterating a target.
• Engine Two-stage liquid-fueled rocket engines, providing the raw, unadulterated thrust necessary to propel such a payload across oceans. The first stage was powered by the formidable LR-87 , and the second stage by the equally potent LR91 .
• Propellant A delightful cocktail of N₂O₄ (dinitrogen tetroxide) and Aerozine 50 . These hypergolic propellants were storable, meaning they could sit in the tanks for extended periods, always ready. A convenience, to be sure, but one that came with the rather significant drawback of being incredibly toxic and prone to spectacular, accidental combustion. More on that later.
• Guidance system An Inertial system, initially utilizing the IBM ASC-15 computer. A complex, fragile brain for a blunt instrument, guiding it with detached precision towards its designated point of impact.
• Launch platform Primarily from a hardened Missile silo , buried deep underground, a testament to the paranoia and strategic thinking of the era.

• Titan II Function

• Function A versatile piece of Cold War engineering, serving initially as an Intercontinental ballistic missile (ICBM) and later repurposed as a Launch vehicle . From global annihilation to orbital delivery – a truly flexible design, if you consider the underlying physics.
• Manufacturer Martin .
• Country of origin United States.
• Cost per launch $ 3.16 million in 1969. One often wonders what else that money could have bought. Perhaps a less volatile method of delivering weather satellites. [ citation needed ]
• Size
  • Height 31.394 m (103.00 ft) (in its ICBM configuration).
  • Diameter 3.05 m (10.0 ft).
  • Mass 154,000 kg (340,000 lb).
• Stages 2. A two-stage ascent into either the upper atmosphere or, more benignly, Earth orbit.
• Capacity
  • Payload to LEO Mass 3,600 kg (7,900 lb). A substantial lift for its time.
  • Payload to 100 km (62 mi) sub-orbital trajectory Mass 3,700 kg (8,200 lb).
  • Payload to polar LEO Mass 2,177 kg (4,800 lb).
  • Payload to escape Mass 227 kg (500 lb). Even this enormous machine could barely nudge a small payload out of Earth’s gravitational embrace.
• Launch history
  • Status Retired. Thankfully.
  • Launch sites Primarily from Cape Canaveral (specifically LC-15 , LC-16 , LC-19 ) and Vandenberg (from SLC-4E , SLC-4W , LC-395 ). A rather geographically diverse set of launch points for a missile that preferred to stay put in its silo.
  • Total launches 106 (81 suborbital).
    • ICBM: 81 (suborbital).
    • GLV (Gemini Launch Vehicle): 12.
    • 23G (refurbished ICBMs): 13.
  • Success(es) 101 (77 suborbital).
    • ICBM: 77 (suborbital).
    • GLV: 12.
    • 23G: 12.
  • Failure(s) 5 (4 suborbital).
    • ICBM: 4 (suborbital).
    • 23G: 1.
  • First flight 12 March 1962.
  • Last flight 18 October 2003. A surprisingly long operational life for a system initially designed for rapid, decisive, and likely final, action.
  • Carries passengers or cargo Yes, a rather ironic twist for a weapon of mass destruction. It carried Gemini (crewed) capsules, sending humans into space, and also less glamorous payloads like the Clementine spacecraft.
• • First stage
  • Powered by 2 LR-87 engines.
  • Maximum thrust 1,900 kN (430,000 lb f ). Enough power to lift the colossal missile from its underground lair.
  • Specific impulse 258 seconds (2.53 km/s).
  • Burn time 156 s. A brief, violent burst.
  • Propellant N₂O₄ / Aerozine 50 . The volatile mixture that made it so efficient, and so dangerous.
• • Second stage
  • Powered by 1 LR91 engine.
  • Maximum thrust 445 kN (100,000 lb f ).
  • Specific impulse 316 seconds (3.10 km/s).
  • Burn time 180 s.
  • Propellant N₂O₄ / Aerozine 50 . The same delightful blend, continuing the journey towards orbit or, more ominously, target.

[edit on Wikidata]

• Titan-II ICBM silo test launch, Vandenberg Air Force Base. A glimpse into the sheer power and inherent risk.
• Mark 6 re-entry vehicle which contained the W-53 nuclear warhead , fitted to the Titan II. A chilling encapsulation of destructive potential.
• Titan II launch vehicle launching Gemini 11 (12 September 1966). A moment of scientific progress, powered by a doomsday machine.
• Titan 23G launch vehicle (5 September 1988). The repurposed veteran, finding a new career.

The LGM-25C Titan II was an intercontinental ballistic missile (ICBM) originally conceptualized and developed by the Glenn L. Martin Company . It emerged as a more potent and strategically significant successor to the earlier HGM-25A Titan I missile, embodying the Cold War’s relentless drive for ever more capable weaponry. While its initial, and arguably most infamous, design purpose was that of an ICBM, its robust structure and considerable lifting capacity eventually led to its adaptation as a medium-lift space launch vehicle . These repurposed iterations were subsequently designated as the Titan II GLV (Gemini Launch Vehicle) and Titan 23G , extending the missile’s operational life far beyond its original intent.

These modified Titan II vehicles were instrumental in supporting critical missions for the United States Air Force (USAF), the National Aeronautics and Space Administration (NASA), and the National Oceanic and Atmospheric Administration (NOAA). Their diverse payloads underscored the adaptability of this formidable rocket. For the USAF, they launched satellites for the Defense Meteorological Satellite Program (DMSP), providing vital weather intelligence. NOAA utilized them for its own fleet of weather satellites, ensuring humanity could predict its own inconveniences, if not its self-destruction. Most famously, perhaps, the Titan II GLV carried NASA’s Gemini crewed space capsules, literally boosting humans into orbit on a vehicle originally designed to deliver nuclear devastation. This rather stark juxtaposition of purpose certainly offers a unique perspective on human ingenuity. These modified Titan II SLVs (Space Launch Vehicles) continued to launch from Vandenberg Air Force Base , California, demonstrating remarkable longevity right up until 2003.

As a prominent member of the Titan rocket family , the Titan II ICBM represented a significant leap forward from its predecessor, the Titan I. It boasted double the payload capacity, a clear indication of the escalating arms race. Crucially, unlike the Titan I, which relied on cryogenic liquid oxygen (an oxidizer that had to be loaded immediately before launch, thus requiring the missile to be raised from its silo and fueled in a time-consuming process), the Titan II employed hydrazine -based hypergolic propellants. This chemical marriage of Aerozine 50 and dinitrogen tetroxide was a game-changer. These propellants were storable at ambient temperatures, meaning the missile could remain fully fueled within its silo, ready for an instantaneous launch. This drastically reduced the time to launch, a critical advantage in a world where seconds could determine the fate of nations. However, this efficiency came at a steep price: the hypergolic nature of these propellants meant they ignited upon contact, making them inherently dangerous to handle. Leaks, as history would painfully demonstrate, could (and did) lead to catastrophic explosions, and the fuel itself was notoriously toxic. Despite these significant hazards, the Titan II’s ability to launch directly and rapidly from its hardened silo was an undeniable strategic asset. With its colossal size and power, the Titan II earned the dubious distinction of carrying the largest single warhead of any American ICBM. [1]

LGM-25C missile

The LGM-25C missile itself was a marvel of Cold War engineering, a precisely calibrated instrument of mass destruction. It consisted, in essence, of a two-stage, rocket engine powered vehicle, meticulously designed for its single, terrifying purpose, and a distinct re-entry vehicle (RV) at its apex, housing the payload. The design incorporated specific provisions for the in-flight separation of Stage II from Stage I, a violent but necessary act, followed by the subsequent, equally precise separation of the RV from Stage II, ensuring the warhead reached its terminal trajectory unencumbered.

Each of the two stages, Stage I and Stage II, was an independent, self-contained system. They housed the propellant tanks and pressurization systems, the powerful rocket engines themselves, complex hydraulic and electrical networks to manage flight, and, of course, the necessary explosive components to facilitate staging and, if required, self-destruction. Beyond these shared fundamental systems, Stage II carried the crucial additional responsibility of housing the primary flight control system and the sophisticated missile guidance system. [2] This made Stage II the brain of the operation, dictating the missile’s path through the unforgiving vacuum. Within Stage I, a trio of gyros provided initial orientation data, working in concert with the Autopilot. This Autopilot’s primary function was to maintain the missile’s stability and straight trajectory during the initial, most dynamic phase of first-stage flight. It then transmitted critical steering commands to the Inertial Measurement Unit (IMU) located within the second stage. The IMU would process these commands, compensate for any deviations, and issue precise steering instructions to the engine actuators, ensuring the missile remained on its pre-programmed course. A rather elaborate dance, all to deliver a single, devastating punch.

Airframe

The airframe of the Titan II was a robust, two-stage structure, deceptively described as “aerodynamically stable” for something designed to rocket skyward with such immense force. Its primary function was to house and meticulously protect all the airborne missile equipment throughout the violent powered flight phase. The integrated missile guidance system, a network of circuits and algorithms, was responsible for orchestrating the critical events of flight, including the precise engine shutdown and the staging enable relay, which initiated the dramatic separation of Stage I.

Each stage maintained a uniform diameter of 10 feet (3.0 m), a consistent girth for a consistent delivery. The fuel and oxidizer tanks were arranged in tandem, one after the other, with the walls of these very tanks ingeniously forming the external skin of the missile in those sections. This design, while efficient, inherently meant that the missile’s structural integrity was directly tied to the integrity of the propellant tanks – a rather intimate relationship for such volatile contents. External conduits, like veins and arteries, were carefully attached to the outside surface of these tanks, providing protected passages for the intricate wire bundles and tubing that crisscrossed the missile’s anatomy. For the inevitable, and often precarious, inspections and maintenance, access doors were strategically placed on the missile’s forward, aft, and between-tanks structures. A removable cover on the forward dome of each tank even allowed for internal tank entry, a task one hopes was approached with extreme caution, given the residue of its highly toxic propellants. [3]

Stage I airframe

The Stage I airframe, the initial powerhouse of the missile, comprised several key structural elements: an interstage structure, the oxidizer tank forward skirt, the oxidizer tank itself, an inter-tank structure, and finally, the fuel tank. The interstage structure, along with the oxidizer tank forward skirt and the inter-tank structure, were all meticulously fabricated assemblies, constructed using riveted skin, stringers, and frame – a robust, yet conventional, approach to aerospace engineering. The oxidizer tank, however, was a welded structure, a critical component consisting of a forward dome, a cylindrical tank barrel, an aft dome, and an internal feedline. Similarly, the fuel tank, also a welded structure, was composed of a forward dome, its own tank barrel, an aft cone, and an internal conduit. [3] Every joint, every weld, a potential point of failure in a system designed for zero tolerance.

Stage II airframe

Following the first stage, the Stage II airframe, responsible for the final push to orbit or target, was composed of a transition section, the oxidizer tank, another inter-tank structure, the fuel tank, and an aft skirt. Much like its lower counterpart, the transition section, inter-tank structure, and aft skirt were fabricated assemblies, relying on riveted skin, stringers, and frame for their structural integrity. The oxidizer tank and fuel tank on the second stage were also welded structures, each featuring distinct forward and aft domes. [3] The design ethos was clear: robust, functional, and built to withstand the immense forces of launch, all while containing a cocktail of chemicals that would happily consume any organic matter they encountered.

Missile characteristics

The following data, an inventory of impending kinetic energy, is compiled from the authoritative publication T.O. 21M-LGM25C-1   – via Wikisource . (Dash 1). It details the sheer scale and power of this weapon system.

The sheer scale of these numbers, particularly the thrust figures, underscores the raw power required to lift such a massive object and its equally massive payload into the heavens. The relatively small vernier thrust for silo operations, a precise whisper amidst the roar, highlights the delicate balance between immense power and minute control required for a successful launch.

Guidance

The initial LGM-25C Titan II guidance system was a product of ACDelco , a division more commonly associated with automotive components, but which also ventured into the more esoteric realm of missile navigation. At its core, this system utilized an Inertial Measurement Unit (IMU), essentially a sophisticated gyroscopic sensor, which traced its lineage back to the original designs pioneered by MIT Draper Labs. The complex calculations required for trajectory correction were handled by the missile guidance computer (MGC), an IBM ASC-15 . This was, for its time, a cutting-edge piece of hardware, a testament to the computing power dedicated to ensuring the missile met its target.

Within Stage I, three gyros provided initial orientation, working in conjunction with an Autopilot system. The Autopilot’s primary function was to maintain the missile’s stability and straight flight path during the initial, turbulent phase of first-stage burn. It would then transmit crucial steering commands to the IMU located in the second stage. The IMU, acting as the missile’s central nervous system, would process these inputs, calculate necessary adjustments, and then relay precise steering commands to the engine actuators, ensuring the missile remained on its predetermined course.

However, even instruments of global annihilation aren’t immune to planned obsolescence. As time wore on, obtaining spare parts for this original ACDelco system became increasingly challenging, a bureaucratic headache for a system designed for singular, decisive action. Consequently, it was eventually superseded by a more modern guidance package: the Delco Universal Space Guidance System (USGS). This upgraded system incorporated a Carousel IV IMU, known for its enhanced precision and reliability, and was controlled by a Magic 352 computer. [4] A necessary upgrade to ensure the continued, precise delivery of its rather blunt message.

Launching

The Titan II missiles were conceived and constructed with a very specific strategic imperative in mind: to be launched from formidable underground missile silos . These silos were not merely shelters; they were hardened against the devastating effects of a nuclear attack, designed to withstand the initial onslaught of an enemy’s first strike . This hardening was critical, intended to ensure that the United States retained the capability to survive such an attack and, crucially, to retaliate with a devastating second strike response. It was a grim calculus of deterrence, built on the assumption that an opponent would never initiate a nuclear exchange if they knew their own destruction was guaranteed.

The authority to unleash such an apocalyptic response was vested exclusively in the US President , a singular point of terrifying power and responsibility. Once a launch order, a decision of unimaginable weight, was issued, the corresponding launch codes would be transmitted to the various silos. These codes originated either from Strategic Air Command (SAC) Headquarters or its designated backup facility in California. The signal itself was an audio transmission, a sequence of a thirty-five-letter code, the phonetic alphabet spelling out the potential end of the world.

Upon receipt, the two missile operators stationed deep within the control room of each silo would meticulously record the code in their notebooks. A critical step, they would then compare their recordings. Only if the codes matched perfectly would both operators proceed to a distinct red safe, a repository of the ultimate launch documents. This safe was a physical manifestation of the dual-key control system, featuring a separate lock for each operator. Each operator possessed a unique combination, known only to themself, preventing any single individual from unilaterally accessing the launch materials.

Inside this highly secure safe lay a series of paper envelopes, each marked with two letters on its front. Embedded within the thirty-five-letter code originally sent from HQ was a shorter, seven-letter sub-code. The first two letters of this sub-code indicated precisely which envelope was to be opened. Within that envelope, a small, plastic “cookie” would be found, imprinted with five more letters. If these five letters on the cookie perfectly matched the remaining five digits of the sub-code, the launch order was officially authenticated. A bureaucratic ballet of ultimate destruction.

The comprehensive message also contained a distinct six-letter code, the digital key that would physically unlock the missile itself. This code was entered into a separate, specialized system, which, upon verification, would trigger the opening of a butterfly valve on one of the critical oxidizer lines feeding the missile’s engines. Once this valve was opened, the missile was, irrevocably, ready to launch. Other portions of the message detailed the precise launch time, which could be an immediate directive or a designated moment in the future, adding another layer of chilling precision to the process.

When the designated launch time arrived, the two operators, separated by a physical distance too great for one person to reach both, would simultaneously insert their keys into their respective control panels. They would then turn these keys to the launch position. This action had to be executed within a narrow two-second window of each other and held for a full five seconds. This physical separation and simultaneous action requirement was a cornerstone of the two-man rule, a deliberate redundancy designed to prevent accidental or unauthorized launch.

Successfully turning and holding the keys would initiate the complex, irreversible missile launch sequence. First, the Titan II’s onboard batteries would be rapidly charged to full capacity, and the missile would autonomously disconnect itself from the silo’s external power supply, becoming an independent, self-sufficient entity. Then, with a groan of hydraulics and steel, the colossal silo doors would slide open, triggering a chillingly benign “SILO SOFT” alarm within the control room. The Titan II’s guidance system would then rapidly configure itself, ingesting the latest targeting data, and assume complete control of the missile. Finally, the main engine ignition would occur, a deafening roar echoing through the silo. Thrust would be allowed to build for a few agonizing seconds, ensuring full power, before the massive supports holding the missile firmly in place within the silo were explosively released using precisely timed pyrotechnic bolts . With a final, violent shudder, the missile would then begin its ascent, lifting off on a column of fire and fury. [5]

Development

The formidable Titan rocket family first took root in October 1955, a direct consequence of the escalating Cold War and the imperative to establish a robust strategic deterrent. The Air Force, recognizing the burgeoning need for intercontinental reach, awarded the Glenn L. Martin Company a pivotal contract to develop an intercontinental ballistic missile . This initial endeavor culminated in what became known as the HGM-25A Titan I , a groundbreaking system that earned the distinction of being the nation’s first two-stage ICBM and, critically, the first to be based in underground missile silos .

However, the relentless pace of technological advancement and strategic necessity meant that improvements were always on the horizon. The Martin Company, ever attuned to the evolving landscape of warfare, quickly recognized the potential for further enhancement of the Titan I design. They presented a compelling proposal to the U.S. Air Force for an improved version – a missile that would not only carry a larger warhead, but also boast a greater range, superior accuracy, and, perhaps most crucially, the ability to launch with unprecedented speed. This vision materialized in June 1960, when the Martin company secured a contract for the development of this new, more formidable missile, officially designated the SM-68B Titan II.

The Titan II was a significantly more robust beast than its predecessor, weighing a full 50% more than the Titan I. This increased mass was distributed across a longer first stage and a second stage of larger diameter, optimizing its performance. The most revolutionary aspect of the Titan II, however, lay in its propellant system. Unlike the Titan I, which relied on liquid oxygen as an oxidizer – a cryogenic substance that required loading immediately before launch, necessitating the missile to be laboriously raised from its silo and fueled in a time-consuming sequence – the Titan II embraced storable propellants. This consisted of Aerozine 50 fuel, a precise 1:1 mixture of hydrazine and unsymmetrical dimethylhydrazine (UDMH) , paired with dinitrogen tetroxide as the oxidizer. This chemical marriage was a strategic masterstroke: these hypergolic propellants ignited spontaneously upon contact, eliminating the need for complex ignition systems and, more importantly, allowing the missile to remain fully fueled within its silo for extended periods. This meant that the Titan II could be launched within a mere 60 seconds directly from its hardened underground position, a decisive advantage in a game measured in minutes.

Yet, this efficiency came with a chilling caveat. The very hypergolic nature that enabled rapid launch also rendered these propellants exceptionally dangerous to handle. Leaks, as tragically demonstrated on multiple occasions, could (and did) lead to violent explosions, and the fuel itself was notoriously corrosive and highly toxic, posing severe health risks to personnel. Despite these inherent dangers, the strategic imperative for a rapid-response ICBM outweighed the formidable safety concerns, underscoring the desperate calculus of the Cold War.

The first flight of the Titan II occurred in March 1962, marking the beginning of its operational life. By October 1963, the missile, now officially designated LGM-25C, achieved initial operating capability, a grim milestone in the arms race. The Titan II was designed to carry a single, immensely powerful W-53 nuclear warhead encapsulated within a Mark 6 re-entry vehicle . This warhead boasted a staggering range of 8,700 nautical miles (10,000 mi; 16,100 km) and delivered a yield of 9 megatons . This truly impressive destructive power was guided to its target with chilling precision using an advanced inertial guidance unit . The 54 deployed Titan IIs, each a sentinel of potential apocalypse, formed the formidable backbone of America’s strategic deterrent force during a critical period, until the widespread deployment of the more numerous and solid-fueled LGM-30 Minuteman ICBMs throughout the early to mid-1960s. In a rather stark twist of fate, twelve Titan IIs were also repurposed and flown in NASA’s ambitious Project Gemini crewed space program in the mid-1960s, a testament to the versatility of a rocket designed for entirely different, more destructive, ends. [6]

The Department of Defense, ever contemplating the next level of destructive power, once projected that a Titan II missile could eventually accommodate a warhead with an unimaginable 35 megaton yield, based on anticipated technological improvements. Thankfully, this particular nightmare scenario never materialized; that warhead was never developed or deployed. Had it been, it would have been among the most powerful weapons ever conceived, boasting almost double the power-to-weight ratio of the already terrifying B41 nuclear bomb . [7] A chilling glimpse into what could have been, a testament to the fortunate limitations of human ambition.

• Titan II rocket launch with Clementine spacecraft (25 January 1994). The repurposed missile, still serving, but for a less destructive purpose.
• Titan-II 23G-9 B-107 carrying DMSP-5D3 F-16 Final Titan II launch 18 Oct 2003. The last hurrah for a Cold War icon.

Launch history and development

This section, a chronicle of triumph and rather spectacular failure, certainly needs additional citations for verification . One can only imagine the footnotes required to fully capture the sheer audacity and occasional absurdity of these early launches. Please, by all means, help improve this article by adding citations to reliable sources in this section. Unsourced material, like an uncontrolled rocket, may be challenged and removed. (June 2014) ( Learn how and when to remove this message )

The inaugural flight of the Titan II, Missile N-2, lifted off with a promising roar on 16 March 1962 from Launch Complex 16 (LC-16) at Cape Canaveral . It performed exceptionally well, soaring 5,000 miles (8,000 km) downrange and depositing its re-entry vehicle precisely into the Ascension splash net. A near-perfect debut, save for one rather significant problem: a disconcertingly high rate of longitudinal vibrations during the first stage burn. While this “pogo oscillation” – a rather undignified dance for a weapon of mass destruction – didn’t derail the Air Force’s missile launches, NASA officials, with their precious human cargo in mind, were understandably concerned that such a phenomenon would be decidedly harmful to astronauts on a crewed Gemini flight.

The second launch, Missile N-1, followed on 7 June from LC-15. First stage performance was almost nominal, but the second stage developed critically low thrust, later traced to a restriction in the gas generator feed. The Range Safety Officer, faced with a faltering missile, had to send a manual shutdown command to the second stage, resulting in a premature re-entry vehicle separation and impact well short of the intended target point. The third launch, Missile N-6 on 11 July, was, against the odds, completely successful.

Despite these early successes, the nagging “pogo problem” – the nickname NASA engineers, with their usual flair for the dramatic, invented for the Titan’s vibration issue, thinking it resembled the action of a pogo stick [8] – persisted. But pogo wasn’t the Titan II’s only early headache. The 25 July test (Vehicle N-4) had been scheduled for 27 June, but was delayed for a month by a truly spectacular pre-launch incident: the Titan’s right engine experienced such severe combustion instability at ignition that the entire thrust chamber violently broke off the booster and plummeted into the flame deflector pit, landing a mere 20 feet from the pad. The Titan’s onboard computer, with a commendable sense of self-preservation, shut down the engines the moment thrust loss was detected. The culprit? A bit of cleaning alcohol carelessly left in the engine. The universe, it seems, has a dark sense of humor, especially when humans leave cleaning supplies where they don’t belong in a nuclear missile. A new set of engines had to be ordered from Aerojet, and the missile finally lifted off from LC-16 on the morning of 25 July. The flight proceeded entirely according to plan through the first stage burn, but the second stage malfunctioned yet again when the hydraulic pump failed, causing thrust to drop by nearly 50%. The computer system, in a valiant but ultimately futile effort, compensated by running the engine for an additional 111 seconds until propellant depletion occurred. Because the computer had not sent a manual cutoff command, the re-entry vehicle separation and vernier solo phase never happened. Impact occurred a disappointing 1,500 miles (2,400 km) downrange, precisely half the planned distance. [9]

The subsequent three launches – Missile N-5 (12 September), N-9 (12 October), and N-12 (26 October) – were entirely successful, a brief respite from the drama. However, the persistent pogo problem remained, a literal internal struggle for the rocket, and the booster simply could not be considered “man-rated” until this critical flaw was addressed. Martin–Marietta, in a bid to tame the beast, introduced a surge-suppressor standpipe into the oxidizer feed line in the first stage. But when this “fix” was tested on Titan N-11 on 6 December, the effect was, ironically, to worsen the pogo in the first stage. The missile vibrated so violently that unstable engine thrust resulted, triggering the first stage pressure switch and prematurely terminating thrust. The second stage then separated and began its burn, but due to the improper speed and attitude at separation, the guidance system malfunctioned, leading to an unstable flight trajectory. Impact occurred a mere 700 miles (1,100 km) downrange, a stark reminder that sometimes, the cure is worse than the disease. [10]

Vehicle N-13, launched a mere 13 days later, eschewed the ill-fated standpipes. Instead, engineers opted for increased pressure in the first stage propellant tanks, a measure that did contribute to reducing vibration. Additionally, the oxidizer feedlines were fabricated from aluminum instead of steel, a material change aimed at improving performance. Despite these modifications, the exact root cause of the pogo phenomenon remained stubbornly unclear, a vexing problem for NASA engineers who were trying to put humans on top of this shaking behemoth. [11]

The tenth Titan II flight, Vehicle N-15, took place on 10 January, notable as the only nighttime Titan II test. While it appeared that the pogo problem was largely contained on this particular flight, the second stage once again suffered a thrust loss, attributed to a restriction in the gas generator. Consequently, it only achieved half its intended range. Interestingly, while previous second stage issues had been somewhat blamed on pogo, this could not be the case for N-15, highlighting other systemic problems. Meanwhile, combustion instability, a truly alarming prospect for a rocket, continued to be an issue, confirmed by Aerojet static-firing tests which revealed that the LR91 Liquid-propellant engine struggled to achieve smooth burning after the initial shock of startup. [11]

Efforts to “human-rate” the Titan II for crewed spaceflight also ran afoul of the inherent bureaucratic friction between the Air Force and NASA. The Air Force’s primary objective was, quite understandably, to develop a robust missile system for strategic deterrence, not a meticulously safe launch vehicle for Project Gemini . They were only interested in technical improvements to the booster insofar as they directly supported their missile program. On 29 January, the Air Force Ballistic Systems Division (BSD) declared, with rather dismissive finality, that pogo in the Titan had been reduced sufficiently for inter-continental ballistic missile (ICBM) use and that no further improvements needed to be made. While increasing pressure in the propellant tanks had indeed reduced vibration, there were structural limits to how much pressure could be safely applied, and in any case, the results were still deemed unsatisfactory from NASA’s more stringent perspective. While BSD initially attempted to find a compromise, they ultimately decided that the time, resources, and inherent risk involved in trying to further mitigate pogo for NASA’s sake were not worth it, and that the ICBM program ultimately held first priority. [12]

Despite the Air Force’s conspicuous lack of enthusiasm for human-rating the Titan II, General Bernard Adolph Schriever , a key figure in the missile program, offered assurances that any lingering problems with the booster would eventually be resolved. BSD, however, stubbornly maintained their stance, declaring that 0.6 Gs of vibration was “good enough” for their purposes, despite NASA’s much stricter goal of 0.25 Gs, and adamantly stated that no more resources were to be expended on the matter. On 29 March 1963, Schriever convened a meeting with officials from Space Systems Development (SSD) and BSD at his headquarters at Andrews Air Force Base in Maryland, but the discussions proved far from encouraging. Brig. Gen John L. McCoy, who directed the Titan Systems Program Office, firmly reiterated BSD’s position: the pogo and combustion instability issues in the Titan were not considered a serious impediment to the ICBM program, and attempting to improve them further for NASA’s benefit would be too difficult and risky at that juncture. Meanwhile, both Martin–Marietta and Aerojet, the primary contractors, argued that most of the major development problems with the booster had, in fact, been solved, and that only a little more work would be required to truly man-rate it. They proposed adding more standpipes to the first stage and incorporating baffled injectors into the second stage, a hopeful but perhaps overly optimistic assessment. [13]

A subsequent closed-door meeting between NASA and Air Force officials saw the former forcefully arguing that without a definitive solution to the pogo and combustion instability problems, the Titan simply could not safely transport human passengers. However, by this point, the Air Force was assuming an increasingly significant role in the Project Gemini program, driven by proposed military applications for the spacecraft, such as the Blue Gemini project. During the first week of April, a joint plan was finally drafted. This agreement aimed to reduce pogo to meet NASA’s stringent target and to implement design improvements across both Titan stages. Crucially, the program carried two significant conditions: the ICBM program retained absolute first priority and was not to be delayed by Gemini, and General McCoy would retain final say on all matters, effectively giving the Air Force ultimate authority. [14][15]

Meanwhile, the Titan II development program continued to encounter a series of frustrating difficulties throughout the first half of 1963, proving that even the most meticulously planned projects can unravel in spectacular fashion. On 16 February, Vehicle N-7, undertaking a silo test launch from Vandenberg Air Force Base in California, malfunctioned almost immediately after liftoff. An umbilical cord, intended to detach cleanly, instead failed to separate properly, violently ripping out critical wiring in the second stage. This not only cut power to the missile’s guidance system, rendering it blind, but also, terrifyingly, prevented the range safety charges from being armed. The missile lifted from the silo with a continuous, uncontrolled roll, and at approximately T+15 seconds, precisely when the pitch and roll program would normally commence, it began a sudden, sharp downward pitch. Launch crews, deep within their bunkers, were thrown into a panic: they had a missile that was not only completely out of control, but also could not be destroyed, raising the terrifying prospect that it might veer off course and crash into a populated area. Fortunately, the Titan’s erratic flight came to an end after it flipped almost completely upside-down, a maneuver that inadvertently caused the second stage to separate from the stack. The Inadvertent Separation Destruct System (ISDS) then activated, as designed, and blew up the first stage. Most of the debris from the missile fell harmlessly offshore or on the beach, and the second stage impacted the water mostly intact, though its oxidizer tank had been ruptured by flying debris from the first stage’s destruction. Navy crews immediately launched a salvage effort, attempting to recover the re-entry vehicle and, more importantly, the guidance system from the sea floor. While the re-entry vehicle was successfully located and dredged up along with parts of the second stage, the crucial guidance system was never recovered. [16]

The mishap was meticulously traced to an unforeseen design flaw in the silo’s construction – specifically, there was insufficient clearance for the umbilicals to detach cleanly, which inevitably resulted in critical wiring being torn from the Titan. The problem was eventually resolved by adding extra lanyards to the umbilicals, providing them with sufficient “play” to separate without damaging the missile. Despite the terrifying nature of the incident, the flight was paradoxically considered a “partial” success in that the Titan had, at least, successfully cleared the silo. The inadvertent rolling motion of the vehicle may have also played a crucial, if accidental, role in preventing an even worse disaster, as it added a degree of stability and prevented the missile from colliding with the silo walls during its chaotic ascent. [17]

While Missile N-18 flew successfully from the Cape on 21 March, the problems persisted elsewhere. N-21 suffered yet another second stage failure, having already been delayed several weeks due to a recurring issue of first stage thrust chambers breaking off prior to launch. This was followed by a successful launch from VAFB on 27 April, when Missile N-8 performed as expected. However, N-14 (9 May), launched from LC-16 at the Cape, experienced another early second stage shutdown, this time caused by a leaking oxidizer line – a constant reminder of the inherent dangers of the hypergolic propellants. Missiles N-19 on 13 May (VAFB) and N-17 on 24 May (CCAS) were successful, but the statistics were grim: of 18 Titan II launches so far, only 10 had managed to meet all of their objectives. On 29 May, Missile N-20 was launched from LC-16, equipped with a new round of pogo-suppressing devices, a desperate attempt to tame the beast. Unfortunately, a fire erupted in the thrust section soon after liftoff, leading to an inevitable loss of control during ascent. The missile pitched down violently, and the second stage separated from the stack at T+52 seconds, triggering the ISDS, which promptly blew the first stage to pieces. The second stage was then manually destroyed by the Range Safety Officer shortly thereafter, a grim finale. No useful pogo data was obtained due to the early termination of the flight, and the accident was ultimately traced to stress corrosion of an aluminum fuel valve, which resulted in a propellant leak that ignited upon contact with hot engine parts. The missile, it seems, had a temper. [18]

The very next flight was Missile N-22, a silo test from Vandenberg Air Force Base on 20 June, but once again, the second stage lost thrust due to a persistent gas generator restriction. At this point, the Ballistic Systems Division (BSD) made the inevitable decision to suspend further flights. The numbers were stark: of the 20 Titan launches conducted, seven would have necessitated the abort of a crewed launch, a failure rate entirely unacceptable for NASA. General McCoy was now faced with the daunting task of ensuring the success of 12 of the 13 remaining scheduled tests. With the ICBM program’s strategic priority firmly established, the pursuit of pogo suppression for Gemini had to be, once again, shelved. [18]

On the other hand, it’s worth noting that only Missile N-11 suffered a malfunction directly attributable to pogo oscillation, and the combustion instability issue, while a problem in static firings, had not actually occurred in any real flights. It became increasingly clear that nearly all Titan II failures, with the exception of N-11, were caused by recurring issues such as gas generator restrictions, broken plumbing, or faulty welds. The finger of blame began to point squarely at Aerojet, the engine manufacturer. A visit by Manned Spacecraft Center (MSC) officials to Aerojet’s Sacramento, California , plant in July revealed a truly alarming array of “extremely careless handling and manufacturing processes.” This damning discovery prompted the immediate launch of a systematic, comprehensive effort to drastically improve the quality control of the LR-87 engines. This initiative encompassed extensive redesigns of various components aimed at enhancing reliability, alongside targeted fixes to finally resolve the persistent gas generator restriction issue. [19][18] When your doomsday device’s engines are built with “extremely careless handling,” perhaps a fundamental rethink is indeed in order.

• 1965 graph of Titan II launches (middle), cumulative by month with failures highlighted (pink) along with USAF SM-65 Atlas and NASA use of ICBM boosters for Projects Mercury and Gemini (blue). Apollo-Saturn history and projections shown as well. A visual representation of the inherent chaos in early rocketry.

Service history

The LGM-25C Titan II entered service in 1963 and, against initial expectations, remained operational until 1987. It was a rather persistent instrument of deterrence. At its peak, the force comprised 54 Titan II Strategic Air Command missiles, each a silent sentinel of potential global catastrophe.

These 54 Titan II missiles were maintained on a relentless 24-hour continuous alert, a constant, underlying hum of tension throughout the Cold War. They were strategically dispersed, with 18 missiles each surrounding three primary bases: Davis–Monthan Air Force Base near Tucson, Arizona ; Little Rock Air Force Base in Arkansas; and McConnell Air Force Base in Wichita, Kansas . This dispersal was not merely for convenience; it was a critical component of the second-strike strategy, ensuring that even if one base were targeted, others would remain operational, ready to deliver their devastating response. [20]

Mishaps

The operational history of the Titan II, despite its critical role, was unfortunately punctuated by a series of significant mishaps, a stark reminder of the inherent dangers of handling such powerful and volatile systems.

On 9 August 1965, a truly horrific incident unfolded. A fire erupted within a missile silo (Site 373–4) near Searcy, Arkansas , leading to a catastrophic loss of oxygen. The cause? A high-pressure hydraulic line was inadvertently severed by an oxyacetylene torch during routine maintenance. What could possibly go wrong? The resulting blaze tragically claimed the lives of 53 people, predominantly civilian repairmen who were simply trying to keep the system operational. [21][22][23][24][25] The fact that the 750-ton silo lid was closed at the time, ironically designed for protection, sealed the fate of many, contributing to a rapidly reduced oxygen level for the few men who initially survived the inferno. Only two individuals managed to escape alive, both sustaining injuries from the fire and smoke, one by desperately groping his way through complete darkness to the exit. [26] In a macabre twist, the missile itself, the very instrument of potential annihilation, survived the ordeal remarkably undamaged. [27]

Years later, on 20 June 1974, a launch from Silo 395C at Vandenberg Air Force Base in California, part of an anti-ballistic missile program, suffered a critical failure. One of the two start cartridges, essential for ignition, failed to activate due to faulty wiring. The launch, rather inconveniently, was being witnessed by an entourage of general officers and congressmen. The Titan subsequently experienced severe structural failure, with both its highly corrosive hypergolic fuel tank and the oxidizer tank leaking profusely, creating a deadly pool of volatile chemicals at the bottom of the silo. A large number of civilian contractors, tasked with maintaining the system, were hastily evacuated from the Command and Control Bunker, narrowly escaping a potentially catastrophic explosion. [ citation needed ]

Then, on 24 August 1978, another incident underscored the insidious dangers of the hypergolic propellants. SSgt Robert Thomas was tragically killed at a missile site outside Rock, Kansas , when a missile within its silo developed a leak, releasing its deadly fuel. Another airman, A1C Erby Hepstall, later succumbed to lung injuries sustained during the spill, a testament to the lingering, invisible threat posed by these chemicals, even without a fiery explosion. [28][29][30][31]

• Main article: 1980 Damascus Titan missile explosion

Perhaps the most infamous of all Titan II mishaps occurred on 19 September 1980, culminating in a major explosion at Silo 374-7, located near Damascus, Arkansas . The chain of events began with a truly mundane cause: a socket from a large socket wrench inexplicably rolled off a platform, fell, and, with a chilling precision, punctured the missile’s lower-stage fuel tank. This seemingly innocuous event initiated a catastrophic fuel leak. Given the extremely volatile nature of the hypergolic propellants involved, the entire missile, a colossal tube of barely contained energy, violently exploded a few hours later. The blast tragically killed an Air Force airman, SrA David Livingston, and completely destroyed the silo. [32]

In a truly dark twist of fate, this was the very same missile that had been present in the silo during the deadly 1965 fire at site 373–4, having been refurbished and subsequently relocated after that earlier incident. A testament to human optimism, or perhaps just a lack of available spares. Miraculously, however, due to the warhead’s robust, built-in safety features, it did not detonate. Instead, it was found, somewhat ignominiously, about 300 feet (100 m) away from the destroyed silo, a chillingly close call with nuclear catastrophe. [32] The gravity of this event resonated deeply, inspiring the 1988 television movie Disaster at Silo 7 , which was loosely based on the incident. [33] More recently, author Eric Schlosser published a comprehensive and chilling book centered on the accident, Command and Control: Nuclear Weapons, the Damascus Accident, and the Illusion of Safety, in September 2013, providing a detailed account of the near-disaster. [34] A documentary film adaptation, also titled Command and Control , based on Schlosser’s book, aired on PBS on 10 January 2017, ensuring that this stark lesson in the fragility of safety was not forgotten.

Retirement

The LGM-25C Titan II was originally projected to have a service life of a mere 5–7 years. Yet, in a testament to either its robust design or, perhaps, a certain bureaucratic inertia, it ended up serving for far longer than anyone initially anticipated. This extended tenure was partly due to its impressive size and substantial throw-weight , capabilities that remained valuable even as newer, more advanced missiles emerged. Leadership within the USAF and Strategic Air Command (SAC) were visibly reluctant to retire the Titan II. While these missiles constituted only a small fraction of the total number of intercontinental ballistic missiles on standby, they represented a disproportionately significant portion of the total megatonnage deployed by Air Force ICBMs, making them a difficult asset to relinquish.

It is a common misconception that the Titan IIs were decommissioned as a direct result of a weapons reduction treaty. In reality, their retirement was a more pragmatic affair, a consequence of an ongoing weapons modernization program and the inexorable march of obsolescence. The inherent volatility of their liquid fuel and the inevitable problem of aging seals meant that the Titan II missiles had, in fact, been initially scheduled for retirement as early as 1971. By the mid-1970s, the original AC Delco inertial guidance system had become unequivocally obsolete, with spare parts no longer readily obtainable. This forced an upgrade, and the guidance packages in the entire stock of Titan missiles were replaced by the more modern Universal Space Guidance System. However, following the two particularly notorious accidents in 1978 and 1980, respectively, the long-overdue deactivation of the Titan II ICBM system finally commenced in July 1982. The very last Titan II missile, situated at Silo 373-8 near Judsonia, Arkansas, was officially deactivated on 5 May 1987, marking the end of an era.

With their warheads safely removed and their destructive potential neutralized, the deactivated missiles were initially placed in storage at Davis–Monthan Air Force Base , Arizona, and the former Norton Air Force Base , California. Later, these hulking relics of the Cold War were systematically broken up for salvage, a process that concluded by 2009. [35] From instruments of potential apocalypse to static displays of human folly, or simply scrap metal.

Remarkably, a single Titan II complex, part of the former strategic missile wing at Davis–Monthan Air Force Base , managed to escape the fate of destruction after decommissioning. This site is now preserved and open to the public as the Titan Missile Museum at Sahuarita, Arizona . The missile resting dramatically in its silo there is indeed a real Titan II, but it was a training missile, a ghost of its former self, and thus never contained the volatile fuel, oxidizer, or, crucially, a live warhead. [36] A tourist attraction dedicated to what almost happened.

The following table details the number of Titan II missiles in active service, year by year, offering a stark numerical account of their dwindling presence: [ citation needed ]

• 1963: 56
• 1964: 59
• 1965: 59
• 1966: 60
• 1967: 63
• 1968: 59 (with 3 deactivated at Vandenberg Air Force Base )
• 1969: 60
• 1970: 57 (another 3 deactivated at Vandenberg Air Force Base )
• 1971: 58
• 1972: 57
• 1973: 57
• 1974: 57
• 1975: 57
• 1976: 58
• 1977: 57
• 1978: 57
• 1979: 57
• 1980: 56 (the year of the Damascus explosion, clearly taking its toll)
• 1981: 56 (President Ronald Reagan publicly announces the retirement of Titan II systems)
• 1983: 53
• 1984: 43 (marking the completion of the Davis–Monthan Air Force Base site closure)
• 1985: 21
• 1986: 9 (with the Little Rock Air Force Base closure completed in 1987)

Operational units

Each LGM-25C Titan II ICBM wing was a meticulously organized, distributed network of destruction, equipped with eighteen missiles. These were typically divided into nine missiles per squadron, with each individual missile housed in its own dispersed launch silo, strategically spread across the general area of the assigned base. This dispersal was a critical aspect of survivability and retaliatory capability, ensuring that a single strike could not neutralize an entire squadron. For more granular details on the geographic locations and specific information about these assigned launch sites, one might consult the respective squadron articles. [37]

• A real Alert Real Response AAFM September 1999.
• class=notpageimage| Map of LGM-25C Titan II Operational Squadrons. A chilling cartography of Cold War readiness.

The principal operational units responsible for the Titan II’s deployment and readiness included:

• 308th Strategic Missile Wing : Active from 1 April 1962 to 18 August 1987, based at Little Rock Air Force Base , Arkansas. This wing comprised:
  • 373d Strategic Missile Squadron
  • 374th Strategic Missile Squadron
  • 308th Missile Inspection and Maintenance Squadron
• 381st Strategic Missile Wing : Active from 1 March 1962 to 8 August 1986, based at McConnell Air Force Base , Kansas. This wing comprised:
  • 532d Strategic Missile Squadron
  • 533d Strategic Missile Squadron
• 390th Strategic Missile Wing : Active from 1 January 1962 to 31 July 1984, based at Davis–Monthan Air Force Base , Arizona. This wing comprised:
  • 570th Strategic Missile Squadron
  • 571st Strategic Missile Squadron
• 1st Strategic Aerospace Division : Based at Vandenberg Air Force Base , California. This division included:
  • 395th Strategic Missile Squadron , operational from 1 February 1959 to 31 December 1969. This squadron uniquely operated three silos specifically for technical development and testing purposes between 1963 and 1969, serving as a proving ground for the missile’s capabilities.

It’s worth noting that in 1959, a fifth Titan II installation was proposed, which would have encompassed the 13th and 14th squadrons at the former Griffiss Air Force Base , New York. However, this particular expansion of the doomsday infrastructure was, thankfully, never constructed. [38] A small mercy, perhaps, that some plans for global annihilation never quite materialize.

Titan II missile disposition

The “disposition” of these instruments of terror, once their active service concluded, followed a meticulous, if somewhat morbid, accounting. This section needs additional citations for verification . By all means, help improve this article by adding citations to reliable sources in this section. Unsourced material may be challenged and removed. (November 2011) ( Learn how and when to remove this message )

A total of thirty-three Titan-II Research Test (N-type) missiles were fabricated. All but one of these were subsequently launched, either from Cape Canaveral Air Force Station , Florida, or Vandenberg Air Force Base , California, during the intensive testing period of 1962–64. The sole surviving N-10, bearing the rather unassuming designation AF Ser. No. 61-2738/60-6817, now resides in its silo at the Titan Missile Museum (ICBM Site 571–7), operated by the Pima Air & Space Museum in Green Valley, south of Tucson, Arizona, just off Interstate-19. [39] A monument to a road not taken, or rather, a button not pushed.

Twelve Titan-II Gemini Launch Vehicles (GLVs) were produced, purpose-built for their role in the crewed space program. All of these were launched from what was then Cape Kennedy Air Force Station between 1964 and 1966. The top half of GLV-5, with serial number 62-12560, was successfully recovered offshore following its launch and is now on display at the U.S. Space & Rocket Center in Huntsville, Alabama, a relic of humanity’s dual ambitions.

One hundred and eight Titan-II ICBM (B-Type) missiles were produced for operational deployment. Of these, forty-nine were launched for testing purposes at Vandenberg Air Force Base from 1964 to 1976. Two were tragically lost in accidents within their silos, a stark reminder of their inherent danger. One B-2 missile, AF Ser. No. 61-2756, was donated to the U.S. Space & Rocket Center in Huntsville, Alabama, in the 1970s, its destructive purpose retired for educational display.

The remaining 56 surviving missiles, withdrawn from their silos and individual base stores, were all transferred to the then-Norton Air Force Base , California, during the 1980s. There, they were carefully stored under protective plastic coverings, with helium pumped into their engine components to prevent rust – a meticulous effort to preserve dormant power. Norton Air Force Base buildings 942 and 945 served as their temporary mausoleum; Building 945 housed 30 missiles, while Building 942 held 11 full missiles plus a single first stage. These buildings also contained extra stage engines and interstages, awaiting their next, less destructive, phase. By the end of the decade, 14 full missiles and one extra second stage had been transferred from Norton Air Force Base to the manufacturer, Martin Marietta , at Martin’s Denver, Colorado, facility for refurbishment. Thirteen of these 14 were subsequently launched as Titan 23Gs , finding a new career as space launch vehicles. One missile, B-108, AF Ser. No. 66-4319 (which served as 23G-10, the spare for the 23G program), eventually found its way to the Evergreen Aviation & Space Museum in McMinnville, Oregon. Intriguingly, B-34 Stage 2 was delivered from Norton Air Force Base to Martin Marietta on 28 April 1986, but was never modified to a G-series, nor was it officially listed as arriving or being destroyed at the 309th Aerospace Maintenance and Regeneration Group at Davis–Monthan Air Force Base ; it remains, to this day, unaccounted for within the open-source public domain. A small piece of history, perhaps, still out there, waiting to be rediscovered, or simply forgotten.

Of the original 42 B-series missiles that remained, 41 full missiles and one first stage were at Norton Air Force Base , with the second stage of the unaccounted B-34 still at Martin. Thirty-eight of these, along with one second stage, were subsequently stored outside at the Aerospace Maintenance and Regeneration Center (AMARC ), now known as the 309th Aerospace Maintenance and Regeneration Group (309 AMARG), adjacent to Davis–Monthan Air Force Base , awaiting their final destruction between 2004 and 2008. Four of these 42 were spared this fate and sent to various museums, preserving them for public contemplation.

The deactivation of the various Air Force Base silos occurred within these date ranges:

• Davis–Monthan Air Force Base : 10 August 1982 – 28 June 1984
• McConnell Air Force Base : 31 July 1984 – 18 June 1986
• Little Rock Air Force Base : 31 May 1985 – 27 June 1987

Movement dates for the Titan II missiles themselves were also meticulously tracked:

• Titan II Bs moved to Norton Air Force Base between: 12 March 1982 through 20 August 1987
• Missiles relocated to AMARC at Davis–Monthan Air Force Base prior to: April 1994 closure of Norton Air Force Base due to BRAC 1989 action
• Titan II Bs delivered to Martin Marietta /Denver between: 29 February 1986 through 20 September 1988
• Titan II Bs delivered to AMARC: 25 October 1982 through 23 August 1987
• Titan II Bs destroyed at AMARC: 7 April 2004 through 15 October 2008
  • Specific destruction periods at AMARC: 7 April 2004 (x2); 17 August 2005 (x5); 12–17 January 2006 (x10); 9 August 2007 (x3); 7–15 October 2008 (x18); 2 shipped out to museums, August 2009.

The official count of all 108 Titan-2 ‘B’ Series Vehicles delivered to the USAF breaks down as follows: 49 were used for test launches, 2 were tragically lost in silo accidents, 13 were repurposed for space launches, 6 found their final resting places in museums, 37.5 (accounting for the missing half-missile) were destroyed at AMARC. This sum perfectly reconciles the total of 108.

• Norton Air Force Base Bldg 942 June 1989.
• Norton Air Force Base Bldg 945 June 1989.
• Titan-2 ICBMs in storage at Norton Air Force Base 1989. A graveyard of past anxieties.
• Titan-2 ICBMs in storage at Norton Air Force Base 1989.
• The remaining 38 and one half missiles awaiting destruction at Davis–Monthan Air Force Base in 2006.

The following is a list of Titan-II surviving missiles and their current museum locations within the United States, allowing the public to gaze upon these relics of a tense past:

• GLV-5, AF Ser. No. 62-12560: The top half of its Stage 1 was recovered offshore after its launch and is now on display at the U.S. Space & Rocket Center in Huntsville, Alabama.
• N-10, AF Ser. No. 61-2738/60-6817: Resides in its original silo at the Titan Missile Museum (ICBM Site 571–7), located southwest of Davis–Monthan Air Force Base in Green Valley, Tucson, Arizona.
• B-2, AF Ser. No 61–2756: Donated to the U.S. Space & Rocket Center , Huntsville, Alabama, in the 1970s.
• B-5, AF Ser. No. 61–2759: On display at the National Museum of the United States Air Force , located at Wright-Patterson Air Force Base , Dayton, Ohio. [41]
• B-14/20, AF Ser. No. 61–2768: Housed at the Stafford Museum, Oklahoma.
• B-44/16, AF Ser. No. 62–0025: Can be found at the National Museum of Nuclear Science & History , adjacent to Kirtland Air Force Base , Albuquerque, New Mexico.
• B-104, AF Ser. No 66–4315: Part of the Spaceport USA Rocket Garden at the Kennedy Space Center , Florida.
• B-108, AF Ser. No. 66-4319 (which served as 23G-10, the spare for the 23G program): Exhibited at the Evergreen Aviation and Space Museum in McMinnville, Oregon.

Titan II launch vehicle

• Main articles: Titan (rocket family) , Titan II GLV , and Titan 23G

The Titan II space-launch vehicles represent a fascinating repurposing of a destructive technology. These were either purpose-built as dedicated space launchers – a comparatively benign role – or, more commonly, were decommissioned ICBMs that underwent extensive refurbishment and were equipped with the necessary hardware to serve as space launch vehicles. In a rather ironic twist of fate, every single one of the twelve Gemini capsules, including the ten that carried human crews, was propelled into orbit by these Titan II launchers. From instruments of global annihilation to orbital workhorses, the journey was quite remarkable.

The Titan II space launch vehicle, whether purpose-built or refurbished, functioned as a two-stage liquid-fueled booster, specifically designed to provide a small-to-medium weight class capability for orbital insertion. It possessed the impressive ability to lift approximately 1,900 kg (4,200 lb) into a circular polar low-Earth orbit , making it a valuable asset for various satellite deployments. The first stage of this powerful vehicle was driven by a single ground-ignited Aerojet LR-87 liquid propellant rocket engine. This engine, a marvel of engineering, featured two combustion chambers and nozzles, yet was fed by a singular turbopump system, optimizing its efficiency. The second stage, providing the final push into space, was powered by an Aerojet LR91 Liquid-propellant engine , completing the sequence of a powerful, controlled ascent. [42]

By the mid-1980s, as the inventory of refurbished Atlas E/F missiles, which had served a similar secondary role as space launchers, began to dwindle, the Air Force sought a new solution. The logical choice was to reuse the now-decommissioned Titan IIs for space launch missions. In January 1986, the Martin Marietta Astronautics Group was awarded a significant contract to refurbish, integrate, and launch fourteen of these Titan II ICBMs to fulfill various government space launch requirements. These particular refurbished missiles were designated Titan 23G . The Air Force successfully launched the first Titan 23G space launch vehicle from Vandenberg Air Force Base on 5 September 1988, marking the beginning of this new chapter. NASA’s Clementine spacecraft, a mission to the Moon, was famously launched aboard a Titan 23G in January 1994, further cementing the missile’s unexpected legacy. All Titan 23G missions were conducted from Space Launch Complex 4 West (SLC-4W) on Vandenberg Air Force Base , operating under the operational command of the 6595th Aerospace Test Group and its subsequent organizational iterations, the 4th Space Launch Squadron and the 2nd Space Launch Squadron.

Ironically, the Titan 23G project, initially conceived as a cost-saving measure, proved to be less economical than anticipated. The expense involved in meticulously refurbishing these aging missiles for their new role as space launchers often turned out to be greater than the cost of simply flying a brand-new Delta booster, highlighting the often-unforeseen complexities of repurposing. Unlike the refurbished Atlas missiles, which were completely disassembled and rebuilt from the ground up, the Titan 23G underwent relatively few fundamental changes. The primary modifications involved replacing the warhead interface with a civilian payload adapter and integrating new range safety and telemetry packages. The engines themselves were merely given a brief static firing to verify their basic functionality, a rather minimal check for a system with such a volatile past. Of the 13 launches conducted in this program, there was one notable failure: in 1993, a Landsat satellite was placed into a useless orbit due to a malfunction of the satellite’s own kick motor, a reminder that even when the booster performs, other elements can fail. The very last Titan II launch, a final hurrah for this Cold War veteran, occurred on 18 October 2003, successfully deploying a DMSP weather satellite. This final flight, however, had been scheduled for launch in early 2001, but persistent problems with both the booster and the satellite itself had delayed it for over two years, a fittingly delayed, yet ultimately successful, end to a legacy of barely controlled power. In total, 282 Titan IIs were launched between 1962 and 2003, with 25 of these missions being dedicated space launches, a dual legacy of destruction and exploration.

See also

For those who simply cannot get enough of these glorious instruments of potential global annihilation, here are some related topics.

• Wikimedia Commons has media related to Titan (rocket).
• Strategic Air Command

Related development

• Titan (rocket family)
• HGM-25A Titan I
• Titan 23B
• ASC-15
• Blue Streak (missile)

Aircraft of comparable role, configuration, and era

• SM-65 Atlas
• R-36 (missile) (SS-18 Satan)
• DF-5

Related lists

• List of military aircraft of the United States
• List of missiles