Lockheed Martin F-35 Lightning II

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

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

F-35 Lightning II
Gray fighter aircraft flying against a backdrop of clouds.
F-35A Lightning II
Role Stealth multirole fighter
National origin United States
Manufacturer Lockheed Martin Aeronautics
First flight 15 December 2006 (F-35A)
Introduction F-35B: 31 July 2015 (USMC)[1][2][3]
F-35A: 2 August 2016 (USAF)[4]
F-35C: 2018 (USN)[5]
Status In service
Primary users United States Air Force
United States Marine Corps
United States Navy
See Operators section for others
Produced 2006–present
Number built 231[N 1] as of March 2017[6][7]
Program cost US$1.508 trillion (through 2070 in then-year dollars), US$55.1B for RDT&E, $319.1B for procurement, $4.8B for MILCON, $1123.8B for operations & sustainment (2015 estimate)[8]
Unit cost
F-35A: $94.6M (low rate initial production lot 10 (LRIP 10) including F135 engine, full production in 2018 to be $85M)[9]
F-35B: US$122.8M (LRIP 10 including engine)[9]
F-35C: US$121.8M (LRIP 10 including engine)[9]
Developed from Lockheed Martin X-35

The Lockheed Martin F-35 Lightning II is a family of single-seat, single-engine, all-weather stealth multirole fighters. The fifth-generation combat aircraft is designed to perform ground attack and air defense missions. It has three main models: the F-35A conventional takeoff and landing (CTOL) variant, the F-35B short take-off and vertical-landing (STOVL) variant, and the F-35C carrier-based Catapult Assisted Take-Off Barrier Arrested Recovery (CATOBAR) variant. On 31 July 2015, the United States Marines declared ready for deployment the first squadron of F-35B fighters after intensive testing.[10][11] On 2 August 2016, the U.S. Air Force declared its first squadron of F-35A fighters combat-ready.[12]

The F-35 descends from the X-35, the winning design of the Joint Strike Fighter (JSF) program. An aerospace industry team led by Lockheed Martin designed and manufactures it. Other major F-35 industry partners include Northrop Grumman, Pratt & Whitney and BAE Systems. The F-35 first flew on 15 December 2006. The United States plans to buy 2,457 aircraft. Its variants are to provide the bulk of the crewed tactical airpower of the U.S. Air Force, Navy and the Marine Corps over the coming decades. Deliveries of the F-35 for the U.S. military are scheduled until 2037[13] with a projected service life up to 2070.[14]

The United States principally funds the F-35 JSF development, with additional funding from partners. The partner nations are either NATO members or close U.S. allies. The United Kingdom, Italy, Australia, Canada, Norway, Denmark, the Netherlands, and Turkey are part of the active development program;[15][16] several additional countries have ordered, or are considering ordering, the F-35.

The program is the most expensive military weapons system in history, and has been much criticized inside and outside government, in the U.S. and in allied countries.[17] Critics argue that the plane is "plagued with design flaws," with many blaming the procurement process in which Lockheed was allowed "to design, test, and produce the F-35 all at the same time, instead of… [identifying and fixing] defects before firing up its production line."[17] By 2014, the program was "$163 billion over budget [and] seven years behind schedule."[18] Critics also contend that the program's high sunk costs and political momentum make it "too big to kill."[19]

Development

JSF program requirements and selection

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

The JSF program was designed to replace the United States military F-16, A-10, F/A-18 (excluding newer E/F "Super Hornet" variants) and AV-8B tactical fighter and attack aircraft, and meet anticipated performance expectation enhancements covering military requirements up to 2035.[20] Originally planned to keep development, production, and operating costs down, a common design was originally optimistically planned in three variants that would share 80 percent of their parts. However, by April 2017 the variants were sharing at most twenty percent common design:[20]

  • F-35A, conventional take off and landing (CTOL) variant.
  • F-35B, short-take off and vertical-landing (STOVL) variant.
  • F-35C, carrier-based CATOBAR (CV) variant.
Engineer handling a metallic scale model of jet fighter in wind-tunnel
An F-35 wind tunnel testing model in the Arnold Engineering Development Center's 16-foot transonic wind tunnel

The design goals call for the F-35 to be the premier strike aircraft through 2040 and to be second only to the F-22 Raptor in air supremacy.[21] George Standridge, Vice President of Strategy and Business Development for Lockheed Martin Aeronautics, predicted in 2006 that the F-35 would be four times more effective than legacy fighters in air-to-air combat, eight times more effective in air-to-ground combat, and three times more effective in reconnaissance and Suppression of Enemy Air Defenses – while having better range and requiring less logistics support and having around the same procurement costs (if development costs are ignored) as legacy fighters.[22]

The JSF development contract was signed on 16 November 1996, and the contract for System Development and Demonstration (SDD) was awarded by the Department of Defense (DoD) on 26 October 2001 to Lockheed Martin, whose X-35 beat the Boeing X-32. Although both aircraft met or exceeded requirements, the X-35 design was considered to have less risk and more growth potential.[23] The designation of the new fighter as "F-35" is out-of-sequence with standard DoD aircraft numbering,[24] by which it should have been "F-24". It came as a surprise even to the company, which had been referring to the aircraft in-house by this expected designation.[25]

The development of the F-35 is unusual for a fighter aircraft in that no two-seat trainer versions have been built for any of the variants; advanced flight simulators mean that no trainer versions were deemed necessary.[26] Instead F-16s have been used as bridge trainers between the T-38 and the F-35. The T-X was intended to be used to train future F-35 pilots, but this might succumb to budget pressures in the USAF.[27]

Design phase

Based on wind tunnel testing, Lockheed Martin slightly enlarged its X-35 design into the F-35. The forward fuselage is Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). longer to make room for avionics. Correspondingly, the horizontal stabilators were moved Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). rearward to retain balance and control. The top surface of the fuselage was raised by Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). along the center line. Also, it was decided to increase the size of the F-35B STOVL variant's weapons bay to be common with the other two variants.[23] Manufacturing of parts for the first F-35 prototype airframe began in November 2003.[28] Because the X-35 did not have weapons bays, their addition in the F-35 would cause design changes which would lead to later weight problems.[29][30]

The F-35B STOVL variant was in danger of missing performance requirements in 2004 because it weighed too much; reportedly, by 2,200 lb (1,000 kg) or 8 percent. In response, Lockheed Martin added engine thrust and thinned airframe members; reduced the size of the common weapons bay and vertical stabilizers; re-routed some thrust from the roll-post outlets to the main nozzle; and redesigned the wing-mate joint, portions of the electrical system, and the portion of the aircraft immediately behind the cockpit.[31] Many of the changes were applied to all three variants to maintain high levels of commonality. By September 2004, the weight reduction effort had reduced the aircraft's design weight by Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value).,[32] but the redesign cost $6.2 billion and delayed the project by 18 months.[33]

On 7 July 2006, the U.S. Air Force, the lead service for the aircraft, officially announced the name of the F-35: Lightning II, in honor of Lockheed's World War II-era twin-propeller Lockheed P-38 Lightning for the United States Army Air Forces and the Cold War-era jet, the English Electric Lightning for the Royal Air Force.[34][N 2]

Lockheed Martin Aeronautics is the prime contractor and performs aircraft final assembly, overall system integration, mission system, and provides forward fuselage, wings and aircraft flight control system. Northrop Grumman provides active electronically scanned array (AESA) radar, electro-optical AN/AAQ-37 Distributed Aperture System (DAS), Communications, Navigation, Identification (CNI), center fuselage, weapons bay, and arrestor gear. BAE Systems provides the Flight Control Software (FCS1), the electronic warfare systems, crew life support and escape systems, aft fuselage, empennages as well as the horizontal and vertical tails. Alenia will perform final assembly for Italy and, according to an Alenia executive, assembly of all European aircraft with the exception of Turkey and the United Kingdom.[36][37] The F-35 program has seen a great deal of investment in automated production facilities. For example, Handling Specialty produced the wing assembly platforms for Lockheed Martin.[38]

On 19 December 2008, Lockheed Martin rolled out the first weight-optimized F-35A, designated AF-1. It was the first F-35 built at full production speed, and is structurally identical to the production F-35As that were delivered starting in 2010.[39] On 5 January 2009, six F-35s had been built, including AF-1; another 13 pre-production test aircraft and four production aircraft were being manufactured.[40] On 6 April 2009, U.S. Secretary of Defense Robert Gates proposed speeding up production for the U.S. to buy 2,443 F-35s.[41]

Program cost overruns and delays

Lua error in package.lua at line 80: module 'strict' not found. The F-35 program has experienced a number of cost overruns and developmental delays. The program's delays have come under fire from the U.S. Congress and some U.S. Department of Defense officials. The program has undergone a number of reassessments and changes since 2006. The Government Accountability Office (GAO) warned in March 2006 that excessive concurrency ("an overlap of flight testing and initial production"[42]) might result in expensive refits for several hundred F-35 aircraft that are planned for production before design testing is completed.[43] In 2010, acquisition chief Ashton Carter issued an Acquisition Decision Memorandum restructuring the F-35 program.[44] In November 2010, the GAO found that "Managing an extensive, still-maturing global network of suppliers adds another layer of complexity to producing aircraft efficiently and on-time" and that "due to the extensive amount of testing still to be completed, the program could be required to make alterations to its production processes, changes to its supplier base, and costly retrofits to produced and fielded aircraft, if problems are discovered."[45] USAF budget data in 2010, along with other sources, projected the F-35 to have a flyaway cost from US$89 million to US$200 million over the planned production run.[46][47] In February 2011, the Pentagon put a price of $207.6 million on each of the 32 aircraft to be acquired in FY2012, rising to $304.16 million (a total acquisition cost of $9.7 billion for 32 aircraft) if its share of research, development, test and evaluation (RDT&E) spending is included.[48][49]

On 21 April 2009, media reports, citing Pentagon sources, said that during 2007 and 2008, spies downloaded several terabytes of data related to the F-35's design and electronics systems, potentially compromising the aircraft and aiding the development of defense systems against it.[50] Lockheed Martin rejected suggestions that the project was compromised, stating it "does not believe any classified information had been stolen".[51] Other sources suggested that the incident caused both hardware and software redesigns to be more resistant to cyber attack.[52] In March 2012, BAE Systems was reported to be the target of cyber espionage. BAE Systems refused to comment on the report, although they did state, "[Our] own cyber security capability can detect, prevent and rectify such attacks."[53] On 9 November 2009, Ashton Carter, under-secretary of defense for acquisition, technology and logistics, acknowledged that the Pentagon "joint estimate team" (JET) had found possible future cost and schedule overruns in the project and that he would be holding meetings to attempt to avoid these.[54] On 1 February 2010, Gates removed the JSF Program Manager, U.S. Marine Corps Major General David Heinz, and withheld $614 million in payments to Lockheed Martin because of program costs and delays.[55][56]

On 11 March 2010, a report from the Government Accountability Office to United States Senate Committee on Armed Services projected the overall unit cost of an F-35A to be $113 million in "today's money."[57] In 2010, Pentagon officials disclosed that the F-35 program had exceeded its original cost estimates by more than 50 percent.[58] An internal Pentagon report critical of the JSF project stated that "affordability is no longer embraced as a core pillar". In 2010, Lockheed Martin expected they would be able to reduce costs projected by government estimators by 20 percent.[59] On 24 March 2010, Robert Gates, Secretary of Defense, in testimony before Congress, declared the cost overruns and delays "unacceptable," characterizing previous cost and schedule estimates as "overly rosy". Gates insisted the F-35 would become "the backbone of U.S. air combat for the next generation" and informed Congress that he had extended the development period by an additional 13 months and budgeted $3 billion more for the testing program, while slowing down production.[60] In August 2010, Lockheed Martin announced delays in resolving a "wing-at-mate overlap" production problem, which would slow initial production.[61] In November 2010, as part of a cost-cutting measure, the co-chairs of the National Commission on Fiscal Responsibility and Reform suggested cancelling the F-35B and halving orders for F-35As and F-35Cs.[62][63][64] Air Force Magazine reported that "Pentagon officials" were considering canceling the F-35B because its short range meant that the forward bases or amphibious ships from which it would operate would be in range of hostile tactical ballistic missiles.[65] Lockheed Martin consultant Loren B. Thompson said that this ″rumor″ was a result of the usual tensions between the U.S. Navy and Marine Corps, and there was no alternative other than the F-35B as a replacement for AV-8B Harrier II.[66] He also confirmed that there were further delays and cost increases due to technical problems with the aircraft and software, blaming most of the delays and extra costs on redundant flight tests.[67] In November 2010, the Center for Defense Information expected that the F-35 program would be restructured, resulting in an additional year of delay and increasing the cost by another $5 billion.[68] On 5 November 2010, the Block 1 software flew for the first time on BF-4.[69] As of the end of 2010, it was said that only 15% of the software remained to be written, but this was reported to include the most difficult sections such as data fusion.[70] In 2011, it was revealed that actually, only 50% of the estimated eight million lines of code needed had been written and that, according to the newest schedule, it would take another six years to complete the software.[71] By 2012, the total estimated lines of code for the entire program (onboard and offboard) had grown from the previous year's estimate of 8 million lines to 24 million lines.[72]

In 2011, the program head and Commander of the Naval Air Systems Command, Vice Admiral David Venlet, confirmed that the concurrency (testing and production at the same time) built into the program "was a miscalculation".[73] This was said during a contract dispute, in which the Pentagon insisted that Lockheed Martin help cover the costs of applying fixes found during testing of aircraft already produced.[74] Lockheed Martin objected that the cost sharing posed an uninsurable, unbounded risk that the company could not cover, and later responded that the "concurrency costs for F-35 continue to reduce".[75][76] The Senate Armed Services Committee strongly backed the Pentagon position.[77] However in December 2011, Lockheed Martin accepted a cost sharing agreement.[78] The Aerospace Industries Association warned that such changes would force them to anticipate cost overruns in the future when bidding on contracts.[79] As of 2012, problems found during flight testing were expected to continue to lead to higher levels of engineering changes through 2019.[80] The total additional cost for concurrency in the program is around $1.3 billion.[81] By the next year the cost had grown to $1.7 billion.[82] In January 2011, Defense Secretary Robert Gates expressed the Pentagon's frustration with the rising costs of the F-35 program when he said, "The culture of endless money that has taken hold must be replaced by a culture of restraint." Focusing his attention on the troubled F-35B, Gates ordered "a two-year probation", saying it "should be canceled" if corrections are unsuccessful.[83] Gates had previously stated his support for the program.[84] Some private analysts, such as Richard Aboulafia, of the Teal Group said that the F-35 program was becoming a money pit.[85] Gates' successor, Leon Panetta, ended the F-35B's probation on 20 January 2012, stating "The STOVL variant has made—I believe and all of us believe—sufficient progress."[86] In February 2011, former Pentagon manager Paul G. Kaminski said that the lack of a complete test plan would add five years to the JSF program.[87] Initial operating capability (IOC) will be determined by software development rather than by hardware production or pilot training.[88] As of May 2013, the USMC plans to have Initial Operating Capability by "mid-2015" for the F-35B, using Block 2B software, which gives basic air-to-air and air-to-ground capability. It is reported that the USAF plans to push ahead, expecting to have Initial Operating Capability with the F-35A in mid-2016, using Block 3I software, rather than waiting for the full-capability Block 3F software, which is expected to be available by mid-2017. The F-35C will not enter service with the USN until mid-2018.[89] The $56.4 billion development project for the aircraft should be completed in 2018 when the Block 5 configuration is expected to be delivered, several years late and considerably over budget.[90]

Delays in the F-35 program may lead to a "fighter gap" with the United States and other countries lacking sufficient fighter aircraft to meet their requirements.[91] Israel may seek to buy second-hand F-15Es,[92] while Australia has considered buying additional F/A-18 Super Hornets in the face of F-35 delays.[93] In May 2011, the Pentagon's top weapons buyer, Ashton Carter, said that the latest price estimate of $133 million per aircraft was not affordable.[94] In 2011, The Economist warned that the F-35 was in danger of slipping into a "death spiral," where increasing per-aircraft costs would lead to cuts in number of aircraft ordered, leading to further cost increases and further cuts in orders.[95] Later that year, four aircraft were cut from the fifth "Low Rate Initial Production (LRIP)" order because of cost overruns.[96] In 2012, a further two aircraft were cut.[97] Lockheed Martin acknowledged that the slowing of purchases would increase costs.[98] David Van Buren, U.S. Air Force acquisition chief, said that Lockheed Martin needed to reduce manufacturing capacity to match the reduced market for their aircraft.[99] However, the company said that the slowdown in American orders would free up capacity, which could be diverted to meet urgent, short-term needs of foreign partners for replacement fighters.[100] Air Force Secretary Michael Donley said that no more money was available and that future price increases would be met with cuts in the number of aircraft ordered.[101] Later that month, the Pentagon reported that costs had risen another 4.3 percent, in part because of production delays.[102] In 2012, the purchase of six out of 31 aircraft was conditioned on progress of development and testing.[103] In 2013, Bogdan repeated that no more money was available, but that he hoped to avoid the death spiral.[104] In 2014 it was reported that another eight aircraft would be cut from the following year's order.[105]

Japan has warned that it may halt its purchase of the F-35 if the cost per aircraft increases and Canada has indicated it has not yet committed to purchase the aircraft.[106][107] The United States is now projected to spend an estimated $323 billion for development and procurement of the F-35, making it the most expensive defense program ever.[108] Testifying before a Canadian parliamentary committee in 2011, Rear Admiral Arne Røksund of Norway estimated that his country's 52 F-35 fighter jets will cost $769 million each over their operational lifetime.[109] In 2012, the total life-cycle cost for the entire U.S. fleet was estimated at US$1.51 trillion over a 50-year life, or $618 million per plane.[110] In hopes of reducing this high lifetime cost, the USAF is considering reducing Lockheed Martin's role in contractor logistics support.[111] The company has responded that the Pentagon's lifetime cost estimate includes future costs beyond its control, such as USAF reorganizations and yet-to-be-specified upgrades.[112] Delays have also negatively affected the program's worldwide supply chain and partner organizations as well.[113]

In 2012, General Norton A. Schwartz decried the "foolishness" of reliance on computer models to arrive at the final design of aircraft before flight testing has found the problems that require changes in design.[114] In 2013, JSF project team leader, USAF Lieutenant General Chris Bogdan, said that "A large amount of concurrency, that is, beginning production long before your design is stable and long before you've found problems in test, creates downstream issues where now you have to go back and retrofit airplanes and make sure the production line has those fixes in them. And that drives complexity and cost".[115] Bogdan remarked on the improvement in the program ever since Lockheed Martin was forced to assume some of the financial risks.[116] In 2012, in order to avoid further delays that would result from design changes, the U.S. DoD accepted a reduced combat radius for the F-35A and a longer takeoff run for the F-35B.[117][118] As a result, the F-35B's estimated combat radius was reduced by 15 percent.[119] In a meeting in Sydney, Australia in March 2012, the United States pledged to eight partner nations that there would be no more program delays.[120] In May 2012, Lockheed Martin Chief Executive Bob Stevens complained that the Defense Department's requirements for cost data were themselves driving up program costs.[121] Stevens also said that a strike by union employees might result in failure to meet that year's production target of 29 F-35s.[122] Striking workers questioned the quality of work done by temporary replacements, noting that even their own work had been cited for "inattention to production quality," resulting in a 16% rework rate.[123] The workers went on strike to protect pensions, the cost of which had been the subject of negotiations with the Department of Defense over orders for the next batch of aircraft.[124] These same pension costs were cited by Fitch in their downgrade of the outlook for Lockheed Martin's stock price.[125] Stevens said that while he hoped to bring down program costs, the industrial base was not capable of meeting the government's cost expectations, given the current number of aircraft on order.[126][127]

According to a June 2012 Government Accountability Office report, the F-35's unit cost had almost doubled, with an increase of 93% over the program's original, 2001 baseline cost estimates.[128] In 2012, Lockheed Martin reportedly feared that the tighter policies of the Obama administration regarding award fees would reduce their profits by $500 million over the coming five years.[129] This in fact occurred in 2012, when the Pentagon withheld the maximum $47 million allowed, for the company's failure to certify its program for tracking project costs and schedules.[130] The GAO also faulted the USAF and USN for not fully planning for the costs of extending legacy F-16 and F-18 fleets to cover the delay in acquiring the F-35.[131] Because of cost-cutting measures, the U.S. Government asserts that the "flyaway" cost (including engines) has been dropping. The U.S. Government estimates that in 2020 an "F-35 will cost some $85m each, or less than half of the cost of the initial units delivered in 2009. Adjusted to today’s dollars, the 2020 price would be $75m each."[132]

In 2013, Lockheed Martin began to lay off workers at the Fort Worth, Texas plant where the F-35s were being assembled.[133] They said that revised estimates indicated that the costs of refitting the 187 aircraft built by the time testing concludes in 2016 would be lower than feared.[134] The GAO's Michael Sullivan said that the company had failed to get an early start on systems engineering and had not understood the requirements or the technologies involved at the program's start.[135] The Pentagon vowed to continue funding the program during budget sequestration if possible.[136] It was feared that the U.S. budget sequestration in 2013 could slow development of critical software[137] and the Congress ordered another study to be made on the software development delays.[138] As of 2014, software development remained the "number one technical challenge" for the F-35.[139] In June 2013, Frank Kendall, Pentagon acquisition, technology and logistics chief, declared "major advances" had been made in the F-35 program over the last three years and that he intended to approve production-rate increases in September. Air Force Lt. Gen. Christopher Bogdan, program executive officer, reported far better communications between government and vendor managers, and that negotiations over Lot 6 and 7 talks were moving fast. It was also stated that operating costs had been better understood since training started. He predicted "we can make a substantial dent in projections" of operating costs.[140] In July 2013, further doubt was cast on the latest production schedule, with further software delays and continuing sensor, display and wing buffet problems.[141] In August it was revealed that the Pentagon was weighing cancellation of the program as one possible response to the budget sequestration[142][143] and the United States Senate Appropriations Subcommittee on Defense voted to cut advanced procurement for the fighter.[144]

On August 21, 2013, C-Span reported that Congressional Quarterly and the Government Accountability Office were indicating the "total estimated program cost now is $400 billion, nearly twice the initial cost". The current investment was documented as approximately $50 billion. The projected $316 billion cost in development and procurement was estimated through 2037 at an average of $12.6 billion per year. These were confirmed by Steve O'Bryan, Vice President of Lockheed Martin, on the same date.[145] In 2013, a RAND study found that during development, the three different versions had drifted so far apart from each other, that having a single base design might have come to be more expensive than if the three services had simply built entirely different aircraft, each tailored to their own requirements.[146] On 10 April 2017 Bloomberg Businessweek reported that the total expenditures for the F-35 program would approach $1 trillion.[147]

In 2014, the airframe cost went below $100 million for the first time, and the Air Force expected unit costs to fall.[148] A 2014 Center for International Policy study cast doubt on the number of indirect jobs created by the program, which has been a key selling point for the F-35 to Congress. Lockheed stood by their job numbers and said that their accounting was in line with industry norms.[149] A January 2014 report by J. Michael Gilmore said that new software delays could delay Block 2B release by 13 months.[150] This estimate was reduced to 4 months in the DOTE report from November 2014.[151] The F-35 program office considered software to be the top technical risk to the program. The USMC was maintaining their expectation of an Initial Operational Capability by July 2015.[152] In 2014, U.S. Senator John McCain blamed cost increases in the program on "cronyism".[153] In 2014, the GAO found that the F-35 fleet would have operating costs 79% higher than the aircraft it was to replace.[154] In 2014, the FY2015 Selected Acquisition Report stated that the program cost had increased 43% from 2001, with Program Acquisition Unit Cost up 68% and Unit Recurring Flyaway up 41%.[155] The F-35A's cost per flying hour in BY2012 dollars is $32,500 while the F-16C/D is $25,500, but each F-35A is expected to fly only 250 hours a year, compared to the F-16's 316 hours a year, resulting in the same yearly operating cost.[155][156] In July 2014, Lockheed Martin, Northrop Grumman, and BAE Systems announced they would invest a combined $170 million in the program[clarification needed], which was anticipated to result in savings of over $10 million per aircraft. This initiative was said to have set the project on track for an $80M (including engine) price tag per aircraft (F-35A) by 2018, when full production is scheduled to begin.[157] The December 2014 Selected Acquisition Report listed a cost decrease of $7.5 billion against a program cost of $391.1 billion ($320 billion in 2012 dollars). Lockheed Martin also stated that there would be an estimated decrease of nearly $60 billion to the operations and support costs.[158]

In December 2015, the FY2017 Selected Acquisition Report had revised the F-35A's cost per flying hour in BY2012 dollars to $29,806, in comparison with the F-16C/D's antecedent of $25,541, also in BY2012 dollars. This was a result of a decrease in the assumed cost per gallon of JP-8 fuel, a decrease in the fuel burn rate for the F-35A variant and a revised cost estimating relationship for hardware modifications.[159] The 2015 DoD annual report stated that the current schedule to complete System Development and Demonstration (SDD) and enter Initial Operational Testing and Evaluation (IOT&E) by August 2017 was unrealistic, instead the program would likely not finish Block 3F development and flight testing prior to January 2018. Based on those projected completion dates for Block 3F developmental testing, IOT&E would not start earlier than August 2018.[160][161]

The Block 3I software was intended to be a revision of the Block 2B software to run on the updated Integrated Core Processor.[162] Unfortunately, it resulted in a timing misalignment that reduced stability, requiring reboots in flight.[163] By May 2016 the software had been improved to the point where it only crashed every 15 hours.[164] Reboots were required over a third of the time for ground cold starts.[165] The following month saw 88 successful sorties untroubled by the stability bug.[166]

Concerns over performance and safety

A Lockheed Martin press release points to USAF simulations regarding the F-35's air-to-air performance against adversaries described as "4th generation" fighters, in which it states the F-35 is "400 percent" more effective. Major General Charles R. Davis, USAF, the F-35 program executive officer, has stated that the "F-35 enjoys a significant Combat Loss Exchange Ratio advantage over the current and future air-to-air threats, to include Sukhois".[167]

In September 2008, in reference to the original plan to fit the F-35 with only two air-to-air missiles (internally), Major 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."[168] The Norwegians have been briefed on a plan to equip the F-35 with six AIM-120D missiles by 2019.[169] Former RAND author John Stillion has written of the F-35A's air-to-air combat performance that it "can't turn, can't climb, can't run"; Lockheed Martin test pilot Jon Beesley has stated that in an air-to-air configuration the F-35 has almost as much thrust as weight and a flight control system that allows it to be fully maneuverable even at a 50-degree angle of attack.[170][171] Consultant to Lockheed Martin Loren B. Thompson has said that the "electronic edge F-35 enjoys over every other tactical aircraft in the world may prove to be more important in future missions than maneuverability".[172]

In an April 2009 interview with the state-run[173] Global Times, Chen Hu, editor-in-chief of World Military Affairs magazine said that the F-35 is too costly because it attempts to provide the capabilities needed for all three American services in a common airframe.[174] U.S. defense specialist Winslow T. Wheeler and aircraft designer Pierre Sprey have commented of the F-35 being "heavy and sluggish" and possessing "pitifully small load for all that money", further criticizing the value for money of the stealth measures as well as lacking fire safety measures; his final conclusion was that any air force would be better off maintaining its fleets of F-16s and F/A-18s compared to buying into the F-35 program.[175] A senior U.S. defense official was quoted as saying that the F-35 will be "the most stealthy, sophisticated and lethal tactical fighter in the sky," and added "Quite simply, the F-15 will be no match for the F-35."[176] After piloting the aircraft, RAF Squadron Leader Steve Long said that, over its existing aircraft, the F-35 will give "the RAF and Navy a quantum leap in airborne capability."[177]

In November 2009, Jon Schreiber, head of F-35 international affairs program for the Pentagon, said that the U.S. will not share the software code for the F-35 with its allies.[178] The US plans to set up a reprogramming facility that will develop JSF software and distribute it to allies.[179] In 2014 in order to deal with capacity issues in the creation of mission data packages at the Air Combat Command reprogramming lab at Eglin Air Force Base, Fla., plans were announced to open additional mission data labs to customize mission data packages with terrain and enemy threat information for different regions and partner nation needs.[180] DARPA is working on the Adaptive Radar Countermeasures (ARC) project to provide protection in real time for previously unknown threat radars.[181]

In 2011, Canadian politicians raised the issue of the safety of the F-35's reliance on a single engine (as opposed to a twin-engine configuration, which provides a backup in case of an engine failure). Canada, and other operators, had previous experience with a high-accident rate with the single-engine Lockheed CF-104 Starfighter with many accidents related to engine failures. When asked what would happen if the F-35's single engine fails in the Far North, Defence Minister Peter MacKay stated "It won’t".[182]

In November 2011, a Pentagon study team identified 13 areas of concern that remained to be addressed in the F-35.[183][184]

In May 2012, Michael Auslin of the American Enterprise Institute questioned the capability of the F-35 to engage modern air defenses.[185] In July 2012, the Pentagon awarded Lockheed Martin $450 million to improve the F-35 electronic warfare systems and incorporate Israeli systems.[186]

In a negative assessment of the Joint Strike Fighter, the think tank Air Power Australia declared that the Joint Strike Fighter is not designed to perform air superiority roles and also is not adapted to performing the long-range penetration strike role filled by previous Australian aircraft like the General Dynamics F-111C. Critically, they also stated that the F-35’s "intended survivability and lethality are mismatched against the operational environment in which the aircraft is intended to be used."[187]

In June 2012, Australia's Air Vice Marshal Osley responded to Air Power Australia's criticisms by saying "Air Power Australia (Kopp and Goon) claim that the F-35 will not be competitive in 2020 and that Air Power Australia's criticisms mainly center around F-35's aerodynamic performance and stealth capabilities." Osley continued, "these are inconsistent with years of detailed analysis that has been undertaken by Defence, the JSF program office, Lockheed Martin, the U.S. services and the eight other partner nations. While aircraft developments, such as the Russian PAK-FA or the Chinese J20, as argued by Airpower Australia, show that threats we could potentially face are becoming increasingly sophisticated, there is nothing new regarding development of these aircraft to change Defence's assessment." He then said that he thinks that the Air Power Australia's "analysis is basically flawed through incorrect assumptions and a lack of knowledge of the classified F-35 performance information."[188]

A report released in 2013 stated that flaws in the fuel tank and fueldraulic (fuel-based hydraulic) systems have left it considerably more vulnerable to lightning strikes and other fire sources, including enemy fire, than previously revealed, especially at lower altitudes,[189] the restriction on blue skies flights was removed in 2015.[190] This report updated a separate report from 2010, in which Lockheed Martin spokesman John Kent said that adding fire-suppression systems would offer "very small" improvement to survivability.[191] The same 2010 report also noted performance degradation of the three variants; the sustained turn rates had been reduced to 4.6 g for the F-35A, 4.5 g for the F-35B, and 5.0 g for the F-35C. The acceleration performance of all three variants was also downgraded, with the F-35C taking 43 seconds longer than an F-16 to accelerate from Mach 0.8 to Mach 1.2; this was judged by several fighter pilots to be a lower performance level than expected from a fourth generation fighter.[192] On 30 August 2013, it was reported that the F-35B and F-35C models take several complex maneuvers in order to "accelerate" to their top speed of Mach 1.6, which consumed almost all of the onboard fuel.[193] The F-35 program office is reconsidering addition of previously removed safety equipment.[194] In 2012, Lockheed Martin program manager Tom Burbage said that while the relatively large cross-sectional area of the fighter that was required by the internal weapons bays gave it a disadvantage against fourth generation fighters that were operating in a clean configuration, the F-35 armed with weapons carried internally had the advantage over fighters carrying their weapons outside the aircraft.[195]

In March 2013, USAF test pilots, flying with pre-operational software that did not utilize the all-aspect infrared AAQ-37 DAS sensor, noted a lack of visibility from the F-35 cockpit during evaluation flights, which would get them consistently shot down in combat. Defense spending analyst Winslow Wheeler concluded from flight evaluation reports that the F-35A "is flawed beyond redemption";[196] in response, program manager Bogdan suggested that pilots worried about being shot down should fly cargo aircraft instead.[197] The same report found (in addition to the usual problems with the aircraft listed above):

  • Current aircraft software is inadequate for even basic pilot training.
  • Ejection seat may fail, causing pilot fatality.
  • Several pilot-vehicle interface issues, including lack of feedback on touchscreen controls.
  • The radar performs poorly, or not at all.
  • Engine replacement takes an average of 52 hours, instead of the two hours specified.
  • Maintenance tools do not work.[198]

The JPO responded that more experienced pilots would be able to safely operate the aircraft and that procedures would improve over time.[199]

Even in the final "3F" software version, the F-35 will lack ROVER, in spite of having close air support as one of its primary missions.[200]

In 2014, David Axe stated design flaws related to its single-engine configuration could vex the F-35 for decades to come, forcing the Pentagon to suspend flying too often for the majority of its fighter fleet.[201]

In November 2014, China unveiled the portable JY-26 Skywatch-U UHF 3-D long-range surveillance radar system, specifically designed to defeat stealth aircraft like the F-35.[202] Responding to a reporter's question about the High-Frequency radar threat General Welsh said "while we may have a new radar developed that allows an acquisition radar to see an airplane, that doesn't mean you can pass the track off to a radar that will then guide a weapon to be able to destroy the airplane. As long as we break the kill chain sometime between when you arrive in the battle space and when the enemy weapon approaches your airplane, you're successful at using stealth."[203]

A 2014 Pentagon report found these issues:

  • First two mission data sets available November 2015, after USMC IOC.
  • Overall operational suitability relies heavily on contractor support and unacceptable workarounds.
  • Aircraft availability reached 51% but short of 60% goal.
  • Fuel Tanks don't retain inerting for required 12 hours after landing.
  • High dynamic loads on the rudder at lower altitudes in 20–26 AoA preventing testing.
  • 82 pounds added to F-35B in last 38 months, 337 pounds below limit.
  • Transonic Roll-Off (TRO) and airframe buffet continue to be program concerns.
  • 572 deficiencies remain affecting Block 2B capability, 151 of which are critical.
  • VSim would likely not support planned Block 2B operational testing in 2015.
  • Maintainability hours still an issue.
  • ALIS requires many manual workarounds.[151]

A 2015 Pentagon report found these issues:[204]

  • The Joint Program Office is re-categorizing or failing to count aircraft failures to try to boost maintainability and reliability statistics;
  • Testing is continuing to reveal the need for more tests, but the majority of the fixes and for capability deficiencies being discovered are being deferred to later blocks rather than being resolved;
  • The F-35 has a significant risk of fire due to extensive fuel tank vulnerability, lightning vulnerability, and its OBIGGS system's inability to sufficiently reduce fire-sustaining oxygen, despite redesigns;
  • Wing drop concerns are still not resolved after six years, and may only be mitigated or solved at the expense of combat maneuverability and stealth;
  • The June engine problems are seriously impeding or preventing the completion of key test points, including ensuring that the F-35B delivered to the Marine Corps for IOC meets critical safety requirements; no redesign, schedule, or cost estimate for a long-term fix has been defined yet, thereby further impeding g testing;
  • Even in its third iteration, the F-35’s helmet continues to show high false-alarm rates and computer stability concerns, seriously reducing pilots’ situational awareness and endangering their lives in combat;
  • The number of Block 2B’s already limited combat capabilities being deferred to later blocks means that the Marine Corps’ FY2015 IOC squadron will be even less combat capable than originally planned;
  • ALIS software failures continue to impede operation, mission planning, and maintenance of the F-35, forcing the Services to be overly reliant on contractors and "unacceptable workarounds";
  • Deficiencies in Block 2B software, and deferring those capabilities to later blocks, is undermining combat suitability for all three variants of the F-35;
  • The program’s attempts to save money now by reducing test points and deferring crucial combat capabilities will result in costly retrofits and fixes later down the line, creating a future unaffordable bow wave that, based on F-22 experience, will add at least an additional $67 billion in acquisition costs; and
  • Low availability and reliability of the F-35 is driven by inherent design problems that are only becoming more obvious and difficult to fix.

Three different types of data "massaging" are identified in the DOT&E report:[205] moving failures from one category to another, less important one; ignoring repetitive failures, thus inflating numbers of failure-free hours; and improper scoring of reliability.[206] Maintenance problems were determined to be so severe that the F-35 is only able to fly twice a week. To address the issue of wing drop and buffet maneuvering, the required control law modifications will reduce the maneuverability of the F-35, "only exacerbating the plane’s performance problems in this area". The F-35C's wing drop problem is "worse than other variants". Testing to investigate the impact of buffet and transonic roll-off (TRO or "wing drop") on the helmet-mounted display and offensive and defensive maneuvering found that "buffet affected display symbology, and would have the greatest impact in scenarios where a pilot was maneuvering to defeat a missile shot." Buffeting also degrades the gyroscopes in the inertial platforms which are essential for flight control, navigation, and weapons aiming. DOT&E explained that this was an ongoing issue: "In heavy buffet conditions, which occur between 20 and 26 degrees angle of attack, faults occurred in the inertial measurement units (IMUs) in the aircraft that degraded the flight control system (two of three flight control channels become disabled), requiring a flight abort."[207]

In early 2015 the AF-2 F-35A, the primary flight sciences loads and flutter evaluation aircraft, was flown by Lockheed Martin F-35 site lead test pilot David "Doc" Nelson in air-to-air combat maneuvers against F-16s for the first time and, based on the results of these and earlier flight-envelope evaluations, said the aircraft can be cleared for greater agility as a growth option. AF-2 was the first F-35 to be flown to 9g+ and −3g, and to roll at design-load factor. Departure/spin resistance was also proven during high angle-of-attack (AOA) testing which eventually went as high as 110 deg. AOA. "When we did the first dogfight in January, they said, ‘you have no limits,’" says Nelson. "It was loads monitoring, so they could tell if we ever broke something. It was a confidence builder for the rest of the fleet because there is no real difference structurally between AF-2 and the rest of the airplanes." "Pilots really like maneuverability, and the fact that the aircraft recovers so well from a departure allows us to say [to the designers of the flight control system laws], ‘you don’t have to clamp down so tight,’" says Nelson.[208]

With the full flight envelope now opened to an altitude of 50,000 ft, speeds of Mach 1.6/700 KCAS and loads of 9 g, test pilots also say improvements to the flight control system have rendered the transonic roll-off (TRO) issue tactically irrelevant. Highlighted as a "program concern" in the Defense Department’s Director of Operational Test and Evaluation (DOT&E) 2014 report, initial flight tests showed that all three F-35 variants experienced some form of wing drop in high-speed turns associated with asymmetrical movements of shock waves. However, TRO "has evolved into a non-factor," says Nelson, who likens the effect to a momentary "tug" on one shoulder harness. "You have to pull high-g to even find it." The roll-off phenomena exhibits itself as "less than 10 deg./sec. for a fraction of a second. We have been looking for a task it affects and we can’t find one."[208]

In July 2015, Lockheed Martin confirmed the authenticity of a leaked report showing the F-35 to be less maneuverable than an older F-16D with wing tanks.[209][210] The pilot who flew the mission reported inferior energy maneuverability, a limited pitch rate and flying qualities that were "not intuitive or favorable" in a major part of the air-combat regime gave the F-16 the tactical advantage. In general the high AoA capabilities of the jet could not be used in an effective way without significantly reducing follow-on maneuvering potential. In an interview with CBC Radio broadcast 2 July 2015, military journalist David Axe claimed to have read the leaked report and stated: "Against a determined foe, the F-35 is in very big trouble."[211] However, the F-35 used was a flight test aircraft with a restricted flight envelope and lacked some features present on the operational aircraft.[212][213] The Pentagon, JPO, and defense analysts have defended the F-35's utility in spite of the report's assertion that it lacks maneuverability by saying it was designed primarily to disrupt the kill chain of advanced air defenses while the F-22 would handle close-in dogfighting, it has advanced sensor and information fusion capabilities to detect and engage enemy aircraft at long ranges before it can be seen and merged with, and that most air combat in recent decades has focused on sensors and weapons that achieved long-range kills rather than close combat.[214][215]

The report's conclusions and recommendations noted loads remained below limits, implying there may be more maneuverability available to the airframe. There were five recommendations: increase pitch rate and available Nz (Normal Acceleration g) to provide the pilot with more maneuverability options given the inherent energy deficit; consider increasing alpha onset to also help offset the energy maneuverability deficit; consider increasing the beginning of the high AoA blended region to 30 degrees or greater to make high AoA maneuvering more predictable and intuitive; consider increasing pilot yaw rate to remove the gradual sluggish yaw response; and improve HMD Boresight performance to account for dynamic maneuvers and consider improving rearward visibility by creating more space for helmet motion.[209][216]

On 14 April 2016 the Government Accountability Office (GAO) released a report on the $16.7 billion Autonomic Logistics Information System (ALIS) expressing concerns that a failure in the logistics system, which serves as the "brains" of the F-35, could ground the entire fleet because it lacked a back-up for processing data. ALIS supports everything from the plane's operations, pilot scheduling, mission planning and supply chain management to maintenance; it is therefore one of the three major components of the jet, along with the airframe and engine. GAO said one of the biggest concerns raised by 120 F-35 pilots, maintenance staff, contractors and program officials interviewed for the report was the lack of a redundant system for processing ALIS data. GAO noted "DOD is aware of risks that could affect ALIS but does not have a plan to prioritize and address them in a holistic manner to ensure that ALIS is fully functional as the F-35 program approaches key milestones – including Air Force and Navy initial operational capability declarations in 2016 and 2018, respectively, and the start of the program’s full-rate production in 2019". A Pentagon-commissioned study from 2013 concluded that any delays or problems with ALIS could add $20 billion to the F-35 program cost.[217][218]

In May 2016, Flightglobal reported that new Block 3i software was finally installed, improving reliability over earlier Block 3 software. With early Block 3 software, it was reported that aircraft had to be shut down and rebooted or a sensor or radar reset "every 4 hours", which was considered an "unacceptable" rate. According to Flightglobal, "F-35 programme director Lt Gen Christopher Bogdan told Congress...that a failure rate of once every 8-10h or greater would be more acceptable, and recent fixes now seem to have achieved that goal."[219]

Pentagon−Lockheed Martin relation issues

In September 2012, the Pentagon criticized, quite publicly, Lockheed Martin's performance on the F-35 program and stated that it would not bail out the program again if problems with the plane's systems, particularly the helmet-mounted display, were not resolved. The deputy F-35 program manager said that the government's relationship with the company was the "worst I've ever seen" in many years of working on complex acquisition programs. Air Force Secretary Michael Donley told reporters the Pentagon had no more money to pour into the program after three costly restructurings in recent years. He said the department was done with major restructuring and that there was no further flexibility or tolerance for that approach. This criticism followed a "very painful" 7 September review that focused on an array of ongoing program challenges. Lockheed Martin responded with a brief statement saying it would continue to work with the F-35 program office to deliver the new fighter.[220]

On 28 September 2012, the Pentagon announced that the F-35 Joint Strike Fighter support program would become an open competition. They invited companies to participate in a two-day forum on 14–15 November for possible opportunities to compete for work managing the supply chain of the aircraft. Their reason is to reduce F-35 life-cycle costs by creating competition within the program and to refine its acquisition strategy and evaluate alternatives that will deliver the best value, long-term F-35 sustainment solution. This could be hazardous to Lockheed Martin, the current prime contractor for sustainment of all three variants, and selection of another company could reduce their revenues.[221]

In 2013, the officer in charge of the program blamed Lockheed Martin and Pratt & Whitney for gouging the government on costs, instead of focusing on the long-term future of the program.[222]

In 2014, Lockheed was reported to be having problems with build quality, including one aircraft with a valve installed backwards and another with gaps in the stealth coating.[223]

Upgrades

Lockheed Martin's development roadmap extends until 2021, including a Block 6 engine improvement in 2019. The aircraft are expected to be upgraded throughout their operational lives.[224]

In September 2013, Northrop Grumman revealed the development of a company-funded Directional Infrared Counter Measures system in anticipation of a requirement to protect the F-35 from heat-seeking missiles. A laser jammer is expected to be part of the F-35 Block 5 upgrade; it must meet low-observability (LO) requirements and fit in the F-35's restricted space. Called the Threat Nullification Defensive Resource (ThNDR), it is to have a small, powerful laser, beam steering and LO window, use liquid cooling, and fit alongside the distributed aperture system (DAS) to provide spherical coverage with minimal changes; the DAS would provide missile warning and cue the jam head.[225]

Combat capabilities of the F-35 are made possible through software increments to advance technical abilities. Block 2A software enhanced simulated weapons, data link capabilities, and early fused sensor integration. Block 2B software enables the F-35 to provide basic close air support with certain JDAMs and the 500 lb GBU-12 Paveway II, as well as fire the AIM-120 AMRAAM. The Air Force is to declare the F-35 initially operational with Block 3i software. Full operational capability will come from Block 3F software; Block 3F enhances its ability to suppress enemy air defenses and enables the Lightning II to deploy the 500 lb JDAM, the GBU-53/B SDB II, and the AIM-9X Sidewinder. Block 4 software will increase the weapons envelope of the F-35 and is made to counter air defenses envisioned to be encountered past the 2040s. Block 4 upgrades will be broken into two increments; Block 4A in 2021 and Block 4B in 2023. This phase will also include usage of weaponry unique to British, Turkish, and other European countries who will operate Lightning II.[226]

Lockheed has offered the potential of "Higher Definition Video, longer range target detection and identification, Video Data Link, and Infrared (IR) Marker and Pointer" for the EOTS in future upgrades.[227]

The contract for follow-on modernization work (after Block 4) is expected to be awarded in late 2018,[228] with a new block upgrade every two years thereafter as threats evolve.[229] These will alternate hardware and software upgrades, with each refreshed once every four years.[230]

In 2016 Robert Weiss, executive vice president of Lockheed Martin Aeronautics, said that buying more F-35s now would make it cheaper to apply planned upgrades to the entire fleet later.[231]

Design

Overview

F-35A prototype being towed to its inauguration ceremony on 7 July 2006.

The F-35 resembles a smaller, single-engine sibling of the twin-engine Lockheed Martin F-22 Raptor and drew elements from it. The exhaust duct design was inspired by the General Dynamics Model 200 design, proposed for a 1972 supersonic VTOL fighter requirement for the Sea Control Ship.[232] Although several experimental designs have been developed since the 1960s, such as the unsuccessful Rockwell XFV-12, the F-35B is to be the first operational supersonic, STOVL stealth fighter.[233]

Acquisition deputy to the assistant secretary of the Air Force, Lt. Gen. Mark D. "Shack" Shackelford has said that the F-35 is designed to be America's "premier surface-to-air missile killer and is uniquely equipped for this mission with cutting edge processing power, synthetic aperture radar integration techniques, and advanced target recognition."[234][235] Lockheed Martin states the F-35 is intended to have close- and long-range air-to-air capability second only to that of the F-22 Raptor.[236] Lockheed Martin has said that the F-35 has the advantage over the F-22 in basing flexibility and "advanced sensors and information fusion".[237] Lockheed Martin has suggested that the F-35 could replace the USAF's F-15C/D fighters in the air superiority role and the F-15E Strike Eagle in the ground attack role.[238]

Some improvements over current-generation fighter aircraft are:

  • Durable, low-maintenance stealth technology, using structural fiber mat instead of the high-maintenance coatings of legacy stealth platforms;[239]
  • Integrated avionics and sensor fusion that combine information from off- and on-board sensors to increase the pilot's situational awareness and improve target identification and weapon delivery, and to relay information quickly to other command and control (C2) nodes[240][241][242]
  • High speed data networking including IEEE 1394b[243] and Fibre Channel.[244] (Fibre Channel is also used on Boeing's Super Hornet.[245])
  • The Autonomic Logistics Global Sustainment (ALGS), Autonomic Logistics Information System (ALIS) and Computerized maintenance management system (CMMS) are to help ensure aircraft uptime with minimal maintenance manpower.[246] The Pentagon has moved to open up the competitive bidding by other companies.[247] This was after Lockheed Martin stated that instead of costing twenty percent less than the F-16 per flight hour, the F-35 would actually cost twelve percent more.[248] Though the ALGS is intended to reduce maintenance costs, the company disagrees with including the cost of this system in the aircraft ownership calculations.[249] The USMC have implemented a workaround for a cyber vulnerability in the system.[250] The ALIS system currently requires a shipping container load of servers to run, but Lockheed is working on a more portable version to support the Marines' expeditionary operations.[251]
  • Electro-hydrostatic actuators run by a power-by-wire flight-control system.[252]
  • A modern and updated flight simulator, which may be used for a greater fraction of pilot training in order to reduce the costly flight hours of the actual aircraft.[253]
  • Lightweight, powerful Lithium-ion batteries potentially prone to thermal runaway, similar to those that have grounded the Boeing 787 Dreamliner fleet.[254] These are required to provide power to run the control surfaces in an emergency,[255] and have been strenuously tested.[256]

Structural composites in the F-35 are 35% of the airframe weight (up from 25% in the F-22).[257] The majority of these are bismaleimide (BMI) and composite epoxy material.[258] The F-35 will be the first mass-produced aircraft to include structural nanocomposites, namely carbon nanotube reinforced epoxy.[259] Experience of the F-22's problems with corrosion led to the F-35 using a gap filler that causes less galvanic corrosion to the airframe's skin, designed with fewer gaps requiring filler and implementing better drainage.[260] The relatively short 35-foot wingspan of the A and B variants is set by the F-35B's requirement to fit inside the Navy's current amphibious assault ship parking area[261] and elevators; the F-35C's longer wing is considered to be more fuel efficient.[262]

A United States Navy study found that the F-35 will cost 30 to 40 percent more to maintain than current jet fighters;[263] not accounting for inflation over the F-35's operational lifetime. A Pentagon study concluded a $1 trillion maintenance cost for the entire fleet over its lifespan, not accounting for inflation.[264] The F-35 program office found that as of January 2014, costs for the F-35 fleet over a 53-year life cycle was $857 billion. Costs for the fighter have been dropping and accounted for the 22 percent life cycle drop since 2010.[265] Lockheed stated that by 2019, pricing for the fifth-generation aircraft will be less than fourth-generation fighters. An F-35A in 2019 is expected to cost $85 million per unit complete with engines and full mission systems, inflation adjusted from $75 million in December 2013.[266]

Engines

An F-35A powerplant on display, 2014

The Pratt & Whitney F135 powers the F-35. An alternative engine, the General Electric/Rolls-Royce F136, was being developed until it was cancelled by its manufacturers in December 2011 for lack of funding from the Pentagon.[267][268] The F135 and F136 engines are not designed to supercruise.[269] However, the F-35 can briefly fly at Mach 1.2 for 150 miles without the use of an afterburner.[270] The F135 is the second (radar) stealthy afterburning jet engine. Like the Pratt & Whitney F119 from which it was derived, the F135 has suffered afterburner pressure pulsations, or 'screech' at low altitude and high speed.[271] The F-35 has a maximum speed of over Mach 1.6. With a maximum takeoff weight of 60,000 lb (27,000 kg),[N 3][273] the Lightning II is considerably heavier than the lightweight fighters it replaces.

The Pratt & Whitney F135 engine with Rolls-Royce LiftSystem, including roll posts, and rear vectoring nozzle for the F-35B, at the 2007 Paris Air Show

The STOVL F-35B is outfitted with the Rolls-Royce LiftSystem, designed by Lockheed Martin and developed by Rolls-Royce. This system more resembles the German VJ 101D/E than the preceding STOVL Harrier Jump Jet and the Rolls-Royce Pegasus engine.[274][275][276] The Lift System is composed of a lift fan, drive shaft, two roll posts and a "Three Bearing Swivel Module" (3BSM).[277] The 3BSM is a thrust vectoring nozzle which allows the main engine exhaust to be deflected downward at the tail of the aircraft. The lift fan is near the front of the aircraft and provides a counterbalancing thrust using two counter-rotating blisks.[278] It is powered by the engine's low-pressure (LP) turbine via a drive shaft and gearbox. Roll control during slow flight is achieved by diverting unheated engine bypass air through wing-mounted thrust nozzles called Roll Posts.[279][280]

F136 funding came at the expense of other program elements, impacting on unit costs.[281] The F136 team stated their engine had a greater temperature margin, potentially critical for VTOL operations in hot, high altitude conditions.[282] Pratt & Whitney tested higher thrust versions of the F135, partly in response to GE's statements that the F136 is capable of producing more thrust than the 43,000 lbf (190 kN) of early F135s. In testing, the F135 has demonstrated a maximum thrust of over 50,000 lbf (220 kN);[283] making it the most powerful engine ever installed in a fighter aircraft as of 2010.[284] It is much heavier than previous fighter engines; the Heavy Underway Replenishment system needed to transfer the F135 between ships is an unfunded USN requirement.[285] Thermoelectric-powered sensors monitor turbine bearing health.[286]

Armament

Close-up view of open aircraft weapons bay. The aircraft mock-up itself is on display, watched on by onlookers
Weapons bay on an F-35 mock-up

The F-35A is armed with a GAU-22/A, a four-barrel version of the 25 mm GAU-12 Equalizer cannon.[287] The cannon is mounted internally with 182 rounds for the F-35A or in an external pod with 220 rounds for the F-35B and F-35C;[288][289] the gun pod has stealth features.[290] Software updates to enable operational firing of the cannon are expected to be completed by 2018.[291] The F-35 has two internal weapons bays, and external hardpoints for mounting up to four underwing pylons and two near wingtip pylons. The two outer hardpoints can carry pylons for the AIM-9X Sidewinder and AIM-132 ASRAAM short-range air-to-air missiles (AAM) only.[292] The other pylons can carry the AIM-120 AMRAAM BVR AAM, AGM-158 Joint Air to Surface Stand-off Missile (JASSM) cruise missile, and guided bombs. The external pylons can carry missiles, bombs, and external fuel tanks at the expense of increased radar cross-section, and thus reduced stealth.[293]

There are a total of four weapons stations between the two internal bays. Two of these can carry air-to-surface missiles up to 2,000 lb (910 kg) in A and C models, or two bombs up to 1,000 lb (450 kg) in the B model; the other two stations are for smaller weapons such as air-to-air missiles.[294][295] The weapon bays can carry AIM-120 AMRAAM, AIM-132 ASRAAM, the Joint Direct Attack Munition (JDAM), Paveway series of bombs, the Joint Standoff Weapon (JSOW), Brimstone anti-tank missiles, and cluster munitions (Wind Corrected Munitions Dispenser).[294] An air-to-air missile load of eight AIM-120s and two AIM-9s is possible using internal and external weapons stations; a configuration of six 2,000 lb (910 kg) bombs, two AIM-120s and two AIM-9s can also be arranged.[294][296] The Terma A/S multi-mission pod (MMP) could be used for different equipment and purposes, such as electronic warfare, aerial reconnaissance, or rear-facing tactical radar.[290][297] The British Ministry of Defence plan to fire the Select Precision Effects at Range (SPEAR) Capability 3 missile from the internal bays of the F-35B, with four missiles per bay.[298][299]

Lockheed Martin states that the weapons load can be configured as all-air-to-ground or all-air-to-air, and has suggested that a Block 5 version will carry three weapons per bay instead of two, replacing the heavy bomb with two smaller weapons such as AIM-120 AMRAAM air-to-air missiles.[300] Upgrades are to allow each weapons bay to carry four GBU-39 Small Diameter Bombs (SDB) for A and C models, or three in F-35B.[301] Another option is four GBU-53/B Small Diameter Bomb IIs in each bay on all F-35 variants.[302] The F-35A has been outfitted with four SDB II bombs and an AMRAAM missile to test adequate bay door clearance,[303] as well as the C-model, but the STOVL F-35B will not be able to carry the required load of four SDB IIs in each weapons bay upon reaching IOC because of weight and dimension constraints; F-35B bay changes are to be incorporated to increase SDB II loadout around 2022 in line with the Block 4 weapons suite.[304] The Meteor air-to-air missile may be adapted for the F-35, a modified Meteor with smaller tailfins for the F-35 was revealed in September 2010; plans call for the carriage of four Meteors internally.[305] The United Kingdom planned to use up to four AIM-132 ASRAAM missiles internally, later plans call for the carriage of two internal and two external ASRAAMs.[306] The external ASRAAMs are planned to be carried on "stealthy" pylons; the missile allows attacks to slightly beyond visual range without employing radar.[292][307]

Norway and Australia are funding an adaptation of the Naval Strike Missile (NSM) for the F-35. Under the designation Joint Strike Missile (JSM), it is to be the only cruise missile to fit the F-35's internal bays; according to studies two JSMs can be carried internally with an additional four externally.[308] The F-35 is expected to take on the Wild Weasel mission, though there are no planned anti-radiation missiles for internal carriage.[309] The B61 nuclear bomb was initially scheduled for deployment in 2017;[310] as of 2012 it was expected to be in the early 2020s,[311] and in 2014 Congress moved to cut funding for the needed weapons integration work.[312] Norton A. Schwartz agreed with the move and said that "F-35 investment dollars should realign to the long-range strike bomber".[313] NATO partners who are buying the F-35 but cannot afford to make them dual-capable want the USAF to fund the conversions to allow their Lightning IIs to carry thermonuclear weapons. The USAF is trying to convince NATO partners who can afford the conversions to contribute to funding for those that cannot. The F-35 Block 4B will be able to carry two B61 nuclear bombs internally by 2024.[314]

According to reports in 2002, solid-state lasers were being developed as optional weapons for the F-35.[315][316][317] Lockheed is studying integrating a fiber laser onto the aircraft that uses spectral beam combining to channel energy from a stack of individual laser modules into a single, high-power beam, which can be scaled up or down for various levels of effects. Adding a laser would give the F-35 the ability to essentially burn missiles and other aircraft out of the sky.[318] The F-35 is also one of the target platforms for the High Speed Strike Weapon if hypersonic missile development is successful.[319]

The Air Force plans to use the F-35A to primarily take up the close air support (CAS) mission in contested environments. Amid criticism that the aircraft is not well suited for the role compared to a dedicated attack platform, Air Force chief of staff Mark Welsh is putting focus on weapons for the F-35 to employ on CAS sorties including guided rockets, fragmentation rockets that would shatter into individual projectiles before impact, and lighter, smaller ammunition in higher capacity gun pods.[320] Fragmentary rocket warheads would have greater effects than cannon shells fired from a gun because a single rocket would create a "thousand-round burst," delivering more projectiles than a strafing run could. Other weapons could take advantage of the aircraft's helmet-mounted cueing system to aim rather than needing to point the nose at a target.[321] Institute for the Study of War's Christopher Harmer has questioned the use of such an expensive aircraft for CAS.[322]

Stealth and signatures

Radar

Landing gear door of the F-35 mockup, showing its stealth sawtooth design.

The F-35 has been designed to have a low radar cross-section that is primarily due to the shape of the aircraft and the use of stealthy, radar-absorbent materials in its construction, including fiber-mat.[239] Unlike the previous generation of fighters, the F-35 was designed for very-low-observable characteristics.[323] Besides radar stealth measures, the F-35 incorporates infrared signature and visual signature reduction measures.[examples needed][324][325]

The Fighter Teen Series (F-14, F-15, F-16, F/A-18) carried large external fuel tanks, but to avoid negating its stealth characteristics the F-35 must fly most missions without them. Unlike the F-16 and F/A-18, the F-35 lacks leading edge extensions and instead uses stealth-friendly chines for vortex lift in the same fashion as the SR-71 Blackbird.[297] The small bumps just forward of the engine air intakes form part of the diverterless supersonic inlet (DSI) which is a simpler, lighter means to ensure high-quality airflow to the engine over a wide range of conditions. These inlets also crucially improve the aircraft's very-low-observable characteristics (by eliminating radar reflections between the diverter and the aircraft's skin).[326] Additionally, the "bump" surface reduces the engine's exposure to radar, significantly reducing a strong source of radar reflection[327] because they provide an additional shielding of engine fans against radar waves. The Y-duct type air intake ramps also help in reducing radar cross-section (RCS), because the intakes run parallel and not directly into the engine fans.

F-35A front profile in flight. The doors are opened to expose the aerial refueling inlet valve.

The F-35's radar-absorbent materials are designed to be more durable and less maintenance-intensive than those of its predecessors. At optimal frequencies, the F-35 compares favorably to the F-22 in stealth, according to General Mike Hostage, Commander of the Air Combat Command.[328][329] Like other stealth fighters, however, the F-35 is more susceptible to detection by low-frequency radars because of the Rayleigh scattering resulting from the aircraft's physical size. However, such radars are also conspicuous, susceptible to clutter, and have low precision.[330][331] Although fighter-sized stealth aircraft could be detected by low-frequency radar, missile lock and targeting sensors primarily operate in the X-band, which F-35 RCS reduction is made for, so they cannot engage unless at close range.[332] Because the aircraft's shape is important to the RCS, special care must be taken to match the "boilerplate" during production.[333] Ground crews require Repair Verification Radar (RVR) test sets to verify the RCS after performing repairs, which is not a concern for non-stealth aircraft.[334][335]

Acoustics

In 2008, the Air Force revealed that the F-35 would be about twice as loud at takeoff as the McDonnell Douglas F-15 Eagle and up to four times as loud during landing.[336] Residents near Luke Air Force Base, Arizona and Eglin Air Force Base, Florida, possible F-35 bases, requested environmental impact studies be conducted regarding the F-35's noise levels.[336] In 2009, the city of Valparaiso, Florida, adjacent to Eglin AFB, threatened to sue over the impending F-35 arrival; this lawsuit was settled in March 2010.[337][338][339] In 2009, testing reportedly revealed the F-35 to be: "only about as noisy as an F-16 fitted with a Pratt & Whitney F100-PW-200 engine...quieter than the Lockheed Martin F-22 Raptor and the Boeing F/A-18E/F Super Hornet."[340] An acoustics study by Lockheed Martin and the Air Force found F-35's noise levels to be comparable to the F-22 and F/A-18E/F.[341] A USAF environmental impact study found that replacing F-16s with F-35s at Tucson International Airport would subject more than 21 times as many residents to extreme noise levels.[342] The USN will need to redesign hearing protection for sailors to protect against the "thundering 152 decibels" of the F-35.[343] The Joint Strike Fighter program office found in October 2014 that the F-35B's take-off noise was only two decibels higher than a Super Hornet, a virtually indistinguishable difference to the human ear, and is even 10 decibels quieter when flying formations or landing.[344]

Cockpit

F-35 cockpit mock-up

The F-35 features a full-panel-width glass cockpit touchscreen[345] "panoramic cockpit display" (PCD), with dimensions of 20 by 8 inches (50 by 20 centimeters).[346] A cockpit speech-recognition system (DVI) provided by Adacel has been adopted on the F-35 and the aircraft will be the first operational U.S. fixed-wing aircraft to employ this DVI system, although similar systems have been used on the AV-8B Harrier II and trialled in previous aircraft, such as the F-16 VISTA.[347]

A helmet-mounted display system (HMDS) will be fitted to all models of the F-35.[348] While some fighters have offered HMDS along with a head up display (HUD), this will be the first time in several decades that a front line fighter has been designed without a HUD.[349] The F-35 is equipped with a right-hand HOTAS side stick controller. The Martin-Baker US16E ejection seat is used in all F-35 variants.[350] The US16E seat design balances major performance requirements, including safe-terrain-clearance limits, pilot-load limits, and pilot size; it uses a twin-catapult system housed in side rails.[351] This industry standard ejection seat can cause the heavier than usual helmet to inflict serious injury on lightweight pilots.[352] The F-35 employs an oxygen system derived from the F-22's own system, which has been involved in multiple hypoxia incidents on that aircraft; unlike the F-22, the flight profile of the F-35 is similar to other fighters that routinely use such systems.[353][354]

Sensors and avionics

Electro-optical target system (EOTS) under the nose of a mockup of the F-35

The F-35's sensor and communications suite has situational awareness, command and control and network-centric warfare capabilities.[236][355] The main sensor on board is the AN/APG-81 Active electronically scanned array-radar, designed by Northrop Grumman Electronic Systems.[356] It is augmented by the nose-mounted Electro-Optical Targeting System (EOTS),[357] it provides the capabilities of an externally mounted Sniper Advanced Targeting Pod with a reduced radar cross-section.[358][359] The AN/ASQ-239 (Barracuda) system is an improved version of the F-22's AN/ALR-94 electronic warfare suite, providing sensor fusion of Radio frequency and Infrared tracking functions, advanced radar warning receiver including geolocation targeting of threats, multispectral image countermeasures for self-defense against missiles, situational awareness and electronic surveillance, employing 10 radio frequency antennae embedded into the edges of the wing and tail.[360][361] In September 2015, Lockheed unveiled the "Advanced EOTS" that offers short-wave infrared, high-definition television, infrared marker, and superior image detector resolution capabilities. Offered for the Block 4 configuration, it fits into the same area as the baseline EOTS with minimal changes while preserving stealth features.[362]

Six additional passive infrared sensors are distributed over the aircraft as part of Northrop Grumman's electro-optical AN/AAQ-37 Distributed Aperture System (DAS),[36] which acts as a missile warning system, reports missile launch locations, detects and tracks approaching aircraft spherically around the F-35, and replaces traditional night vision devices. All DAS functions are performed simultaneously, in every direction, at all times. The electronic warfare systems are designed by BAE Systems and include Northrop Grumman components.[363] Functions such as the Electro-Optical Targeting System and the electronic warfare system are not usually integrated on fighters.[364] The F-35's DAS is so sensitive, it reportedly detected the launch of an air-to-air missile in a training exercise from 1,200 mi (1,900 km) away, which in combat would give away the location of an enemy aircraft even if it had a very low radar cross-section.[365]

The communications, navigation and identification (CNI) suite is designed by Northrop Grumman and includes the Multifunction Advanced Data Link (MADL), as one of a half dozen different physical links.[366] The F-35 will be the first fighter with sensor fusion that combines radio frequency and IR tracking for continuous all-direction target detection and identification which is shared via MADL to other platforms without compromising low observability.[272] Link 16 is also included for communication with legacy systems.[367] The F-35 has been designed with synergy between sensors as a specific requirement, the aircraft's "senses" being expected to provide a more cohesive picture of the battlespace around it and be available for use in any possible way and combination with one another; for example, the AN/APG-81 multi-mode radar also acts as a part of the electronic warfare system.[368] The Program Executive Officer (PEO) General Bogdan has described the sensor fusion software as one of the most difficult parts of the program.[369]

Much of the F-35's software is written in C and C++ because of programmer availability; Ada83 code also is reused from the F-22.[370] The Integrity DO-178B real-time operating system (RTOS) from Green Hills Software runs on COTS Freescale PowerPC processors.[371] The final Block 3 software is planned to have 8.6 million lines of code.[372] In 2010, Pentagon officials discovered that additional software may be needed.[373] General Norton Schwartz has said that the software is the biggest factor that might delay the USAF's initial operational capability.[374] In 2011, Michael Gilmore, Director of Operational Test & Evaluation, wrote that, "the F-35 mission systems software development and test is tending towards familiar historical patterns of extended development, discovery in flight test, and deferrals to later increments."[375]

The electronic warfare and electro-optical systems are intended to detect and scan aircraft, allowing engagement or evasion of a hostile aircraft prior to being detected.[368] The CATbird avionics testbed aircraft has proved capable of detecting and jamming radars, including the F-22's AN/APG-77.[376] The F-35 was previously considered a platform for the Next Generation Jammer; attention shifted to using unmanned aircraft in this capacity instead.[377] Several subsystems use Xilinx FPGAs;[378] these COTS components enable supply refreshes from the commercial sector and fleet software upgrades for the software-defined radio systems.[371]

Lockheed Martin's Dave Scott stated that sensor fusion boosts engine thrust and oil efficiency, increasing the aircraft's range.[379] Air Force official Ellen M. Pawlikowski has proposed using the F-35 to control and coordinate multiple unmanned combat aerial vehicles (UCAVs). Using its sensors and communications equipment, a single F-35 could orchestrate an attack made by up to 20 armed UCAVs.[380]

Helmet-mounted display system

VSI Helmet-mounted display system for the F-35

The F-35 does not need to be physically pointing at its target for weapons to be successful.[294][381] Sensors can track and target a nearby aircraft from any orientation, provide the information to the pilot through their helmet (and therefore visible no matter which way the pilot is looking), and provide the seeker-head of a missile with sufficient information. Recent missile types provide a much greater ability to pursue a target regardless of the launch orientation, called "High Off-Boresight" capability. Sensors use combined radio frequency and infra red (SAIRST) to continually track nearby aircraft while the pilot's helmet-mounted display system (HMDS) displays and selects targets; the helmet system replaces the display-suite-mounted head-up display used in earlier fighters.[382] Each helmet costs $400,000.[383]

The F-35's systems provide the edge in the "observe, orient, decide, and act" OODA loop; stealth and advanced sensors aid in observation (while being difficult to observe), automated target tracking helps in orientation, sensor fusion simplifies decision making, and the aircraft's controls allow the pilot to keep their focus on the targets, rather than the controls of their aircraft.[384][N 4]

Problems with the Vision Systems International helmet-mounted display led Lockheed Martin-Elbit Systems to issue a draft specification for alternative proposals in early 2011, to be based around the Anvis-9 night vision goggles.[385] BAE Systems was selected to provide the alternative system in late 2011.[386] The BAE Systems alternative helmet was to include all the features of the VSI system.[387] However, adopting the alternative helmet would have required a cockpit redesign,[388] but in 2013 development on the alternative helmet was halted because of progress on the baseline helmet.[389]

In 2011, Lockheed Martin-Elbit granted VSI a contract to fix the vibration, jitter, night-vision and sensor display problems in their helmet-mounted display.[390] A speculated potential improvement is the replacement of Intevac’s ISIE-10 day/night camera with the newer ISIE-11 model.[391] In October 2012, Lockheed Martin-Elbit stated that progress had been made in resolving the technical issues of the helmet-mounted display, and cited positive reports from night flying tests; it had been questioned whether the helmet system allows pilots enough visibility at night to carry out precision tasks.[392] In 2013, in spite of continuing problems with the helmet display, the F-35B model completed 19 nighttime vertical landings on board the USS Wasp at sea,[393] by using the DAS instead of the helmet's built-in night vision capabilities, which offer at best 20/35 vision.[394]

In October 2013, development of the alternate helmet was halted. The current Gen 2 helmet is expected to meet the requirements to declare, in July 2015, that the F-35 has obtained initial operational capability. Beginning in 2016 with low rate initial production (LRIP) lot 7, the program will introduce a Gen 3 helmet that features an improved night vision camera, new liquid crystal displays, automated alignment and other software enhancements.[389]

In July 2015, an F-35 pilot commented that the helmet may have been one of the issues that the F-35 faced while dogfighting against an F-16 during a test; "The helmet was too large for the space inside the canopy to adequately see behind the aircraft. There were multiple occasions when the bandit would've been visible (not blocked by the seat) but the helmet prevented getting in a position to see him (behind the high side of the seat, around the inside of the seat, or high near the lift vector)."[395]

Maintenance

The program's maintenance concept is for any F-35 to be maintained in any F-35 maintenance facility and that all F-35 parts in all bases will be globally tracked and shared as needed.[396] The commonality between the different variants has allowed the USMC to create their first aircraft maintenance Field Training Detachment to directly apply the lessons of the USAF to their F-35 maintenance operations.[397] The aircraft has been designed for ease of maintenance, with 95% of all field replaceable parts "one deep" where nothing else has to be removed to get to the part in question. For instance the ejection seat can be replaced without removing the canopy, the use of low-maintenance electro-hydrostatic actuators instead of hydraulic systems and an all-composite skin without the fragile coatings found on earlier stealth aircraft.[398]

The F-35 Joint Program Office has stated that the aircraft has received good reviews from pilots and maintainers, suggesting it is performing better than its predecessors did at a similar stage of development, and that the stealth type has proved relatively stable from a maintenance standpoint. This reported improvement is attributed to better maintenance training, as F-35 maintainers have received far more extensive instruction at this early stage of the program than on the F-22 Raptor. The F-35's stealth coatings are much easier to work with than those used on the Raptor. Cure times for coating repairs are lower and many of the fasteners and access panels are not coated, further reducing the workload for maintenance crews. Some of the F-35's radar-absorbent materials are baked into the jet's composite skin, which means its stealthy signature is not easily degraded.[399] It is still harder to maintain (because of the need to preserve its stealth characteristics) than fourth-generation aircraft.[400]

However, the DOT&E Report on the F-35 program published in January 2015 determined that the plane has not, in fact, reached any of the nine reliability measures the program was supposed to achieve by this point in its development and that the Joint Program Office has been re-categorizing failure incidents to make the plane look more reliable than it actually is. Further, the complexity of maintaining the F-35 means that, currently, none of the Services are ready to keep it in working order and instead "rely heavily on contractor support and unacceptable workarounds." DOT&E found that the program achieved 61 percent of planned flight hours and that the average rate of availability was as low as 28 percent for the F-35A and 33 percent for the F-35B. The program created a new "modeled achievable" flight hour projection "since low availability was preventing the full use of bed-down plan flight hours." According to the Assistant Secretary of the Air Force for Financial Management, in FY2014, each non-test F-35 flew only 7.7 hours per month, which amounts to approximately one sortie every 5.5 days—for combat purposes, a sortie rate so low as to be crippling. Mean flight hours between removal (MFHBR) have increased, but are still only 59 percent to 65 percent of the required threshold. DOT&E found that mean corrective maintenance time for critical failures got worse for the F-35A and the F-35C over the last year. Structural cracking is also proving to be a recurring and enduring problem that is not yet resolved.[204][401]

Operational history

Testing

The first F-35A (designated AA-1) was rolled out in Fort Worth, Texas, on 19 February 2006. In September 2006, the first engine run of the F135 in an airframe took place.[402] On 15 December 2006, the F-35A completed its maiden flight.[403] A modified Boeing 737–300, the Lockheed Martin CATBird has been used as an avionics test-bed for the F-35 program, including a duplication of the cockpit.[300]

The first F-35B (designated BF-1) made its maiden flight on 11 June 2008, piloted by BAE Systems' test pilot Graham Tomlinson. Flight testing of the STOVL propulsion system began on 7 January 2010.[404] The F-35B's first hover was on 17 March 2010, followed by its first vertical landing the next day.[405] During a test flight on 10 June 2010, the F-35B STOVL aircraft achieved supersonic speeds[406] as had the X-35B before.[407] In January 2011, Lockheed Martin reported that a solution had been found for the cracking of an aluminum bulkhead during ground testing of the F-35B.[408] In 2013, the F-35B suffered another bulkhead cracking incident.[409] This will require redesign of the aircraft, which is already very close to the ultimate weight limit.[410]

The first delivered USAF F-35 on its delivery flight to Eglin Air Force Base in July 2011.
External video
F-35B tests on USS Wasp in 2011
video icon Short TakeOff
video icon BF-04 vertical landing

By June 2009, many of the initial flight test targets had been accomplished but the program was behind schedule.[411] During 2008, a Pentagon Joint Estimate Team (JET) estimated that the program was two years behind the public schedule, a revised estimate in 2009 predicted a 30-month delay.[412] Delays reduced planned production numbers by 122 aircraft through 2015 to provide an additional $2.8 billion for development; internal memos suggested that the official timeline would be extended by 13 months.[412][413] The success of the JET led Ashton Carter calling for more such teams for other poorly performing projects.[414]

File:F-35C First Carrier Landing 1.webm
A U.S. Navy F-35C makes the aircraft's first arrested landing aboard the carrier USS Nimitz (CVN 68) off the coast of San Diego.

Nearly 30 percent of test flights required more than routine maintenance to make the aircraft flightworthy again.[415] As of March 2010, the F-35 program had used a million more man-hours than predicted.[416] The United States Navy projected that lifecycle costs over a 65-year fleet life for all American F-35s to be $442 billion higher than U.S. Air Force projections.[417] F-35 delays have led to shortfall of up to 100 jet fighters in the Navy/Marines team, although measures have been taken using existing assets to manage and reduce this shortfall.[418]

The F-35C's maiden flight took place on 7 June 2010, at NAS Fort Worth JRB. A total of 11 U.S. Air Force F-35s arrived in fiscal year 2011.[419] On 9 March 2011, all F-35s were grounded after a dual generator failure and oil leak in flight;[420] the cause of the incident was discovered to have been the result of faulty maintenance.[421] In 2012, Navy Commander Erik Etz of the F-35 program office commented that rigorous testing of the F-35's sensors had taken place during exercise Northern Edge 2011, and had served as a significant risk-reduction step.[422][423]

On 2 August 2011, an F-35's integrated power package (IPP) failure during a standard engine test at Edwards Air Force Base led to the F-35 being immediately grounded for two weeks.[424][425] On 10 August 2011, ground operations were re-instituted; preliminary inquiries indicated that a control valve did not function properly, leading to the IPP failure.[426][427] On 18 August 2011, the flight ban was lifted for 18 of the 20 F-35s; two aircraft remained grounded for lack of monitoring systems.[428] The IPP suffered a second software-related incident in 2013, this resulted in no disruption as the fleet was already grounded by separate engine issues.[429]

On 25 October 2011, the F-35A reached its designed top speed of Mach 1.6 for the first time.[430] Further testing demonstrated Mach 1.61 and 9.9g.[431] On 11 February 2013, an F-35A completed its final test mission for clean wing flutter, reporting to be clear of flutter at speeds up to Mach 1.6.[432] On 15 August 2012, an F-35B completed airborne engine start tests.[433]

During testing in 2011, all eight landing tests of the F-35C failed to catch the arresting wire; a redesigned tail hook was developed and delivered two years later in response.[434][435] In October 2011, two F-35Bs conducted three weeks of initial sea trials aboard USS Wasp.[436]

On 6 October 2012, the F-35A dropped its first bomb,[437] followed three days later by an AIM-120 AMRAAM.[438] On 28 November 2012, an F-35C performed a total of eleven weapon releases, including a GBU-31 JDAM and GBU-12 Paveway from its weapons bay in the first weapons released for the F-35C.[439] On 5 June 2013, an F-35A at the Point Mugu Sea Test Range completed the first in-flight missile launch of an AIM-120 C5 AAVI (AMRAAM Air Vehicle Instrumented). It was launched from the internal weapons bay.[440]

On 16 November 2012, the U.S. Marines received the first F-35B at MCAS Yuma, and the VMFA(AW)-121 unit is to be redesignated from a Boeing F/A-18 Hornet unit to an F-35B squadron.[441] A February 2013 Time article revealed that Marine pilots are not allowed to perform a vertical landing—the maneuver is deemed too dangerous, and it is reserved only for Lockheed test pilots.[442] On 10 May 2013, the F-35B completed its first vertical takeoff test.[443] On 3 August 2013, the 500th vertical landing of an F-35 took place.[444]

On 18 January 2013, the F-35B was grounded after the failure of a fueldraulic line in the propulsion system on 16 January.[445] The problem was traced to an "improperly crimped" fluid line manufactured by Stratoflex.[446][447] The Pentagon cleared all 25 F-35B aircraft to resume flight tests on 12 February 2013.[448] On 22 February 2013, the U.S. Department of Defense grounded the entire fleet of 51 F-35s after the discovery of a cracked turbine blade in a U.S. Air Force F-35A at Edwards Air Force Base.[449] On 28 February 2013, the grounding was lifted after an investigation concluded that the cracks in that particular engine resulted from stressful testing, including excessive heat for a prolonged period during flight, and did not reflect a fleetwide problem.[450][451] The F-35C Lightning II carrier variant Joint Strike Fighter conducted its first carrier-based night flight operations aboard an aircraft carrier off the coast of San Diego on 13 November 2014.[452]

On 5 June 2015, the U.S. Air Education and Training Command Accident Investigation Board reported that catastrophic engine failure had led to the destruction of an Air Force F-35A assigned to the 58th Fighter Squadron at Eglin Air Force Base, Florida, on 23 June 2014. The third-stage forward integral arm of a rotor had fractured and broke free during the takeoff roll. Pieces cut through the engine's fan case, engine bay, internal fuel tank and hydraulic and fuel lines before leaving through the aircraft's upper fuselage. Leaked fuel and hydraulic fluid ignited the fire, which destroyed the rear two-thirds of the aircraft. The destruction of the airframe resulted in the cancelation of the F-35's international debut at the 2014 Farnborough Airshow in England, the temporary grounding of the F-35 fleet[453] and ongoing restrictions in the flight envelope.[454]

On 19 June 2015 the RAF successfully launched two 500 lb Paveway IV precision-guided bombs, making the test the first time non-US munitions were deployed by the aircraft.[455]

The US Marines declared the aircraft had met initial operational capability on 31 July 2015, despite shortcomings in night operations, communications, software and weapons carriage capabilities.[456] However, J. Michael Gilmore, director of the Pentagon’s Operational Test and Evaluation Office, criticized the operational trials as not valid. In an internal memo, Gilmore concluded "the exercise was so flawed that it 'was not an operational test … in either a formal or informal sense of the term.' Furthermore, the test 'did not—and could not—demonstrate' that the version of the F-35 that was evaluated 'is ready for real-world operational deployments, given the way the event was structured.'"[457]

On 11 April 2016 the Joint Program Office confirmed that the Royal Netherlands Air Force (RNLAF) had cleared its KDC-10 aerial tanker to refuel the F-35, paving the way for the fighter’s international public debut at the RNLAF’s Open Dagen (Open Day) at Leeuwarden on June 10–11, 2016. The testing required the fighter to refuel in daylight, dusk and night, with 30,000 lb. of fuel being transferred during the tests.[458]

Training

In 2011, the Director of Operational Test and Evaluation warned that the USAF's plan to start unmonitored flight training "risks the occurrence of a serious mishap".[459] The leaders of the United States Senate Committee on Armed Services called on Defense Secretary Leon Panetta to address the issue.[460] Despite the objections, expanded trial flights began in September 2012.[461]

(From the top) 33rd FW F-35A, F-35B and F-35C near Eglin AFB in May 2014.

The F-35A and F-35B were cleared for flight training in early 2012.[462] A military flight release for the F-35A was issued on 28 February 2012.[463] The aircraft were restricted to basic maneuvers with no tactical training allowed.[464] On 24 August 2012, an F-35 flew its 200th sortie while at Eglin Air Force Base, flown by a Marine pilot. The pilot said, "The aircraft have matured dramatically since the early days. The aircraft are predictable and seem to be maintainable, which is good for the sortie production rate. Currently, the flight envelope for the F-35 is very, very restricted, but there are signs of improvement there too." The F-35s at the base no longer need to fly with a chase aircraft and are operating in a normal two-ship element.[465]

On 21 August 2012, J. Michael Gilmore wrote that he would not approve the Operational Test and Evaluation master plan until his concerns about electronic warfare testing, budget and concurrency were addressed.[466] On 7 September 2012, the Pentagon failed to approve a comprehensive operational testing plan for the F-35.[467] Instead, on 10 September 2012, the USAF began an operational utility evaluation (OUE) of the F-35A entire system, including logistical support and maintenance, maintenance training, pilot training, and pilot execution.[468] By 1 October, the OUE was reported as "proceeding smoothly", pilots started on simulators prior to flying on 26 October.[469] The OUE was completed on 14 November with the 24th flight, the four pilots involved having completed six flights each.[470]

During the Low Rate Initial Production (LRIP) phase of the aircraft, the U.S. had taken a tri-service approach to developing tactics and procedures for the F-35 using flight simulators prior to the type entering service. Simulated flights had tested the flight controls' effectiveness, helping to discover technical problems and refine aircraft design.[471] Maintenance personnel have discovered that it is possible to correct deficiencies in the F-35, which is a software-defined aircraft, simply by rebooting the aircraft's software and onboard systems.[472]

Air Force pilot training F-35A began in January 2013 at Eglin Air Force Base; the program currently has a maximum capacity of 100 military pilots and 2,100 maintainer students.[473]

On 23 June 2014, an F-35A experienced a fire in the engine area during its takeoff at Eglin AFB. In response, the Pentagon's Joint Program Office halted training in all F-35 models the next day,[474][475] and on 3 July, the F-35 fleet was formally grounded.[476] The fleet was returned to flight on 15 July,[477] but the engine inspection regimen caused the aircraft's debut at the Farnborough 2014 Air Show to be canceled.[478][479]

At Red Flag 2017 the F-35 scored a kill ratio of 15:1 against an F-16 aggressor squadron.[480]

Basing plans for future U.S. F-35s

On 9 December 2010, a media report stated that the "USMC will base 216 F-35Bs on the East Coast and 184 of them on the West Coast, documents showed." This report continued: "Cherry Point will get 128 jets to form eight squadrons; Beaufort will have three squadrons and a pilot training center using 88 aircraft; Miramar will form six operational squadrons with 96 jets and 88 F-35s will go to Yuma for five operational squadrons with an additional test and evaluation unit."[481]

In 2011, the USMC and USN signed an agreement that the USMC will purchase 340 F-35B and 80 F-35C fighters. The five squadrons of USMC F-35Cs would be assigned to Navy carriers while F-35Bs would be used ashore.[482][483]

In February 2014, the U.S. Air Force announced that the first Air National Guard unit to fly the new F-35 Lightning II will be the 158th Fighter Wing of the Vermont Air National Guard based at the Burlington Air Guard Station. The 158th currently flies F-16 Fighting Falcons, which are nearing the end of their useful service lives. Burlington Air Guard Station is expected to receive 18 F-35As, replacing the 18 F-16 Fighting Falcons currently assigned. The F-35A is expected to arrive in 2020.[484]

On 11 March 2014, the first F-35A Lightning II assigned to Luke Air Force Base arrived at the base. 16 F-35s are to be delivered to the base by the end of 2014, with 144 Lightning IIs to be stationed there, arriving over the course of the next decade.[485][486]

On 8 January 2015, the Royal Air Force base RAF Lakenheath in the UK was chosen as the first U.S. Air Force base in Europe to station two F-35 squadrons, following an announcement by the Pentagon. 48 F-35s, making up 2 squadrons, will add to the 48th Fighter Wing's already existing F-15C and F-15E Strike Eagle jets.[487]

Procurement and international participation

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

Participant nations:
  Primary customer: United States
  Level 1 partner: United Kingdom
  Level 2 partners: Italy and the Netherlands
  Level 3 partners: Australia, Canada, Denmark, Norway, and Turkey
  Security Cooperative Participants: Israel and Singapore

While the United States is the primary customer and financial backer, the United Kingdom, Italy, the Netherlands, Canada, Turkey, Australia, Norway, and Denmark have agreed to contribute US$4.375 billion towards development costs.[488] Total development costs are estimated at more than US$40 billion. The purchase of an estimated 2,400 aircraft is expected to cost an additional US$200 billion.[489] The initial plan was that the nine major partner nations would acquire over 3,100 F-35s through 2035.[490] Sales to partner nations are made through the Pentagon's Foreign Military Sales program.[491]

There are three levels of international participation.[492] The levels generally reflect financial stake in the program, the amount of technology transfer and subcontracts open for bid by national companies, and the order in which countries can obtain production aircraft. The United Kingdom is the sole "Level 1" partner, contributing US$2.5 billion, which was about 10% of the planned development costs[493] under the 1995 Memorandum of Understanding that brought the UK into the project.[494] Level 2 partners are Italy, which is contributing US$1 billion; and the Netherlands, US$800 million. Level 3 partners are Turkey, US$195 million; Canada, US$160 million; Australia, US$144 million; Norway, US$122 million and Denmark, US$110 million. Israel and Singapore have joined as Security Cooperative Participants (SCP).[495][496][497] Japan announced on 20 December 2011 its intent to purchase 42 F-35s with deliveries beginning in 2016 to replace the F-4 Phantom II; Japan seeks 38 F-35s, to be assembled domestically.[498]

By 2012, many changes had occurred in the order book. Italy became the first country to announce a reduction of its overall fleet procurement, cutting its buy from 131 to 90 aircraft. Other nations reduced initial purchases or delayed orders while still intending to purchase the same final numbers. The United States canceled the initial purchase of 13 F-35s and postponed orders for another 179. The United Kingdom cut its initial order and delayed a decision on future orders. Australia decided to buy the Boeing F/A-18E/F Super Hornet as an interim measure. Turkey also cut its initial order of four aircraft to two, but confirmed plans to purchase 100 F-35As.[499][500] Turkey will buy four F-35s to be delivered in 2015 and 2016, while the order may be increased from 100 to 120 aircraft.[501] These changes resulted in increased procurement prices, and increased the likelihood of further cuts.[502][503]

On 3 April 2012, the Auditor General of Canada Michael Ferguson published a report outlining problems with Canada's procurement of the jet, including misinformation over the final cost. According to the Auditor General, the government knowingly understated the final price of the 65 jets by $10 billion.[504] Canada's Conservative government had stated it would not reduce its order, and anticipated a $75–80 million unit cost; the procurement was termed a "scandal" and "fiasco" by the media and faced a full review to determine any Canadian F-35 purchase.[505][506][507] On 13 December 2012, in a scathing editorial published by CBC News, journalist Brian Stewart termed the F-35 project a "global wrecking ball" for its runaway costs and lack of affordability for many participating nations.[508]

In May 2013, Lockheed Martin declared that Turkey is projected to earn $12 billion from licensed production of F-35 components.[509][510]

In November 2014, the United Kingdom confirmed its first order for 14 F-35Bs to be delivered in 2016.[511]

Procurement costs

Estimated cost of airplane in Low Rate Initial Production (LRIP) and Full Rate Production (FRP) batches:

Contract date Batch Number and Variant Unit cost (millions) Notes
Apr 2007 LRIP-1 2 F-35A $221.2[512]
(excl. engine)
Jul 2007 LRIP-2 6 F-35A
6 F-35B
$161.7
(excl. engine)[513]
Cost of the batch rose from initial 771 million to 1.15 billion.[513]
May 2008 LRIP-3 9 F-35A
9 F-35B
$128.2
(avg. per unit)
(excl. engine)[512]
According to Pentagon, estimated engine costs are: F-35A – $16M, F-35B – $38M.[514]
Batch includes 1 F-35A for the Netherlands and 2 F-35B for the UK.
Nov 2009 LRIP-4 11 F-35A
17 F-35B
4 F-35C
F-35A – $111.6
F-35B – $109.4
F-35C – $142.9
(excl. engine)[512]
First batch with a fixed price. Total batch price – $3.4 billion.[512]
Batch includes 1 F-35A for the Netherlands and 1 F-35B for the UK.
Dec 2011 LRIP-5 22 F-35A
3 F-35B
7 F-35C
F-35A – $107
F-35B – $?
F-35C – $?
(excl. engine)[515]
Total batch price – $4 billion
Sep 2013 LRIP-6 23 F-35A
6 F-35B
7 F-35C
F-35A – $103
F-35B – $109
F-35C – $120
(excl. engine)[516]
Total batch price – $4.4 billion.
Batch includes 2 F-35A for Australia and 3 F-35A for Italy.
Sep 2013 LRIP-7 24 F-35A
7 F-35B
4 F-35C
F-35A – $98
F-35B – $104
F-35C – $116
(excl. engine)[516]
Total batch price – $11.45 billion.
Batch includes 3 F-35A for Italy, 2 F-35A for Norway and 1 F-35B for the UK.
Nov 2014 LRIP-8 29 F-35A
10 F-35B
4 F-35C
F-35A – $94.8
F-35B – $102
F-35C – $115.7
(excl. engine)[517]
Total batch price – $4.6 billion for order of 43 units.
Batch includes 2 F-35A for Israel, 2 F-35A for Italy, 4 F-35A for Japan, 2 F-35A for Norway and 4 F-35B for the UK.
Nov 2015 LRIP-9 41 F-35A
12 F-35B
2 F-35C
F-35A: $102.1
F-35B: $131.6
F-35C: $132.2
(includes engine)[518]
Total batch price is $5.37 billion. Batch includes 6 F-35A for Norway, 7 F-35A for Israel, 2 F-35A for Japan and 6 F-35B for the UK.
2016[519] LRIP-10 76 F-35A
12 F-35B
2 F-35C[520]
F-35A: $94.6
F-35B: $122.8
F-35C: $121.8[521]
Total batch price is $9.5 billion. Batch includes 3 F-35B for UK, 6 F-35A for Norway, 8 F-35A for Australia, 2 F-35A for Turkey, 4 F-35A for Japan, 6 F-35A for Israel, 6 F-35A for South Korea
2017[519] LRIP-11 6 F-35A
3 F-35B
4 F-35C[522]
N/A
2018 (planned)[519] FRP-1 107 (planned) N/A First full rate production batch.
2019 (planned) FRP N/A F-35A: $83.4
F-35B: $108.1
F-35C: $93.3[523]
(target price incl. engine)
Costs are estimated as of 2012.

Variants

Configuration of the three original F-35 variants

The F-35 is being built in three different main versions to suit various combat missions.

F-35A

The F-35A is the conventional takeoff and landing (CTOL) variant intended for the U.S. Air Force and other air forces. It is the smallest, lightest F-35 version and is the only variant equipped with an internal cannon, the GAU-22/A. This 25 mm cannon is a development of the GAU-12 carried by the USMC's AV-8B Harrier II. It is designed for increased effectiveness against ground targets compared to the 20 mm M61 Vulcan cannon carried by other USAF fighters.

US Air Force F-35A maneuvers to refuel from a KC-135.

The F-35A is expected to match the F-16 in maneuverability and instantaneous high-g performance, and outperform it in stealth, payload, range on internal fuel, avionics, operational effectiveness, supportability, and survivability.[524] It is expected to match an F-16 that is carrying the usual external fuel tank in acceleration performance.[525]

The A variant is primarily intended to replace the USAF's F-16 Fighting Falcon. At one point it was also intended to replace the A-10 Thunderbolt II starting in 2028.[526][527] The F-35A can be outfitted to receive fuel via either of the two main aerial refueling methods; this was a consideration in the Canadian procurement and a deciding factor for the Japanese purchase.[528][529][530] On 18 December 2013, the Netherlands became the second partner country to operate the F-35A, when Maj. Laurens J.W. Vijge of the Royal Netherlands Air Force took off from Eglin Air Force Base.[531]

On 27 January 2014, General Mike Hostage, head of Air Combat Command, stated he would fight "to the death" to not have a single plane of the USAF's planned 1,763 F-35 purchase be cut, because the allies and partners of the US got "weak in the knees" when seeing the USAF "back away" from the F-35. He said the F-15 and F-16 fleets would become tactically obsolete in the middle of the next decade regardless of improvements. Hostage also commented that the F-35 would be "irrelevant" without the F-22 fleet being viable as the F-35 was not an air superiority fighter,[532] and that an F-35 pilot who enters a dogfight has made a mistake.[533]

The F-35As for the Royal Norwegian Air Force will have drag chute installed. Norway will be the first country to adopt the drag chute pod.[534]

On 2 August 2016, the U.S. Air Force declared the F-35A basic combat ready.[535] The 34th Fighter Squadron located at Hill Air Force Base, Utah, has at least 12 combat-ready jets capable of global deployment. F-35A is scheduled to be full combat ready in 2017 with its 3F software upgrade. Air Combat Command will initially deploy F-35A to Red Flag exercises and as a "theater security package" to Europe and the Asia-Pacific. It will probably not be fighting the Islamic State in the Middle East earlier than 2017, but ACC commander General Herbert "Hawk" Carlisle wouldn't mind deploying them earlier.[536]

F-35B

The F-35B is the short takeoff and vertical landing (STOVL) variant of the aircraft. Similar in size to the A variant, the B sacrifices about a third of the A variant's fuel volume to accommodate the vertical flight system. Vertical takeoffs and landings are riskier because of threats such as foreign object damage.[537][538] Whereas the F-35A is stressed to 9 g,[539][540] the F-35B's stress goal is 7 g. As of 2014, the F-35B is limited to 4.5 g and 400 knots. The next software upgrade includes weapons, and allows 5.5 g and Mach 1.2, with a final target of 7 g and Mach 1.6.[541] The first test flight of the F-35B was conducted on 11 June 2008.[542] Another milestone, the first successful ski-jump launch was carried out by BAE test pilot Peter Wilson on 24 June 2015.[543]

Unlike other variants, the F-35B has no landing hook. The "STOVL/HOOK" control instead engages conversion between normal and vertical flight.[544] Jet thrust is sent directly downwards during vertical flight; the nozzle is being redesigned to spread the output across an oval rather than circular shape in order to limit damage to asphalt and ship decks.[545] The variant's three-bearing swivel nozzle that directs the full thrust of the engine is moved by a "fueldraulic" actuator using pressurized fuel as the working fluid.[546]

The United States Marine Corps plans to purchase 340 F-35Bs,[88] to replace current inventories of both the F/A-18 Hornet (A, B, C and D-models), and the AV-8B Harrier II, in the fighter and attack roles.[547] The Marines plan to use the F-35B from "unimproved surfaces at austere bases" but with "special, high-temperature concrete designed to handle the heat."[548][549] The USMC declared initial operational capability with about 50 F-35s running interim block 2B software on 31 July 2015.[550] The USAF had considered replacing the A-10 with the F-35B, but will not do so because of the F-35B's inability to generate enough sorties.[551]

On 6 January 2011, Gates said that the 2012 budget would call for a two-year pause in F-35B production during which the aircraft faced redesign, or cancellation if unsuccessful.[83][552] In 2011, Lockheed Martin executive vice president Tom Burbage and former Pentagon director of operational testing Tom Christie stated that most program delays were due to the F-35B, which forced massive redesigns of other versions.[553] Lockheed Martin Vice President Steve O’Bryan has said that most F-35B landings will be conventional to reduce stress on vertical lift components.[554] These conventional mode takeoffs and landings cause an "unacceptable wear rate" to the aircraft's "poorly designed" tires.[555] USMC Lt. Gen. Robert Schmidle has said that the vertical lift components would only be used "a small percentage of the time" to transfer the aircraft from carriers to land bases.[556] On 3 October 2011, the F-35B began its initial sea-trials by performing a vertical landing on the deck of the amphibious assault ship USS Wasp,[557] to continue in 2015.[558] Probation status was reportedly ended by Defense Secretary Leon Panetta in January 2012 based on progress made.[86] A heat-resistant anti-skid material called Thermion is being tested on Wasp, also useful against the V-22 exhaust.[559]

Britain's Royal Air Force and Royal Navy plan to introduce the F-35B as a replacement for the Harrier GR9, which was retired in 2010, and Tornado GR4, which will retire in 2019. The F-35 is intended to be the United Kingdom's primary strike attack aircraft for the next 3 decades. One of the Royal Navy requirements for the F-35B design was a Shipborne Rolling and Vertical Landing (SRVL) mode to increase maximum landing weight to bring back unused ordnance by using wing lift during landing.[560][561] In July 2013, Chief of the Air Staff, Air Chief Marshal Sir Stephen Dalton announced that 617 Squadron would be the first operational Royal Air Force squadron to receive the F-35.[562][563] The second operational squadron will be the Fleet Air Arm's 809 NAS.[564] In June 2013, the Royal Air Force had received three aircraft of the 48 on order, all of which based at Eglin Air Force base.[565] The F-35 will be based at Royal Air Force Marham and become operational in 2018.[566][567] In June 2015, the F-35B undertook its first launches from a ski-jump, when one of the UK's aircraft took off using a ramp constructed at NAS Patuxent River.[568] When required to operate from the sea, the Royal Air Force and Royal Navy will operate the F-35B from ships fitted with ski-jumps, as will the Italian Marina Militare. In 2011, the Marina Militare was preparing Grottaglie Air Station for F-35B operations; they are to receive 22 aircraft between 2014 and 2021, with the aircraft carrier Cavour set to be modified to operate them by 2016.[569]

Commandant of the U.S. Marine Corps, General James Amos has said that, in spite of increasing costs and schedule delays, there is no plan B to the F-35B.[570] The F-35B is larger than the aircraft it replaces, which required USS America to be designed without well deck capabilities.[571] In 2011, the USMC and USN signed an agreement by which the USMC will purchase 340 F-35B and 80 F-35C fighters, while the USN will purchase 260 F-35Cs. The five squadrons of USMC F-35Cs will be assigned to Navy carriers; F-35Bs will be used on amphibious ships and ashore.[482][483]

Although the Australian Canberra-class landing helicopter dock ships were not originally planned to operate fixed-wing aircraft, in May 2014, the Minister for Defence David Johnston stated in media interviews that the government was considering acquiring F-35B fighters for Canberras, and Prime Minister Tony Abbott instructed 2015 Defence White Paper planners to consider the option of embarking F-35B squadrons aboard the two ships.[572][573][574] Supporters of the idea stated that providing fixed-wing support to amphibious operations would maximize aircraft capability, and the presence of a ski-jump ramp, inherited from the original design, meant that the vessels were better suited to STOVL operations than equivalent ships with flat flight decks.[575] Opponents to the idea countered that embarking enough F-35Bs to be effective required abandoning the ships' amphibious capability and would make the pseudo-carriers more valuable targets, modifications would be required to make the flight deck capable of handling vertical-landing thrust and to increase fuel and ordnance capacity for sustained operations, and that the F-35B project itself has been the most expensive and most problematic of the Joint Strike Fighter variants.[576][577][578] In July 2015 Australia ended consideration of buying the F-35B for its two largest assault ships, as the ship modifications were projected to cost more than AUS$5 billion (US$4.4 billion). The plan was opposed by the Royal Australian Air Force, as an F-35B order could have diminished the number of F-35As purchased.[579][580]

The U.S Marine Corps plans to disperse its F-35Bs among forward deployed bases to enhance survivability while remaining close to a battlespace, similar to RAF Harrier deployment late in the Cold War which relied on the use of off-base locations that offered short runways, shelter, and concealment. Known as distributed STOVL operations (DSO), Marine F-35Bs would sustain operations from temporary bases in allied territory within the range of hostile ballistic and cruise missiles, but be moved between temporary locations inside the enemy's 24- to 48-hour targeting cycle. This strategy accounts for the F-35B's short range, the shortest of the three variants, with mobile forward arming and refueling points (M-Farps) accommodating KC-130 and MV-22 Osprey aircraft to rearm and refuel the jets, as well as littoral areas for sea links of mobile distribution sites on land. M-Farps could be based on small airfields, multi-lane roads, or damaged main bases, while F-35Bs would return to U.S. Navy ships, rear-area U.S. Air Force bases, or friendly carriers for scheduled maintenance; metal planking would be needed to protect unprepared roads from the F-35B's engine exhaust, which would be moved between sites by helicopters, and the Marines are studying lighter and more heat-resistant products.[581]

F-35C

All main F-35 variants in formation, the greater wing area of the F-35C (left) can be seen when compared to the F-35B (middle) and the F-35A (right).
A F-35C of VX-23 making the first arrested landing aboard USS Nimitz (CVN-68) on 3 November 2014.
F-35C of VFA-101

Compared to the F-35A, the F-35C carrier variant features larger wings with foldable wingtip sections, larger wing and tail control surfaces for improved low-speed control, stronger landing gear for the stresses of carrier arrested landings, a twin-wheel nose gear, and a stronger tailhook for use with carrier arrestor cables. The larger wing area allows for decreased landing speed while increasing both range and payload.

The United States Navy intends to buy 480 F-35Cs to replace the F/A-18A, B, C, and D Hornets and complement the Super Hornet fleet.[582] On 27 June 2007, the F-35C completed its Air System Critical Design Review (CDR), allowing the production of the first two functional prototypes.[583] The C variant was expected to be available beginning in 2014.[584] The first F-35C was rolled out on 29 July 2009.[585] The United States Marine Corps will also purchase 80 F-35Cs, enough for five squadrons, for use with navy carrier air wings in a joint service agreement signed on 14 March 2011.[482][483] A recent 2014 document stated that the USMC will also have 4 squadrons of F-35Cs with 10 aircraft per squadron for the Marine Corps' contribution to U.S. Navy carrier air wings.[586]

On 6 November 2010, the first F-35C arrived at Naval Air Station Patuxent River. The replacement engines for at-sea repair are too large to be transported by current underway replenishment systems.[587] In 2011, the F-35Cs were grounded for six days after a software bug was found that could have prevented the control surfaces from being used during flight.[588] On 27 July 2011, the F-35C test aircraft CF-3 completed its first steam catapult launch during a test flight at Naval Air Engineering Station Lakehurst; the TC-13 Mod 2 test steam catapult, representative of current fleet technology, was used. In addition to catapult launches at varying power levels, a three-week test plan included dual-aircraft jet blast deflector testing and catapult launches using a degraded catapult configuration to measure the effects of steam ingestion on the aircraft.[589]

On 13 August 2011, the F-35 successfully completed jet blast deflector (JBD) testing at Lakehurst. F-35C test aircraft CF-1 along with an F/A-18E tested a combined JBD cooling panel configuration. The tests measured temperature, pressure, sound level, velocity, and other environmental data; the JBD model will enable the operation of all carrier aircraft, including the F-35C. Further carrier suitability testing continued in preparation for initial ship trials in 2013.[590] On 18 November 2011, the U.S. Navy used its new Electromagnetic Aircraft Launch System (EMALS) to launch an F-35C into the air for the first time.[591]

On 22 June 2013, Strike Fighter Squadron VFA-101 received the Navy's first F-35C at Eglin Air Force Base, Florida.[592][593]

The USN is dealing with the following issues in adapting their carriers to operate the F-35C.[594]

  • The F135 engine exceeds the weight capacity of traditional underway replenishment systems and generates more heat than previous engines.
  • The stealthy skin requires new repair techniques; extensive skin damage will necessitate repairs at Lockheed's land-based facilities.
  • The adoption of lithium-ion batteries needing careful thermal management, and higher voltage systems than traditional fighters.
  • Storing of new weapons not previously employed on carrier aircraft.
  • Large quantities of classified data generated during missions shall require additional security.

In February 2014, Lockheed said the F-35C was on schedule for sea trials after the tailhook was redesigned. The new tailhook has a different shape to better catch arresting wires. Testing on land achieved 36 successful landings. Sea trials were scheduled for October 2014.[595]

On 3 November 2014, an F-35C of VX-23, one of the Navy's flight test units, made its first landing on an aircraft carrier when it recovered aboard USS Nimitz; this started a 2 week deployment of a pair of aircraft for the initial at sea Development Testing I or DTI, the first of three at sea tests planned for the F-35C.[596][597] The initial deployment was completed on November 14.[598]

The U.S. Navy may use the F-35C as part of its UCLASS effort to operate a carrier-based unmanned aerial vehicle. Though it has been suggested that the UCLASS could carry air-to-air weapons, an unmanned aircraft lacks situational awareness and is more vulnerable to electronic countermeasures than manned aircraft, and autonomy for deploying lethal weapons is not under development. With the F-35C as the center of a network of naval systems, it could feed information to the UCLASS and order it to fire on a certain target. Large numbers of F-35Cs operating in contested environments can generate a clear picture of the battlespace, and share it with unmanned assets that can be directed to attack.[599]

Other versions

F-35I

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

The F-35I Adir (Hebrew: <templatestyles src="Script/styles_hebrew.css" />אדיר‎, meaning "Awesome",[600] or "Mighty One"[601]) is an F-35A with Israeli modifications. A senior Israel Air Force official stated "the aircraft will be designated F-35I, as there will be unique Israeli features installed in them". Despite an initial refusal to allow such modifications, the U.S. has agreed to let Israel integrate its own electronic warfare systems, such as sensors and countermeasures, into the aircraft. The main computer will have a plug-and-play feature to allow add-on Israeli electronics to be used; proposed systems include an external jamming pod, and new Israeli air-to-air missiles and guided bombs in the internal weapon bays.[602][603]

Israel Aerospace Industries (IAI) has considered playing a role in the development of a proposed two-seat F-35; an IAI executive stated: "There is a known demand for two seats not only from Israel but from other air forces."[604] IAI plans to produce conformal fuel tanks.[605] A senior IAF official stated that elements of the F-35's stealth may be overcome in 5 to 10 years, while the aircraft will be in service for 30 to 40 years, which is why Israel insisted on installing their own electronic warfare systems: "The basic F-35 design is OK. We can make do with adding integrated software."[606] Israel is interested in purchasing up to 75 F-35s.[607]

On 12 December 2016, Israel began receiving its first F-35Is of the 50 it plans to purchase. Israel is to be the second nation with an operational F-35 squadron following the U.S.[608][609][610]

CF-35

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

The Canadian CF-35 is a proposed variant that would differ from the F-35A through the addition of a drogue parachute and may include an F-35B/C-style refueling probe.[534][611] In 2012, it was revealed that the CF-35 would employ the same boom refueling system as the F-35A.[612] One alternative proposal would have been the adoption of the F-35C for its probe refueling and lower landing speed; the Parliamentary Budget Officer's report cited the F-35C's limited performance and payload as being too high a price to pay.[613] Following the 2015 Federal Election, in which the Liberal Party, whose campaign had included a pledge to cancel the F-35 procurement,[614] won a majority in the House of Commons, and stated it would run a new competition for an aircraft to replace the existing CF-18 Hornet.[615]

F-35D

Early-stage design study for a possible upgrade of the F-35A to be fielded by the 2035 target date of the Air Force Future Operating Concept.[616][617]

Operators

One of the RAAF's first two F-35As in December 2014
File:IAF-F-35I-and-F-16I-nf.jpg
The F-35I Adir (accompanied by a 253 Squadron F-16I Sufa) on its debut flight by the Israeli Air Force in Israel, December 2016

F-35A

 Australia
 Denmark
 Israel
 Italy
 Japan
File:RNLAF F-35 F-001 01.jpg
Dutch F-35A in July 2013
 Netherlands
 Norway
 Republic of Korea
 Turkey
 United States

F-35B

File:RAF F-35B.jpg
A British F-35B in flight in 2016
 Italy
 United Kingdom4 in use for testing;[649] 14 on order,[650][651] with 42 (24 FOC fighters and 18 training aircraft) to be fast-tracked by 2023;[652][653] 138 F-35s total planned[654][655]
 United States

F-35C

 United States

Accidents

On 23 June 2014, an F-35A preparing to take off on a training flight at Eglin Air Force Base experienced a fire in the engine area. The pilot escaped unharmed. The accident caused all training to be halted on 25 June, and all flights halted on 3 July.[474][475][476] During the incident investigation, engine parts from the burned aircraft were discovered on the runway, indicating it was a substantial engine failure.[670] The fleet was returned to flight on 15 July with restrictions in the flight envelope.[477] Preliminary findings suggests that excessive rubbing of the engine fan blades created increased stress and wear and eventually resulted in catastrophic failure of the fan.[671]

In early June 2015, the USAF Air Education and Training Command (AETC) issued its official report on the incident. It found that the incident was the result of a failure of the third stage rotor of the engine's fan module. The report explained that "pieces of the failed rotor arm cut through the engine's fan case, the engine bay, an internal fuel tank, and hydraulic and fuel lines before exiting through the aircraft's upper fuselage". Pratt and Whitney, the engine manufacturers, developed two remedies to the problem. The first is an extended "rub-in" to increase the gap between the second stator and the third rotor integral arm seal. The second is the redesign to pre-trench the stator. Both should be complete by early 2016. Cost of the problem was estimated at US$50 million. All aircraft resumed operations within 25 days of the incident.[672]

Specifications (F-35A)

F-35A three-view.PNG
The first of 15 pre-production F-35s
F-35B cutaway with LiftFan

Data from Lockheed Martin specifications,[273][673][674] F-35 Program brief,[294] F-35 JSF Statistics,[288] F-35 Program Status[675]

General characteristics

Performance

Armament

Avionics

Differences between variants
F-35A
CTOL
F-35B
STOVL
F-35C
CATOBAR
Length Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). 50.5 ft (15.4 m) 50.8 ft (15.5 m)
Wingspan Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value).
Wing Area 460 ft² (42.7 m²) 460 ft² (42.7 m²) 620 ft² (62.1 m²)
Empty weight 29,098 lb (13,199 kg) 32,300 lb (14,700 kg) 34,800 lb (15,800 kg)
Internal fuel 18,498 lb (8,390 kg) 13,326 lb (6,045 kg) 19,624 lb (8,900 kg)
Max takeoff weight 70,000 lb class (31,800 kg) 60,000 lb class (27,200 kg) 70,000 lb class (31,800 kg)
Range >1,200 nmi (2,220 km) >900 nmi (1,670 km) >1,200 nmi (2,220 km)
Combat radius on
internal fuel[689]
625 nmi (1,158 km) 467 nmi (865 km) 630 nmi (1,167 km)
Thrust/weight
 • full fuel:
 • 50% fuel:
0.87
1.07
0.90
1.04
0.75
0.91

Appearances in media

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

See also

Related development
Aircraft of comparable role, configuration and era
Related lists

References

Notes

  1. F-35A: 136, F-35B: 64, F-35C: 31
  2. Quote: "The F-35 Lightning II will carry on the legacy of two of the greatest and most capable fighter aircraft of all time. Just as the P-38 and the British Lightning were at the top of their class during their day, the F-35 will redefine multi-role fighter capability in the 21st century." Ralph D. Heath, president of Lockheed Martin Aeronautics Co.[35]
  3. Quote: "The F-35A, with an air-to-air mission takeoff weight of 49,540 lb."[272]
  4. Quote: "Brigadier Davis was more forthright in his comments to media in Canberra, saying the ‘Raptor’ lacks some of the key sensors and the enhanced man-machine interface of the F-35."[384]
  5. C is 51.5 ft (15.7 m)
  6. B is the same, C: 14.9 ft (4.54 m)
  7. F-35B: 47,996 lb (21,771 kg); F-35C: 57,094 lb (25,896 kg)
  8. C is same, B: 60,000 lb (27,000 kg)
  9. F-35B: vertical thrust 39,700 lbf (176 kN)
  10. F-35B: 13,326 lb (6,352 kg); F-35C: 19,624 lb (9,110 kg)
  11. F-35B: 7.5 g, F-35C: 7.5 g
  12. F-35B and F-35C have the cannon in an external pod with 220 rounds

Citations

  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. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. http://www.jsf.mil/news/docs/20160324_Fact-Sheet.pdf
  9. 9.0 9.1 9.2 Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  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. Lockheed F-35 service life extended to 2070 – Flightglobal.com, 25 March 2016
  15. "F-35 Global Partnerships." Archived 2 September 2012 at the Wayback Machine Lockheed Martin. Retrieved: 31 October 2012.
  16. Dudley, Richard. "Program Partners Confirm Support for F-35 Joint Strike Fighter". Defence Update, 5 March 2012. Retrieved: 18 March 2012.
  17. 17.0 17.1 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. 20.0 20.1 Lua error in package.lua at line 80: module 'strict' not found..
  21. "F-35 Joint Strike Fighter (JSF) Lightning II." Global Security. Retrieved: 7 April 2010.
  22. "Lockheed Martin F22 and F35 5th Gen Revolution In Military Aviation." Space Daily, 22 February 2006.
  23. 23.0 23.1 Keijsper 2007, p. 119.
  24. Polmar 2005, p. 398.
  25. Parsch, Andreas. "Designation Systems." Designation Systems, 27 April 2006. Retrieved 23 November 2009.
  26. Thompson, Mark. "The Most Expensive Weapon Ever Built." Time magazine, 25 February 2013, pp. 26–30 (lack of 2-seat trainer variants cited on p. 27).
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Keijsper 2007, pp. 122, 124.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Fulghum, David A. and Robert Wall. "USAF Plans for Fighters Change." Aviation Week and Space Technology, 19 September 2004.
  32. Keijsper 2007, p. 124,
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. "'Lightning II' moniker given to Joint Strike Fighter." Air Force Link, United States Air Force, 7 June 2006. Retrieved 1 December 2008.
  35. Lua error in package.lua at line 80: module 'strict' not found. (DOC) via jsf.mil
  36. 36.0 36.1 "F-35 Distributed Aperture System (EO DAS)." Northrop Grumman. Retrieved 6 April 2010.
  37. "Italy Wins JSF Final Assembly: U.K. Presses Maintenance, Support." Aviation Week, February 2013.
  38. "Handling Specialty Turn Key Capabilities." Archived 11 March 2012 at the Wayback Machine handling.com. Retrieved: 16 November 2010.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Moore, Mona. "F-35 production on target." Northwest Florida Daily News, 5 January 2009, Volume 62, Number 341, p. A1.
  41. Gearan, Anne. "Defense Secretary Gates proposes weapons cuts." Archived 24 May 2009 at the Wayback Machine The Seattle Times, 7 April 2009.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. GAO-06-356, "DOD Plans to Enter Production before Testing Demonstrates Acceptable Performance." GAO, March 2006.
  44. untitled
  45. GAO-11-233SP, "Defense Acquisitions: Assessments of Selected Weapon Programs." Gao.gov, 29 August 2008. Retrieved 4 December 2011.
  46. "FY 2011 Budget Estimates." U.S. Air Force, February 2010, pp. 1–47.
  47. Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. Lua error in package.lua at line 80: module 'strict' not found.
  50. Gorman, Siobhan. "Computer Spies Breach Fighter-Jet Project." The Wall Street Journal, 21 April 2009. Retrieved 29 March 2010.
  51. Cullen, Simon. "Jet maker denies F-35 security breach." Australian Broadcasting Corporation, 22 April 2009. Retrieved 29 March 2010.
  52. Lua error in package.lua at line 80: module 'strict' not found.
  53. Lua error in package.lua at line 80: module 'strict' not found.
  54. Bennett, John T. "Plan Afoot to Halt F-35 Cost Hikes, Delays."[dead link] defensenews.com, 9 November 2009. Retrieved 23 November 2009.
  55. Clark, Colin. "Gates Fires JSF Program Manager." dodbuzz.com, 1 February 2010. Retrieved 21 March 2010.
  56. Lua error in package.lua at line 80: module 'strict' not found.
  57. "JSF faces US Senate grilling." australianaviation.com.au, 12 March 2010.
  58. Shalal-Esa, Andrea and Tim Dobbyn, ed. "Price of F35 fighter soars." Reuters. Retrieved: 12 September 2011.
  59. Lua error in package.lua at line 80: module 'strict' not found.
  60. Thompson, Mark. "The Costly F-35: The Saga of America's Next Fighter Jet." Time, 25 March 2010.
  61. Trimble, Stephen. "Fix for F-35 final assembly problem pushed back."[dead link] Flight International, 16 August 2010. Retrieved: 24 August 2010.
  62. Clark, Colin. "Prez Panel Wants $100B DoD Cut; Freeze Pay, Kill F-35B, EFV." DoDBuzz, 10 November 2010.
  63. $200 billion in illustrative savings point 47 National Commission on Fiscal Responsibility and Reform, 10 November 2010.
  64. "Lockheed F–35 Fighter In Deficit Panel's Sights." The New York Times, 10 November 2010.
  65. Tirpak, John A. "Shorting the F-35." Archived 2 December 2010 at the Wayback Machine Air Force Association, 15 November 2010.
  66. Thompson, Loren B. "Rumor Of Marine F-35 Termination Talks Is Wrong." Lexington Institute, 15 November 2010.
  67. Thompson, Loren. "Pentagon Factional Disputes Are A Key Driver Of F-35 Cost Increases." Lexington Institute, 1 November 2010.
  68. Trimble, Stephen. "Lockheed's F-35 faces second restructuring this year." Archived 6 November 2010 at the Wayback Machine Flight International, 3 November 2010.
  69. "Lockheed Martin F-35 Begins Flying Block 1 Software." Lockheed Martin, 15 November 2010.
  70. Hoyle, Craig. "Can Lockheed deliver on the Joint Strike Fighter dream? " Archived 13 January 2011 at the Wayback Machine Flight International, 14 December 2010.
  71. Warwick, Graham and Amy Butler. "F-35 Replan Adds Time, Resources For Testing." Aviation Week, 8 February 2011.
  72. Charette, Robert N. "F-35 Program Continues to Struggle with Software." IEEE Spectrum, 19 September 2012.
  73. Whittle, Richard. "JSF's Build And Test Was 'Miscalculation,' Adm. Venlet Says; Production Must Slow." Aol Defense, 1 December 2011.
  74. Cox, Bob. "Pentagon takes a harder line with Lockheed Martin over F-35." Star-Telegram, 26 October 2011. Archived 28 October 2012 at the Wayback Machine
  75. Thompson, Loren. "Why Pentagon Weapon 'Efficiencies' Are Often An Illusion." Forbes, 1 November 2011.
  76. Katz, Yaakov. "Will Iran influence pick for next IAF commander?" The Jerusalem Post, 4 December 2011.
  77. DiMascio, Jen. "McCain Backs Hard-Line Pentagon F-35 Stance." Aviation Week, 18 November 2011.[dead link]
  78. Clark, Colin. "McCain Slams JSF, Calls Program 'Scandal And A Tragedy;' Contract Talks Advance." Aol Defense, 5 December 2011.
  79. "US defence firms blast Pentagon on contract changes: companies warn of layoffs, higher costs." Archived 10 March 2012 at the Wayback Machine Reuters, 12 December 2011.
  80. "GAO-12-525T: Restructuring Added Resources and Reduced Risk, but Concurrency Is Still a Major Concern." GAO. 20 March 2012.
  81. Pincus, Walter. "Slack budgeting at Defense." Washington Post, 6 June 2012.
  82. Lua error in package.lua at line 80: module 'strict' not found.
  83. 83.0 83.1 Trimble, Stephen. "US military unveils possible F-35B redesign in sweeping budget reforms." Archived 11 January 2011 at the Wayback Machine Flight International, 6 January 2011.
  84. Gates, Robert. "Speech to Air Force Academy." Archived 4 March 2011 at the Wayback Machine defense.gov, 4 March 2011. Retrieved 8 March 2011.
  85. Rabechault, Mathieu. "F-35 looking more like white elephant." Yahoo News, 13 January 2011.
  86. 86.0 86.1 Marshall, Tyrone C. Jr. "Panetta Lifts F-35B Probation." Aviation Week, 20 January 2012.
  87. Fulghum, David A. "Repairing the F-35 Program." Aviation Week, 10 February 2011.
  88. 88.0 88.1 Majumdar, Dave. "F-35 Tests Proceed, Revealing F/A-18-Like Performance." Defense News, 16 May 2011.
  89. Lua error in package.lua at line 80: module 'strict' not found.
  90. "Program Restructuring Should Improve Outcomes, but Progress Is Still Lagging Overall." star-telegram.com, 15 March 2011.
  91. Trimble, Stephen. "USAF rules out new F-15s and F-16s to narrow ‘fighter gap’." Archived 12 August 2011 at the Wayback Machine Flight International, 4 June 2010.
  92. "Israel eyes used F-15s to fill for F-35s." United Press International, 18 April 2011.
  93. "Australia may buy more Super Hornets amid F-35 delays: report." Reuters, 13 May 2011.
  94. "Lockheed Addressing F-35 ‘Development Risks,’ Congress Told." Bloomberg News, 19 May 2011.
  95. "The last manned fighter." The Economist, 14 July 2011.
  96. Capaccio, Tony. "Pentagon Cuts Four Lockheed Jets From Next Order, Pentagon Says." Bloomberg, 26 October 2011.
  97. Lerman, David. "Pentagon Budget for 2013 Calls for Two Fewer of Lockheed’s F-35 Fighters." Bloomberg News. 13 February 2012.
  98. Gibbs, Walter. "U.S. slowdown on F-35 jet buy to raise cost: Lockheed." Reuters, 14 February 2012.
  99. "Pentagon, Lockheed see price of F-35 going up." Reuters, 14 February 2012.
  100. "Japan tells U.S. it may halt F-35 purchase if prices rise." Mainichi Japan. 23 February 2012.
  101. Shalal-Esa, Andrea. "'No more money' for F-35 cost overruns: Pentagon." Reuters, 20 March 2012.
  102. Shalal-Esa, Andrea. "Pentagon says F-35 fighter delayed, costs rise 4.3 percent." Reuters, 29 March 2012.
  103. Cox, Bob. "Pentagon to tie F-35 orders more closely to development and testing progress." Star Telegram, 8 May 2012.
  104. Lua error in package.lua at line 80: module 'strict' not found.
  105. Lua error in package.lua at line 80: module 'strict' not found.
  106. Campion-Smith, Bruce. "Canada may not buy F-35 fighter jets, Ottawa admits." The Star, 13 March 2012. Retrieved 23 March 2012.
  107. "The F-35: Not just costly but obsolete; To aviation nerds, the Joint Strike Fighter is looking more and more like an ugly mutt." Maclean's, 13 April 2012.
  108. "Pentagon's F-35 Fighter Under Fire in Congress." Archived 9 October 2010 at the Wayback Machine PBS. Retrieved 22 August 2010.
  109. "41st Parliament, 1st Session, Standing Committee on National Defence." Parliament of Canada, 24 November 2011.
  110. Shalal-Esa, Andrea. "Government sees lifetime cost of F-35 fighter at $1.51 trillion." Reuters, 2 April 2012.
  111. Butler, Amy. "USAF Reducing Possible JSF Basing Locations." Aviation Week. 2 March 2012.
  112. "Lockheed Martin Statement on 2011 SAR Report." Archived 1 April 2012 at the Wayback Machine Lockheed Martin. 31 March 2012.
  113. Williams, Peter. "Quickstep finds cash harder to come by." The West Australian, 4 January 2012.
  114. Weisgerber, Marcus. "DoD Anticipates Better Price on Next F-35 Batch." Defense News. 8 March 2012.
  115. Lua error in package.lua at line 80: module 'strict' not found.
  116. Lua error in package.lua at line 80: module 'strict' not found.
  117. Weisgerber, Marcus. "Schwartz defends reduced F-35 combat radius." AirForce Times. 6 March 2012.
  118. "Pentagon agrees to F-35A combat radius reduction." Flight International, 8 March 2012.
  119. "JSFail? Not When the Pentagon Grades the F-35 on a Curve."[dead link] DefPro.News, 7 March 2012.
  120. Regan, James. "U.S. seeks to ease concerns over F-35 delays, costs."[dead link] Reuters, 15 March 2012.
  121. "U.S. weapons maker pushes back at Pentagon." Reuters, 1 June 2012.
  122. Shalal-Esa, Andrea. "Lockheed hires temps at strike-hit Fort Worth plant."[dead link] Reuters, 1 June 2012.
  123. Shalal-Esa, Andrea. "Lockheed F-35 scrap rate at 16 percent – Pentagon." Reuters, 8 June 2012.
  124. Shalal-Esa, Andrea. "Lockheed brings in more workers as strike drags on." Reuters, 14 June 2012.
  125. "Fitch lowers Lockheed Martin outlook to negative." Trefis, 13 June 2012.
  126. "Lockheed says more orders key to cutting F-35 cost." Reuters, 19 June 2012.
  127. Freeman, Ben. "The Guerilla Warfare of Pentagon Contractors." POGO, 21 June 2012.
  128. Wheeler, Winslow. "How the F-35 Nearly Doubled In Price (And Why You Didn’t Know)." Time, 9 July 2012.
  129. Cox, Bob. "Pentagon tightens grading standards, cuts into Lockheed profits." Star-Telegram, 24 July 2012.
  130. Capaccio, Tony. "Pentagon Withholds $47 Million From Lockheed on F-35." Archived 21 September 2013 at the Wayback Machine Business Week, 26 October 2012.
  131. Lua error in package.lua at line 80: module 'strict' not found.
  132. Lua error in package.lua at line 80: module 'strict' not found.
  133. Lua error in package.lua at line 80: module 'strict' not found.
  134. Lua error in package.lua at line 80: module 'strict' not found.
  135. Lua error in package.lua at line 80: module 'strict' not found.
  136. Lua error in package.lua at line 80: module 'strict' not found.
  137. Lua error in package.lua at line 80: module 'strict' not found.
  138. Lua error in package.lua at line 80: module 'strict' not found.
  139. Lua error in package.lua at line 80: module 'strict' not found.
  140. F-35 No Longer the Problem Child. Airforcemag.com (14 June 2013). Retrieved on 16 August 2013.
  141. Lua error in package.lua at line 80: module 'strict' not found.
  142. Lua error in package.lua at line 80: module 'strict' not found.
  143. Lua error in package.lua at line 80: module 'strict' not found.
  144. Lua error in package.lua at line 80: module 'strict' not found.
  145. Lua error in package.lua at line 80: module 'strict' not found. Video not archived.
  146. Lua error in package.lua at line 80: module 'strict' not found.
  147. Paul Barrett. "Danger Zone". Bloomberg Businessweek. 10 April 2017, pp. 50-55.
  148. Isby, David C. "Status of the Joint Strike Fighter". Air International, January 2014, p. 86. Accessed: 17 June 2014.
  149. Lua error in package.lua at line 80: module 'strict' not found.
  150. Lua error in package.lua at line 80: module 'strict' not found.
  151. 151.0 151.1 http://www.dote.osd.mil/pub/reports/FY2014/pdf/dod/2014f35jsf.pdf
  152. Lua error in package.lua at line 80: module 'strict' not found.
  153. Lua error in package.lua at line 80: module 'strict' not found.
  154. Lua error in package.lua at line 80: module 'strict' not found.
  155. 155.0 155.1 Department of Defense (2015). Selected Acquisition Report (SAR) – F-35 Joint Strike Fighter Aircraft (F-35). Retrieved 25 May 2015.
  156. Robbert, Albert A., Costs of Flying Units in Air Force Active and Reserve Components, USAF, ISBN 978-0-8330-7666-3, retrieved 25 May 2015
  157. Lua error in package.lua at line 80: module 'strict' not found.
  158. Lua error in package.lua at line 80: module 'strict' not found.
  159. Lua error in package.lua at line 80: module 'strict' not found.
  160. http://www.dote.osd.mil/pub/reports/FY2015/pdf/dod/2015f35jsf.pdf
  161. Lua error in package.lua at line 80: module 'strict' not found.
  162. Lua error in package.lua at line 80: module 'strict' not found.
  163. Lua error in package.lua at line 80: module 'strict' not found.
  164. Lua error in package.lua at line 80: module 'strict' not found.
  165. Lua error in package.lua at line 80: module 'strict' not found.
  166. Lua error in package.lua at line 80: module 'strict' not found.
  167. Kent, John R. "Setting the Record Straight On F-35." Lockheed Martin, 19 September 2008.
  168. Sweetman, Bill. "JSF Leaders Back In The Fight." Aviation Week, 22 September 2008. Retrieved 3 July 2010.
  169. "Lockheed Martin briefing package for Norway." Archived 12 October 2012 at the Wayback Machine Lockheed Martin, 24 April 2008.
  170. Pocock, Chris. "LM defends F-35 JSF agility against critics." Aviation International News, 15 June 2009.
  171. Lua error in package.lua at line 80: module 'strict' not found.
  172. Thompson, Loren B. "F-35 Fighter Confounding Critics As Flight Tests Ramp Up." Lexington Institute, 1 March 2011.
  173. Beijing-based newspaper Global Times launches English edition, People's Daily, 20 April 2009
  174. Lua error in package.lua at line 80: module 'strict' not found.
  175. "Amerikaanse twijfel over JSF" (in Dutch). Nova, 12 July 2010. Retrieved 22 July 2010.
  176. Entous, Adam. "U.S.-Saudi Arms Plan Grows to Record Size: Addition of Apaches, Black Hawks Swells Deal to $60 billion." The Wall Street Journal, 14 August 2010. Retrieved 16 August 2010.
  177. "First RAF pilot flies Joint Strike Fighter." British Ministry of Defence via Defence News, 9 February 2010.
  178. Wolf, Jim. "Exclusive: US to withhold F-35 fighter software codes." Reuters, 24 November 2009. Retrieved: 12 September 2011.
  179. Lua error in package.lua at line 80: module 'strict' not found.
  180. Lua error in package.lua at line 80: module 'strict' not found.
  181. Lua error in package.lua at line 80: module 'strict' not found.
  182. Stevens, Geoff. "Single-engine F-35’s may endanger Canadian crews." TheRecord, 31 January 2011.
  183. Axe, David. "Trillion-Dollar Jet Has Thirteen Expensive New Flaws." Wired, 13 December 2011.
  184. "F-35 Joint Strike Fighter Concurrency Quick Look Review." Department of Defense, 29 November 2011. Retrieved 25 January 2012.
  185. Auslin, Michael. "Flying Not Quite as High." Weekly Standard, 7 May 2012.
  186. "U.S., Lockheed Martin reach deal on Israeli F-35 fighter jets." Reuters, 26 July 2012.
  187. Lua error in package.lua at line 80: module 'strict' not found.
  188. "Department of Defence annual report 2010–1." ParlInfo – Parliamentary Joint Committee on Foreign Affairs, Defence and Trade, 16 March 2012. Retrieved 6 June 2012.
  189. "Report: Lightning a threat to F-35." Navy Times
  190. Lua error in package.lua at line 80: module 'strict' not found.
  191. Shachtman, Noah. "Gajillion-Dollar Stealth Fighter, Now Easier to Shoot Down." Wired, 11 June 2010.
  192. Lua error in package.lua at line 80: module 'strict' not found.
  193. Lua error in package.lua at line 80: module 'strict' not found.
  194. Lua error in package.lua at line 80: module 'strict' not found.
  195. Lua error in package.lua at line 80: module 'strict' not found.
  196. Lua error in package.lua at line 80: module 'strict' not found.
  197. Lua error in package.lua at line 80: module 'strict' not found.
  198. Lua error in package.lua at line 80: module 'strict' not found.
  199. Lua error in package.lua at line 80: module 'strict' not found.
  200. Lua error in package.lua at line 80: module 'strict' not found.
  201. Lua error in package.lua at line 80: module 'strict' not found.
  202. Lua error in package.lua at line 80: module 'strict' not found.
  203. Lua error in package.lua at line 80: module 'strict' not found.
  204. 204.0 204.1 Lua error in package.lua at line 80: module 'strict' not found.
  205. Lua error in package.lua at line 80: module 'strict' not found.
  206. Lua error in package.lua at line 80: module 'strict' not found.
  207. Lua error in package.lua at line 80: module 'strict' not found.
  208. 208.0 208.1 Lua error in package.lua at line 80: module 'strict' not found.
  209. 209.0 209.1 Lua error in package.lua at line 80: module 'strict' not found.
  210. http://aviationweek.com/site-files/aviationweek.com/files/uploads/2015/06/F-35%20High%20AoA%20Maneuvers.pdf
  211. Lua error in package.lua at line 80: module 'strict' not found.
  212. Lua error in package.lua at line 80: module 'strict' not found.
  213. Lua error in package.lua at line 80: module 'strict' not found.
  214. You Say The F-35 Can’t Dogfight? I Say Good. – LexingtonInstitute.org, 30 June 2015
  215. F-16 Vs. F-35 In A Dogfight: JPO, Air Force Weigh In On Who’s Best – Breakingdefense.com, 2 July 2015
  216. https://d262ilb51hltx0.cloudfront.net/max/1029/1*Cvd15pTLP_xPYJDRQ-Tgxw.png
  217. Lua error in package.lua at line 80: module 'strict' not found.
  218. Lua error in package.lua at line 80: module 'strict' not found.
  219. Lua error in package.lua at line 80: module 'strict' not found.
  220. "Pentagon Tells Lockheed to Shape Up on F-35 Fighter." Reuters.com, 17 September 2012.
  221. "Pentagon seeks competition for sustainment of Lockheed F-35."[dead link] Chicago Tribune, 28 September 2012.
  222. Lua error in package.lua at line 80: module 'strict' not found.
  223. Lua error in package.lua at line 80: module 'strict' not found.
  224. Lua error in package.lua at line 80: module 'strict' not found.
  225. Lua error in package.lua at line 80: module 'strict' not found.
  226. Lua error in package.lua at line 80: module 'strict' not found.
  227. Lua error in package.lua at line 80: module 'strict' not found.
  228. Lua error in package.lua at line 80: module 'strict' not found.
  229. Lua error in package.lua at line 80: module 'strict' not found.
  230. Lua error in package.lua at line 80: module 'strict' not found.
  231. Lua error in package.lua at line 80: module 'strict' not found.
  232. "Vertiflight". Journal of the American Helicopter Society, January 2004.
  233. Kent, John R. and Chris Geisel. "F-35 STOVL supersonic." lockheedmartin.com. Retrieved 16 November 2010.
  234. Johns, Darnell Sharkleford. "Air Force presentation to House Subcommittee on Air and Land Forces." armedservices.house.gov, 20 May 2009, p. 10.
  235. Amaani, USAF Tech. Sgt. Lyle. "Air Force takes combat air acquisitions priorities to Hill." U.S. Air Force, 3 April 2009.
  236. 236.0 236.1 "Capabilities." (archived version) Lockheed Martin. Retrieved 24 July 2010.
  237. "LockMart F-35 FAQ." Lockheed Martin, 2011.
  238. Trimble, Stephen. "Lockheed Martin sees F-35A replacing USAF air superiority F-15C/Ds." Archived 15 February 2010 at the Wayback Machine Flight International, 4 February 2010. Retrieved 2 March 2010.
  239. 239.0 239.1 Butler, Amy. "New Stealth Concept Could Affect JSF Cost." Aviation Week, 17 May 2010. Retrieved 5 June 2010.[dead link]
  240. L3 (March 2011), Open System Architecture (OSA) Secure Processing
  241. Lua error in package.lua at line 80: module 'strict' not found.
  242. Lua error in package.lua at line 80: module 'strict' not found.
  243. Philips, E. H. "The Electric Jet." Aviation Week & Space Technology, 5 February 2007.
  244. Parker, Ian. "Reducing Risk on the Joint Strike Fighter." Avionics Magazine, Access Intelligence, LLC, 1 June 2007. Retrieved 8 June 2007.
  245. "F/A-18E/F Super Hornet." Boeing.
  246. Giese, Jack. "F-35 Brings Unique 5th Generation Capabilities." lockheedmartin.com, 23 October 2009.
  247. Shalal-Esa, Andrea. "Pentagon seeks competition for sustainment of Lockheed F-35."[dead link] Reuters, 28 September 2012.
  248. Sweetman, Bill. "Wrongheaded? Really?" Archived 4 April 2013 at the Wayback Machine Aviation Week, 18 October 2012.
  249. "F-35 Cost Per Flying Hour: A Tale of Two Numbers." Archived 3 June 2013 at the Wayback Machine
  250. Majumdar, Dave. "USMC finds workaround for cyber vulnerability on F-35 logistics system." Flight International, 20 November 2012.
  251. Lua error in package.lua at line 80: module 'strict' not found.
  252. Trimble, Stephen. "Farnborough: Lockheed encouraged by pace of F-35 testing." Flight International, 12 July 2010. Retrieved 22 July 2010.
  253. Lua error in package.lua at line 80: module 'strict' not found.
  254. Lua error in package.lua at line 80: module 'strict' not found.
  255. Lua error in package.lua at line 80: module 'strict' not found.
  256. Lua error in package.lua at line 80: module 'strict' not found.
  257. Lua error in package.lua at line 80: module 'strict' not found.
  258. "Contract Awarded To Validate Process For JSF." onlineamd.com, 17 May 2010. Retrieved 22 July 2010.
  259. Trimble, Stephen. "Lockheed Martin reveals F-35 to feature nanocomposite structures." Archived 30 May 2011 at the Wayback Machine Flight International, 26 May 2011.
  260. Edwards, Jack E. "Defense Management: DOD Needs to Monitor and Assess Corrective Actions Resulting from Its Corrosion Study of the F-35 Joint Strike Fighter." United States Government Accountability Office, Washington, DC, 16 December 2010.
  261. Ryberg, Eric S. "The Influence of Ship Configuration on the Design of the Joint Strike Fighter", p. 5. Naval Surface Warfare Center Dahlgren Division, 26 February 2002. Accessed: 1 December 2013.
  262. Lua error in package.lua at line 80: module 'strict' not found.
  263. Clark, Colin. "AF Worries JSF Costs May Soar." DoD Buzz 27 January 2011.
  264. Capaccio, Tony. "Lockheed Martin F-35 Operating Costs May Reach $1 Trillion." Archived 29 April 2011 at the Wayback Machine Bloomberg News, 21 April 2011.
  265. Lua error in package.lua at line 80: module 'strict' not found.
  266. Lua error in package.lua at line 80: module 'strict' not found.
  267. Trimble, Stephen. "Rolls-Royce: F136 survival is key for major F-35 engine upgrade." Archived 14 June 2009 at the Wayback Machine Flight International, 11 June 2009.
  268. "GE, Rolls Royce Stop Funding F-35 Alt Engine." Defense News, 4 December 2011.
  269. "Frequently Asked Questions about JSF." JSF. Retrieved 6 April 2010.
  270. Lua error in package.lua at line 80: module 'strict' not found.
  271. Warwick, Graham. "Screech, the F135 and the JSF Engine War." Aviation Week, 17 March 2011.
  272. 272.0 272.1 272.2 Nativi, Andy. "F-35 Air Combat Skills Analyzed." Aviation Week, 5 March 2009. Archived 26 December 2010 at the Wayback Machine
  273. 273.0 273.1 273.2 Lua error in package.lua at line 80: module 'strict' not found.
  274. "Swivel nozzle VJ101D and VJ101E." Vstol.org, 20 June 2009.
  275. Hirschberg, Mike. ""V/STOL Fighter Programs in Germany: 1956–1975", p. 50. International Powered Lift Conference, 1 November 2000. Retrieved 3 October 2012.
  276. "How the Harrier hovers." harrier.org. Retrieved 16 November 2010.
  277. "LiftSystem." Rolls-Royce. Retrieved 23 November 2009.
  278. Zolfagharifard, Ellie. "Rolls-Royce's LiftSystem for the Joint Strike Fighter" The Engineer, 28 March 2011.
  279. Kjelgaard, Chris. "From Supersonic to Hover: How the F-35 Flies". Space, 21 December 2007. Retrieved 18 October 2010.
  280. Hutchinson, John. "Going Vertical: Developing a STOVL system." ingenia.org.uk. Retrieved 23 November 2009.
  281. Warwick, Graham. "Second Engine Could Cut F-35 Production." Aviation Week. Retrieved 6 April 2010.[dead link]
  282. "GE Rolls-Royce Fighter Engine Team completes study for Netherlands." rolls-royce.com. Retrieved 23 November 2009.
  283. "Pratt Raises Stakes In JSF Engine Battle." Aviation Week, 27 August 2010. Retrieved 25 November 2010.
  284. "Lockheed Martin F-35 Joint Strike Fighter Succeeds In First Vertical Landing." lockheedmartin.com, Press Release, 18 March 2010.
  285. Lua error in package.lua at line 80: module 'strict' not found.
  286. Swedberg, Claire. "Energy-Harvesting Sensors to Monitor Health of Jet Engines." RFID Journal, 31 May 2011.
  287. "F-35 gun system" Archived 6 June 2011 at the Wayback Machine, "GAU-22/A" Archived 17 July 2011 at the Wayback Machine. General Dynamics Armament and Technical Products. Retrieved 7 April 2011.
  288. 288.0 288.1 288.2 288.3 288.4 "F-35 Joint Strike Fighter Media Kit Statistics." JSF.mil August 2004.
  289. Keijsper 2007, p. 233.
  290. 290.0 290.1 Donald, David. "Terma Highlights F-35 Multi-Mission Pod." AINonline, 11 July 2012.
  291. Lua error in package.lua at line 80: module 'strict' not found.
  292. 292.0 292.1 Hewson, Robert. "UK changes JSF configuration for ASRAAM." Jane's, 4 March 2008. Archived 16 September 2012 at the Wayback Machine
  293. Keijsper 2007, pp. 220, 239.
  294. 294.0 294.1 294.2 294.3 294.4 294.5 294.6 294.7 Davis, Brigadier General Charles R. "F-35 Program Brief." USAF, 26 September 2006.
  295. "JSF Suite: BRU-67, BRU-68, LAU-147 – Carriage Systems: Pneumatic Actuated, Single Carriage."[dead link] es.is.itt.com, 2009.
  296. 296.0 296.1 Digger, Davis. "JSF Range & Airspace Requirements." Headquarters Air Combat Command, Defense Technical Information Center, 30 October 2007.
  297. 297.0 297.1 Bolsøy, Bjørnar. "F-35 Lightning II status and future prospects." f-16.net, 17 September 2009. Retrieved 23 November 2009.
  298. 298.0 298.1 Lua error in package.lua at line 80: module 'strict' not found.
  299. Lua error in package.lua at line 80: module 'strict' not found.
  300. 300.0 300.1 Lake 2010, pp. 37–45.
  301. "F-35B STOVL Variant." Lockheed Martin. Retrieved 25 November 2010.
  302. "Small Diameter Bomb II – GBU-53/B." Defense Update. Retrieved 28 August 2010.
  303. Lua error in package.lua at line 80: module 'strict' not found.
  304. F-35B Internal Weapons Bay Can't Fit Required Load Of Small Diameter Bomb IIs – Insidedefense.com, 25 February 2015
  305. 305.0 305.1 Trimble, Stephen. "MBDA reveals clipped-fin Meteor for F-35." Archived 21 September 2010 at the Wayback Machine Flight International, 7 November 2010.
  306. "F-35 Lightning II News: ASRAAM Config Change For F-35." f-16.net, 4 March 2008.
  307. Tran, Pierre. "MBDA Shows Off ASRAAM." Defense News, 22 February 2008.
  308. "Important cooperative agreement with Lockheed Martin." Kongsberg Defence & Aerospace, 9 June 2009.
  309. Trimble, Stephen. "Raytheon gets DARPA boost for AMRAAM, HARM replacement." Archived 8 November 2010 at the Wayback Machine Flight International, 4 November 2010.
  310. Reed, John. "Minuteman III Follow-On Being Eyed, Nukes for JSF Delayed." DoD Buzz, 6 April 2011.
  311. Muradian, Vego. "The Future of the U.S. Nuclear Enterprise." Defense News, 14 October 2012.
  312. Lua error in package.lua at line 80: module 'strict' not found.
  313. Lua error in package.lua at line 80: module 'strict' not found.
  314. Lua error in package.lua at line 80: module 'strict' not found.
  315. Fulghum, David A. "Lasers being developed for F-35 and AC-130." Aviation Week and Space Technology, 8 July 2002.
  316. Morris, Jefferson. "Keeping cool a big challenge for JSF laser, Lockheed Martin says." Aerospace Daily, 26 September 2002.
  317. Fulghum, David A. "Lasers, HPM weapons near operational status." Aviation Week and Space Technology, 22 July 2002.
  318. Lockheed considering laser weapon concepts for F-35 – Flightglobal.com, 5 October 2015
  319. Lua error in package.lua at line 80: module 'strict' not found.
  320. USAF chief keeps sights on close air support mission – Flightglobal.com, 15 February 2015
  321. Long Road Ahead For Possible A-10 Follow-On – Aviationweek.com, 24 March 2015
  322. Lua error in package.lua at line 80: module 'strict' not found.
  323. "F-35 Joint Strike Fighter (JSF) Lightning II." GlobalSecurity.org. Retrieved 16 November 2010.
  324. "USAF FY00 activity on the JSF." Archived 23 July 2011 at the Wayback Machine U.S. Director, Operational Test & Evaluation. Retrieved: 17 l 2012.
  325. "F-35 Norwegian Executive Summary." Archived 12 October 2012 at the Wayback Machine Lockheed Martin, April 2008.
  326. Hehs, Eric. "JSF Diverterless Supersonic Inlet." Code One Magazine. Retrieved 28 December 2012.
  327. "Fast History: Lockheed's Diverterless Supersonic Inlet Testbed F-16" Archived 7 September 2013 at the Wayback Machine aviationintel.com, 13 January 2013
  328. Lua error in package.lua at line 80: module 'strict' not found.
  329. Clark, Colin. [1] Breaking Defense, 6 June 2014.
  330. Ralston, J; Heagy, J; et al. "Environmental/Noise Effects on UHF/VHF UWB SAR". dtic.mil, September 1998. Retrieved: 2 January 2015.
  331. Plopsky, Guy and Fabrizio Bozzato. "The F-35 vs. The VHF Threat." The Diplomat, 21 August 2014.
  332. F-35 – Beyond Stealth – Defense-Update.com, 14 June 2015
  333. Capaccio, Tony. "Lockheed Martin’s F-35 Fighter Jet Passes Initial Stealth Hurdle." Bloomberg News, 4 May 2011.
  334. Lua error in package.lua at line 80: module 'strict' not found.
  335. Brewer, Jeffrey and Shawn Meadows. "Survivability of the Next Strike Fighter", p. 23. Aircraft Survivability: Susceptibility Reduction via Joint Aircraft Survivability Program Office (JASPO), Summer 2006.
  336. 336.0 336.1 Alaimo, Carol Ann. "Noisy F-35 Still Without A Home." Arizona Daily Star, 30 November 2008. Retrieved 23 November 2009.
  337. Moore, Mona. "Val-P to sue the Air Force." Northwest Florida Daily News, 19 February 2009, Volume 63, Number 20, p. A1.
  338. Barlow, Kari C. "Val-p wants Okaloosa to reimburse F-35 legal fees." thedestinlog.com, 16 April 2010. Archived 5 April 2012 at the Wayback Machine
  339. Nicholson, Brendan. "Noise triggers legal bid to down jet fighter." The Australian, 12 April 2011.
  340. Perrett, Bradley. "F-35 May Need Thermal Management Changes." Aviation Week, 12 March 2009. Retrieved 23 November 2009.[dead link]
  341. "Joint Communications Release, JSF Program Office & Lockheed Martin. Subject: F-35 Acoustics Based on Edwards AFB Acoustics, Test." JSF Program Office & Lockheed Martin, April 2009. Retrieved 15 January 2011.
  342. Alaimo, Carol Ann. "Noisy F-35 could affect thousands, study finds." Arizona Daily Star, 13 June 2012.
  343. Lua error in package.lua at line 80: module 'strict' not found.
  344. F-35Bs No Louder than F/A-18 Super Hornets – Defensetech.org, 25 November 2014
  345. Lua error in package.lua at line 80: module 'strict' not found.
  346. Goebel, Greg. "The Lockheed Martin F-35 Joint Strike Fighter (JSF)." vectorsite.net. Retrieved 23 November 2009. Archived 22 June 2012 at the Wayback Machine
  347. Schutte, John. "Researchers fine-tune F-35 pilot-aircraft speech system." Archived 23 April 2016 at the Wayback Machine US Air Force, 10 October 2007.
  348. "Joint Helmet Mounted Cueing System." Boeing. Retrieved 23 November 2009.
  349. "VSI's Helmet Mounted Display System flies on Joint Strike Fighter." Rockwell Collins, 2007. Retrieved 8 June 2008. Archived 17 August 2011 at the Wayback Machine
  350. "Martin-Baker." Archived 21 October 2008 at the Wayback Machine JSF. Retrieved 23 November 2009.
  351. "JSF" Martin-Baker. Retrieved 23 November 2009.
  352. Lua error in package.lua at line 80: module 'strict' not found.
  353. Peladeau, Jean. "Pilots worry about F-35 oxygen system." QMI Agency, 11 May 2012.
  354. Bennett, John T. "F-22's Oxygen Issues Raise Questions About F-35." US News, 24 May 2012.
  355. Lua error in package.lua at line 80: module 'strict' not found.
  356. "APG-81 (F-35 Lightning II)." Northrop Grumman Electronic Systems. Retrieved 4 August 2007. Archived 23 January 2013 at the Wayback Machine
  357. "Lockheed Martin Missiles and Fire Control: Joint Strike Fighter Electro-Optical Targeting System." Lockheed Martin. Retrieved 11 April 2008. Archived 6 January 2009 at the Wayback Machine
  358. Scott, William B. "Sniper Targeting Pod Attacks From Long Standoff Ranges." Aviation Week, 3 October 2004. Retrieved 23 November 2009. Archived 15 April 2012 at the Wayback Machine
  359. Pappalardo, Joe. "How an F-35 Targets, Aims and Fires Without Being Seen."[dead link] Popular Mechanics, December 2009. Retrieved: 6 April 2010.
  360. Lua error in package.lua at line 80: module 'strict' not found.
  361. Lua error in package.lua at line 80: module 'strict' not found.
  362. Lockheed reveals Advanced EOTS targeting sensor for F-35 Block 4 – Flightglobal.com, 10 September 2015
  363. "JSF EW Suite." istockanalyst.com. Retrieved 23 November 2009.
  364. Lua error in package.lua at line 80: module 'strict' not found.
  365. ‘A God’s Eye View Of The Battlefield:’ Gen. Hostage On The F-35 – Breakingdefense.com, 6 June 2014
  366. Lua error in package.lua at line 80: module 'strict' not found.
  367. "Israel, US Negotiate $450 Million F-35I Avionic Enhancements." Defense Update, 27 July 2012.
  368. 368.0 368.1 Sherman, Ron. "F-35 Electronic Warfare Suite: More Than Self-Protection." aviationtoday.com, 1 July 2006. Retrieved 22 August 2010.
  369. Lua error in package.lua at line 80: module 'strict' not found.
  370. Lua error in package.lua at line 80: module 'strict' not found.
  371. 371.0 371.1 Lua error in package.lua at line 80: module 'strict' not found.
  372. Warwick, Graham. "Flight Tests Of Next F-35 Block Underway." Aviation Week, 12 June 2010. Retrieved 12 June 2010.[dead link]
  373. Cox, Bob. "Pentagon officials to meet to address F-35 program's problems." Star-Telegram, 21 November 2010. Archived 22 November 2010 at the Wayback Machine
  374. Reed, John. "Schwartz Concerned About F-35A Delays." DoD buzz, 23 November 2010.
  375. Sweetman, Bill. "More F-35B Delays, Software Schedule At Risk." Aviation Week, 13 January 2011.
  376. David A. Fulghum, Bill Sweetman, Bradley Perrett and Robert Wall. "Stealthy Chinese J-20 Vulnerable." Aviation Week, 14 January 2011.
  377. Fulghum, David. "New Plan: NGJ To Go Unmanned." Aviation Week, 25 January 2012.
  378. Lua error in package.lua at line 80: module 'strict' not found.
  379. Lua error in package.lua at line 80: module 'strict' not found.
  380. Pawlikowski On Air Force Offset Strategy: F-35s Flying Drone Fleets – Breakingdefense.com, 15 December 2014
  381. "F-35 Distributed Aperture System EO DAS." YouTube. Retrieved 23 November 2009.
  382. Lua error in package.lua at line 80: module 'strict' not found.
  383. Lua error in package.lua at line 80: module 'strict' not found.
  384. 384.0 384.1 "JSF: the first complete ‘OODA Loop’ aircraft." Australian Defence Business Review, December 2006, p. 23.
  385. Warwick, Graham. "Lockheed Weighs Alternate F-35 Helmet Display." Aviation Week, 21 April 2011.
  386. "Lockheed Martin Selects BAE Systems to Supply F-35 Joint Strike Fighter (JSF) Helmet Display Solution." BAE Systems, 10 October 2011.
  387. Szondy, David. "BAE Systems to provide new helmet display for F-35 pilots." Gizmag, 21 October 2011.
  388. Carey, Bill. "BAE Drives Dual Approach To Fixing F-35 Helmet Display Issues." AINonline . 15 February 2012.
  389. 389.0 389.1 Lua error in package.lua at line 80: module 'strict' not found.
  390. "Lockheed Martin Awards F-35 Contract." Zacks Investment Research, 17 November 2011.
  391. Jean, Grace V. "New Sensor Aims to Give F-35 Pilots a ‘Window Into the Night’." National Defense Magazine, August 2011.
  392. "Lockheed Cites Good Reports on Night Flights of F-35 Helmet." Reuters.com, 30 October 2012.
  393. Lua error in package.lua at line 80: module 'strict' not found.
  394. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  395. Lua error in package.lua at line 80: module 'strict' not found.
  396. "F-35, Maintenance and the Challenge of Service Standardization." Second Line of Defense, 9 June 2011.
  397. Hawkins, Dan. "F-35 maintenance training spawns USMC's first air FTD." USMC, 27 July 2012.
  398. Clark, Colin. "Why Lockheed Thinks F-35 Beats Boeing's F-18." Aol Defense, 3 November 2011.
  399. "US Air Force praises early performance of Lockheed Martin F-35."Flightglobal.com, 6 November 2012.
  400. Majumdar, Dave. "Stealth isn’t becoming obsolete anytime soon." Flight International, 30 November 2012. Retrieved 1 December 2012.
  401. Lua error in package.lua at line 80: module 'strict' not found.
  402. "Mighty F-35 Lightning II Engine Roars to Life." Lockheed Martin, 20 September 2006.
  403. "F-35 First Flight."[dead link] TeamJSF.com. Retrieved 10 October 2007.
  404. "News Breaks: F-35B Engages Stovl Mode." Aviation Week, 11 January 2010, p. 15.
  405. Wolf, Jim. "F-35 fighter makes first vertical landing." Reuters, 18 March 2010.
  406. Cavas, Christopher P. "F-35B STOVL fighter goes supersonic." Archived 14 July 2011 at the Wayback Machine Marine Corps Times, 15 June 2010.
  407. "X-planes". PBS: Nova transcript. Retrieved 9 January 2010.
  408. Majumdar, Dave. "Lockheed says it’s fixed key F-35B issue." Defense News, 10 January 2011.
  409. Lua error in package.lua at line 80: module 'strict' not found.
  410. Lua error in package.lua at line 80: module 'strict' not found.
  411. Sweetman, Bill. "Get out and fly." Defense Technology International, June 2009, pp. 43–44.
  412. 412.0 412.1 Cox, Bob. "Internal Pentagon memo predicts that F-35 testing won't be complete until 2016." Fort Worth Star Telegram, 1 March 2010.
  413. Capaccio, Tony. "Lockheed F-35 Purchases Delayed in Pentagon’s Fiscal 2011 Plan." Archived 10 January 2010 at the Wayback Machine Bloomberg BusinessWeek, 6 January 2010.
  414. Bennett, John T. "Carter: More U.S. Programs To Get JET Treatment." defensenews.com, 29 March 2010.
  415. Thompson, Loren B. "F-35 Cost Rise Is Speculative, But Progress Is Real." lexingtoninstitute.org, 12 March 2010.
  416. "Senate Armed Services Committee Holds Hearing on President Obama's Fiscal 2011 Budget Request for the F-35 Joint Strike Fighter Program." Congressional Record via startelegram.typepad.com, 11 March 2010.
  417. "USAF Disputes Navy F-35 Cost Projections." Aviation Week. Retrieved 3 July 2010.
  418. Grant, Greg "JSF Production "Turned The Corner." dodbuzz.com. Retrieved 15 April 2010.
  419. Rolfsen, Bruce. "Jobs to change with focus on irregular warfare." Army Times Publishing Company, 16 May 2010.
  420. Warwick, Graham. "In-flight Failure Halts F-35 Flight Tests." Av Leak, 11 March 2011.
  421. Cavas, Christopher P. "All F-35s Cleared To Resume Flight Tests."[dead link] DefenseNews, 25 March 2011.
  422. Branch, Ricardo, Army Sgt. "Northern Edge fields new radar system." Archived 27 October 2013 at the Wayback Machine Northern Edge Joint Information Bureau, 8 March 2012.
  423. Saiki, Lt. Col. Tracey. "Continued testing of F-35 JSF sensors a success at Northern Edge 2011." Af.mil. Retrieved 18 April 2012.
  424. Trimble, Stephen. "F-35 fleet grounded after electrical subsystem failure."[dead link] Flight International, 3 August 2011.
  425. Majumdar, Dave. "F-35s Grounded After Power Package Fails." Defense News, 3 August 2011.
  426. "Statement on JPO Reinstituting Ground Operations for the F-35 Program." Joint Strike Fighter Program Office, 10 August 2011.
  427. "F-35 Fleet Cleared For Ground Operations." Defense News, 10 August 2011.
  428. Lerman, David. "Air Force Lifts Flight Ban on Lockheed F-35 Fighter Jet." Bloomberg News, 18 August 2011.
  429. "Honeywell to test some F-35 parts after smoke incident." Reuters.
  430. "F-35 JSF Flight Test Update." Defense Tech, 4 November 2011.
  431. 431.0 431.1 Norris, Guy. "F-35A pushes to Mach 1.6." Aviation Week & Space Technology, 9 December 2011.
  432. F-35A Completes 3-Year Clean Wing Flutter Testing Program Lockheed press release, 11 February 2013
  433. "F-35B completes air start testing at Edwards AFB." Flight International, 4 September 2012.
  434. Majumdar, Dave. "F-35C Tailhook Design Blamed for Landing Issues." Defense News, 17 January 2012.
  435. Lua error in package.lua at line 80: module 'strict' not found.
  436. "F-35B completes first sea trials on USS Wasp." navair.navy. Retrieved: 17 July 2012.
  437. "F-35A releases first air-launched weapon." Flight International, 17 October 2012.
  438. "F-35A Completes First AIM-120 Amraam Internal Weapons Release." Lockheed Martin press release, 22 October 2012.
  439. "F-35C Lightning II Hits Weapons Testing Milestone." Globalsecurity.org, 30 November 2012.
  440. "F-35A Completes First In-Flight Missile Launch". Lockheed Martin, 7 June 2013.
  441. Majumdar, Dave. "MCAS Yuma receives(sic) first operational F-35B." Flight International, 17 November 2012.
  442. Time magazine, 25 February 2013, pp. 26–30, "The Most Expensive Weapon Ever Built", by Mark Thompson; restriction on vertical landings cited on page 28.
  443. "F-35B Completes First Vertical Takeoff". Lockheed Martin, 20 May 2013.
  444. Lua error in package.lua at line 80: module 'strict' not found.
  445. Lua error in package.lua at line 80: module 'strict' not found.
  446. Lua error in package.lua at line 80: module 'strict' not found.
  447. Lua error in package.lua at line 80: module 'strict' not found.
  448. Lua error in package.lua at line 80: module 'strict' not found.
  449. Lua error in package.lua at line 80: module 'strict' not found.
  450. Mount, Mike. "Military Clears F-35 Joint Strike Fighter to Fly". CNN, 1 March 2013.
  451. "F-35s cleared to resume flight operations". Flight International, 28 February 2013.
  452. Lua error in package.lua at line 80: module 'strict' not found.
  453. Lua error in package.lua at line 80: module 'strict' not found.
  454. Lua error in package.lua at line 80: module 'strict' not found.
  455. Lua error in package.lua at line 80: module 'strict' not found.
  456. Lua error in package.lua at line 80: module 'strict' not found.
  457. Lua error in package.lua at line 80: module 'strict' not found.
  458. Lua error in package.lua at line 80: module 'strict' not found.
  459. Schwellenbach, Nick. "Concerns Regarding Plans for the Joint Strike Fighter to Begin Training Flights and Conduct an Operational Utility Evaluation." POGO, 31 October 2011. Archived 30 October 2012 at the Wayback Machine
  460. "U.S. Senators Press Panetta to Review F-35 Training Safety." Archived 13 January 2012 at the Wayback Machine Bloomberg News, 9 December 2011.
  461. Capaccio, Tony. "Air Force Expands F-35 Trials Over Tester’s Objections." Bloomberg BusinessWeek, 28 September 2012.
  462. Shalal-Esa, Andrea. "USMC Near Start Of F-35 Training Flights." Aviation Week. 27 February 2012.[dead link]
  463. "Air Force issues flight release for Eglin AFB F-35A" www.af.mil. 28 February 2012. Retrieved 5 May 2012
  464. Majumdar, Dave. "First Air National Guard pilot starts transition to F-35." Flight Magazine, 17 July 2012.
  465. "Eglin F-35s fly 200th sortie." Flight International, 24 August 2012.
  466. "Pentagon's Testing Czar Questions F-35 Program's OTE Plan." Aol Defense, 28 August 2012.
  467. Shalal-Esa, Andrea. "More problems raised at Pentagon F-35 fighter review." Reuters, 10 September 2012.
  468. Majumdar, Dave. "USAF to start F-35 operational utility evaluation on 10 September." Flight International, 7 September 2012.
  469. Majumdar, Dave. "F-35 operational utility evaluation proceeding smoothly." Flightglobal.com, 1 October 2012.
  470. Lua error in package.lua at line 80: module 'strict' not found.
  471. Majumdar, Dave. "Simulation plays vital role in building F-35 tactics and aircraft development." Flight International, 21 November 2012.
  472. Majumdar, Dave. "US Air Force praises early performance of Lockheed Martin F-35." Flight International, 6 November 2012.
  473. "F-35 pilot training starts next month at Eglin>" Militarytimes.com, 17 December 2012.
  474. 474.0 474.1 Lua error in package.lua at line 80: module 'strict' not found.
  475. 475.0 475.1 Lua error in package.lua at line 80: module 'strict' not found.
  476. 476.0 476.1 Lua error in package.lua at line 80: module 'strict' not found.
  477. 477.0 477.1 Lua error in package.lua at line 80: module 'strict' not found.
  478. Lua error in package.lua at line 80: module 'strict' not found.
  479. "Pentagon: F-35 Will Not Go to Farnborough". Defense News
  480. Lua error in package.lua at line 80: module 'strict' not found.
  481. "Military plans to send jets to S.C., N.C., Calif., Ariz." The Associated Press, 9 December 2010, Susanne M. Schafer.
  482. 482.0 482.1 482.2 Daniel, Lisa. "Plan Improves Navy, Marine Corps Air Capabilities." Archived 29 May 2011 at the Wayback Machine American Forces Press Service, 14 March 2011.
  483. 483.0 483.1 483.2 Cavas, Christopher P. "More Marines to fly carrier-variant JSFs." Archived 28 April 2011 at the Wayback Machine Marine Corps Times, 14 March 2011.
  484. Lua error in package.lua at line 80: module 'strict' not found.
  485. Lua error in package.lua at line 80: module 'strict' not found.
  486. Lua error in package.lua at line 80: module 'strict' not found.
  487. "RAF Lakenheath was selected as the first base to host USAFE F-35s." The Aviationist, Retrieved January 13, 2015.
  488. "F-35 Joint Strike Fighter (JSF) Lightning II – International Partners." Global Security. Retrieved 7 April 2010.
  489. Merle, Renae. "GAO Questions Cost Of Joint Strike Fighter." The Washington Post, 15 March 2005.
  490. "Estimated JSF Air Vehicle Procurement Quantities." JSF.mil, Updated as of April 2010.
  491. Tae-hoon, Lee. "Seoul fears delivery delays of F-35 jets." The Korea Times, 6 March 2012.
  492. "F-35 Lightning: The Joint Strike Fighter Program, 2012." Defense Industry Daily, 30 October 2012.
  493. "JSF Global Partners." Archived 4 October 2007 at the Wayback Machine teamjsf.com. Retrieved 30 March 2007.
  494. "US, UK sign JAST agreement." Aerospace Daily New York: McGraw-Hill, 25 November 1995, p. 451.
  495. Schnasi, Katherine V. "Joint Strike Fighter Acquisition: Observations on the Supplier Base." US Accounts Office. Retrieved 8 February 2006.
  496. "Industry Canada F-35 Joint Strike Fighter (JSF) Canada's Next Generation Fighter Capability." Archived 22 September 2010 at the Wayback Machine ic.gc.ca. Retrieved 25 November 2010.
  497. Combat Aircraft Monthly, September 2010, p. 24.
  498. "US Lockheed Martin F-35 chosen as Japan fighter jet." BBC News, 20 December 2011. Retrieved: 20 December 2011.
  499. "Update 1-Turkey keeps plan to buy 100 F-35 fighter jets." Reuters, 23 February 2012.
  500. "Turkey plans to buy 100 F-35 jet fighters." Archived 21 May 2012 at the Wayback Machine turkishpress.com, 24 February 2012.
  501. "Turkey to Buy Two Planes in Second F-35 Shipment." turkishweekly.net, 4 September 2012.
  502. Harper, Tim. "Tim Harper: The Conservatives and their F-35 fairy tale." Toronto Star, 14 February 2012.
  503. Vasarri, Chiara. "Italy to Cut F-35 Fighter Jet Orders as Part of Defense Revamp." Bloomberg Business Week, 14 February 2012.
  504. Postmedia News. "A timeline on Canada's involvement in the F-35 program." Archived 10 April 2012 at the Wayback Machine Canada.com, 5 April 2012.
  505. "Video: MPs hold Mackay to account in F-35 scandal." The Canadian Press via Globe and Mail, 4 April 2012.
  506. Coyne, Andrew. "Peeling back the layers of misconduct in the F-35 fiasco." Archived 4 January 2013 at archive.today National Post, 4 April 2012.
  507. "The F-35 Fiasco." CBC News, 5 April 2012.
  508. Stewart, Brian. "Super-costly F-35s, a global wrecking ball." Canadian Broadcasting Corporation, 13 December 2012.
  509. Lua error in package.lua at line 80: module 'strict' not found.
  510. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  511. Lua error in package.lua at line 80: module 'strict' not found.
  512. 512.0 512.1 512.2 512.3 F-35 LRIP-4 Costs Detailed DoDBuzz.com 17 Dec 2010
  513. 513.0 513.1 «F-35 LRIP overrun value raised to $1.15b» Archived 3 September 2011 at the Wayback Machine flightglobal.com 15 July 2011
  514. aviationweek.com: Latest F-35 Deal Targets Unit Cost Below $100 Million Archived 24 April 2014 at the Wayback Machine aviationweek.com, 7 July 2013
  515. Pentagon cuts cost of F-35 fighters by 4 percent: sources 4-traders.com, 12 Dec 2012
  516. 516.0 516.1 f35.com: LRIP 6 & 7 Contract Agreements f35.com, 27 September 2013
  517. "Lockheed, Pentagon ink $4.7 billion deal for eighth batch of F-35 fighters". Reuters, 21 November 2014.
  518. Lua error in package.lua at line 80: module 'strict' not found.
  519. 519.0 519.1 519.2 F-35 Program Information – Non Export Controlled Information Keith P. Knotts, 9 July 2013
  520. Lua error in package.lua at line 80: module 'strict' not found.
  521. Lua error in package.lua at line 80: module 'strict' not found.
  522. http://www.airforce-technology.com/news/newslockheed-wins-13bn-lrip-11-contract-for-f-35-lightning-ii-aircraft-4882949
  523. Pentagon Approves Lockheed F-35 for Continued Development Tony Capaccio for Bloomberg 29 March 2012
  524. Pike, John. "F-35A Joint Strike Fighter." Globalsecurity.org. Retrieved 23 November 2009.
  525. "Flying The F-35: An Interview With Jon Beesley, F-35 Chief Test Pilot." lockheedmartin.com. Retrieved 25 November 2010.[dead link]
  526. Hebert, Adam J. "Lightning II: So Far, So Good." Archived 21 February 2009 at the Wayback Machine airforce-magazine.com, Air Force Association, Volume 90, Issue 7, July 2007. Retrieved 3 December 2008.
  527. Laurenzo, Ron. "Air Force: No Plan To Retire A-10." GlobalSecurity.org, Defense Weekly, 9 June 2003. Retrieved 3 December 2008.
  528. Waldron, Greg. "IN FOCUS: Tokyo casts wary eye on Chinese airpower developments." Flight International, 2 August 2012.
  529. "F-35s face communication problems in Arctic." The Canadian Press, 23 October 2011.
  530. Ewing, Philip. "Lockheed’s comprehensive Q&A on the F-35." DoD Buzz, 19 June 2012.
  531. Lua error in package.lua at line 80: module 'strict' not found.
  532. Lua error in package.lua at line 80: module 'strict' not found.
  533. Lua error in package.lua at line 80: module 'strict' not found.
  534. 534.0 534.1 Lua error in package.lua at line 80: module 'strict' not found.
  535. Lua error in package.lua at line 80: module 'strict' not found.
  536. Lua error in package.lua at line 80: module 'strict' not found.
  537. Hancock, Ben D. "The STOVL Joint Strike Fighter in Support of the 21st Century Marine Corps." USMC, 1997.
  538. Lua error in package.lua at line 80: module 'strict' not found.
  539. Sweetman, Bill. "Numbers Crunch: True cost of JSF program remains to be seen." Defense Technology International, February 2009, p. 22.
  540. "F-35 HMDS Pulls the Gs". Defense Industry Daily, 25 October 2007.
  541. Norris, Guy. "Pilot reaction to flying the F-35B" Aviation Week & Space Technology, 24 April 2014. Accessed: 15 September 2014. Archived on 27 September 2014
  542. Norris, Guy and Graham Warwick. "F-35B First Flight Boosts JSF as F-22 Loses Supporters." Aviation Week, 15 June 2008.
  543. Lua error in package.lua at line 80: module 'strict' not found.
  544. "F-35B STOVL-mode Flight." defenceaviation.com. Retrieved 25 November 2010.
  545. Lua error in package.lua at line 80: module 'strict' not found.
  546. "Custom tool to save weeks in F-35B test and evaluation." Naval Air Systems Command, 6 May 2011.
  547. Lua error in package.lua at line 80: module 'strict' not found.
  548. Lua error in package.lua at line 80: module 'strict' not found.
  549. Diamant, Aaron. "JSF construction lands another first." USMC, 22 December 2011.
  550. Majumdar, Dave. "U.S. Military May Deploy F-35 Before Formal IOC." Defense News, 24 May 2011.
  551. Majumdar, Dave. "USAF: F-35B cannot generate enough sorties to replace A-10." Flight Magazine, 16 May 2012.
  552. Pew, Glenn. "Pentagon May Cancel STOVL Version of F-35." AvWeb, January 2011.
  553. Cox, Bob. "F-35 started with recipe for trouble, analysts say." Star Telegram, 29 January 2011.
  554. Ewing, Philip. "Lockheed: Many F-35B landings won’t be vertical." DoD Buzz, 7 June 2011.
  555. Lua error in package.lua at line 80: module 'strict' not found.
  556. Lua error in package.lua at line 80: module 'strict' not found.
  557. Trimble, Stephen. "VIDEO: F-35B completes first shipboard vertical landing." The DEWline, 4 October 2011.
  558. Lua error in package.lua at line 80: module 'strict' not found.
  559. Lua error in package.lua at line 80: module 'strict' not found.
  560. "Major Projects Report 2008." Ministry of Defence. Retrieved 23 November 2009. Archived 7 August 2012 at the Wayback Machine
  561. "US Marines eye UK JSF shipborne technique."[dead link] Flight International, 15 June 2007.
  562. Lua error in package.lua at line 80: module 'strict' not found.
  563. Lua error in package.lua at line 80: module 'strict' not found.
  564. Lua error in package.lua at line 80: module 'strict' not found.
  565. Lua error in package.lua at line 80: module 'strict' not found.
  566. Lua error in package.lua at line 80: module 'strict' not found.
  567. Lua error in package.lua at line 80: module 'strict' not found.
  568. Lua error in package.lua at line 80: module 'strict' not found.
  569. "F-35B on Italian "Cavour" aircraft carrier." Military-today.com, 4 December 2011.
  570. Kovach, Gretel C. "Commandant calls Joint Strike Fighter essential." U-T San Diego, 8 December 2010.
  571. Jean, Grace V. "Marines Question the Utility of Their New Amphibious Warship." National Defense Industrial Association, September 2008.
  572. Lua error in package.lua at line 80: module 'strict' not found.
  573. Lua error in package.lua at line 80: module 'strict' not found.
  574. Lua error in package.lua at line 80: module 'strict' not found.
  575. Lua error in package.lua at line 80: module 'strict' not found.
  576. Lua error in package.lua at line 80: module 'strict' not found.
  577. Lua error in package.lua at line 80: module 'strict' not found.
  578. Lua error in package.lua at line 80: module 'strict' not found.
  579. Lua error in package.lua at line 80: module 'strict' not found.
  580. Lua error in package.lua at line 80: module 'strict' not found.
  581. Marines Propose Rapidly Mobile F-35 Operations – Aviationweek.com, 16 December 2014
  582. "F-35C Carrier Variant Joint Strike Fighter (JSF)." GlobalSecurity.org. Retrieved 16 June 2010.
  583. "F-35 Navy Version Undergoes Successful Design Review, Readies for Production." Lockheed Martin, 7 June 2007. Retrieved 16 June 2010.
  584. Grant, Rebecca L., PhD "Navy Speeds Up F-35." Lexington Institute, 14 September 2009. Retrieved 20 September 2009.
  585. "F-35C Lightning II rolled out." Archived 31 July 2009 at the Wayback Machine FrontierIndia.net, 29 July 2009.
  586. Lua error in package.lua at line 80: module 'strict' not found.
  587. "JSF Engine too big for regular transport at sea." Navy Times, 30 November 2010.
  588. Cavas, Christopher P. "U.S. Navy JSFs Resume Flight Ops After Glitch." Defense News, 24 June 2011.
  589. "Catapult launches F-35C for the first time." Naval Air Systems Command, 27 July 2011. Retrieved 31 December 2011 Archived 17 October 2014 at the Wayback Machine
  590. "F-35C completes jet blast deflector testing." NAVAIR, 22 August 2011. Retrieved 23 August 2011. Archived 18 December 2014 at the Wayback Machine
  591. Ewing, Philip. "The future is here: EMALS launches F-35." DODbuzz.com, 28 November 2011.
  592. Lua error in package.lua at line 80: module 'strict' not found.
  593. Lua error in package.lua at line 80: module 'strict' not found.
  594. Majumdar, Dave. "US Navy works through F-35C air-ship integration issues." Flight International, 1 October 2012.
  595. Lua error in package.lua at line 80: module 'strict' not found.
  596. Lua error in package.lua at line 80: module 'strict' not found.
  597. Lua error in package.lua at line 80: module 'strict' not found.
  598. Lua error in package.lua at line 80: module 'strict' not found.
  599. Lua error in package.lua at line 80: module 'strict' not found.
  600. Lua error in package.lua at line 80: module 'strict' not found.
  601. Lua error in package.lua at line 80: module 'strict' not found.
  602. Ben-David, Alon. "Israel To Buy F-35s With Cockpit Mods." Aviation Week, 27 August 2010.[dead link]
  603. Ben-David, Alon, Amy Butler and Robert Wall. "Israel, U.S. Strike F-35 Technology Deal." Aviation Week, 7 July 2011. Retrieved 8 October 2011.[dead link]
  604. Trimble, Stephen. "Israel sets sights on two-seater F-35." Flight International, 22 January 2010.
  605. Egozi, Arie. "Israel to boost range of future F-35 fleet." Flight International. 11 January 2008.
  606. "Israel, U.S. Agree To $450 Million In F-35 EW Work." Archived 10 May 2013 at the Wayback Machine Aviation Week, 6 August 2012.
  607. Lua error in package.lua at line 80: module 'strict' not found.
  608. Lua error in package.lua at line 80: module 'strict' not found.
  609. Lua error in package.lua at line 80: module 'strict' not found.
  610. Lua error in package.lua at line 80: module 'strict' not found.
  611. Lua error in package.lua at line 80: module 'strict' not found.
  612. Lua error in package.lua at line 80: module 'strict' not found.
  613. Lua error in package.lua at line 80: module 'strict' not found.
  614. Lua error in package.lua at line 80: module 'strict' not found.
  615. Lua error in package.lua at line 80: module 'strict' not found.
  616. Lua error in package.lua at line 80: module 'strict' not found.
  617. Lua error in package.lua at line 80: module 'strict' not found.
  618. Lua error in package.lua at line 80: module 'strict' not found.
  619. Lua error in package.lua at line 80: module 'strict' not found.
  620. Lua error in package.lua at line 80: module 'strict' not found.
  621. WATCH: THREE NEW F-35 FIGHTER JETS LAND IN ISRAEL BY ANNA AHRONHEIM, Jerusalem Post, APRIL 23, 2017
  622. Lua error in package.lua at line 80: module 'strict' not found.
  623. Lua error in package.lua at line 80: module 'strict' not found.
  624. Israel ups stealth fighter purchase to 50 planes Arutz Sheva Staff, 27/11/16
  625. Italy Takes Delivery of First F-35, defensenews.com. Retrieved 03 February 2015.
  626. Italy Plans First F-35 Flight in October, defensenews.com. Retrieved 7 April 2016.
  627. Italy claims first F-35 transatlantic crossing, Flightglobal. Retrieved 7 April 2016.
  628. 628.0 628.1 628.2 628.3 628.4 628.5 Lua error in package.lua at line 80: module 'strict' not found.
  629. Lua error in package.lua at line 80: module 'strict' not found.
  630. Lockheed Martin and Japan Celebrate Roll Out of Japan Air Self Defense Force’s First F-35A, retrieved 29 September 2016
  631. Lua error in package.lua at line 80: module 'strict' not found.
  632. Lua error in package.lua at line 80: module 'strict' not found.
  633. Lua error in package.lua at line 80: module 'strict' not found.
  634. Lua error in package.lua at line 80: module 'strict' not found.
  635. Lua error in package.lua at line 80: module 'strict' not found.
  636. Lua error in package.lua at line 80: module 'strict' not found.
  637. Lua error in package.lua at line 80: module 'strict' not found.
  638. BURAK EGE BEKDIL. "Turkey Orders First Two F-35s" DefenseNews, 7 May 2014. Accessed: 10 May 2014.
  639. 639.0 639.1 639.2 Lua error in package.lua at line 80: module 'strict' not found.
  640. Lua error in package.lua at line 80: module 'strict' not found.
  641. Lua error in package.lua at line 80: module 'strict' not found.
  642. Lua error in package.lua at line 80: module 'strict' not found.
  643. Lua error in package.lua at line 80: module 'strict' not found.
  644. Lua error in package.lua at line 80: module 'strict' not found.
  645. Lua error in package.lua at line 80: module 'strict' not found.
  646. Lua error in package.lua at line 80: module 'strict' not found.
  647. Lua error in package.lua at line 80: module 'strict' not found.
  648. 648.0 648.1 Italian AF, Navy Head for F-35B Showdown Archived 11 February 2015 at archive.today, defensenews.com. Retrieved 10 February 2015.
  649. Joint Strike Fighter Aircraft:Written question – HL2709. Retrieved 24 November 2015.
  650. Lua error in package.lua at line 80: module 'strict' not found.
  651. Prince of Wales aircraft carrier ‘makes little sense’ without aircraft to fly from it, The Guardian. Retrieved 24 November 2015.
  652. 652.0 652.1 Lua error in package.lua at line 80: module 'strict' not found.
  653. Defence Review: Fighting old battles?, BBC News. Retrieved 24 November 2015.
  654. Lua error in package.lua at line 80: module 'strict' not found.
  655. Lua error in package.lua at line 80: module 'strict' not found.
  656. Lua error in package.lua at line 80: module 'strict' not found.
  657. 657.0 657.1 657.2 657.3 657.4 657.5 Lua error in package.lua at line 80: module 'strict' not found.
  658. 'Immortal’ air squadron to fly Royal Navy’s newest jets, royalnavy.mod.uk. Retrieved 31 May 2015.
  659. Lua error in package.lua at line 80: module 'strict' not found.
  660. Lua error in package.lua at line 80: module 'strict' not found.
  661. Lua error in package.lua at line 80: module 'strict' not found.
  662. Lua error in package.lua at line 80: module 'strict' not found.
  663. Lua error in package.lua at line 80: module 'strict' not found.
  664. Lua error in package.lua at line 80: module 'strict' not found.
  665. Lua error in package.lua at line 80: module 'strict' not found.
  666. Lua error in package.lua at line 80: module 'strict' not found.
  667. Lua error in package.lua at line 80: module 'strict' not found.
  668. Lua error in package.lua at line 80: module 'strict' not found.
  669. https://www.dvidshub.net/news/221416/first-pacific-based-f-35c-fighters-arrive-nas-lemoore
  670. Lua error in package.lua at line 80: module 'strict' not found.
  671. Lua error in package.lua at line 80: module 'strict' not found.
  672. Lua error in package.lua at line 80: module 'strict' not found.
  673. "F-35B Short Takeoff/Vertical Landing Variant." Lockheed Martin. Retrieved 13 July 2012.
  674. "F-35C Carrier Variant." Lockheed Martin. Retrieved 13 July 2012.
  675. "F-35 Lightning II Program Status and Fast Facts." Lockheed Martin, 13 March 2012. Retrieved 22 May 2012. Archived 24 May 2013 at the Wayback Machine
  676. 676.0 676.1 Lua error in package.lua at line 80: module 'strict' not found.
  677. Lua error in package.lua at line 80: module 'strict' not found.
  678. "F-35 variants." JSF. Retrieved 22 August 2010.
  679. 679.0 679.1 "The Pratt & Whitney F135". Jane's Aero Engines. Jane's Information Group, 2009. (subscription version, dated 10 July 2009).
  680. "Lockheed Martin F-35 Lightning II". Jane's All the World's Aircraft. Jane's Information Group, 2010. (subscription article, dated 1 February 2010).
  681. Lua error in package.lua at line 80: module 'strict' not found.
  682. [2]. Selected Acquisition Report (SAR)
  683. [3]. Lockheed Martin. Retrieved 31 March 2016.
  684. "ATK Awarded $55 Million Advanced Anti-Radiation Guided Missile Low Rate Initial Production ..." Archived 23 June 2013 at the Wayback Machine Reuters, 21 January 2009. Retrieved: 13 July 2011.
  685. Dupont, Jean and Conal Walker. "MBDA Launches SPEAR High Precision Surface Attack Weapon During Farnborough 2012." MBDA, 9 July 2012.
  686. Ewing, Philip. "The Navy’s advanced weapons shopping list". Military.com, 3 July 2012.
  687. "Nuclear Posture Review Report." Archived 7 December 2014 at the Wayback Machine Department of Defense, Washington, D.C., April 2010. Retrieved: 7 April 2010.
  688. [4] Northrop Gurmman
  689. Lua error in package.lua at line 80: module 'strict' not found.

Bibliography

External links