This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| Atlas V Heavy | |
|---|---|
| Name | Atlas V Heavy |
| Manufacturer | United Launch Alliance |
| Country | United States |
| Status | Proposed / Conceptual |
| Family | Atlas |
| Boosters | 2 or 3 RD-180 strap-ons |
Atlas V Heavy The Atlas V Heavy is a conceptual heavy-lift variant of the Atlas V expendable launch vehicle proposed during development phases of the Atlas family. It was envisioned to increase payload capacity for missions under programs managed by the United States Department of Defense, National Aeronautics and Space Administration, and commercial customers such as Intelsat and SES S.A.. The concept drew on technologies and suppliers associated with United Launch Alliance, Aerojet Rocketdyne, and manufacturing sites like Decatur, Alabama and Cape Canaveral Space Force Station.
The Atlas V Heavy concept aimed to leverage the Atlas V Common Core Booster architecture to provide enhanced performance for low Earth orbit, geostationary transfer orbit, and interplanetary missions. It was positioned as a response to heavy-lift demands that included competition from vehicles such as the Delta IV Heavy, Falcon Heavy, and later heavy-lift proposals from Blue Origin and SpaceX. Stakeholders included program offices within the United States Air Force, commercial launch operators, and prime contractors such as Boeing and Lockheed Martin prior to the formation of United Launch Alliance.
Development work referenced legacy systems from the Atlas family, including propulsion heritage from the RD-180 first-stage engine produced by NPO Energomash and upper-stage expertise tied to the RL10 engine produced by Aerojet Rocketdyne. Design studies explored structural adaptations to support multiple Common Core Boosters arranged in parallel, avionics upgrades from heritage electronics used on Atlas V missions to support heavier payload telemetry requirements for programs like National Reconnaissance Office launches. Concepts also intersected with policy debates in the United States Congress over reliance on foreign propulsion and subsequent domestic engine initiatives such as those involving Blue Origin BE-4 development.
Proposed Atlas V Heavy configurations considered combinations of two or three strap-on cores, varying the number and size of solid rocket motors, and multiple upper-stage options including the Centaur upper stage and concepts for a dual-engine Centaur or an enhanced Centaur with larger propellant tanks. Configuration studies referenced mission profiles comparable to those of the Delta Cryogenic Second Stage and cross-compatibility considerations with payload fairings used by customers such as Eutelsat and Telesat.
As a conceptual derivative, Atlas V Heavy did not enter operational flight history separate from Atlas V; therefore there is no maiden flight to attribute to it. The Atlas family, however, has a documented operational record that includes launches supporting programs like Mars Science Laboratory, New Horizons, and numerous GPS launches. Lessons from Atlas V flight history, launch failures, and successes informed engineering trade-offs in heavy variant studies and contributed to risk assessments used by agencies such as the Defense Advanced Research Projects Agency.
Design studies for Atlas V Heavy targeted high-mass payloads including large communications satellites for operators such as DirecTV, scientific spacecraft for institutions like the Jet Propulsion Laboratory, and classified payloads for the National Reconnaissance Office. Conceptual mission sets included heavy interplanetary voyagers akin to Juno (spacecraft)-class missions, dual-satellite geostationary insertion, and potential human-rated cargo delivery for programs coordinated with NASA Johnson Space Center and launch infrastructure at Kennedy Space Center.
The Atlas V Heavy concept extrapolated from Atlas V baseline characteristics: a LOX/kerosene first-stage core powered by an RD-180 equivalent, a Centaur cryogenic upper stage using liquid hydrogen/liquid oxygen and RL10-derived engines, and strap-on boosters to augment thrust at liftoff. Estimated performance metrics varied by study, with projected increases in payload to low Earth orbit and geostationary transfer orbit when compared to single-core Atlas V variants. Structural and aerodynamic modifications considered center-of-gravity shifts, vehicle guidance updates tied to avionics suites used on Atlas V, and ground support changes at facilities such as Vandenberg Space Force Base.
Manufacture and integration concepts for Atlas V Heavy relied on industrial capabilities at supplier locations including Decatur, Alabama tank fabrication sites, propulsion integration facilities formerly operated by Rocketdyne contractors, and final assembly at launch complexes like those at Cape Canaveral Space Force Station and Vandenberg Space Force Base. Launch operations planning incorporated safety reviews by organizations such as the Federal Aviation Administration Office of Commercial Space Transportation and mission assurance processes from United Launch Alliance and partner primes. Ground support equipment, transport logistics via the BNSF Railway network and maritime channels, and pad modifications for heavy-lift processing were subjects of risk and cost studies by payload customers and government acquisition offices.