Joint Strike Fighter program

For other uses of "Joint Strike Fighter", see Joint Strike Fighter (disambiguation).
Joint Strike Fighter (JSF)
X-32B at Patuxent River Naval Air Museum
Project for Strike Fighter
Issued by Multiple services
Prototypes Boeing X-32
Lockheed Martin X-35
Outcome X-35 selected for production as F-35 Lightning II
Predecessor programs Common Affordable Lightweight Fighter (CALF)
Joint Advanced Strike Technology

Joint Strike Fighter (JSF) is a development and acquisition program intended to replace a wide range of existing fighter, strike, and ground attack aircraft for the United States, the United Kingdom, Turkey, Italy, Canada, Australia, the Netherlands and their allies. After a competition between the Boeing X-32 and the Lockheed Martin X-35, a final design was chosen based on the X-35. This is the F-35 Lightning II, which will replace various tactical aircraft, including the US F-16, A-10, F/A-18, AV-8B and British Harrier GR7 & GR9s. The projected average annual cost of this program is $12.5 billion with an estimated program life-cycle cost of $1.1 trillion.[1]

Project formation

The JSF program was the result of the merger of the Common Affordable Lightweight Fighter (CALF) and Joint Advanced Strike Technology (JAST) projects.[2][3] The merged project continued under the JAST name until the engineering, manufacturing and development (EMD) phase, during which the project became the Joint Strike Fighter.[4]

The CALF was a DARPA program to develop a STOVL strike fighter (SSF) for the United States Marine Corps and replacement for the F-16 Fighting Falcon. The United States Air Force passed over the F-16 Agile Falcon in the late 1980s, essentially an enlarged F-16, and continued to mull other designs. In 1992, the Marine Corps and Air Force agreed to jointly develop the Common Affordable Lightweight Fighter, also known as Advanced Short Takeoff and Vertical Landing (ASTOVL). CALF project was chosen after Paul Bevilaqua persuaded[5] the Air Force that his team's concept[6] (if stripped of its lift system) had potential as a complement to the F-22 Raptor.[5] Thus, in a sense the F-35B begat the F-35A, not the other way around.

The Joint Advanced Strike Technology (JAST) program was created in 1993, implementing one of the recommendations of a United States Department of Defense (DoD) "Bottom-Up Review to include the United States Navy in the Common Strike Fighter program."[7] The review also led the Pentagon to continue the F-22 Raptor and F/A-18E/F Super Hornet programs, cancel the Multi-Role Fighter (MRF) and the A/F-X programs, and curtail F-16 and F/A-18C/D procurement. The JAST program office was established on 27 January 1994 to develop aircraft, weapons, and sensor technology with the aim of replacing several disparate US and UK aircraft with a single family of aircraft; the majority of those produced would replace F-16s. Merrill McPeak, former Chief of Staff of the United States Air Force, has complained that Les Aspin's decision to force all three services to use a single airframe greatly increased the costs and difficulty of the project.[8]

In November 1995, the United Kingdom signed a memorandum of understanding to become a formal partner, and agreed to pay $200 million, or 10% of the concept demonstration phase.[4]

In 1997, Canada's Department of National Defence signed on to the Concept Demonstration phase with an investment of US$10 million. This investment allowed Canada to participate in the extensive and rigorous competitive process where Boeing and Lockheed Martin developed and competed their prototype aircraft.[9]

JSF competition

Studies supporting JAST/JSF started in 1993 and led to STOVL submissions to the DOD by McDonnell Douglas, Northrop Grumman, Lockheed Martin and Boeing:[10]

1) McDonnell Douglas proposed an aircraft powered by a reheated turbofan, with a remote gas driven fan to augment lift in the STOVL mode. Later General Electric did a ground demonstration of this engine configuration.

2) The Northrop Grumman aircraft featured an auxiliary lift engine augmenting the dry thrust from a reheated turbofan fitted with a pair of thrust vectoring nozzles.

3) The Lockheed Martin aircraft concept utilised a reheated turbofan with thrust augmentation from a remote shaft-driven lift fan. This engine configuration was to lead eventually to the F135-PW-600 which powers the F-35B JSF production aircraft.

4) Boeing decided against thrust augmentation. They proposed an aircraft powered by a reheated turbofan that could be reconfigured (in the STOVL mode) into a direct lift engine with a pair of thrust vectoring nozzles located near the aircraft centre-of-gravity. This led to the F119-PW-614S which powered the X-32B JSF demonstrator.

Two contracts to develop prototypes were awarded on November 16, 1996, one each to Lockheed Martin and Boeing. Each firm would produce two aircraft to demonstrate conventional takeoff and landing (CTOL), carrier takeoff and landing (CV version), and short takeoff and vertical landing (STOVL). McDonnell Douglas' bid was rejected in part due to the complexity of its design.[11] Lockheed Martin and Boeing were each given $750 million for the development of the concept demonstrators and definition of the Preferred Weapon System Concept (PWSC). The aim of this funding limit was to prevent one or both contractors bankrupting themselves in an effort to win such an important contract.[3]

Also in 1996, the UK Ministry of Defence launched the Future Carrier Borne Aircraft project. This program sought a replacement for the Sea Harrier (and later the Harrier GR7); the Joint Strike Fighter was selected in January 2001.

During concept definition, two Lockheed Martin airplanes were flight-tested: the X-35A (which was later converted into the X-35B), and the larger-winged X-35C.[12] Arguably the most persuasive demonstration of the X-35's capability was the final qualifying Joint Strike Fighter flight trials, in which the X-35B STOVL aircraft took off in less than 500 feet (150 m), went supersonic, and landed vertically – a feat that Boeing's entry was unable to achieve.[13]

Outcome

The contract for System Development and Demonstration (SDD) was awarded on 26 October 2001 to Lockheed Martin,[14] whose X-35 beat the Boeing X-32. One of the main reasons for this choice appears to have been the method of achieving STOVL flight, with the Department of Defense judging that the higher performance lift fan system was worth the extra risk. When near to the ground, the Boeing X-32 suffered from the problem of hot air from the exhaust circulating back to the main engine, which caused the thrust to weaken and the engine to overheat.[13]

The United States Department of Defense officials and William Bach, the UK Minister of Defence Procurement, said the X-35 consistently outperformed the X-32, although both met or exceeded requirements.[13] The development of the JSF will be jointly funded by the United States, United Kingdom, Italy, the Netherlands, Canada, Turkey, Australia, Norway and Denmark.

Lockheed Martin's X-35 would become the basis of the F-35 Lightning II, currently in development. On April 6, 2009 US Secretary of Defense Robert Gates announced that the US would buy a total of 2,443 JSFs.[15]

Program issues

Alleged Chinese espionage

In April 2009, the Wall Street Journal reported that computer spies, allegedly Chinese but acknowledged to be from uncertain sources, had penetrated the database and acquired terabytes of secret information about the fighter, possibly compromising its future effectiveness.[16]

Cost overruns

On February 1, 2010 Secretary of Defense Robert M. Gates announced that, due to delays and other problems with the JSF development program, he was removing Major General David R. Heinz from command of the program and would withhold $614 million in bonuses from Lockheed Martin.[17] On February 16, 2010 Deputy Defense Secretary Bill Lynn announced that the program will be delayed one year.[18] According to some estimates, overruns could increase the program's total costs to $388 billion, a 50% increase from the initial price tag.[19] Many of the program's financial and technical complications result from the Marine version of the JSF, capable of vertical take-offs and landings.[19]

On 11 March 2010, United States Senate Committee on Armed Services investigated the progress of the JSF program in a meeting with Pentagon officials, emphasizing cost due to the risk of a Nunn-McCurdy process.[20] According to the Government Accountability Office, F-35A cost has risen from $50m in 2002, via $69m in 2007 to $74m in 2010, all measured in 2002 dollars.[20]

Canada reviewed their commitment to the project in December 2012, due to the cost overruns. The decision was made following a report by auditing firm KPMG that showed that Canada’s purchase would cost C$45bn over 42 years. Rona Ambrose, Canada’s public works minister said: “We have hit the reset button and are taking the time to do a complete assessment of all available aircraft.” [21] Defence Minister Peter MacKay announced Canada’s plan to buy the F-35 in 2010 saying that the purchase price was $9 billion, but did not provide operating cost estimates. During an election campaign in 2011, the Conservatives declared that the total cost over 20 years would be $16 billion.[22]

Performance concerns

Concerns about the F-35's performance have resulted partially from reports of simulations by RAND Corporation in which three regiments of Russian Sukhoi fighters defeat six F-22s by denying tanker refueling.[23]

As a result of these media reports, then Australian defence minister Joel Fitzgibbon requested a formal briefing from the Australian Department of Defence on the simulation. This briefing stated that the reports of the simulation were inaccurate and that it did not compare the F-35's performance against that of other aircraft.[24][25]

Andrew Hoehn, Director of RAND Project Air Force, made the following statement: "Recently, articles have appeared in the Australian press with assertions regarding a war game in which analysts from the RAND Corporation were involved. Those reports are not accurate. RAND did not present any analysis at the war game relating to the performance of the F-35 Joint Strike Fighter, nor did the game attempt detailed adjudication of air-to-air combat. Neither the game nor the assessments by RAND in support of the game undertook any comparison of the fighting qualities of particular fighter aircraft."[26]

Furthermore, Maj. Richard Koch, chief of USAF Air Combat Command's advanced air dominance branch is reported to have said that "I wake up in a cold sweat at the thought of the F-35 going in with only two air-dominance weapons" with an Aviation Week article casting an extremely skeptical eye over the (USAF) source of claims that the F-35 would be "400% more effective" than projected opponents.[27]

The experience of the JSF program has led to a more conservative and open-ended Future Vertical Lift program.[28]

See also

References

  1. "JOINT STRIKE FIGHTER - DOD Actions Needed to Further Enhance Restructuring and Address Affordability Risks" (PDF). United States Government Accountability Office. Retrieved 1 August 2012.
  2. A history of the Joint Strike Fighter Program, Martin-Baker. Retrieved April 2011
  3. 1 2 Nicholls, Mark (August 2000). "JSF: The Ultimate Prize". Air Forces Monthly (Key Publishing): 32–38.
  4. 1 2 "US, UK sign JAST agreement". Aerospace Daily (McGraw-Hill). 1995-11-25. p. 451.
  5. 1 2 Wilson, George C. "The engine that could" GovExec, January 22, 2002. Retrieved December 2009. Archived on 19 October 2013.
  6. "Propulsion system for a vertical and short takeoff and landing aircraft", United States Patent 5209428
  7. Bolkcom, Christopher. JSF: Background, Status, and Issues page CRS-2, dtic.mil, 16 June 2003. Retrieved: 18 September 2010.
  8. "Prices soar, enthusiasm dives for F-35 Lightning."
  9. . "Government of Canada" 16 July 2010 Retrieved: 26 July 2010
  10. https://www.flightglobal.com/pdfarchive/view/1995/1995%20-%200834.html
  11. Fulghum, David; Morrocco, John (1996-11-25). "Final JSF Competition Offers No Sure Bets". Aviation Week and Space Technology (McGraw-Hill). p. 20.
  12. Joint Strike Fighter official site - History page
  13. 1 2 3 PBS: Nova transcript "X-planes"
  14. Bolkcom, Christopher. JSF: Background, Status, and Issues page CRS-4, dtic.mil, 16 June 2003. Retrieved: 18 September 2010.
  15. Gates, Dominic, "Aerospace Giant 'Hit Harder' Than Peers", Seattle Times, April 7, 2009, p. 1.
  16. Gorman S, Cole A, Dreazen Y (April 21, 2009). "Computer Spies Breach Fighter-Jet Project Article". The Wall Street Journal.
  17. Whitlock, Craig, "Gates To Major General: You're Fired", Washington Post, February 2, 2010, p. 4.
  18. Reed, John, "Pentagon Official Confirms 1-Year Delay For JSF", DefenseNews.com, February 16, 2010.
  19. 1 2 Shachtman, Noah. "The Air Force Needs a Serious Upgrade", The Brookings Institution, 15 July 2010.
  20. 1 2 JSF faces US Senate grilling, australianaviation.com.au 12 March 2010.
  21. "Canada puts JSF on ice". Financial Times. December 13, 2012. Retrieved 2013-08-18.
  22. "Canada Reviews Plans to Buy F-35 Fighter Jets". New York Times. December 12, 2012. Retrieved 2013-08-18.
  23. Trimble, Stephen. "US defence policy – and F-35 – under attack." Flight International, Reed Business Information, 15 October 2008.
  24. "Fighter criticism 'unfair' and 'misrepresented'." ABC News, 25 September 2008. Retrieved: 30 October 2008.
  25. Wolf, Jim. "Air Force chief links F-35 fighter jet to China." reuters.com, 19 September 2007. Retrieved: 3 July 2010.
  26. Hoehn, Andrew. "Statement Regarding Media Coverage of F-35 Joint Strike Fighter." RAND, 12 October 2010. Retrieved 17 May 2012.
  27. Sweetman, Bill. "JSF Leaders Back In The Fight." aviationweek.com, 22 September 2008. Retrieved: 3 July 2010.
  28. Sydney J. Freedberg Jr. "Future Vertical Lift: One Program Or Many?" Breaking Defense, 5 June 2014. Accessed: 22 June 2014. Archived on 6 June 2014.

External links

External images
Official JSF program videos
This article is issued from Wikipedia - version of the Sunday, April 10, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.