Next-Generation Bomber

From Infogalactic: the planetary knowledge core
(Redirected from New Generation Bomber)
Jump to: navigation, search

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

Next-Generation Bomber
300px
Boeing/Lockheed Martin "2018 Bomber" concept image
Project for Stealth bomber
Issued by United States Air Force
Outcome Cancelled
Successor programs Long Range Strike Bomber

The Next-Generation Bomber (NGB; unofficially called 2018 Bomber) was a program to develop a new medium bomber for the United States Air Force. The NGB was initially projected to enter service around 2018 as a stealthy, subsonic, medium-range, medium payload bomber to supplement and possibly—to a limited degree—replace the U.S. Air Force's aging bomber fleet (B-52 Stratofortress and B-1 Lancer). The NGB program was superseded by the Long Range Strike Bomber (LRS-B) heavy bomber program.

Development

2018 Bomber

The sinking of ex-USS Schenectady as a test during Operation Resultant Fury in 2004 demonstrated that heavy bombers could successfully engage naval targets on their own. This led to the requirement for a new bomber that could survive against modern defenses.[1][2] In 2004–06, the USAF Air Combat Command studied alternatives for a new bomber type aircraft to augment the current bomber fleet which now consists of largely 1970s era airframes, with a goal of having a fully operational aircraft on the ramp by 2018.[3] Some speculation suggested that the next generation bomber might be hypersonic and unmanned.[4] However, these were put to rest when US Air Force Major General Mark T. Matthews, head of ACC Plans and Programs stated that available technology indicates a manned subsonic bomber at a May 2007 Air Force Association sponsored event.[5] He later stated that a manned subsonic bomber provides the "best value" to meet the required range and payload performance by 2018.[6] The 2018 bomber was expected to serve as a stop-gap until the more advanced "2037 Bomber" entered service.[7]

The 2006 Quadrennial Defense Review (QDR), directed the Air Force to develop a new long-range precision strike capability by 2018.[8][9] USAF officials identified the new bomber as having top-end low-observability characteristics with the ability to loiter for hours over the battlefield area and respond to threats as they appear. Major General David E Clary, ACC vice-commander, summed it up by saying the new bomber would "penetrate and persist". Deployment of cruise missiles was another issue for the new bomber. The B-52 is the only aircraft currently in the Air Force inventory allowed under strategic nuclear arms reduction treaty to be armed with nuclear cruise missiles. Major consideration was paid to operation readiness and flexibility. In 2006, the program expected that a prototype could be flying as early as 2009.[10] In September 2007, several Air Force generals stressed that it was still their plan to field the bomber by 2018. In order to meet the tight schedule, the Air Force would initially pursue a basic model then improves its capabilities subsequently.[11]

On 25 January 2008, Boeing and Lockheed Martin announced an agreement to embark on a joint effort to develop a new US Air Force strategic bomber, with plans for it to be in service by 2018.[12] This collaborative effort for a long-range strike program will include work in advanced sensors and future electronic warfare solutions, including advancements in network-enabled battle management, command and control, and virtual warfare simulation and experimentation.[13] Under their joint arrangement, Boeing, the No. 2 Pentagon supplier, would be the primary contractor with about a 60% share, and Lockheed Martin, the world's largest defense contractor, would have around a 40% share, according to sources familiar with the companies' plans.[14] Northrop Grumman, another major defense contractor, received $2 billion in funding in 2008 for "restricted programs" – also called black programs – for a demonstrator that could fly in 2010.[15]

The Air Force was expected to announce late in 2009 its precise requirements for a new bomber that would be operating by 2018.[16] In May 2009, testimony before Congress, US Secretary of Defense Robert Gates mentioned that the Pentagon is considering a pilotless aircraft for the next-generation bomber role.[17]

Move to LRS-B

Lua error in Module:Details at line 30: attempt to call field '_formatLink' (a nil value).

In April 2009, Defense Secretary Gates announced a delay in the new generation bomber project that would push it past the 2018 date.[18] This was caused not only by budget considerations, but also by nuclear arms treaty considerations.[19] 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 QDR.[20] In June 2009, the two teams working on NGB proposals were told to "close up shop".[21] On 1 March 2010, Boeing said that the joint project with Lockheed Martin had been suspended[22] and on 24 June 2010, Lieutenant General Philip M. Breedlove said that the term "next-generation bomber" was dead and that the Air Force was working on a long-range strike "family" that would draw on the capabilities of systems like the F-35 and F-22 to help a more affordable and versatile bomber complete its missions.[23]

On 13 September 2010, U.S. Air Force Secretary Michael Donley said that long range strike would continue cautiously with proven technologies and that the plan to be submitted with the 2012 budget could call for either a missile or an aircraft.[24][25] The bomber is to be nuclear-capable, but not certified for nuclear use until later. On 24 February 2012, Air Force Secretary Michael Donley announced that a competition was under way with a target delivery in the mid-2020s.[26] On 27 October 2015, Northrop Grumman was awarded the contract to build the new bomber.[27]

Design

The design goals in January 2011 were:[28]

An August 2008 paper by Northrop Grumman highlighted the following trends and requirements:[32]

  • Airfields available for American use have declined since the Cold War.
  • Hostile cruise and ballistic missiles could shut down the few available airfields.
  • Fewer fighter aircraft will be available to escort the bomber force.
  • Advanced fighter aircraft and surface to air missiles are being made available to potentially hostile states.
  • The current USAF bomber force is small and largely outdated.

See also

Aircraft of comparable role, configuration and era
Related lists

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. Grant 2007, pp. 17–20.
  4. Grant 2007, pp. 6–7.
  5. Warwick, Graham. "USAF says next bomber will be subsonic and manned". Flight International, 3 May 2007.
  6. Warwick, Graham. "Speed bump: USAF sets modest goals for new bomber". Flight International, 12 June 2007.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. "Why the US Wants a New Bomber", The Diplomat, 6 May 2012.
  9. Ehrhard, Tom. "An Air Force Strategy for the Long Haul". Center for Strategic and Budgetary Assessments, 17 September 2009.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. "Senior Air Force Generals To Skeptics: We Can Field A New Bomber In 2018".[dead link] Defense Daily, 26 September 2007.
  12. Lua error in package.lua at line 80: module 'strict' not found..
  13. Lua error in package.lua at line 80: module 'strict' not found..
  14. Lua error in package.lua at line 80: module 'strict' not found..
  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. Lua error in package.lua at line 80: module 'strict' not found..
  19. Lua error in package.lua at line 80: module 'strict' not found..
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. RL34406, "Air Force Next-Generation Bomber: Background and Issues for Congress". Congressional Research Service, 18 September 2009
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Reed, John. "AFA: New bomber program 'underway'." DoD Buzz. 24 February 2012.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. 28.0 28.1 28.2 28.3 28.4 28.5 28.6 Majumdar, Dave. "U.S. Air Force May Buy 175 Bombers." Defense News, 23 January 2011.
  29. Grant, Greg. "Air Force chief describes future bomber." Government Executive, 31 October 2007.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Majumdar, Dave. "New bomber could conduct long-range missions." AirForce Times, 12 February 2011.
  32. The 2018 Bomber: The Case for Accelerating the Next Generation Long-Range Strike System

Bibliography

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

External links

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