This is a good article. Click here for more information.

Saab JAS 39 Gripen

From Infogalactic: the planetary knowledge core
(Redirected from Gripen NG)
Jump to: navigation, search
JAS 39 Gripen
Grey fighter aircraft banking right, showing its top view, against a light-blue sky
Swedish Air Force JAS 39 Gripen
Role Fighter, attack and reconnaissance aircraft
Manufacturer Saab Group
Design group Industrigruppen JAS, FMV
First flight 9 December 1988
Introduction 1 November 1997
Status In service
Primary users Swedish Air Force
South African Air Force
Czech Air Force
Hungarian Air Force
Produced 1987–present
Number built Approx. 247[Nb 1]
Program cost US$ 13.54 billion (2006)[Nb 2]
Unit cost
US$ 68.90 million (2006)[1][Nb 3]

The Saab JAS 39 Gripen (English: "griffin"[Nb 4][3]) is a light single-engine multirole fighter aircraft manufactured by the Swedish aerospace company Saab. It was designed to replace the Saab 35 Draken and 37 Viggen in the Swedish Air Force (Flygvapnet). The Gripen has a delta wing and canard configuration with relaxed stability design and fly-by-wire flight controls. It is powered by the Volvo RM12, and has a top speed of Mach 2. Later aircraft are modified for NATO interoperability standards and to undertake in-flight refuelling.

In 1979, the Swedish government began development studies for an aircraft capable of fighter, attack and reconnaissance missions to replace the Saab 35 Draken and 37 Viggen. A new design from Saab was selected and developed as the JAS 39, first flying in 1988. Following two crashes during flight development and subsequent alterations to the aircraft's flight control software, the Gripen entered service with the Swedish Air Force in 1997. Upgraded variants, featuring more advanced avionics and adaptations for longer mission times, began entering service in 2003.

In order to market the aircraft to export customers, Saab has formed several partnerships and collaborative efforts with multiple overseas aerospace companies. One example of such efforts was Gripen International, a joint partnership between Saab and BAE Systems formed in 2001. Gripen International was responsible for marketing the aircraft, and was heavily involved in the successful export of the type to South Africa; the organization was later dissolved amidst allegations of bribery being employed to secure foreign interest and sales. On the export market, the Gripen has achieved moderate success in sales to nations in Central Europe, South Africa and Southeast Asia; bribes have been reportedly involved in some of these procurements.[4]

A further version, designated Gripen JAS 39E/F, is under development as of 2014; it has been referred to as Gripen NG or Super-JAS.[5] The changes include the adoption of a new powerplant, the General Electric F414G, an active electronically scanned array radar, and significantly increased internal fuel capacity. Saab has proposed other derivatives, including a navalised Sea Gripen for carrier operations and an optionally manned aircraft for unmanned operations. Sweden and Brazil have ordered the Gripen E/F and Switzerland initially selected it for procurement. As of 2013, more than 247 Gripens have been built.[Nb 1]

Development

Origins

In the late 1970s, Sweden sought to replace its ageing Saab 35 Draken and Saab 37 Viggen.[7] The Swedish Air Force required an affordable Mach 2 aircraft with good short-field performance for a defensive dispersed basing plan in the event of invasion; the plan included 800 m long by 9 m wide rudimentary runways as stated in the Base 90 directives.[8] One goal was for the aircraft to be smaller than the Viggen while equalling or improving on its payload-range characteristics.[9] Early proposals included the Saab 38, also called B3LA, intended as an attack aircraft and trainer,[10] and the A 20, a development of the Viggen that would have capabilities as a fighter, attack and sea reconnaissance aircraft.[11] Several foreign designs were also studied, including the General Dynamics F-16 Fighting Falcon, the McDonnell Douglas F/A-18 Hornet,[12] the Northrop F-20 Tigershark and the Dassault Mirage 2000.[13] Ultimately, the Swedish government opted for a new fighter to be developed by Saab (Svenska Aeroplan Aktiebolag).[12]

In 1979, the government began a study calling for a versatile platform capable of "JAS", standing for Jakt (air-to-air), Attack (air-to-surface), and Spaning (reconnaissance), indicating a multirole, or swingrole, fighter aircraft that can fulfill multiple roles during the same mission.[12] Several Saab designs were reviewed, the most promising being "Project 2105" (redesignated "Project 2108" and, later, "Project 2110"), recommended to the government by the Defence Materiel Administration (Försvarets Materielverk, or FMV).[12] In 1980, Industrigruppen JAS (IG JAS, "JAS Industry Group") was established as a joint venture by Saab-Scania, LM Ericsson, Svenska Radioaktiebolaget, Volvo Flygmotor and Försvarets Fabriksverk, the industrial arm of the Swedish armed forces.[14]

The preferred aircraft was a single-engine, lightweight single-seater, embracing fly-by-wire technology, canards, and an aerodynamically unstable design.[15] The powerplant selected was the Volvo-Flygmotor RM12, a license-built derivative of the General Electric F404-400; engine development priorities were weight reduction and lowering component count.[15][16] On 30 June 1982, with approval from the Riksdag,[17] the FMV issued contracts worth SEK 25.7 billion to Saab, covering five prototypes and an initial batch of 30 production aircraft.[18][19] By January 1983, a Viggen was converted to a flying test aircraft for the JAS 39's intended avionics, such as the fly-by-wire controls.[20] The JAS 39 received the name Gripen (griffin) via a public competition,[21] which is the heraldry on Saab's logo.[Nb 5]

Testing, production and improvements

External video
video icon Ground footage of the 1989 Gripen crash

The first Gripen was rolled out on 26 April 1987, marking Saab's 50th anniversary.[24] Originally planned to fly in 1987,[16] the first flight was delayed by 18 months due to issues with the flight control system. On 9 December 1988, the first prototype (serial number 39-1) took its 51-minute maiden flight with pilot Stig Holmström at the controls.[15][25] During the test programme, concern surfaced about the aircraft's avionics, specifically the fly-by-wire flight control system (FCS), and the relaxed stability design. On 2 February 1989, this issue led to the crash of the prototype during an attempted landing at Linköping; the test pilot Lars Rådeström walked away with a broken elbow. The cause of the crash was identified as pilot-induced oscillation, caused by problems with the FCS's pitch-control routine.[15][26][27]

In response to the crash Saab and US firm Calspan introduced software modifications to the aircraft. A modified Lockheed NT-33A was used to test these improvements, which allowed flight testing to resume 15 months after the accident. On 8 August 1993, production aircraft 39102 was destroyed in an accident during an aerial display in Stockholm. Test pilot Rådeström lost control of the aircraft during a roll at low altitude when the aircraft stalled, forcing him to eject. Saab later found the problem to be high amplification of the pilot's quick and significant stick command inputs. The ensuing investigation and flaw correction delayed test flying by several months, resuming in December 1993.[15]

The first order included an option for another 110, which was exercised in June 1992. Batch II consisted of 96 one-seat JAS 39As and 14 two-seat JAS 39Bs.[28][29] The JAS 39B variant is 66 cm (26 in) longer than the JAS 39A to accommodate a second seat, which also necessitated the deletion of the cannon and a reduced internal fuel capacity.[30] By April 1994, five prototypes and two series-production Gripens had been completed; but a beyond-visual-range missile (BVR) had not yet been selected.[31] A third batch was ordered in June 1997, composed of 50 upgraded single-seat JAS 39Cs and 14 JAS 39D two-seaters,[30] known as 'Turbo Gripen', with NATO compatibility for exports.[32] Batch III aircraft, delivered between 2002 and 2008, possess more powerful and updated avionics, in-flight refuelling capability via retractable probes on the aircraft's starboard side, and an on-board oxygen-generating system for longer missions.[33] In-flight refueling was tested via a specially equipped prototype (39‐4) used in successful trials with a Royal Air Force VC10 in 1998.[30]

Teaming agreements

Head on view of fighter jet banking right while releasing flares against a background of green woodland.
Czech Gripen deploying defensive flares, 2011

During the 1995 Paris Air Show, Saab Military Aircraft and British Aerospace (BAe, now BAE Systems) announced the formation the joint-venture company Saab-BAe Gripen AB with the goal of adapting, manufacturing, marketing and supporting Gripen worldwide.[30][34] The deal involved the conversion of the A and B series aircraft to the "export" C and D series, which developed the Gripen for compatibility with NATO standards.[35] This cooperation was extended in 2001 with the formation of Gripen International to promote export sales.[36] In December 2004, Saab and BAE Systems announced that BAE was to sell a large portion of its stake in Saab, and that Saab would take full responsibility for marketing and export orders of the Gripen.[37] In June 2011, Saab announced that an internal investigation revealed evidence of acts of corruption by BAE Systems, including money laundering, in South Africa, one of the Gripen's customers.[38]

On 26 April 2007, Norway signed a NOK150 million joint-development agreement with Saab to cooperate in the development programme of the Gripen, including the integration of Norwegian industries in the development of future versions of the aircraft.[39] In June of the same year, Saab also entered an agreement with Thales Norway A/S concerning the development of communications systems for the Gripen fighter; this order was the first to be awarded under the provisions of the Letter of Agreement signed by the Norwegian Ministry of Defence and Gripen International in April 2007.[39] As a result of the United States diplomatic cables leak in 2010, it was revealed that US diplomats had become concerned with cooperation between Norway and Sweden on the topic of the Gripen, and had sought to exert pressure against a Norwegian purchase of the aircraft.[40]

In December 2007, as part of Gripen International's marketing efforts in Denmark, a deal was signed with Danish technology supplier Terma A/S which allows them to participate in an industrial cooperation programme over the next 10–15 years. The total value of the programme is estimated at over DKK10 billion, and is partly dependent on a procurement of the Gripen by Denmark.[41]

Controversies, scandals, and costs

Developing an advanced multi-role fighter was a major undertaking for Sweden. The predecessor Viggen, despite being less advanced and less expensive, had been criticized for occupying too much of Sweden's military budget and was branded "a cuckoo in the military nest" by critics as early as 1971. At the 1972 party congress of the Social Democrats, the dominant party in Swedish politics since the 1950s, a motion was passed to stop any future projects to develop advanced military aircraft.[42] In 1982, the Gripen project passed in the Riksdag by a narrow of margin of 176 for and 167 against, with the entire Social Democratic voting against the proposal due to demands for more studies. A new bill was introduced in 1983[43] and a final approval was given in April 1983 with the condition that the project was to have a predetermined fixed-price contract,[44] a decision that would later be criticized as unrealistic due to later cost overruns.[42]

According to Annika Brändström, in the aftermath of the 1989 and 1993 crashes, the Gripen risked a loss of credibility and the weakening of its public image. There was public speculation that failures to address technical problems exposed in the first crash had directly contributed to the second crash and thus had been avoidable.[45] Brändström observed that media elements had called for greater public accountability and explanation of the project; ill-informed media analysis had also distorted public knowledge of the Gripen.[46] The sitting Conservative government quickly endorsed and supported the Gripen – Minister of Defense Anders Björck issued a public reassurance that the project was very positive for Sweden.[47] In connection to the Gripen's marketing efforts to multiple countries, including South Africa, Austria, the Czech Republic and Hungary, there were reports of widespread bribery and corruption by BAE Systems and Saab.[48][49] In 2007, Swedish journalists reported that BAE had paid bribes equivalent to millions of dollars.[50][51][52] Following criminal investigations in eight countries, only one individual in Austria, Alfons Mensdorf-Pouilly, was prosecuted for bribery. The scandal tarnished the international reputation of the Gripen, BAE Systems, Saab, and Sweden.[49]

The Gripen's cost has been subject to frequent attention and speculation. In 2008, Saab announced reduced earnings for that year, partly attributing this to increased marketing costs for the aircraft.[53] In 2008, Saab disputed Norway's cost calculations for the Gripen NG as overestimated and in excess of real world performance with existing operators.[54] A 2007 report by the European Union Institute for Security Studies stated the total research and development costs of Gripen to be €1.84 billion.[55] According to a study by Jane's Information Group in 2012, the Gripen's operational cost was the lowest among several modern fighters; it was estimated at $4,700 per flight hour.[56] The Swedish Ministry of Defense estimated the cost of the full system, comprising 60 Gripen E/F, at SEK 90 billion distributed over the period 2013–42. The Swedish Armed Forces estimated that maintaining 100 C/D-model aircraft until 2042 would cost SEK 60 billion, while buying aircraft from a foreign supplier would cost SEK 110 billion.[57]

Further developments

 Three quarter view of grey jet fighter fitted with external fuel tanks on dirt-colored ground
Saab Gripen NG demonstrator at RIAT 2010

A two-seat aircraft, designated "Gripen Demo", was ordered in 2007 as a testbed for various upgrades.[58][59] It was powered by the General Electric F414G, a development of the Boeing F/A-18E/F Super Hornet's engine.[60] The Gripen NG's maximum take off weight was increased from 14,000 to 16,000 kg (30,900–35,300 lb), internal fuel capacity was increased by 40 per cent by relocating the undercarriage, which also allowed for two hardpoints to be added on the fuselage underside. Its combat radius was 1,300 kilometres (810 mi) when carrying six AAMs and drop tanks.[59][61] The PS-05/A radar is replaced by the new Raven ES-05[62] active electronically scanned array (AESA) radar, which is based on the Vixen AESA radar family from Selex ES.[63][64] The Gripen Demo's maiden flight was conducted on 27 May 2008.[65] On 21 January 2009, the Gripen Demo flew at Mach 1.2 without reheat to test its supercruise capability.[66] The Gripen Demo served as a basis for the Gripen E/F, also referred to as the Gripen NG (Next Generation) and MS (Material Standard) 21.[67][68]

Saab studied a variant of the Gripen capable of operating from aircraft carriers in the 1990s. In 2009, it launched the Sea Gripen project in response to India's request for information on a carrier-borne aircraft. Brazil may also require new carrier aircraft.[69][70] Following a meeting with Ministry of Defence (MoD) officials in May 2011, Saab agreed to establish a development center in the UK to expand on the Sea Gripen concept.[71] In 2013, Saab's Lennart Sindahl stated that development of an optionally manned version of the Gripen E capable of flying unmanned operations was being explored by the firm; further development of the optionally manned and carrier versions would require the commitment of a customer.[72][73] On 6 November 2014, the Brazilian Navy expressed interest in a carrier-based variant of the Gripen.[74]

Sweden awarded Saab a four-year contract in 2010 to improve the Gripen's radar and other equipment, integrate new weapons, and lower its operating costs.[75] In June 2010, Saab stated that Sweden planned to order the Gripen NG, designated as JAS 39E/F, and was to enter service in 2017 or earlier dependent on export orders.[67] On 25 August 2012, following Switzerland's intention to buy 22 of the E/F variants, Sweden announced it planned to buy 40–60 Gripen E/Fs.[76] The Swedish government approved the decision to purchase 60 Gripen Es on 17 January 2013,[77] with the first deliveries pushed back to 2018.[78] In July 2013, assembly began on the first pre-production aircraft.[79] The first flight of the pre-production E aircraft is expected in 2015, with the first production aircraft delivered in 2018.[80] In March 2014 Saab revealed the detailed design and indicated it planned to receive military type certification in early 2018.[80]

In September 2015, Saab Aeronautics head Lennard Sindhal announced that an electronic warfare version of the Gripen F two-seater was under development.[81]

Design

Overview

Light grey aircraft banking tightly, revealing its underside.
Underside of a Gripen in flight, 2012

The Gripen is a multirole fighter aircraft, intended to be a lightweight and agile aerial platform incorporating advanced, highly adaptable avionics. It has canard control surfaces which contributes a positive lift force at all speeds, while the generous lift from the delta wing compensates for the rear stabilizer producing negative lift at high speeds, increasing induced drag.[82] Being intentionally unstable and employing digital fly-by-wire flight controls to maintain stability removes many flight restrictions, improves maneuverability, and reduces drag.[83][84] The Gripen also has good short takeoff performance, being able to maintain a high sink rate and strengthened to withstand the stresses of short landings.[85] A pair of air brakes are located on the sides of the rear fuselage; the canards also angle downward to act as air brakes and decrease landing distance.[86] It is capable of flying at a 70-80 degrees angle of attack.[87]

In order to enable the Gripen to have a long service life, projected to be roughly 50 years, the aircraft was designed to have low maintenance requirements;[88] major systems such as the RM12 engine and PS-05/A radar are of a modular type to reduce operating cost and increase reliability.[84] The Gripen was designed to be flexible as it had been anticipated that newly developed sensors, computers, and armaments would need to be integrated as technology advances.[89] The aircraft was estimated to be roughly 67% sourced from Swedish or European suppliers and 33% from the United States.[90]

One key aspect of the Gripen program that Saab have been keen to emphasize has been technology-transfer agreements and industrial partnerships with export customers.[91] The Gripen is typically customized to customer requirements, enabling the routine inclusion of local suppliers in the manufacturing and support processes. A number of South African firms provide components and systems – including the communications suite and electronic warfare systems – for the Gripens operated by South African Air Force.[92] Operators also have access to the Gripen's source code and technical documentation, allowing for upgrades and new equipment to be independently integrated.[93] Some export customers intend to domestically assemble the Gripen; it has been proposed that Brazilian aerospace manufacturer Embraer may produce Gripens for other export customers as well.[94][95]

Avionics and sensors

All of the Gripen's avionics are fully integrated using total of five MIL-STD-1553B digital data buses, described as "sensor fusion".[84] The total integration of the avionics makes the Gripen a "programmable" aircraft, allowing software updates to be introduced over time to increase performance and allow for additional operational roles and equipment.[96] The Ada programming language was adopted for the Gripen, and is used for the primary flight controls on the final prototypes from 1996 onwards and all subsequent production aircraft.[97] The Gripen's software is continuously being improved to add new capabilities, as compared to the preceding Viggen which was updated only in an 18-month schedule.[88]

Much of the data generated from the onboard sensors and by cockpit activity is digitally recorded throughout the length of an entire mission. This information can be replayed in the cockpit or easily extracted for detailed post-mission analysis using a data transfer unit that can also be used to insert mission data to the aircraft.[98][99] The Gripen, like the Viggen, was designed to operate as one component of a networked national defence system, which allows for automatic exchange of information in real-time between Gripen aircraft and ground facilities.[100] According to Saab, the Gripen features "the world's most highly developed data link".[84] The Gripen's Ternav tactical navigation system combines information from multiple onboard systems such as the air data computer, radar altimeter, and GPS to continuously calculate the Gripen's location.[101]

The Gripen entered service using the PS-05/A pulse-Doppler X band multi-mode radar, developed by Ericsson and GEC-Marconi, which is based on the latter's advanced Blue Vixen radar for the Sea Harrier that also served as the basis for the Eurofighter's CAPTOR radar.[102][84] The all-weather radar is capable of locating and identifying targets 120 km (74 mi) away,[103] and automatically tracking multiple targets in the upper and lower spheres, on the ground and sea or in the air. It can guide several beyond visual range air-to-air missiles to multiple targets simultaneously.[104] Saab stated the PS-05/A is able to handle all types of air defense, air-to-surface, and reconnaissance missions,[84] and is developing a Mark 4 upgrade to it.[105][106] The Mark 4 version has a 150% increase in high-altitude air-to-air detection ranges, detection and tracking of smaller targets at current ranges, 140% improvement in air-to-air mode at low altitude, and full integration of modern weapons such as the AIM-120C-7 AMRAAM, AIM-9X Sidewinder, and MBDA Meteor missiles.[107]

The future Gripen E/F will make use of a new active electronically scanned array (AESA) radar, Raven ES-05, based on the Vixen AESA radar family from Selex ES.[64] Among other improvements, the new radar is to be capable of scanning over a greatly increased field of view and improved range.[108] In addition, the new Gripen integrates the Skyward-G Infra-red search and track (IRST) sensor, which is capable of passively detecting thermal emissions from air and ground targets in the aircraft's vicinity.[109] The sensors of the Gripen E are claimed to be able to detect low radar cross-section (RCS) targets at beyond visual range.[110] Targets are tracked by a "best sensor dominates" system, either by onboard sensors or through the Transmitter Auxiliary Unit (TAU) data link function of the radar.[111][112]

Cockpit

The primary flight controls are compatible with the HOTAS control principle – the centrally mounted stick, in addition to flying the aircraft, also controls the cockpit displays and weapon systems. A triplex, digital fly-by-wire system is employed on the Gripen's flight controls,[84] with a mechanical backup for the throttle.[113] Additional functions, such as communications, navigational and decision support data, can be accessed via the up front control panel, directly above the central cockpit display.[114] The Gripen includes the EP-17 cockpit display system, developed by Saab to provide pilots with a high level of situational awareness and reduces pilot workload through intelligent information management. The Gripen features a sensor fusion capability, information from onboard sensors and databases is combined, automatically analysed, and useful data is presented to the pilot via a wide field-of-view head-up display, three large multi-function colour displays, and optionally a helmet mounted display system (HMDS).[99]

Of the three multi-function displays (MFD), the central display is for navigational and mission data, the display to the left of the center shows aircraft status and electronic warfare information, and the display to the right of the center has sensory and fire control information.[114] In two-seat variants, the rear seat's displays can be operated independently of the pilot's own display arrangement in the forward seat, Saab has promoted this capability as being useful during electronic warfare and reconnaissance missions, and while carrying out command and control activities.[99] In May 2010, Sweden began equipping their Gripens with additional onboard computer systems and new displays.[115] The MFDs are interchangeable and designed for redundancy in the event of failure, flight information can be presented on any of the displays.[113]

Saab and BAE developed the Cobra HMDS for use in the Gripen, based on the Striker HMDS used on the Eurofighter.[116] By 2008, the Cobra HMDS was fully integrated on operational aircraft, and is available as an option for export customers; it has been retrofitted into older Swedish and South African Gripens.[116] The HMDS provides control and information on target cueing, sensor data, and flight parameters, and is optionally equipped for night time operations and with chemical/biological filtration.[98] All connections between the HMDS and the cockpit were designed for rapid detachment, for safe use of the ejection system.[117]

Engine

 Headphone-wearing technician in green uniform, inspecting the engine nozzle of a single-engine fighter jet
A technician visually inspecting a Gripen's RM12 engine in-situ

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

All in-service Gripens as of January 2014 are powered by a Volvo RM12 turbofan engine (now GKN Aerospace Engine Systems), a license-manufactured derivative of General Electric F404, fed by a Y-duct with splitter plates; changes include increased performance and improved reliability to meet single engine use safety criteria, as well as a greater resistance to bird strike incidents.[113][118] Several subsystems and components were also redesigned to reduce maintenance demands.[119] By November 2010, the Gripen had accumulated over 143,000 flight hours without a single engine-related failure or incident; Rune Hyrefeldt, head of Military Program management at Volvo Aero, stated "I think this must be a hard record to beat for a single-engine application".[119]

The JAS 39E and F variants currently under development are to adopt the F414G powerplant, a variant of the General Electric F414. The F414G can produce 20% greater thrust than the current RM12 engine, enabling the Gripen to supercruise (maintain speed beyond the sound barrier without the use of afterburners) at a speed of Mach 1.1 while carrying an air-to-air combat payload.[60] In 2010, Volvo Aero stated it was capable of further developing its RM12 engine to better match the performance of the F414G, and claimed that developing the RM12 would be a less expensive option.[120] Prior to Saab's selection of the F414G, the Eurojet EJ200 had also been under consideration for the Gripen; proposed implementations included the use of thrust vectoring.[121]

Equipment and armaments

The Gripen is compatible with a number of different armaments, beyond the aircraft's single 27 mm Mauser BK-27 cannon (omitted on the two-seat variants),[122] including air-to-air missiles such as the AIM-9 Sidewinder, air-to-ground missiles such as the AGM-65 Maverick, and anti-ship missiles such as the RBS-15.[123] In 2010, the Swedish Air Force's Gripen fleet completed the MS19 upgrade process, enabling compatibility with a range of weapons, including the long-range MBDA Meteor missile, the short-range IRIS-T missile and the GBU-49 laser-guided bomb.[124] Speaking on the Gripen's selection of armaments, Saab's campaign director for India Edvard de la Motte stated that: "If you buy Gripen, select where you want your weapons from. Israel, Sweden, Europe, US… South America. It's up to the customer".[108]

In flight, the Gripen is typically capable of carrying up to 14,330 lb (6.50 t) of assorted armaments and equipment.[96] Equipment includes external sensor pods for reconnaissance and target designation, such as Rafael's LITENING targeting pod, Saab's Modular Reconnaissance Pod System, or Thales' Digital Joint Reconnaissance Pod.[125] The Gripen has an advanced and integrated electronic warfare suite, capable of operating in an undetectable passive mode or to actively jam hostile radar; a missile approach warning system passively detects and tracks incoming missiles.[109][126] In November 2013, it was announced that Saab will be the first to offer the BriteCloud expendable Active jammer developed by Selex ES.[127] In June 2014, the Enhanced Survivability Technology Modular Self Protection Pod, a defensive missile countermeasure pod, performed its first flight on the Gripen.[128]

Saab describes the Gripen as a "swing-role aircraft", stating that it is capable of "instantly switching between roles at the push of a button". The human/machine interface changes when switching between roles, being optimized by the computer in response to new situations and threats.[98] The Gripen is also equipped to use a number of different communications standards and systems, including SATURN secure radio, Link-16, ROVER, and satellite uplinks.[129] Equipment for performing long range missions, such as an aerial refueling probe and onboard oxygen generation system (OBOGS), was integrated upon the Gripen C/D.[130]

Usability and maintenance

Three-quarter hind view of grey jet aircraft taking off in snowy environment. Its engine is kicking up snow on the ground
Gripen during takeoff in snowy conditions, 2012

During the Cold War, the Swedish Armed Forces were to be ready to defend against a possible invasion. This scenario required combat aircraft to be dispersed in order to maintain an air defence capacity.[131] Thus, a key design goal during the Gripen's development was the ability to take off from snow-covered landing strips of only 800 metres (2,600 ft);[132] furthermore, a short-turnaround time of just ten minutes, during which a team composed of a technician and five conscripts would be able to re-arm, refuel, and perform basic inspections and servicing inside that time window before returning to flight.[132][133]

During the design process, great priority was placed on facilitating and minimising aircraft maintenance; in addition to a maintenance-friendly layout, many subsystems and components require little or no maintenance at all.[88] Aircraft are fitted with a Health and Usage Monitoring Systems (HUMS) that monitors the performance of various systems, and provides information to technicians to assist in servicing it.[134] Saab operates a continuous improvement programme; information from the HUMS and other systems can be submitted for analysis.[135] According to Saab, the Gripen provides "50% lower operating costs than its best competitor".[84]

A 2012 Jane's Aerospace and Defense Consulting study compared the operational costs of a number of modern combat aircraft, concluding that Gripen had the lowest cost per flight hour (CPFH) when fuel used, pre-flight preparation and repair, and scheduled airfield-level maintenance together with associated personnel costs were combined. The Gripen had an estimated CPFH of $4,700 whereas the next lowest, the F-16 Block 40/50, had a 49% higher CPFH at $7,000.[56]

Operational history

Sweden

JAS 39 Gripen in flight

The Swedish Air Force placed a total order for 204 Gripens[136] in three batches. The first delivery occurred on 8 June 1993, when 39102 was handed over to the Flygvapnet during a ceremony at Linköping;[137] the last was handed over on 13 December 1996.[29] The air force received its first Batch II example on 19 December 1996.[138] Instead of the fixed-price agreement of Batch I, Batch II aircraft were paid as a "target price" concept: any cost under/overruns would be split between FMV and Saab.[30]

The JAS 39 entered service with the F 7 Wing (F 7 Skaraborgs Flygflottilj) on 1 November 1997.[139][140] The final Batch three aircraft was delivered to FMV on 26 November 2008.[33] This was accomplished at 10% less than the agreed-upon price for the batch, putting the JAS 39C flyaway cost at under US$30 million.[33] This batch of Gripens was equipped for in-flight refuelling from specially equipped TP84s.[30] In 2007, a programme was started to upgrade 31 of the air force's JAS 39A/B fighters to JAS 39C/Ds.[141] The SwAF had a combined 134 JAS 39s in service in January 2013.[142]

On 29 March 2011, the Swedish parliament approved the Swedish Air Force for a 3-month deployment to support the UN-mandated no-fly zone over Libya. Deployment of eight Gripens, ten pilots, and other personnel began on 2 April.[143] On 8 June 2011, the Swedish government announced an agreement to extend the deployment for five of the Gripens.[144] By October 2011, Gripens have flown more than 650 combat missions, almost 2,000 flight hours, and delivered approximately 2,000 reconnaissance reports to NATO.[145] Journalist Tim Hepher suggested that the Libyan operations may stimulate sales of the Gripen and other aircraft.[146]

A Swedish Gripen during an exercise, 2013

In November 2012, Lieutenant Colonel Lars Helmrich of the Swedish Air Force testified to the Riksdag regarding the Gripen E. He stated that the current version of the Gripen would be outdated in air-to-air combat by 2020.[147] With 60 Gripens having been judged to be the minimum required to defend Swedish Airspace, the Swedish Air Force wants to have 60–80 Gripens upgraded to the E/F standard by 2020.[148]

On 25 August 2012, the Swedish government announced that 40–60 JAS 39E/F Gripens were expected to be procured and in service by 2023.[76][149] On 11 December 2012, the Riksdag approved the purchase of 40 to 60 JAS 39E/Fs with an option to cancel if at least 20 aircraft are not ordered by other customers.[150] on 17 January 2013, the government approved the deal for 60 JAS 39Es to be delivered between 2018 and 2027.[77] On 3 March 2014, the Swedish defence minister stated that another 10 JAS 39Es might be ordered, this was later confirmed by the government.[151][152] Originally 60 JAS 39Cs were to be retrofitted to the E level by 2023;[153] in June 2014, the acquisition was revised to all Gripen Es being new-built. This change frees Swedish JAS 39Cs for leasing to potential customers, such as Brazil.[154][155] On 19 March 2015, the Swedish Air Force received its final JAS 39C (aircraft 39294).[156]

Czech Republic

File:QRA Gripen (4678910099).jpg
Czech Gripen with Caslav AFB in the background

When the Czech Republic became a NATO member in 1999, the need to replace their existing Soviet-built MiG-21 fleet with aircraft compatible with NATO interoperability standards became apparent. In 2000, the Czech Republic began evaluating a number of aircraft, including the F-16, F/A-18, Mirage 2000, Eurofighter Typhoon and the Gripen. One major procurement condition was the industrial offset agreement, set at 150% of the expected purchase value.[157] In December 2001, having reportedly been swayed by Gripen International's generous financing and offset programme, the Czech Government announced that the Gripen had been selected.[158] In 2002, the deal was delayed until after parliamentary elections had taken place; alternative means of air defense were also studied, including leasing the aircraft.[159]

 Three-quarter bottom view of two jet aircraft inn flight against a blue sky.
Pair of Czech Gripens during a Baltic Air Policing mission in Lithuania

On 14 June 2004, it was announced that the Czech Republic was to lease 14 Gripen aircraft, modified to comply with NATO standards.[160] The agreement also included the training of Czech pilots and technicians in Sweden. The first six were delivered on 18 April 2005.[161] The lease was for an agreed period of 10 years at a cost of €780 million; the 14 ex-Swedish Air Force aircraft included 12 single-seaters and two JAS 39D two-seat trainers.[162][163] In September 2013, the Defence and Security Export Agency announced that a follow-up agreement with the Czech Republic had been completed to extend the lease by 14 years, until 2029; the leased aircraft shall also undergo an extensive modernisation process, including the adoption of new datalinks.[164] The lease also has an option of eventually acquiring the fighters outright.[163] In 2014 the lease was extended to 2027 and the Saab service contract was extended to 2026.[165][166]

As of November 2014, the Czech Government considers leasing further six Gripens due to Russia's deteriorating relationship with the West.[167] More recently, it decided to upgrade its fleet to the MS20 configuration.[168]

Hungary

Following Hungary's membership of NATO in 1999, there were several proposals to achieve a NATO-compatible fighter force. Considerable attention went into studying second-hand aircraft options as well as modifying the nation's existing MiG-29 fleet. In 2001, Hungary received several offers of new and used aircraft from various nations, including Sweden, Belgium, Israel, Turkey, and the United States.[169] Although the Hungarian government initially intended to procure the F-16, in November 2001 it was in the process of negotiating a 10-year lease contract for 12 Gripen aircraft, with an option to purchase the aircraft at the end of the lease period.[170][171]

 Jet aircraft with centerline external fuel tank during invert flight against blue sky
Hungarian Air Force Gripen during inverted flight, 2007

As part of the procurement arrangements, Saab had offered an offset deal valued at 110 per cent of the cost of the 14 fighters.[172] Initially, Hungary had planned to lease several Batch II aircraft; however, the inability to conduct aerial refuelling and weapons compatibility limitations had generated Hungarian misgivings.[173] The contract was renegotiated and was signed on 2 February 2003 for a total of 14 Gripens, which had originally been A/B standard and had undergone an extensive upgrade process to the NATO-compatible C/D 'Export Gripen' standard.[174] The last aircraft deliveries took place in December 2007.[175]

While the Hungarian Air Force operates a total of 14 Gripen aircraft under lease,[163] in 2011, the country reportedly intended to purchase these aircraft outright.[176] However, in January 2012, the Hungarian and Swedish governments agreed to extend the lease period for a further ten years; according to Hungarian Defence Minister Csaba Hende, the agreement represented considerable cost savings.[177]

Two Gripens were lost in crashes in May and June 2015,[178][179][180] leaving 12 Gripens in operation.[181]

South Africa

In 1999, South Africa signed a contract with BAe/Saab for the procurement of 26 Gripens (C/D standard) with minor modifications to meet their requirements.[182] Deliveries to the South African Air Force commenced in April 2008.[183] By April 2011, 18 aircraft (nine two-seater aircraft and nine single-seaters) had been delivered.[184] While the establishment of a Gripen Fighter Weapon School at Overberg Air Force Base in South Africa had been under consideration, in July 2013 Saab ruled out the option due to a lack of local support for the initiative; Thailand is an alternative location being considered,[185] as well as the Čáslav Czech air base.[186]

Between April 2013 and December 2013, South African contractors held prime responsibility for maintenance work on the Gripen fleet as support contracts with Saab had expired; this arrangement led to fears that extended operations may not be possible due to a lack of proper maintenance.[187] In December 2013, Armscor awarded Saab a long-term support contract for the company to perform engineering, maintenance, and support services on all 26 Gripens through 2016.[188] On 13 March 2013, South African Defense Minister Nosiviwe Mapisa-Nqakula stated that "almost half of the SAAF Gripens" have been stored because of an insufficient budget to keep them flying.[189] In September 2013, the SAAF decided not to place a number of its Gripens in long-term storage; instead all 26 aircraft would be rotated between flying cycles and short-term storage.[190] Speaking in September 2013, Brigadier-General John Bayne testified that the Gripen met the SAAF's minimum requirements, as the country faced no military threats.[191]

Thailand

Three-quarter hind bottom view of jet aircraft in flight generating wingtip vortices, against a blue cloudy sky
Royal Thai Air Force Gripen

In 2007, Thailand's Parliament authorized the Royal Thai Air Force to spend up to 34 billion baht (US$1.1 billion) as part of an effort to replace Thailand's existing Northrop F-5 fleet.[192] In February 2008, the Thai Air Force ordered six Gripens (two single-seat C-models and four two-seat D-models) from Saab; deliveries began in 2011.[193] Thailand ordered six more Gripen Cs in November 2010; deliveries began in 2013.[194] Thailand may eventually order as many as 40 Gripens.[195] In 2010, Thailand selected the Surat Thani Airbase as the main operating base for its Gripens.[196] The first of the six aircraft were delivered on 22 February 2011.[197]

Saab delivered three Gripens in April 2013, and three more in September 2013.[198] In September 2013, Air Force Marshal Prajin Jantong stated that Thailand is interested in purchasing six aircraft more in the near future, pending government approval.[192][199] Thai Supreme Commander General Thanasak Patimapragorn has stated that the air force intends for the Gripen's information systems to be integrated with Army and Navy systems; the armed forces will officially inaugurate the Gripen Integrated Air Defence System during 2014.[192]

United Kingdom

An ETPS Gripen at RIAT 2008

The Empire Test Pilots' School (ETPS) in the United Kingdom has used the Gripen for advanced fast jet training of test pilots since 1999.[200] It operates a D aircraft.[201]

Potential and future operators

Brazil

In October 2008, Brazil selected three finalists for its F-X2 fighter programme: the Dassault Rafale B/C, the Boeing F/A-18E/F Super Hornet, and the JAS 39E/F Gripen NG.[202] The Brazilian Air Force initially planned to procure at least 36 and possibly up to 120 later,[203][204] to replace its Northrop F‐5EM and Dassault Mirage 2000C aircraft.[205] In February 2009, Saab submitted a tender for 36 Gripen NGs.[206] On 5 January 2010, reports claimed that the Brazilian Air Force's final evaluation report placed the Gripen ahead of other contenders; the decisive factor was reportedly lower unit cost and operational costs.[207] Amid delays due to financial constraints,[208][209] there were reports in 2010 of the Rafale's selection,[210] and in 2011 of the F/A-18's selection.[70][211] On 18 December 2013, President Dilma Rousseff announced the Gripen NG's selection.[205][212]

Key decision factors were the domestic manufacturing opportunities, participation in developing the Gripen, and potential exports to Africa, Asia and Latin America;[94][213] Argentina and Ecuador are interested in procuring Gripens from or through Brazil,[214] and Mexico is considered an export target.[215] Another factor was the distrust of the US due to the NSA surveillance scandal.[216] The Gripen is not immune to foreign pressure, the UK may use their 30% component percentage in the Gripen to veto a sale to Argentina due to the Falkland Islands dispute; thus Argentina is considering Russian or Chinese aircraft instead.[217] Until Gripen E deliveries begin, Brazil intends to lease several Gripen C aircraft.[95][213]

On 24 October 2014, Brazil and Sweden signed a 39.3 billion SEK (US$5.44 bn, R$13 bn) contract for 28 Gripen E and 8 Gripen F aircraft to be delivered from 2019 to 2024 and maintained until 2050;[218][219] the Swedish government will provide a subsidized 25-year, 2.19% interest rate loan for the purchase.[220] At least 15 aircraft are to be assembled in Brazil, and Brazilian companies are to be involved in the full production run; Gripen Fs are to be delivered later. An almost $1 billion price increase since selection is due to developments requested by Brazil,[221] such as a single screen display.[222] The compensation package is set at US$9 billion, or 1.7 times the order value.[223] Two Brazilian pilots were trained in Sweden between November 2014 and April 2015.[224] The Brazilian Air Force has a requirement for 108 Gripens, to be delivered in three batches.[225][226] The Brazilian Navy is interested in the Sea Gripen to replace its Douglas A-4KU Skyhawk carrier-based fighters.[70][227] Brazil and Sweden finalized the deal in 2015.[228]

Croatia

A Gripen deal including 12 aircraft (10 single-seat C-models, and 2 two-seat D-models) valued at 700 million euro (US$1.1 billion) was first offered to Croatia in 2007. However, this procurement stalled due to the 2008 financial crisis, in which the Croatian government had to reprioritise government spending programmes.[citation needed]

On 24 October 2015, Sweden announced its bid of the JAS 39 Gripen C/D for Croatia's fighter replacement requirement, following a request for information from the Croatian Ministry of Defence in June for between 8 and 12 newly built aircraft in order to replace the Croatian fleet of ageing MiG-21bis aircraft. According to the Ministry of Defence's Long-Term Development Plan (LTDP), however, the MiG-21 is to remain in service until 2024 as a result of ongoing modernisation programmes. The LTDP will run from 2015 to 2024 and is scheduled to have funding available for a replacement aircraft in 2019. Second-hand F-16s from another country may also be considered.[229]

Finland

In June 2015, a working group set up by the Finnish MoD proposed starting the HX program to replace Finnish Air Force's current fleet of F/A-18 Hornet. The group recognises five potential types: Boeing F/A-18E/F Super Hornet, Dassault Rafale, Eurofighter Typhoon, Lockheed Martin F-35, and Saab JAS Gripen.[230]

In December 2015 Finnish MoD sent a letter to Great Britain, France, Sweden and the United States where it informed that the fighter project was launched in the Defence Forces. The goal of the project is to replace the Hornet fleet, which will be decommissioned as of 2025, with multi-role fighters. The project has been named as HX Fighter Program. JAS-39 is mentioned in the letter as a potential fighter for the program. The request for information concerning the HX Fighter Program will be sent at the latest in March 2016. A call for tender will be sent in spring 2018 and the buying decision is scheduled to take place in 2021.[231]

Poland

The Gripen C/D was a contender for 48 multirole fighters for the Polish Air Force started in 2001. On 27 December 2002, the Polish Defence Minister announced the F-16C/D Block 50/52+'s selection.[232] According to Stephen Larrabee, the selection was heavily influenced by Lockheed Martin's lucrative offset agreement (totaling $3.5 billion and 170% offset against Gripen International's €3.2 billion with 146% offset) and by a political emphasis on Poland's strategic relationship with the US and NATO.[173] Both Gripen International and Dassault Aviation (who offered the Mirage 2000-5 Mk 2) described the decision as political.[233] According to a former Polish military defence vice-minister, the JAS 39 offer was better and included research participation proposals.[234]

Poland plans to purchase 64 multirole combat aircraft from 2021 to replace the Polish Air Force's fleet of Sukhoi Su-22M4 'Fitter-K' ground attack aircraft and Mikoyan MiG-29 fighters. The open tender procedure could include the F-35 Lightning II, the JAS 39 Gripen E/F, the Eurofighter Typhoon, the Dassault Rafale, and Boeing's F/A-18E/F Advanced Super Hornet.[235][236]

Slovakia

On 30 August 2014, the Czech Republic, Slovakia and Sweden signed a letter of intent agreeing to co-operate on using the Gripen, which may lead to acquisition of the aircraft by the Slovak Air Force. The letter of intent laid the foundation for bilateral co-operation around a common airspace surveillance of Slovakia and the Czech Republic. Slovakia is looking to replace its MiG-29 fighters and the Gripen has been reported as the aircraft of choice, although the requirement will go to open competition. They may seek to lease fighters rather than buy, as did neighbouring Hungary and the Czech Republic.[237]

Switzerland

In January 2008, the Swiss Defence Material Administration invited Gripen International to submit bids to replace the nation's ageing F-5 fleet.[238] Saab responded with an initial proposal on 2 July 2008;[239] other contenders were the Dassault Rafale and Eurofighter Typhoon.[240] On 30 November 2011, the Swiss government announced its decision to buy 22 Gripen NG aircraft for 3.1 billion Swiss francs.[241][242] In 2012, a confidential report of the Swiss Air Force's 2009 tests of the three contenders was leaked, which had rated the Gripen as performing substantially below both the Rafale and the Eurofighter. The Gripen was assessed as satisfactory for reconnaissance but unsatisfactory for combat air patrol and strike missions.[243][244] The JAS 39C/D was evaluated, while the Gripen NG had been bid.[245] The parliamentary security commission found that the Gripen offered the most risks, but voted to go ahead as it was the cheapest option.[246]

On 25 August 2012, the plan to order was confirmed by both Swedish and Swiss authorities.[247] Deliveries were expected to run from 2018 to 2021 at a fixed price of CHF 3.126 billion ($3.27 billion) including development costs, mission planning systems, initial spares and support, training, and certification; the Swedish government also guaranteed the price, performance and operational suitability. 8 JAS 39Cs and 3 JAS 39Ds were to be leased from 2016 to 2020 to train Swiss pilots and allow the F-5s to be retired.[248][249] In 2013, Saab moved to increase Swiss industry offsets above 100% of the deal value after the Swiss parliament's upper house voted down the deal's financing.[250] On 27 August 2013, the National Council's Security Commission approved the purchase,[251] followed by the lower and upper houses of the parliament's approval in September 2013.[252][253] Elements of the left and center of the political spectrum often criticized the Gripen as unnecessary and too expensive. On 18 May 2014, 53.4% of Swiss voters voted against the plan in a national referendum.[254][255] According to the press, objectors questioned the role of manned fighter aircraft in general, and the relevance of alternatives such as UAVs, surface-to-air missiles, or cyberwarfare capabilities.[256]

In April 2015, Switzerland is set to relaunch the F-5E/F replacement programme,[257] the Gripen is again the favourite.[258]

Others

Other nations that have expressed interest in Gripen include Argentina (E/F versions from Brazil, subject to UK veto),[259][260] Austria (C/D or E/F versions),[261][262] Belgium (E/F),[263][264] Botswana[263] (C/D),[261] Bulgaria[265] (C/D),[261] Colombia[201] (C/D or E/F[261] from Brazil), Croatia (possibly newly built[266] C/D),[267][268] Ecuador[214] (C/D or E/F[261] from Brazil), Estonia,[263] Finland[269] (E/F)[261] India (Sea Gripen[227] and E/F[261][270]), Indonesia[263] (C/D),[261] Kenya[271] (C/D),[261] Latvia,[263] Lithuania,[263] Malaysia[263] (C/D),[261] Mexico[215] (C/D or E/F[261] from Brazil), Namibia[201] (C/D),[261] Peru[263] (C/D or E/F[261] from Brazil), the Philippines[263] (C/D),[261] Portugal[263] (C/D),[261] Serbia,[272] Slovakia (C/D),[261] Slovenia,[273] Uruguay (C/D or E/F[261] from Brazil) and Vietnam.[274]

Saab's head of exports Eddy de La Motte has stated that the Gripen's chances have improved as nations waver in their commitments to the F-35.[275] Richard Aboulafia of the Teal Group (an aerospace & defense analysis enterprise[276]) has attributed difficulty securing export sales to the Swedish government's inability to offer the same sort of strategic partnership as some rival aircraft manufacturing nations.[277] In September 2013, Saab's CEO Håkan Buskhe said he envisioned Gripen sales to reach 400 or 450 aircraft.[278]

Failed bids

Denmark

In 2007, Denmark signed a Memorandum of Understanding between the Defence Ministers of Sweden and Denmark to evaluate the Gripen as a replacement for Denmark's fleet of 48 F-16s. Denmark also requested the development of Gripen variants featuring more powerful engines, larger payloads, longer range, and additional avionics; this request contributed to Saab's decision to proceed with the JAS E/F's development.[41][279] Denmark repeatedly delayed the purchase decision;[280] in 2013, Saab indicated that the Gripen was one of four contenders for the Danish purchase, alongside Boeing's Super Hornet, Lockheed Martin's F-35 Joint Strike Fighter, and the Eurofighter.[281] Denmark is a level-3 partner in the JSF programme, and has already invested US$200 million. The final selection will be in mid-2015 where 24 to 30 fighters are expected.[282] The Swedish government announced on 21 July 2014 the Gripen's withdrawal from the Danish competition, having chosen not to respond to the invitation to tender.[283]

India

Jet aircraft in the distance preparing to take off from rural airport surrounded by green trees
Saab Gripen at Aero India 2011, Yelahanka Air force Base Bangalore

The Gripen was a contender for the Indian MRCA competition for 126 multirole combat aircraft.[284] In April 2008, Gripen International offered the Next Generation Gripen for India's tender[285] and opened an office in New Delhi in order to support its efforts in the Indian market.[286] On 4 February 2009, Saab announced that it had partnered with India's Tata Group to develop the new Gripen variant to fit India's needs.[287]

The Indian Air Force (IAF) conducted extensive field trials and evaluated Gripen's flight performance, logistics capability, weapons systems, advanced sensors and weapons firing.[288] In April 2011, the IAF rejected Gripen's bid in favour of the Eurofighter Typhoon and the Dassault Rafale.[289] Senior Indian Air Force officials, while happy with the improved capabilities of Gripen NG, identified its high reliance on US-supplied hardware, including electronics, weaponry and the GE F414 engine, as a factor that may hamper its ability to be exported.[290]

In 2015 after the Rafale order was cut back to just 36 aircraft, Saab indicated a willingness to set up joint production of the Gripen in India.[291]

Netherlands

In July 2008, the Netherlands announced it would evaluate Gripen NG together with four other competitors;[292] in response, Saab offered 85 aircraft to the Royal Netherlands Air Force in August 2008.[293] On 18 December 2008, it was reported that the Netherlands had evaluated the F-35 as having a better performance-price relation than the Gripen NG.[294][295] On 13 January 2009, NRC Handelsblad claimed that, according to Swedish sources, Saab had offered to deliver 85 Gripens for €4.8 billion to the Dutch Air Force, about 1 billion euro cheaper than budgeted for the F-35.[296]

Norway

On 18 January 2008, the Norwegian Ministry of Defence issued a Request for Binding Information (RBI) to the Swedish Defence Material Administration,[297] who issued an offer for 48 Gripens in April 2008.[298][299] On 20 November 2008, the selection of the F-35 Lightning II for the Royal Norwegian Air Force was announced, stating that the F-35 is the only candidate to meet all operational requirements;[300] media reports claimed the requirements were tilted in the F-35's favour.[301] Saab and Sweden's defence minister Sten Tolgfors stated that Norway's cost calculations were flawed;[54] the offer being for 48 Gripens over 20 years, but Norway had extrapolated it to operating 57 aircraft over 30 years, thus doubling the cost; cost projections also failed to relate to the Gripen's operational costs. Norway also calculated greater attrition losses than what Sweden considered reasonable. According to Tolgfors, Norway's decision complicated further export deals.[302][303]

In December 2010 leaked United States diplomatic cables revealed that the United States deliberately delayed Sweden's request for access to a US AESA radar until after Norway's selection. The cables also indicated that Norwegian consideration of the Gripen "was just a show" and that Norway had decided to purchase the F-35 due to "high-level political pressure" from the US.[40]

Others

The Gripen was one of the candidates to replace the Austrian Air Force's ageing Saab 35 Drakens; the Eurofighter Typhoon was selected in 2003.[304] Oman ended up with the Eurofighter Typhoon.[305][306] Romania went with the F-16 instead.[307]

Variants

Jet aircraft taxiing against a background of a shed and green trees
JAS 39 Gripen taxiing in after display, Farnborough 2006
  • JAS 39A: initial version that entered service with the Swedish Air Force in 1996. A number have been upgraded to the C standard.[308]
  • JAS 39B: two-seat version of the 39A for training, specialised missions and type conversion.[309] To fit the second crew member and life support systems, the internal cannon and an internal fuel tank were removed and the airframe lengthened 0.66 m (2 ft 2 in).[30]
  • JAS 39C: NATO-compatible version of Gripen with extended capabilities in terms of armament, electronics, etc. Can be refuelled in flight.[310]
  • JAS 39D: two-seat version of the 39C, with similar alterations as the 39B.[35]
  • Gripen NG: improved version following on from the Gripen Demo technology demonstrator.[65] Changes from the JAS 39C/D include the more powerful F414G engine, Raven ES-05 AESA radar, increased fuel capacity and payload, two additional hardpoints, and other improvements.[59][60] These improvements have reportedly increased the Gripen NG costs to an estimated 24,000 Swiss Francs (US$27,000) per hour,[311] and increased the flyaway cost to 100 million Swiss Francs (US$113M).[312]
  • JAS 39E: single-seat production version developed from the Gripen NG program. Sweden has ordered the variant, with Brazil and, originally, Switzerland to place orders.[77][150][205]
  • JAS 39F: two-seat version of the E variant. Eight ordered by Brazil,[218] to be developed and assembled there;[313] planned for pilot training and combat, being optimised for back seat air battle management, with jamming, information warfare and network attack, besides weapon system officer and electronic warfare roles.[314]

Proposals

  • Sea Gripen: proposed carrier-based version based on the Gripen NG.[69] As of 2011, its development was underway.[71] As of 2013, Brazil and India[227] were interested.
  • Gripen UCAV: proposed unmanned combat aerial vehicle (UCAV) variant of the Gripen E.[73]
  • Gripen EW: proposed electronic war (EW) ‘Growler’ variant of the Gripen F.[81]

Operators

Gripen operators in blue with orders in cyan
Grey jet aircraft banking right over rural area with residential housing. The background is mostly green with yellow areas.
Saab JAS 39 Gripen of the Czech Air Force

There were 186 Gripens in service with military users as of January 2013.[142]

 Brazil
The Brazilian Air Force ordered 28 Gripen E and 8 Gripen F aircraft.[218]
 Czech Republic
The Czech Air Force has 14 Gripens on lease, they serve at the "211 Taktická letka" (211th Tactical Squadron); these include 12 single-seat C models and two two-seat D models, in operation as of January 2013.[142]
 Hungary
The Hungarian Air Force operates 14 Gripens (12 C-models and two D-models) on a lease-and-buy arrangement as of January 2013.[142]
"Puma" Harcászati repülőszázad
 South Africa
The South African Air Force (SAAF) ordered 26 aircraft; 17 single-seat C-models and nine two-seater D-models.[17] The first delivery, a two-seater, took place on 30 April 2008.[183][315]
No. 2 Squadron
 Sweden
The Swedish Air Force originally ordered 204 aircraft, including 28 two-seaters. Sweden leases 28 of the aircraft, to the Czech and Hungarian Air Forces. The SwAF has 134 JAS 39s, including 50 JAS 39As, 13 JAS 39Bs, 60 JAS 39Cs and 11 JAS 39D Gripens in inventory in January 2013,[142] with approximately 100 JAS 39C/D Gripens in operational use (including 31 A models refitted to the C level).[316]
F 7 Såtenäs
F 17 Kallinge
F 21 Luleå
 Thailand
The Royal Thai Air Force ordered 12 JAS 39 Gripens (eight single-seat JAS 39C and four JAS 39D two-seaters).[197] It had six JAS 39s, including four JAS 39Cs, and two JAS 39Ds in use As of January 2013.[142] Nine were delivered in April 2013,[198] and another three in September 2013.[198] On 18 October 2013, the Thai government announced its intention to purchase another six Gripens.[199]
701 Fighter Squadron
 United Kingdom
The Empire Test Pilots' School operates Gripens for training. ETPS instructor pilots and students undergo simulator training with the Swedish Air Force, and go on to fly the two-seater Gripen at Saab in Linköping, in two training campaigns per year (Spring and Autumn). The agreement was renewed in 2008.[317]

Aircraft on display

Saab JAS 39 Gripen on display at the F 7 Såtenäs wing

Accidents and incidents

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

As of July 2011, the Gripen has been involved in eight incidents, including five hull-loss accidents, with no loss of life.[319]

The first two crashes, in 1989 and 1993 respectively, occurred during public displays of the Gripen and resulted in considerable negative media reports. The first crash was filmed by a Sveriges Television news crew and led to calls from previous critics of the project to cancel development altogether.[320] The second crash occurred in an empty area on the island of Långholmen during the 1993 Stockholm Water Festival with tens of thousands of spectators present. The decision to display the Gripen over large crowds was publicly criticised, and was compared to the 1989 crash.[321][322] Both the 1989 and 1993 crashes were related to flight control software issues.[323]

Specifications (JAS 39C/D Gripen)

JAS39 Gripen.svg
Side-view of circular aircraft engine exhaust nozzle, showing two distinct layers
Gripen engine nozzle
External image
image icon A detailed and labeled cutaway drawing of the Gripen from Saab[324]

Data from Spick 2000, p. 431; Williams 2003, p. 90; Saab,[325][326] Czech Air Force.[327]

General characteristics

  • Crew: 1 (2 for JAS 39D)
  • Payload: 5,300 kg (11,700 lb)
  • Length: 14.1 m (46 ft 3 in); two-seater: 14.8 m (48 ft 5 in)
  • Wingspan: 8.4 m (27 ft 7 in)
  • Height: 4.5 m (14 ft 9 in)
  • Wing area: 30.0 m² (323 ft²)
  • Empty weight: 6,800 kg[325] (14,990 lb)
  • Loaded weight: 8,500 kg (18,700 lb)
  • Max. takeoff weight: 14,000 kg (31,000 lb)
  • Powerplant: 1 × Volvo RM12 afterburning turbofan
    • Dry thrust: 54 kN (12,100 lbf)
    • Thrust with afterburner: 80.5 kN (18,100 lbf)
  • Wheel track: 2.4 m (7 ft 10 in)

Performance

Armament

See also

Related lists

References

Notes

  1. 1.0 1.1 Comprising 204 (30 Batch I, 110 Batch II, 64 Batch III) Gripens delivered to Sweden, 26 to South Africa, and 12 to Thailand. This figure does not include those of the Empire Test Pilots School, or Czech and Hungarian Gripens, with the latter two having received ex-Swedish Air Force aircraft. Five development aircraft were built.[6]
  2. The Defense Material Agency reported 99 billion Swedish krona for the program between 1982 and 2009, including expenses for weapons and simulators.[1]
  3. IHS Jane's reports the unit cost as between US$50 and $60 million (2008 dollars).[2]
  4. Literally "the Griffin", as the names of Swedish combat aircraft, like Viggen or Draken, are in the definite form.
  5. Griffin is the animal[22] on the coat of arms of Östergötland, the province in which Saab AB is headquartered (Linköping).[23]

Citations

  1. 1.0 1.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. Nilsson 2012.
  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. Frawley 2002, p. 147.
  8. Altaya 2011, Características especiais: 'O Gripen foi concebido conforme as diretivas da força aérea sueca – a Base 90 – que previa a utilização de pistas rudimentares de 800 m de comprimento e 9 m de largura… [The Gripen was conceived according to the Base 90 Swedish Air Force directives that foresaw the use of rudimentary runways 800 m long and 9 m wide…]'
  9. Spick 2000, pp. 426–27.
  10. Björeman 2009, pp. 139–49.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. 12.0 12.1 12.2 12.3 Williams 2003, p. 72.
  13. Green & Swanborough 1987, p. 225.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. 15.0 15.1 15.2 15.3 15.4 Williams 2003, p. 73.
  16. 16.0 16.1 Cross 1986, p. 27.
  17. 17.0 17.1 Lua error in package.lua at line 80: module 'strict' not found.
  18. Williams 2003, pp. 73, 88.
  19. Keijsper 2003, p. 12.
  20. Flight International 1983, p. 64.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Winchester 2004, p. 216.
  25. Flight International 1988, p. 3.
  26. Gaines 1989, p. 4.
  27. Flight International 1989, p. 3.
  28. Keijsper 2003, pp. 12, 21.
  29. 29.0 29.1 Matláry & Ø̈sterud 2007, p. 150.
  30. 30.0 30.1 30.2 30.3 30.4 30.5 30.6 Williams 2003, p. 88.
  31. Forsberg 1994, p. 223.
  32. Altaya 2011, Diversas versões ¶1a: "A necessidade de adaptar o Gripen às especificidades da Otan, para estimular as vendas no estrangeiro, levou ao desenvolvimento de uma nova versão chamada 'Turbo Gripen'. [The need to adapt the Gripen to the Otan specificities, to stimulate foreign sales, led to the development of a new version called 'Turbo Gripen'.]"
  33. 33.0 33.1 33.2 Lua error in package.lua at line 80: module 'strict' not found.
  34. Lorell 2002, p. 147.
  35. 35.0 35.1 Eliasson 2010, p. 256.
  36. Lorell 2002, pp. 147–48.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. 39.0 39.1 Lua error in package.lua at line 80: module 'strict' not found.
  40. 40.0 40.1 Lua error in package.lua at line 80: module 'strict' not found.
  41. 41.0 41.1 Lua error in package.lua at line 80: module 'strict' not found.
  42. 42.0 42.1 Lua error in package.lua at line 80: module 'strict' not found.
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. Björeman 2009, pp. 137–49.
  45. Brändström 2003, pp. 61, 72.
  46. Brändström 2003, pp. 57–62.
  47. Brändström 2003, pp. 58–62, 72–73.
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. 49.0 49.1 Lua error in package.lua at line 80: module 'strict' not found.
  50. Lua error in package.lua at line 80: module 'strict' not found.
  51. Lua error in package.lua at line 80: module 'strict' not found.
  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. 54.0 54.1 Lua error in package.lua at line 80: module 'strict' not found.
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. 56.0 56.1 Lua error in package.lua at line 80: module 'strict' not found.
  57. Lua error in package.lua at line 80: module 'strict' not found.
  58. Lua error in package.lua at line 80: module 'strict' not found.
  59. 59.0 59.1 59.2 Lua error in package.lua at line 80: module 'strict' not found.
  60. 60.0 60.1 60.2 Lua error in package.lua at line 80: module 'strict' not found.
  61. Lua error in package.lua at line 80: module 'strict' not found.
  62. Lua error in package.lua at line 80: module 'strict' not found..
  63. Lua error in package.lua at line 80: module 'strict' not found.
  64. 64.0 64.1 Lua error in package.lua at line 80: module 'strict' not found.
  65. 65.0 65.1 Lua error in package.lua at line 80: module 'strict' not found.
  66. Lua error in package.lua at line 80: module 'strict' not found.
  67. 67.0 67.1 Lua error in package.lua at line 80: module 'strict' not found.
  68. Lua error in package.lua at line 80: module 'strict' not found..
  69. 69.0 69.1 Lua error in package.lua at line 80: module 'strict' not found.
  70. 70.0 70.1 70.2 Lua error in package.lua at line 80: module 'strict' not found.
  71. 71.0 71.1 Lua error in package.lua at line 80: module 'strict' not found.
  72. Lua error in package.lua at line 80: module 'strict' not found.
  73. 73.0 73.1 Lua error in package.lua at line 80: module 'strict' not found.
  74. Lua error in package.lua at line 80: module 'strict' not found.
  75. Lua error in package.lua at line 80: module 'strict' not found.
  76. 76.0 76.1 Lua error in package.lua at line 80: module 'strict' not found.
  77. 77.0 77.1 77.2 Lua error in package.lua at line 80: module 'strict' not found.
  78. Lua error in package.lua at line 80: module 'strict' not found.
  79. Lua error in package.lua at line 80: module 'strict' not found.
  80. 80.0 80.1 Lua error in package.lua at line 80: module 'strict' not found.
  81. 81.0 81.1 Mader 2015: ‘One of the ideas, once we have that F-model […] is that the future market will need a dedicated electronic-attack version…’
  82. Lua error in package.lua at line 80: module 'strict' not found..
  83. Lindqvist & Widfeldt 2003, pp. 50–60, 133–37.
  84. 84.0 84.1 84.2 84.3 84.4 84.5 84.6 84.7 Lua error in package.lua at line 80: module 'strict' not found.
  85. Green & Swanborough 1987, pp. 227–28.
  86. Williams 2003, pp. 81–82.
  87. Lua error in package.lua at line 80: module 'strict' not found..
  88. 88.0 88.1 88.2 Eliasson 2010, p. 125.
  89. Lua error in package.lua at line 80: module 'strict' not found.
  90. Lua error in package.lua at line 80: module 'strict' not found.
  91. Lua error in package.lua at line 80: module 'strict' not found.
  92. Henk 2006, p. 73.
  93. Lua error in package.lua at line 80: module 'strict' not found.
  94. 94.0 94.1 Lua error in package.lua at line 80: module 'strict' not found.
  95. 95.0 95.1 Lua error in package.lua at line 80: module 'strict' not found.
  96. 96.0 96.1 Frédriksen 2001, p. 280.
  97. Frisberg 1998, p. 288.
  98. 98.0 98.1 98.2 Lua error in package.lua at line 80: module 'strict' not found.
  99. 99.0 99.1 99.2 Lua error in package.lua at line 80: module 'strict' not found.
  100. Eliasson 2010, p. 126.
  101. Lua error in package.lua at line 80: module 'strict' not found.
  102. Lake 2008, p. 2.
  103. Williams 2003, p. 74.
  104. Signal 1994, p. 32.
  105. Lua error in package.lua at line 80: module 'strict' not found.
  106. Lua error in package.lua at line 80: module 'strict' not found.
  107. Lua error in package.lua at line 80: module 'strict' not found.
  108. 108.0 108.1 Lua error in package.lua at line 80: module 'strict' not found.
  109. 109.0 109.1 Lua error in package.lua at line 80: module 'strict' not found.
  110. Lua error in package.lua at line 80: module 'strict' not found..
  111. Lua error in package.lua at line 80: module 'strict' not found.
  112. Lua error in package.lua at line 80: module 'strict' not found.
  113. 113.0 113.1 113.2 Lua error in package.lua at line 80: module 'strict' not found.
  114. 114.0 114.1 Lua error in package.lua at line 80: module 'strict' not found.
  115. Lua error in package.lua at line 80: module 'strict' not found.
  116. 116.0 116.1 Larsson & Ekrot 2010, p. 1.
  117. Larsson & Ekrot 2010, pp. 2, 4.
  118. Flight International 1994, p. 15.
  119. 119.0 119.1 Lua error in package.lua at line 80: module 'strict' not found.
  120. Lua error in package.lua at line 80: module 'strict' not found.
  121. Lua error in package.lua at line 80: module 'strict' not found.
  122. Lua error in package.lua at line 80: module 'strict' not found.
  123. Lua error in package.lua at line 80: module 'strict' not found.
  124. Lua error in package.lua at line 80: module 'strict' not found.
  125. Lua error in package.lua at line 80: module 'strict' not found.
  126. Lua error in package.lua at line 80: module 'strict' not found.
  127. Lua error in package.lua at line 80: module 'strict' not found..
  128. Lua error in package.lua at line 80: module 'strict' not found.
  129. Lua error in package.lua at line 80: module 'strict' not found.
  130. Lua error in package.lua at line 80: module 'strict' not found.
  131. Spick 2000, p. 426.
  132. 132.0 132.1 Williams 2003, p. 82.
  133. Chant & Taylor 1999, p. 48.
  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. Elliott 1993, p. 30.
  138. Keijsper 2003, p. 30.
  139. Eden 2004, p. 390.
  140. Spick 2000, p. 431.
  141. Lua error in package.lua at line 80: module 'strict' not found.
  142. 142.0 142.1 142.2 142.3 142.4 142.5 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.
  146. Lua error in package.lua at line 80: module 'strict' not found.
  147. Lua error in package.lua at line 80: module 'strict' not found.
  148. Lua error in package.lua at line 80: module 'strict' not found.
  149. Lua error in package.lua at line 80: module 'strict' not found.
  150. 150.0 150.1 Lua error in package.lua at line 80: module 'strict' not found.
  151. Lua error in package.lua at line 80: module 'strict' not found..
  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. Lua error in package.lua at line 80: module 'strict' not found.
  156. Lua error in package.lua at line 80: module 'strict' not found.
  157. Lua error in package.lua at line 80: module 'strict' not found.
  158. Spreen 2007, p. 77.
  159. Lua error in package.lua at line 80: module 'strict' not found.
  160. Lua error in package.lua at line 80: module 'strict' not found.
  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. 163.0 163.1 163.2 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. Lua error in package.lua at line 80: module 'strict' not found..
  168. Lua error in package.lua at line 80: module 'strict' not found..
  169. Lua error in package.lua at line 80: module 'strict' not found.
  170. Lua error in package.lua at line 80: module 'strict' not found.
  171. Larrabee 2003, p. 24.
  172. Stohl & Grillot 2009, p. 46.
  173. 173.0 173.1 Larrabee 2003, p. 25.
  174. Lua error in package.lua at line 80: module 'strict' not found.
  175. Lua error in package.lua at line 80: module 'strict' not found.
  176. Lua error in package.lua at line 80: module 'strict' not found.
  177. Lua error in package.lua at line 80: module 'strict' not found.
  178. Lua error in package.lua at line 80: module 'strict' not found.
  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. Eliasson 2010, p. 256: 'BAe/Saab & the South African government signed a contract to produce 26 Gripen C & D aircraft (the export version), including additional modifications for the South African version & support systems (logistics, ILS &c).'
  183. 183.0 183.1 Lua error in package.lua at line 80: module 'strict' not found.
  184. Lua error in package.lua at line 80: module 'strict' not found.
  185. Lua error in package.lua at line 80: module 'strict' not found.
  186. Lua error in package.lua at line 80: module 'strict' not found.
  187. Lua error in package.lua at line 80: module 'strict' not found.
  188. Lua error in package.lua at line 80: module 'strict' not found..
  189. Lua error in package.lua at line 80: module 'strict' not found.
  190. Lua error in package.lua at line 80: module 'strict' not found.
  191. Lua error in package.lua at line 80: module 'strict' not found.
  192. 192.0 192.1 192.2 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. Acharya 2009, p. 163.
  196. Lua error in package.lua at line 80: module 'strict' not found.
  197. 197.0 197.1 Lua error in package.lua at line 80: module 'strict' not found.
  198. 198.0 198.1 198.2 Lua error in package.lua at line 80: module 'strict' not found.
  199. 199.0 199.1 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. 201.0 201.1 201.2 Cavas 2015: ‘Seven air forces operate or are committed to operating Gripens, along with one British Gripen D test aircraft. […] ″We know Colombia is going to replace their Kfir fleet, we've had questions from them,″ Ahlqvist said’
  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. Lua error in package.lua at line 80: module 'strict' not found..
  205. 205.0 205.1 205.2 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. Lua error in package.lua at line 80: module 'strict' not found.
  209. Lua error in package.lua at line 80: module 'strict' not found.
  210. Lua error in package.lua at line 80: module 'strict' not found.
  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. 213.0 213.1 Lua error in package.lua at line 80: module 'strict' not found.
  214. 214.0 214.1 Lua error in package.lua at line 80: module 'strict' not found..
  215. 215.0 215.1 Jasper & Rolander 2014: 'A carrier version of the plane may be an option for Brazil, with Argentina, Ecuador and Mexico among possible export targets.'
  216. Lua error in package.lua at line 80: module 'strict' not found.
  217. Lua error in package.lua at line 80: module 'strict' not found.
  218. 218.0 218.1 218.2 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. Lua error in package.lua at line 80: module 'strict' not found.
  221. Lua error in package.lua at line 80: module 'strict' not found.
  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. 227.0 227.1 227.2 Jennings 2013: 'the deal for 36 aircraft for the Brazilian Air Force "opens up a whole new realm of possibilities" for the Sea Gripen, with the Navy having a notional requirement for 24 aircraft to operate from its São Paulo aircraft carrier. […] discussions with India have been taking place behind the scenes. "There has been a conversation with the Indian Navy, which is looking at the Sea Gripen separate to the [Indian Air Force] MMRCA [Medium MultiRole Combat Aircraft requirement]," he said, adding: "The Indian Navy [interest in Sea Gripen] never went away."'
  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. Lua error in package.lua at line 80: module 'strict' not found.
  233. Lua error in package.lua at line 80: module 'strict' not found.
  234. Lua error in package.lua at line 80: module 'strict' not found.
  235. Lua error in package.lua at line 80: module 'strict' not found.. Archived February 26, 2014 at the Wayback Machine
  236. Lua error in package.lua at line 80: module 'strict' not found.. Archived April 29, 2014 at the Wayback Machine
  237. Lua error in package.lua at line 80: module 'strict' not found..
  238. Lua error in package.lua at line 80: module 'strict' not found.
  239. Lua error in package.lua at line 80: module 'strict' not found.
  240. Lua error in package.lua at line 80: module 'strict' not found.
  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. Lua error in package.lua at line 80: module 'strict' not found.
  244. Lua error in package.lua at line 80: module 'strict' not found.
  245. Lua error in package.lua at line 80: module 'strict' not found.
  246. Lua error in package.lua at line 80: module 'strict' not found.
  247. Lua error in package.lua at line 80: module 'strict' not found.
  248. Lua error in package.lua at line 80: module 'strict' not found.
  249. Lua error in package.lua at line 80: module 'strict' not found.
  250. Lua error in package.lua at line 80: module 'strict' not found.
  251. Lua error in package.lua at line 80: module 'strict' not found.
  252. Lua error in package.lua at line 80: module 'strict' not found.
  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. Lua error in package.lua at line 80: module 'strict' not found.
  259. Lua error in package.lua at line 80: module 'strict' not found.
  260. Lua error in package.lua at line 80: module 'strict' not found..
  261. 261.00 261.01 261.02 261.03 261.04 261.05 261.06 261.07 261.08 261.09 261.10 261.11 261.12 261.13 261.14 261.15 261.16 Jennings 2015.
  262. Lua error in package.lua at line 80: module 'strict' not found..
  263. 263.0 263.1 263.2 263.3 263.4 263.5 263.6 263.7 263.8 263.9 Jennings 2014.
  264. Lua error in package.lua at line 80: module 'strict' not found..
  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. Lua error in package.lua at line 80: module 'strict' not found.
  268. Lua error in package.lua at line 80: module 'strict' not found.
  269. Lua error in package.lua at line 80: module 'strict' not found.
  270. Lua error in package.lua at line 80: module 'strict' not found..
  271. Lua error in package.lua at line 80: module 'strict' not found.
  272. Lua error in package.lua at line 80: module 'strict' not found.
  273. Lua error in package.lua at line 80: module 'strict' not found.
  274. Lua error in package.lua at line 80: module 'strict' not found..
  275. Lua error in package.lua at line 80: module 'strict' not found.
  276. Lua error in package.lua at line 80: module 'strict' not found..
  277. Lua error in package.lua at line 80: module 'strict' not found.
  278. Lua error in package.lua at line 80: module 'strict' not found.
  279. Lua error in package.lua at line 80: module 'strict' not found.
  280. Lua error in package.lua at line 80: module 'strict' not found.
  281. Lua error in package.lua at line 80: module 'strict' not found.
  282. Lua error in package.lua at line 80: module 'strict' not found.
  283. Lua error in package.lua at line 80: module 'strict' not found.
  284. Lua error in package.lua at line 80: module 'strict' not found.
  285. Lua error in package.lua at line 80: module 'strict' not found.
  286. Lua error in package.lua at line 80: module 'strict' not found.
  287. Lua error in package.lua at line 80: module 'strict' not found.
  288. Lua error in package.lua at line 80: module 'strict' not found.
  289. Lua error in package.lua at line 80: module 'strict' not found.
  290. Lua error in package.lua at line 80: module 'strict' not found.
  291. Lua error in package.lua at line 80: module 'strict' not found.
  292. Lua error in package.lua at line 80: module 'strict' not found.
  293. Lua error in package.lua at line 80: module 'strict' not found.
  294. Lua error in package.lua at line 80: module 'strict' not found.
  295. Lua error in package.lua at line 80: module 'strict' not found.
  296. Lua error in package.lua at line 80: module 'strict' not found.
  297. Lua error in package.lua at line 80: module 'strict' not found.
  298. 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. Lua error in package.lua at line 80: module 'strict' not found.
  301. Lua error in package.lua at line 80: module 'strict' not found.
  302. Lua error in package.lua at line 80: module 'strict' not found.
  303. Lua error in package.lua at line 80: module 'strict' not found.
  304. Lua error in package.lua at line 80: module 'strict' not found.
  305. Lua error in package.lua at line 80: module 'strict' not found..
  306. Lua error in package.lua at line 80: module 'strict' not found.
  307. Lua error in package.lua at line 80: module 'strict' not found.
  308. Lua error in package.lua at line 80: module 'strict' not found.
  309. Lua error in package.lua at line 80: module 'strict' not found.
  310. Eliasson 2010, p. 256: '…this involved modifying the JAS 39 Gripen aircraft to NATO standards and for in‐flight refueling.'
  311. Lua error in package.lua at line 80: module 'strict' not found..
  312. Lua error in package.lua at line 80: module 'strict' not found..
  313. Coelho 2014.
  314. Lua error in package.lua at line 80: module 'strict' not found.
  315. Lua error in package.lua at line 80: module 'strict' not found..
  316. Lua error in package.lua at line 80: module 'strict' not found.
  317. Lua error in package.lua at line 80: module 'strict' not found.
  318. Lua error in package.lua at line 80: module 'strict' not found.
  319. Lua error in package.lua at line 80: module 'strict' not found. Note page has two entries for the 31 May 2010 accident with the same serial number.
  320. Brändström 2003, pp. 17–18, 23–24.
  321. Brändström 2003, pp. 5–6.
  322. Lua error in package.lua at line 80: module 'strict' not found.
  323. Eden 2004, p. 389.
  324. Lua error in package.lua at line 80: module 'strict' not found..
  325. 325.0 325.1 Lua error in package.lua at line 80: module 'strict' not found.
  326. Lua error in package.lua at line 80: module 'strict' not found.
  327. Lua error in package.lua at line 80: module 'strict' not found.

Bibliography

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

External links

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