Long Range Strike Bomber program

From Infogalactic: the planetary knowledge core
(Redirected from Long Range Strike Bomber)
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Long Range Strike Bomber program
Artist Rendering B21 Bomber Air Force Official.jpg
U.S. Air Force Artist rendering of the B-21
Project for Strategic stealth bomber
Issued by United States Air Force
Proposals  • Boeing/Lockheed Martin

 • Northrop Grumman

Date concluded 27 October 2015
(contract awarded for development)
Outcome Northrop Grumman selected to produce its entry as B-21
Predecessor programs Next-Generation Bomber

The Long Range Strike Bomber program (LRS-B) is a development and acquisition program to develop a long-range strategic bomber for the United States Air Force,[1] intended to be a heavy-payload stealth aircraft capable of carrying thermonuclear weapons.[2] Initial capability is planned for the mid-2020s. A request for proposal to develop the aircraft was issued in July 2014. The Air Force plans to purchase 80–100 LRS-B aircraft at a cost of $550 million each (2010 dollars). A development contract was awarded to Northrop Grumman in October 2015.

Origins

On 19 May 2009, Air Force Chief of Staff General Norton Schwartz said that the USAF's focus in the 2010 budget was on "Long-range strike, not next-generation bomber" and will push for this in the Quadrennial Defense Review.[3] In June 2009, the two teams working on next-generation bomber proposals were told to "close up shop".[4] On 16 September 2009, Secretary of Defense Robert Gates endorsed the concept of a new bomber but insisted that it must be affordable,[5] stating: "What we must not do is repeat what happened with our last manned bomber. By the time the research, development, and requirements processes ran their course, the aircraft, despite its great capability, turned out to be so expensive – $2 billion each in the case of the B-2 Spirit—that less than one-sixth of the planned fleet of 132 was ever built."[6] On 5 October 2009, Under Secretary of Defense for Acquisition Ashton Carter said that the DoD was still deciding if the USAF needed a new bomber and that, if approved, the aircraft would need to handle reconnaissance as well as strike missions.[7] In July 2010, Carter said he intended to "make affordability a requirement" for the next-generation intelligence and strike platform.[8]

On 11 December 2009, Gates said that the QDR had shown the need for both manned and unmanned long range strike and that the 2011 budget would likely include funding for the future bomber.[9] The USAF plans for the new bomber to be multi-role with intelligence, surveillance, and reconnaissance (ISR) capabilities.[10] As a bomber, the LRS-B will be under Air Force Global Strike Command, while ISR assets are managed by Air Combat Command's 25th Air Force.[11]

In 2010, Andrew Krepinevich, director of the Center for Strategic and Budgetary Assessments, questioned a reliance on short range aircraft like the F-35 to manage China in a future conflict and promoted reducing the F-35 buy in favor of a longer range platform like the Next-Generation Bomber; then-United States Secretary of the Air Force Michael Wynne had rejected this plan in 2007.[12][13][14] During debate on the New START treaty in December 2010, several senators raised the LRS-B as a reason to oppose or delay ratification.[15][16]

On 6 January 2011, Secretary of Defense Gates made a speech on the U.S. defense budget for FY 2012, which announced major investment in developing a long-range, nuclear-capable bomber, also to be optionally remotely piloted. He also said the aircraft "will be designed and developed using proven technologies, an approach that should make it possible to deliver this capability on schedule and in quantity. It is important that we begin this project now to ensure that a new bomber can be ready before the current aging fleet goes out of service. The follow on bomber represents a key component of a joint portfolio of conventional deep-strike capabilities—an area that should be a high priority for future defense investment given the anti-access challenges our military faces."[17] In July 2011, Joint Chief Vice Chairman James Cartwright called for a large UAV instead of a manned aircraft, including for the nuclear mission.[18] Retired Air Force colonel and Center for Strategic and Budgetary Assessments analyst Mark Gunzinger has called for an optionally manned bomber, stating that purely unmanned bombers would be at a disadvantage without direct human pilot awareness and vulnerable to communication disruption.[19]

In March 2011, the USAF decided to purchase 80 to 100 aircraft.[20][21] The Global Strike Command indicated that one requirement for the bomber is to carry a weapon of similar effect to the Massive Ordnance Penetrator.[22][23] In addition to the strategic bombing, tactical bombing, and prompt global strike roles typical for a bomber, the aircraft is to be part of a family of systems responsible for ground surveillance and electronic attack.[24] The Obama Administration in its 2012 budget request asked for $197 million and a total of $3.7 billion over five years to develop the bomber, including modular payloads for intelligence, surveillance, reconnaissance (ISR), electronic attack (EA), and communications.[25][26] It shall be nuclear-capable, but shall not be certified as such until older bombers are set to retire.[27][28]

In 2011, the House Armed Services Committee added language that would require two engine programs for the bomber; Ashton Carter objected that the addition would interfere with plans to reuse an existing engine.[29] Reportedly, the two most likely engines are the Pratt & Whitney PW9000 engine, which uses a combination of Pratt & Whitney F135 and commercial turbofan technology, and a derivative of the General Electric/Rolls-Royce F136.[30][31] In May 2011, Air Force Undersecretary Erin Conaton announced that a program office was being set up for the bomber.[32] The USAF asked for $292 million for the program in its 2013 budget request.[33] The program has also been referred to as "Long-Range Strike-B" (LRS-B).[34] In 2012, former Pentagon weapons tester Thomas P. Christie speculated that the bomber program had been initiated so that the Air Force would have a sacrificial program to offer during anticipated defense budget shortfalls.[35] The USAF seems committed to the program, given a lack of other non-nuclear options to deal with "deeply buried and/or hardened targets,"[36][37] and committed two percent of their investment budget to the project, compared to three percent to sustain existing bombers.[38]

As of August 2013, the USAF believes that the LRS-B can reach Initial Operating Capability (IOC) in 2025. Reportedly, the main risk is funding, in light of the F-35 Lightning II's acquisition difficulties and a lack of an "urgent threat". Prior bomber programs were hindered by a lack of funding, only 21 B-2 Spirits were produced out of 132 planned and fewer B-1 Lancers were built than were envisioned; both programs were scaled down due to spiraling per aircraft costs. Research funding was allocated, as stealthy technologies to counter anti-access/area-denial threats were spared from budget cuts. The USAF stated the LRS-B is a top priority as it is believed that China will overcome the B-2's low-observable features by the 2020s. Where possible, existing technologies and proven subsystems will be used in order to keep it within budget, instead of developing new and riskier ones. Components such as engines and radars may be off-the-shelf or adaptions of existing models, such as derivative technologies of the F-35. The LRS-B is intended to perform any long range mission, rather than one specialized mission, which drove up the cost of the B-2. The USAF expects it to cost $1 billion each with development costs factored in, and aims for a per-aircraft cost of $550 million, considered reasonable for a limited production run military aircraft.[39]

On 25 October 2013, Boeing and Lockheed Martin announced their teaming up for the LRS-B. Boeing will be the prime contractor. The two companies previously joined together for the program in 2008, but the partnership ended in 2010 when requirements shifted. Boeing believes that as the program had evolved, they can readdress their partnership to specifically address requirements. The team has Boeing's bomber experience and Lockheed Martin's stealth experience. At the time of the announcement, official details about the LRS-B were that it will likely be optionally manned and use stealth technology.[40] On 30 January 2014, Northrop Grumman stated their intention to invest in developing needed technology for the bomber, such as stealth designs, mission management systems, and autonomous controls.[41]

In January 2014, General Schwartz said that the Pentagon should abandon plans to outfit the F-35 with nuclear weapons in favor of the LRS-B. A 2010 Nuclear Posture Review stated that replacing the F-16 with the F-35 retains dual conventional and nuclear delivery capabilities for USAF fighters. The Congressional Budget Office determined that upgrading the F-35 for nuclear deployment would cost $350 million over the next decade. Schwartz said that without financial support from NATO, where some nuclear-capable F-35s would be deployed, those funds should be transferred to the LRS-B. At the same time, Congress cut funding for the B61 nuclear bomb, stripping $10 million from F-35 integration and $34.8 million for life extension; Schwartz stated that B61's life extension must proceed.[42]

On 20 February 2014, the USAF reasserted the bomber's need at the annual Air Force Association Air Warfare Symposium in Orlando, Fla. It was stated it will be fielded in the mid-2020s, and between 80 and 100 of the bombers will be procured. Lt. Gen. Burton Field clarified the 80 to 100 range is due to uncertainty over the price rather than a figure representing the minimum number of bombers needed to mitigate risk.[43][44] Some USAF leaders expect the unit cost limit of $550 million per aircraft will be exceeded with additional equipment added to the airframe. The cost goal is to set design constraints to prevent extra requirements for capability growth desires and untested technologies that would increase the price more from being incorporated during development. Though the final cost may be greater than planned, a fixed price objective is expected to keep average procurement costs affordable.[45] Rather than the price ceiling being too low to meet requirements, the USAF sees it as them and the potential contractor being disciplined about the bomber's missions and roles. Research and development expenses are likely to be "significant", but not expected to be double the cost of production aircraft.[46]

The USAF intended to release a full request for proposals (RFP), a final RFP, and begin the competition for the Long-Range Strike Bomber in fall 2014. Two teams, Northrop Grumman and Boeing–Lockheed Martin, were working on pre-proposals for the competition.[47] In June 2014, the USAF revealed that the LRS-B RFP would be released "soon," with proposals to be submitted by fall 2014 and evaluations completed in early 2015, with a contract award after that. Some public information includes that it will be operational in the mid-2020s, based on existing technologies, have a large payload, may possibly be optionally-manned, and is being designed to work with a "family of systems" that includes ISR, electronic attack, and communication systems. Early aircraft will be designed around fixed requirements with mature technologies that will be adaptable through open architecture for future sensor and weapons capabilities.[48] Although the LRS-B request for proposals (RFP) was to be released by the end of June, the USAF hesitated to publicly announce it to keep the process fair and less likely to give sensitive information to "potential adversaries". Public announcements of future acquisition milestones are to be "released as appropriate."[49]

Competitive phase

The USAF released its RFP for the LRS-B on 9 July 2014. By entering the competitive phase of acquisition, the USAF is limited with what it is able to release, and few details were expected to be made public until the contract is awarded in the second quarter of 2015. The LRS-B is expected to replace the B-52 fleet, possibly replace a portion of the B-1 fleet, and complement the B-2 fleet.

Northrop Grumman could base production in Florida if they won the contract, which would provide tax credits, while California passed a bill offering tax credits to the manufacturer if they build it in their state, which would mainly benefit the Boeing–Lockheed Martin team.[50][51] On 14 August 2014, the California legislature passed a measure to apply tax benefits equally to prime and subcontractors. The previous measure only applied to subcontractors, meaning Lockheed Martin as part of the Boeing–Lockheed Martin team, placing Northrop Grumman at a near half-billion-dollar disadvantage in the bidding; the new measure levels the tax benefit field by also applying them to prime contractors, as Northrop Grumman has no subcontractor and also has operations in Palmdale.[52]

With a target price of $550 million per aircraft, Defense News quoted a source with knowledge of the program predicting that the LRS-B may be smaller than the B-2, perhaps half the size, powered by two engines in the Pratt & Whitney F135 power class.[53] The target unit cost of $550 million is based on 2010 dollars and is $606 million in 2016 dollars.[54] One of the program's main effects will be its impact on the industrial base; three of the country's five largest defense firms are competing. After the LRS-B, the USAF will not have another major attack aircraft program until the 2030s for a new fighter, with a follow-on bomber after that. With that stretch of time in between, the loser may be forced to leave the industry entirely; Northrop Grumman would likely not retain the infrastructure required for the next major undertaking, and Boeing's main aircraft field is now its commercial products.[55][56] Industrial impact may cause any contract to be contested by Congress from representatives that receive campaign donations from a company whose award would create jobs for constituents. In addition to competing with other USAF priorities, budgets may put the LRS-B at odds with other services' priorities such as the Ohio Replacement Submarine.[53]

In April 2015, Pentagon undersecretary for acquisition Frank Kendall revealed that individual technologies for the LRS-B will be competed to enhance flexibility, increase competition, and drive down costs. This means even though one team will build the aircraft, other competitors will have the chance to compete for sustainment and upgrade features.[57] Although a contract was planned to be awarded in early summer 2015, it was pushed back to September 2015 to sure up requirements. Prolonging this part of the process is seen as a time and money-saver later in the acquisition to ensure the resulting bomber can be useful over a 50-year lifespan.[58]

In September 2015, the USAF revealed that the LRS-B's development was much further along than had been publicly acknowledged, and more than usual before a contract award. Final requirements had been finalized since May 2013. Both competitors had mature proposals with prototyping activities and wind tunnel tests along with subsystems, although no demonstrator had been built. The designs are "very different" from each other with different teams on subsystems such as engines, electronic warfare suites, and communications systems; subcontractors will likely not be announced when the winner is picked. The bomber seems similar to the B-2, but more advanced using improved materials for superior low observability, similar to or smaller in size, and will operate alone or as part of a strike package with other airborne assets. Conducting of tests and risk reduction this early in the acquisition process is in part because the program has been handled by the Air Force Rapid Capabilities Office since 2011, which has more freedom in how it procures technologies. To reduce risk, the aircraft's production rate will probably remain steady and fairly modest over the course of the aircraft's production.[59][60] In late September 2015, the contract award was again delayed.[61]

Contract award

On 27 October 2015, the Defense Department awarded the development contract to Northrop Grumman.[62] The initial value of the contract is $21.4 billion, but the deal could eventually be worth up to $80 billion.[63][64][65] On 6 November 2015, Boeing and Lockheed Martin protested the decision to the Government Accountability Office (GAO). Development costs have been estimated to be from US$10 to $23 billion.[66][67] On 16 February 2016, the GAO denied the protest, and Northrop Grumman resumed work on the project.[68] In February 2016, Boeing and Lockheed decided not to pursue a lawsuit against the US Air Force over the selection of Northrop Grumman.[69]

At the 2016 Air Warfare Symposium, the LRS-B aircraft was formally designated as B-21.[70] The head of the US Air Force Global Strike Command expects that 100 B-21 bombers is the minimum ordered and envisions some 175–200 bombers in service.[71] A media report states that the bomber could also be used as an intelligence gatherer, battle manager, and interceptor aircraft.[72]

See also

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. RL34406, "Air Force Next-Generation Bomber: Background and Issues for Congress". Congressional Research Service, 18 September 2009
  5. "Gates endorses new U.S. bomber project". Reuters
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. "Carter: DoD, White House Crafting New Presidential Helo Specs". Defense News
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Fulghum, David A. "New Bomber To Focus Heavily On ISR". Aviation Week, 17 December 2009.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Clark, Colin. "Strategy, What Strategy?" dodbuzz.com, 29 June 2010. Retrieved: 3 July 2010.
  13. Kosiak, Steve and Barry Watts. "US Fighter Modernization Plans: Near-term Choices." Csbaonline.org Retrieved: 3 July 2010.
  14. Wolf, Jim. "Air Force chief links F-35 fighter jet to China." Reuters, 19 September 2007. Retrieved: 3 July 2010.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Tirpak, John A. "Confessions of a 'Bomber Hater'." Air Force Magazine, 15 July 2011.
  19. http://www.csbaonline.org/wp-content/uploads/2010/09/2010.09.14-Sustaining-Americas-Strategic-Advantage-in-Long-Range-Strike.pdf
  20. Reed, John. "Air Force Hopes to Buy 80 to 100 Next Gen Bombers." DoD Buzz, 30 March 2011.
  21. Erwin, Sandra. "Air Force Chief: We Will Not 'Overdesign' the New Stealth Bomber." National Defense Industrial Association. 9 February 2012.
  22. Trimble, Stephen. "Penetrate faster, harder with new AFRL weapon." Flight Global, 20 February 2011.
  23. "A Slimmer MOP". AirForce Magazine, Daily Report, 25 June 2010.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Majumdar, Dave. "Budget shrinks; acquisition programs outlined" AirForce Times, 15 February 2011.
  26. Shane, Leo. "Budget breakdown: Air Force." Stars and Stripes, 14 February 2011.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Majumdar, Dave. "New Bomber Won't Be Nuclear-Capable at First: USAF Chief." Defense News, 2 November 2011.
  29. Bedard, Paul. "Pentagon, Obama Bomb House Bid To Revive Jet Engine." US News, 24 May 2011.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.(subscription required)
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Munoz, Carlo. "DoD Fast Tracks New Bomber; 'Planning Number' is $550 Million Per Plane." AOL Defense. 15 February 2012.
  34. Butler, Amy. "Amid Cuts USAF Cautiously Funds F-35, Bomber." Aviation Week. 13 February 2012.
  35. Axe, David. "Why Can't the Air Force Build an Affordable Plane?" The Atlantic. 26 March 2012.
  36. "U.S. Air Force Is 'Committed' To Long-Range Strike Bomber."
  37. "Air Force Wants A Bomber That Balances Cost With Capability."
  38. "Sec. Donley: Why The Air Force Can't Delay Modernization."
  39. "Budget Pressures Seen as Biggest Risk to Long Range Bomber Program". National Defense Magazine, September 2013.
  40. Boeing, Lockheed Team on Long Range Strike Bomber – Defensenews.com, 25 October 2013
  41. Northrop to ‘position’ for future bomber work as LRS-B progressesFlightGlobal, 4 February 2014
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. USAF Defends Need for New Long-Range Bomber Defense News, 20 February 2014
  44. Lua error in package.lua at line 80: module 'strict' not found.
  45. General: 'Of course' new Air Force bomber will be more than $550M per planeMilitary Times, 5 March 2014
  46. Air Force Keeps Bomber Price Tag at $550 Million – DoDBuzz.com, 12 March 2014
  47. Lua error in package.lua at line 80: module 'strict' not found.
  48. RFP for bomber coming soon, Air Force's top buyer saysMilitary Times, 13 June 2014
  49. Bomber RFP News to Stay HiddenAirForce Magazine, 27 June 2014
  50. Air Force sends next-gen bomber requirements to industry, few details made public - AirForcetimes.com, 10 July 2014
  51. USAF launches competition for new bomber - Flightglobal.com, 11 July 2014
  52. Northrop Bomber Team Relieved Over California Legislation - Aviationweek.com, 15 August 2014
  53. 53.0 53.1 Shrouded in Mystery, New Bomber Makes Waves - Defensenews.com, 19 January 2015
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. Lua error in package.lua at line 80: module 'strict' not found.
  57. Kendall: New AF Bomber Will Compete Upgrades - Defensenews.com, 9 April 2015
  58. Air Force Plans Bomber Contract for September - Military.com, 22 July 2015
  59. LRS-B Details Emerge: Major Testing, Risk Reduction Complete - Defensenews.com, 2 September 2015
  60. New details emerge about LRS-B as contract announcement nears - Flightglobal.com, 4 September 2015
  61. Lua error in package.lua at line 80: module 'strict' not found.
  62. Lua error in package.lua at line 80: module 'strict' not found.
  63. Lua error in package.lua at line 80: module 'strict' not found.
  64. Lua error in package.lua at line 80: module 'strict' not found.
  65. Lua error in package.lua at line 80: module 'strict' not found.
  66. http://aviationweek.com/blog/lrsb-yet-another-tale-two-protests
  67. https://www.flightglobal.com/news/articles/boeing-and-lockheed-protest-usafs-bomber-award-to-n-418723/
  68. GAO Denies Boeing’s Protest of Bomber Contract; Northrop Gets Back to Work
  69. http://www.defensenews.com/story/defense/air-space/strike/2016/02/26/boeing-lockheed-lawsuit-b-21-bomber-lrsb/80991832/
  70. http://www.af.mil/News/ArticleDisplay/tabid/223/Article/673784/air-force-reveals-b-21-long-range-strike-bomber.aspx
  71. https://www.flightglobal.com/news/articles/usaf-global-strike-chief-seeks-beefed-up-bomber-forc-422469/
  72. http://www.defenseone.com/technology/2015/09/air-force-bomber-missions-bombs/120881/?oref=search_Long%20Range%20Strike-Bomber

External links

  • Lua error in package.lua at line 80: module 'strict' not found.