- \n
- ULA Forum Section<\/li>\n
- L2 Master Section<\/li>\n
- Click here to Join L2<\/li>\n<\/ul>\n
At the center of this row is the RD-180 engine, built by RD AMROSS, a U.S. joint venture of Pratt & Whitney Rocketdyne, located in West Palm Beach, Florida, and NPO Energomash of Khimki, Russia.<\/p>\n
Under the original joint-venture contract, Energomash was contracted to deliver 101 RD-180 engines, enough for 101 missions of the Atlas V, for the fixed price of $1 billion USD over the course of several years.<\/p>\n
Thus, the RD-180s could be used for any Atlas V mission \u2013 be it a commercial, civil, government, or national security payload.<\/p>\n
Aerospace industry analysis
<\/path>SpaceX launch tickets <\/path>Spaceflight history books <\/path>\n (adsbygoogle = window.adsbygoogle || []).push({});<\/p>\n
![\"2014-11-07](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2014\/11\/2014-11-07-01_09_01-Atlas_V_RD180.jpg-700%C3%97459-350x242.jpg\")
However, U.S.-imposed sanctions against Russia in 2014 relating to issues in Ukraine and the Crimea peninsula saw Russia impose a ban on yet-to-be-delivered RD-180s, eliminating those engines ULA did not already have possession of from use on U.S. military launches.<\/p>\nA subsequent Congressional ban against the further purchase of the Russian-made engines limited ULA and the Atlas V to its already existing stockpile of RD-180s.<\/p>\n
This, according to ULA and the U.S Department of Defence (DoD), placed into jeopardy military and national security launch services \u2013 a majority of which occur using Atlas V, not Delta IV.<\/p>\n
![\"2016-01-29-210117\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2016\/01\/2016-01-29-210117-350x242.jpg\")
In response to these RD-180 bans, along with growing pressure from SpaceX for greater competition and lower costs in the commercial launch market, ULA began a research and development (R&D) partnership with Blue Origin for a U.S.-produced rocket engine while near-simultaneously announcing a planned successor to the Atlas V and Delta IV rockets in the form of Vulcan.<\/p>\nFor the engine R&D program, ULA contracted with Blue Origin for their BE-4 engine to serve ULA\u2019s \u201cnext generation launch vehicle\u201d as well as a potential replacement engine on Atlas V\u2019s core stage.<\/p>\n
*Click here to read an extensive Q&A between ULA\u2019s Dr. George Sowers and NASASpaceFlight.com members on the ULA\/Blue Origin Deal*<\/p>\n
![\"2014-12-12](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2014\/12\/2014-12-12-22_13_17-Atlas-V-launch-ingition-Google-Search-350x251.jpg\")
At the same time, ULA stated they had enough engines to fly the Atlas V for non-military missions with the 29 RD-180s procured before the purchase ban as well as enough already-purchased RD-180s (nine as of January 2016) earmarked for U.S. military missions in 2016 and 2017.<\/p>\nBeyond that, ULA stated that if the RD-180 bans continued, ULA could not guarantee its ability to fly U.S. military missions starting sometime in 2018.<\/p>\n
This seemed confusing at the time as the Delta IV rocket was designed largely to satisfy the need for U.S. military launches, uses solely U.S.-made engines, and is owned and operated by ULA \u2013 making a switch of payloads from Atlas V to Delta IV seem an obvious intermediate step to continue U.S. military launch operations until the Atlas V engine could be replaced with a domestic engine.<\/p>\n
![\"2014-12-03](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2014\/12\/2014-12-03-17_48_26-Delta-IV-Heavy-DSP-F-23-Google-Search-350x232.jpg\")
However, ULA\u2019s subsequent announcement in March 2015 that it planned to phase out all Delta IV variants less the Delta IV-Heavy by 2018 and focus on the Atlas V to sharpen competitiveness with SpaceX shed some light on the company\u2019s \u201cnot beyond 2017\u201d guarantee for U.S. military launches.<\/p>\nNonetheless, the Fiscal Year 2016 (FY16) budget crisis\/disagreement in the U.S. Congress yet again changed the landscape of the conversation.<\/p>\n
In December 2015, Congress reversed course on the Russian engine purchase ban due in large part to a campaign from Senators Richard Shelby (Republican \u2013 Alabama) and Dick Durbin (Democrat \u2013 Illinois).<\/p>\n
In the final FY16 budget, Congress lifted the ban, allowing ULA to purchase RD-180 engines for its Atlas V fleet \u2013 for which the company immediately submitted an order for 20 more RD-180s.<\/p>\n
![\"Screen](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2016\/01\/Screen-Shot-2016-01-29-at-15.24.12-350x194.png\")
A public hearing on January 27, 2016 expanded upon a drive in both chambers of the U.S. legislature to reinstate the engine ban.<\/p>\nThis past Wednesday, the issue came up in full force during a Senate Armed Services Committee hearing led by Senator John McCain of Arizona \u2013 the Republican nominee for President in the 2008 General Election.<\/p>\n
During the course of the hearing, Senator McCain \u2013 as he did in December 2015 \u2013 railed against the lifting of the Russian engine purchase ban and accused the U.S. Congress of placing Russia\u2019s economy ahead of U.S. military and national security interests.<\/p>\n
The crux of Sen. McCain\u2019s argument seemed to be that use of Russian engines on an American-made rocket would in some way endanger U.S. security and military satellite launches \u2013 though when (if ever) Russia removed its ban on the use of RD-180 engines for U.S. military launches is unclear.<\/p>\n
![\"Screen](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2016\/01\/Screen-Shot-2016-01-29-at-15.23.07-350x195.png\")
Moreover, Senator McCain\u2019s assertions seemingly contradict ULA\u2019s statement in December 2015 that the newly purchased engines were for \u201cexisting civil and potential civil and commercial customer\u201d missions only.<\/p>\nRegardless, Senator McCain said at the hearing that he would submit legislation to the Senate to reinstate the RD-180 engine ban at the same time that his colleague in the House of Representatives, Representative McCarthy, would submit identical legislation in the House.<\/p>\n
Exactly what the fallout of this legislation will be, which was introduced in both the House and Senate on Thursday, is currently unknown \u2013 nor is it known at this time whether the legislation has enough support to pass both chambers of Congress.<\/p>\n
Even if it does pass, it is unknown whether President Obama would sign the bill into law.<\/p>\n
![\"2014-11-07](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2014\/11\/2014-11-07-01_49_31-Atlas-V-RD-180-Google-Search-350x228.jpg\")
Regardless of the specific outcome of Senator McCain and Representative McCarthy\u2019s legislation, ULA\u2019s purchase in December of 2015 is valid under U.S. federal law, and the company will take possession of those 20 engines in the coming years.<\/p>\nIn large part, the ban itself was lifted at the urging of the U.S. DoD and the work of Alabama Senator Richard Shelby and Illinois Senator Dick Durbin.<\/p>\n
Senator Durbin, in speaking on the issue in December 2015, said that lifting the engine purchase ban had everything to do with ensuring launch market redundancies.<\/p>\n
According to Senator Durbin, allowing ULA to continue purchasing and using the RD-180 engines until the BE-4 engine replacement or the Atlas V\u2019s successor are ready was the correct move for the U.S. military launch program.<\/p>\n
![\"2016-01-29-210003\"](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2016\/01\/2016-01-29-210003-350x234.jpg\")
Moreover, Senator Durbin said continuing the engine ban would essentially eliminate the Atlas V from competition and bidding for U.S. military launches and leave only SpaceX as the sole provider for U.S. military launch needs.<\/p>\nSenator Durbin\u2019s comments regarding ULA\u2019s potential inability to bid on military launch contracts followed a November 2015 moment when ULA declined to bid on a competitive GPS III-3 launch contract.<\/p>\n
That bidding process was the first competitive bid between ULA and SpaceX following the latter company\u2019s completion of Air Force and U.S. national government certification for the launch of sensitive government payloads on its Falcon 9 rocket.<\/p>\n
At the time of bidding, ULA declined to submit a bid citing accounting uncertainties.<\/p>\n
This caught the ire of Senator John McCain who, during Wednesday\u2019s briefing, discussed what he viewed as gross negligence on ULA\u2019s part in not bidding for the GPS III-3 mission given ULA\u2019s $800 million USD annual appropriation from the Air Force.<\/p>\n
![\"2014-09-16](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2014\/09\/2014-09-16-02_06_47-Atlas-V401-CLIO-Cape-Canaveral-Sept-16-2014-350x240.jpg\")
The issue here is that McCain\u2019s comments do not match the reality of that annual $800 million USD payment from the Air Force to ULA.<\/p>\nThat payment is part of the Air Force\u2019s block buy in 2014 of numerous U.S. national security payload launches from ULA and is therefore disbursed to ULA to help the company maintain its launch facilities, remain in compliance with all U.S. military and national security launch requirements, and augment the production lines for the Atlas V and Delta IV rockets needed for those block buy missions.<\/p>\n
This annual $800 million USD appropriation is a holdover from a previous, separate ELC \u2013 EELV (Evolved Expendable Launch Vehicle) Launch Capability \u2013 contract between the DoD and ULA that, in 2014, was rolled into the overall block buy contract as a separate line item.<\/p>\n
Importantly, the ELC portion of the block buy contract is not connected to the GPS III-3 contract ULA declined to bid for.<\/p>\n
![\"Rollout](\"https:\/\/www.nasaspaceflight.com\/wp-content\/uploads\/2013\/05\/Z57-350x239.jpg\")
Moreover, the ELC does not require or mandate that ULA bid for every government payload launch.<\/p>\nTherefore, since the GPS III-3 launch contract was competitive and not part of the already-in-place block buy, ULA declined to bid for it in part because it was not required of them to do so and also because it was a direct price comparison bid that they had no realistic chance of winning from SpaceX.<\/p>\n
In this manner, attempting to connect the ELC portion of the block buy contract and ULA\u2019s non-bid for GPS III-3 would be inaccurate.<\/p>\n
However, ULA\u2019s non-bid may rightly be viewed as a misstep on the company\u2019s part \u2013 even though they likely didn\u2019t have a realistic chance of winning the contract \u2013 given the large amount of federal appropriations granted to them each year.<\/p>\n
Nonetheless, this entire conversation sheds light on the changing nature of the U.S. launch market and the role the U.S. government should play in assessing the best fiscal policy for support of future missions on either ULA rockets or SpaceX rockets.\n<\/p>\n
(Images: ULA, Senate Armed Service Committee hearing and L2 \u2013 including Falcon Heavy and Vulcan renders from L2 artist Nathan Koga \u2013 The full gallery of Nathan\u2019s (SpaceX Dragon to MCT, SLS, Commercial Crew and more) L2 images can be *found here*)<\/p>\n
(To join L2, click here: http:\/\/www.nasaspaceflight.com\/l2\/)<\/p>\n","protected":false},"excerpt":{"rendered":"
The U.S. Congress is debating the reinstatement of a purchasing ban on Russian RD-180 engines \u2013 the heart of the Atlas V core stage. Congress lifted that ban in December 2015. However, some Congressional members are questioning that decision as well as ULA\u2019s decision to not bid for the 2018 competitive U.S. military GPS III-3 satellite […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"footnotes":"","_links_to":"","_links_to_target":""},"categories":[2],"tags":[7758,479,316,363],"class_list":["post-39139","post","type-post","status-publish","format-standard","hentry","category-news","tag-atlas-v","tag-falcon-9","tag-spacex","tag-ula"],"acf":[],"_links":{"self":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/39139"}],"collection":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/comments?post=39139"}],"version-history":[{"count":0,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/posts\/39139\/revisions"}],"wp:attachment":[{"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/media?parent=39139"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/categories?post=39139"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/starpath.global\/blog\/wp-json\/wp\/v2\/tags?post=39139"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}