Meteor (missile)
| Company type | Private |
|---|---|
| Industry | Defence |
| Headquarters | Europe |
| Products | Meteor (air-to-air missile) |
Meteor is a European-developed beyond-visual-range air-to-air missile (BVRAAM) produced by MBDA. It possesses multi-shot capabilities and can engage highly agile targets such as jet fighters, UAVs, and cruise missiles, even under intense electronic countermeasure (ECM) conditions, with an operational range exceeding .
The missile is propelled by a solid-fuel ramjet engine, enabling it to sustain speeds above Mach 4, which provides continuous thrust and acceleration during mid-course flight. A two-way data link facilitates mid-flight updates or retargeting from the launch platform using information from multiple sources. This communication channel also relays missile status and target acquisition data. According to MBDA, Meteor delivers kinetic performance three to six times greater than similar air-to-air missiles. It incorporates both proximity and impact fusing systems to enhance its lethality and reliability.
Created through a collaborative European program, Meteor was introduced into service with the Swedish Air Force’s Saab JAS 39 Gripen in April 2016, reaching initial operational capability by July of the same year. It is also deployed on the Dassault Rafale aircraft of the French Air and Space Force and Navy, as well as on Eurofighter Typhoons operated by the Royal Air Force, German Air Force, Italian Air Force, and Spanish Air Force. Plans are underway to integrate the missile onto British and Italian F-35 Lightning II platforms. Additionally, Meteor has been exported to various operators of Rafale, Typhoon, and Gripen aircraft.
Requirement
The development of Meteor was driven by the UK’s Staff Requirement (Air) 1239 (SR(A)1239), which called for a Future Medium Range Air-to-Air Missile (FMRAAM) intended to replace the Royal Air Force’s Skyflash missiles. Serving as Eurofighter’s principal air-to-air armament, Meteor is designed to engage both fixed-wing and rotary-wing aircraft, including unmanned aerial vehicles and cruise missiles.
Although specific performance details remain classified, the missile was required to achieve launch success zones and no-escape envelopes nearly twice as large as those of the then-leading AMRAAM missile. Its design had to accommodate Eurofighter’s semi-recessed underfuselage launchers originally tailored for AMRAAM deployment. Essential requirements included stealthy launch characteristics, superior kinematic performance for intercepting highly maneuverable targets, strong resistance against countermeasures, and enabling rapid disengagement of the launching aircraft to enhance survivability. These criteria were influenced by threats posed by advanced Russian Su-27 "Flanker" fighters armed with extended-range ramjet-powered R-77 missiles.
Competition
In February 1994, the UK Ministry of Defence released a Request for Information (RFI) seeking proposals for an advanced medium-range air-to-air missile. Four propulsion concepts combining rocket and ramjet technologies were submitted:
- S225XR developed by British Aerospace (BAe), Alenia Difesa, GEC-Marconi, and Saab Dynamics.
- A derivative of the MICA missile from Matra.
- Advanced Air-to-Air Missile (A3M) from Daimler-Benz Aerospace and Bayern-Chemie.
- An AMRAAM-based design from Hughes.
The formal competition commenced in June 1995 as the UK, France, and Germany aimed to harmonize their requirements and establish a joint industrial partnership, framing the contest as a European alternative to US offerings.
The US government consented to transfer advanced propulsion technology development responsibilities to the UK in support of Hughes’ bid. Hughes initially proposed a variable-flow ducted rocket (VFDR) system developed by Atlantic Research Corporation (ARC)/Alliant Techsystems; however, the United States Air Force did not intend to extend AMRAAM’s range so as not to conflict with support for the F-22 Raptor program. ARC also engaged with BAe regarding VFDR integration into S225XR and held discussions with Bayern Chemie and Volvo. Furthermore, ARC negotiated with Royal Ordnance—the only UK company capable of ramjet development after Rolls-Royce discontinued its efforts.
In December 1995, the UK Ministry of Defence issued an Invitation to Tender (ITT) valued at £800 million with submissions due by June 1996. By February 1996, the US team had been organized while European efforts remained somewhat fragmented.
European proposal
Matra and DASA's missile division (LFK) were on the verge of a collaborative bid, which was also under consideration by BAe and Alenia. Their joint offering was derived from Matra's MICA-Rustique initiative, utilizing a self-regulating solid-fuel ramjet. In 1996, Matra and BAE merged their missile operations to create Matra BAe Dynamics (MBD). The finalized European consortium—comprising BAe Dynamics, Matra Defense, Alenia Difesa, GEC-Marconi, Saab Dynamics, LFK, and Bayern-Chemie—was assembled just six weeks before the 11 June 1996 submission deadline. With BAe at the helm, the alliance avoided fragmentation in Europe's effort to present a viable alternative to the US missile proposal.
BAe Dynamics' initial S225XR concept lacked wings; however, following international consultations, the UK and German designs converged closely except for the German model’s inclusion of wings. The wings enhanced roll damping, beneficial for the asymmetric intake layout, leading to adoption of the German A3M winged configuration for the European missile project named Meteor.
Hughes proposal
Hughes formed a consortium including Aérospatiale (propulsion), Shorts (integration and final assembly), Thomson-Thorn Missile Electronics (TTME), Fokker Special Projects (fin actuation), and Diehl BGT Defence (warhead). Hughes supplied the seeker with electronics from its Scottish subsidiary, Hughes Micro Electronics Europa. Upgrades involved compressed guidance electronics, an electronic safe-and-arm device inspired by Diehl BGT Defence's IRIS-T system, a two-way conformal microwave proximity fuze, and a shortened control mechanism. The seeker and warhead largely remained consistent with those from AMRAAM.
To increase European involvement, Hughes replaced the ARC/ATK VFDR with an Aérospatiale-Celerg liquid-fuel ramjet featuring an ARC integrated nozzleless booster. This design utilized an inflatable elastomer bladder to regulate fuel flow, offering cost advantages over regulated liquid ramjets employing turbopumps. Approximately 80% of FMRAAM production and development activities were planned for Europe, with 72% located in the UK.
Risk reduction
Initial expectations targeted contract awards by late 1997 and first deliveries by 2005. By early 1997, however, risk assessments deemed immediate development too risky, prompting the UK's Defence Procurement Agency (DPA) and Sweden's Defence Materiel Administration (FMV) to initiate a Project Definition and Risk Reduction (PDRR) programme lasting 12 months. This phase refined designs, identified risks, and formulated mitigation strategies. PDRR contracts commenced in August 1997, followed by a second Invitation to Tender in October. By 1998, the anticipated in-service date (ISD) had slipped to 2007.
In July 1997, the UK Ministry of Defence convened a government-level briefing with Italy, Germany, and Sweden to discuss joint BVRAAM procurement efforts. Funding arrangements for risk-reduction contracts remained unsettled; some nations were proposed to contribute financially in exchange for data access.
The European consortium aimed for Meteor adoption by Germany, Italy, Sweden, and France if selected by the UK. Germany introduced more stringent requirements that led DASA/LFK to propose Euraam—a variant of A3M incorporating advanced seeker and propulsion technologies designed to counter electronic countermeasures and enhance target accuracy. DASA sought governmental approval for a two-year demonstration culminating in flight tests as a contingency if the UK favored Raytheon's submission.
Updated bids were delivered on 28 May 1998. US Secretary of Defense William Cohen assured the UK that acquiring Raytheon's missile would not impose export restrictions affecting Eurofighter exports; he promised "open and complete technology transfer" and suggested forming a joint commission to oversee approvals involving sensitive countries.
In July 1998, the UK, Germany, Italy, Sweden, and Spain signed a statement of intent for collaborative missile procurement contingent upon UK selection of Meteor.
By September 1998, Raytheon provided cost estimates for AIM-120B AMRAAMs as interim armaments on Tornado and Eurofighter platforms during BVRAAM development but declined sales of the improved AIM-120C variant. This reflected Raytheon's incremental approach to gradually introduce FMRAAM capabilities.
Raytheon's phased plan included the Extended Range Air-to-Air Missile (ERAAM), which combined FMRAAM seeker and guidance systems with a dual-pulse solid rocket motor. ERAAM promised readiness aligned with Eurofighter's 2004 ISD while delivering approximately 80% of FMRAAM capability at half its cost—an attractive option given MoD budget constraints and diminished urgency from R-77 threats. Subsequent upgrades could integrate thrust vectoring, hybrid fuels, and ramjet propulsion.
Meteor's team considered an interim dual-pulse rocket option but chose to pursue a fully compliant design outright, viewing staged enhancements as potentially more expensive than Raytheon suggested.
In February 1999, Raytheon introduced AIM-120B+, combining FMRAAM seeker/guidance with AIM-120B propulsion—ready for Eurofighter’s 2004 ISD with upgrade potential to ERAAM or FMRAAM configurations through propulsion swaps and software updates.
At the 1999 Paris Air Show, France expressed interest in joining Meteor development, proposing up to 20% funding contingent on Meteor winning the UK competition. France formally joined the programme in September 1999.
In July 1999, Sweden announced withdrawal from Meteor funding due to budget limitations but maintained participation through alternative financing avenues.
Political pressure escalated when US President Bill Clinton wrote to UK Prime Minister Tony Blair in August 1999 emphasizing transatlantic defence industry collaboration for interoperability. Clinton reaffirmed support for Raytheon's bid in February 2000 amidst lobbying from French, German, and Spanish officials.
Late in 1999 Raytheon proposed ERAAM+, merging US AMRAAM and UK BVRAAM programmes under joint management for Eurofighter, JSF, and F-22 platforms. ERAAM+ promised delivery by 2007 at less than half BVRAAM’s projected cost. The UK would gain substantial development roles plus access to the larger US air-to-air missile market estimated at roughly 15,000 units over fifteen years.
Although ERAAM’s dual-pulse motor did not fully satisfy SR(A)1239 specifications, it was considered adequate until improvements became available around 2012–2015. The slow progress of Russia’s ramjet R-77 variant supported postponing a full-spec missile introduction.
To counter Raytheon's transatlantic bid effort, Boeing joined the European consortium offering expertise in aircraft integration, risk management practices, lean manufacturing processes, marketing strategies, and US Department of Defense relations—critical factors for potential US adoption of Meteor. Initially interested in developing a SEAD variant as a HARM successor platform, Boeing's involvement diminished as development advanced.
By late 1999 Sweden rejoined Meteor participation. Both consortia submitted final bids by early 2000 with an expected award decision in March following MoD Equipment Approvals Committee deliberations on 21 February. However, last-minute Treasury concerns over Meteor’s cost compared with Raytheon's less expensive incremental strategy delayed final selection.
Decision
In May 2000, the UK Secretary of State for Defence, Geoff Hoon, declared Meteor as the chosen missile to fulfill SR(A)1239 requirements. Fabrice Bregier, then CEO of MBD, remarked, "This selection represents a landmark achievement in creating a European defence capability. For the first time, European fighter jets will be equipped with a domestically developed air-to-air missile, enhancing interoperability and enabling independent exports." At that point, the planned In Service Date was established for 2008.
The Defence Select Committee of the British House of Commons identified several key factors influencing the choice: Meteor provided a superior military option compared to the Raytheon alternative, supported the unification of Europe's missile industry, served as a counterbalance to US market dominance, and imposed fewer export limitations on Eurofighter. The programme aimed to avoid pitfalls experienced in previous European projects by removing arbitrary workshare allocations and ensuring definitive UK leadership. The Ministry of Defence was encouraged to sustain progress through early contracts that would secure partner commitments. Although conservative, the target in-service date was essential for Eurofighter’s operational prospects.
Despite Meteor’s selection, Raytheon retained UK orders for AIM-120 missiles to equip Eurofighter during its initial deployment before Meteor’s completion.
Pre-contract
In 2001, Matra BAe Dynamics merged with EADS' Aerospatiale Matra Missiles and Alenia Marconi Systems’ missile division to establish MBDA, which became the world’s second-largest missile manufacturer after Raytheon.
Negotiations for contracts proceeded, culminating at the 2001 Paris Air Show where defence ministers from France, Sweden, and the UK signed a Memorandum of Understanding endorsing Meteor. Germany, Italy, and Spain expressed intent but postponed formal agreements due to their procurement processes; Italy finalized its commitment in September 2001 and Spain followed in December 2001.
Germany’s financial contribution was vital but delayed by over two years due to repeated funding rejections by its defence budget committee. During this interval, MBDA financed Meteor’s development internally, investing approximately £70 million by June 2002—primarily allocated to Bayern-Chemie for propulsion risk mitigation. Germany stipulated that the UK must place a contract and MBDA guarantee performance; both conditions were fulfilled by April 2002. Ultimately, Germany authorized funding in December 2002 but reduced its planned missile procurement from 1,488 to 600 units.
Seeker
The missile’s terminal guidance employs an active radar homing seeker developed collaboratively by MBDA's Seeker Division and Thales Airborne Systems. This design builds upon their joint work on the AD4A seeker family used in MICA and Aster missiles.
Forebody
The active radar proximity fuze subsystem (PFS), provided by Saab Bofors Dynamics since 2003, is responsible for target detection and calculating optimal detonation timing to maximize warhead effectiveness. The PFS incorporates four antennae arranged symmetrically around the body and contains the Impact Sensor. Positioned behind it are thermal batteries supplied by ASB, along with the AC Power Supply Unit and the Power and Signal Distribution Unit.
Warhead
The blast-fragmentation warhead, manufactured by TDW, also functions as an integral structural element of the missile.
Propulsion
The propulsion sub-system (PSS) employs a throttleable ducted rocket (TDR) combined with an integrated nozzleless booster, developed and produced by Bayern-Chemie. This arrangement provides extended range, consistently high speeds, a wide operational range from sea level to high altitudes, and adaptable mission capabilities through active variable thrust management. Its design offers logistical advantages over traditional solid-fuel rocket engines. The PSS serves as a load-bearing missile component, featuring a steel-cased gas generator and ramcombustor; the propulsion control electronics are installed within the port intake fairing ahead of the fin actuation mechanism.
The PSS consists of four primary elements:
- Ramcombustor with built-in nozzleless booster: the solid propellant booster accelerates the missile to velocities sufficient for TDR activation; its low-smoke propellant conforms to STANAG 6016 standards.
- Titanium air intakes: sealed during the boost phase by port covers.
- Interstage section: contains the Motor Safety Ignition Unit (MSIU), booster igniter, and gas generator control valve.
- Gas generator: ignited by hot gases from the booster through an open control valve; it contains oxygen-deficient composite solid propellant that produces hot, fuel-rich gases which auto-ignite upon mixing with air. The boron-enriched propellant increases specific impulse threefold compared to standard solid motors, extending the no-escape zone to more than triple that of the AIM-120 AMRAAM.
Thrust modulation is achieved via a valve that adjusts the gas generator nozzle throat diameter; reducing throat size elevates pressure and burn rate, thereby increasing fuel flow into the ramcombustor. This mass flow is continuously variable over a range exceeding 10:1.
Control
The Meteor missile's flight path is controlled aerodynamically by four fins positioned at the rear, engineered to allow rapid maneuvering while preserving propulsion efficiency. The fin actuation subsystem (FAS), located behind the intake fairings, includes intricate linkages connecting actuators to fins mounted on the missile body.
Initially created by the Claverham Group, responsibility for FAS development later passed to MBDA UK and subsequently to Spanish firm SENER, which finalized its development, certification, and prototype manufacturing.
Datalink
Meteor incorporates a "network-enabled" datalink enabling mid-course target updates or retargeting from either the launch platform or external sources. The datalink electronics reside within the starboard intake fairing, with its antenna positioned at the rear. Aircraft such as Eurofighter and Gripen utilize two-way datalinks to update target information during flight. This system transmits kinematic data and signals when the seeker locks onto a target.
Testing performed by Bayern-Chemie in 1996 demonstrated that signal attenuation caused by the missile’s boron-rich exhaust plume was considerably less than expected, alleviating concerns regarding interference with ramjet propulsion.
Support
Meteor utilizes an Integrated Logistics Support approach that removes the need for line maintenance; missiles are kept in specialized containers and sent back to MBDA for repairs if Built-In Test equipment identifies any issues. The missile is engineered to have a 1,000-hour airborne service life before requiring maintenance.
Orders
The comprehensive development and manufacturing phase commenced in 2003 with the UK signing a £1.2 billion contract on behalf of France, Germany, Italy, Spain, Sweden, and the UK.
Ownership shares evolved over time; Germany scaled back its purchase, transferring 5% of its share to the UK (which now holds 39.6%), while Germany retained 16%, France 12.4%, Italy 12%, and both Sweden and Spain maintained 10% each.
An Integrated Project Team (IPT) based at MoD Abbey Wood oversees the programme for all partners, reporting to UK Defence Procurement and an International Steering Committee composed of air force delegates from the partner countries.
MBDA directs execution through its entities in France, Italy, and the UK, cooperating with Bayern-Chemie/Protac (Germany), Inmize Sistemas SL (Spain), and Saab Bofors Dynamics (Sweden). More than 250 European firms contribute, with work distributed according to commercial value roughly matching national funding proportions.
The project heavily depends on computer simulations to reduce physical missile firings; initial firing from a Gripen was anticipated in 2005, with operational introduction planned by August 2012.
In December 2009, Spain approved the purchase of 100 Meteor missiles along with associated support equipment. Sweden finalized a production agreement in September 2010 aiming for deployment by 2015.
Qatar procured 160 Meteors in May 2015 for its Dassault Rafale fleet. Greece intends to equip its Rafales with Meteors; the missile officially entered Greek service in March 2023.
Although Egypt’s Rafale acquisition in 2021 did not include Meteors despite US approval since 2019, reports differ on whether Egypt later obtained Meteor missiles.
Key milestones
The UK Ministry of Defence established four critical contractual milestones for the Meteor programme; failure to meet any would obligate MBDA to reimburse development costs:
- Prove successful transition from boost to sustain propulsion.
- Demonstrate control over the asymmetric airframe, verified through computer models from Air Launched Demonstrator (ALD) tests.
- Confirm transfer alignment of the missile's inertial measurement system essential for precise navigation.
- Validate Meteor's electronic counter-countermeasures (ECCM) capabilities within MBDA’s Rome laboratory.
QinetiQ served as an independent assessor during milestone evaluations.
Development
At the Paris Air Show in 2003, MBDA awarded Bayern-Chemie/Protac a contract exceeding EUR250 million covering Meteor PSS development, initial production, and logistics support. Additionally, MBDA and Thales secured a EUR46 million deal for seeker development and initial production intended for RAF missiles.
By mid-2003, MBDA completed Meteor’s external design, eliminating mid-mounted wings based on wind tunnel results and wingless guidance experience gained from ASRAAM. The control fins were redesigned into four identical units.
In October 2003, a full-scale model underwent fit checks on the Eurofighter Typhoon across different launcher configurations. Saab Aerosystems received a contract valued at 435 million SEK from FMV for Gripen integration efforts, supported by Ericsson Microwave Systems, Saab Bofors Dynamics, and MBDA UK. Later that year, MBDA and Saab Bofors agreed on a 485 million SEK contract covering program management, system participation, software development, test equipment provision, and validation activities.
April 2004 marked successful mechanical interface testing between Meteor, Gripen’s Multi-Missile Launcher (MML), and aircraft at Saab’s Linköping facility. Aerodynamic properties and air intake functionality were confirmed through wind tunnel testing at BAE Systems (UK) and ONERA (France).
In August 2004 Bayern-Chemie delivered the first inert PSS for structural testing purposes. By summer 2005, two inert missiles were sent to Modane for free-jet trials aimed at verifying propulsion system performance under supersonic conditions ahead of ALD firings.
The inaugural Meteor flight took place on 9 September 2005 from a French Navy Rafale M at Istres Air Base. Subsequent carrier trials aboard Charles de Gaulle in December 2005 assessed missile handling under operational conditions using Ground Handling Training Missiles (GHTM) and Environmental Data Gathering (EDG) missiles.
December 2005 also saw Sweden conducting flight trials with the avionics missile (GMA5) on Gripen 39.101 to validate mechanical, electrical, and functional interfaces including two-way missile-aircraft communication—an essential step before ALD firings postponed until Spring 2006 due to limited daylight at Vidsel Test Range.
Eurofighter performed air-carry trials utilizing GHTMs to evaluate handling during maneuvers. January 2006 preparations verified system communications ahead of the first firing attempt.
The first ALD firing on 9 May 2006 from a Gripen achieved Mach 2 boost but failed transition to sustain propulsion due to timing issues in the gas generator valve control software developed by a Bayern-Chemie subcontractor. After rectification, a successful repeat firing on 20 May demonstrated sustained flight with autopilot-controlled maneuvers simulating engagement phases.
On 30 June 2006, the first flight featuring an operational seeker (SDG missile) under Gripen gathered data across varied flight conditions supporting seeker refinement towards the first guided firing planned for 2008.
The third ALD firing on 5 September 2006 successfully validated multiple flight profiles under similar launch parameters.
The UK National Audit Office’s Major Projects Report (2006) cited a delay of approximately one year postponing service entry to August 2013, primarily due to Eurofighter aircraft availability rather than missile issues. The Minister of Defence Procurement warned of potential AMRAAM shortages stemming from this delay.
On 28 April 2015, France conducted Meteor’s first guided launch from a Dassault Rafale at DGA Essais de Missiles in Biscarrosse.
On 21 April 2017, the UK government awarded MBDA a £41 million contract to integrate Meteor onto RAF Eurofighter Typhoons and F-35B Lightning IIs. RAF Typhoons completed their initial active mission carrying Meteor missiles in December 2018.
MBDA inaugurated a final assembly plant in Bolton, England in July 2018 servicing all six European partner nations.
In late May to early June 2022, Saab announced the inaugural firing of Meteor from Gripen E over Sweden’s Vidsel Test Range.
By February 2025, Meteor completed its maiden flight test on the F-35B at Naval Air Station Patuxent River using an inert missile to collect environmental data as part of integration validation.
Future Developments
MBDA aims to have the Meteor missile integrated onto the F-35 platform by 2027, specifically for the air forces of the UK and Italy. The missile is designed to fit inside the JSF's internal weapons bays and is compatible with internal air-to-ground stations; however, adapting it for air-to-air stations requires a fin modification as part of a "role change kit."
India expressed interest in incorporating the Meteor missile into its Sukhoi Su-30MKI and HAL Tejas aircraft fleets, but MBDA chose not to proceed with this integration.
Collaborative New Air-to-Air Missile Project
On 17 July 2014, MBDA UK entered an agreement to co-develop a missile derived from the Meteor in partnership with Japan. The Ministry of Defense (Japan) announced in 2016 that this Joint New Air-to-Air Missile (JNAAM) would blend British missile technology with Japanese seeker systems. The missile will employ the active electronically scanned array seeker from Mitsubishi Electric’s AAM-4B, as the AAM-4B itself is too large to fit within the Japanese F-35’s internal weapons bay.
Japan’s Ministry of Defense intends to utilize gallium nitride modules in the seeker to achieve a balance between miniaturization and performance. They are targeting an initial launch test from a British fighter jet by 2023. Funding proposals include a request for JPY1.2 billion (approximately US$11.4 million) to support JNAAM's co-development efforts with the UK.
Current Operators
- (100)
- In 2019, contracted for 100 Meteor missiles worth €200 million from MBDA, intended for deployment on the Gripen E/F.
- Equipped on the Rafale aircraft operated by the Croatian Air Force.
- (200)
- Utilized by the Egyptian Air Force on its fleet of Rafale jets, acquired alongside a second batch of 30 Rafales.
- (160)
- Operated by both the French Air and Space Force and French Naval Aviation on Rafale platforms.
- Originally ordered 200 missiles in 2011, later reduced to 100 before increasing again to 160 by 2021; all units delivered by March 2023.
- (250)
- Deployed by the German Air Force on its Eurofighter fighters.
- Initial procurement of 150 missiles in 2013, delivered between 2016 and 2018.
- Additional order of 100 missiles placed in 2019 valued at €185 million.
- Further acquisition approved in November 2024 with a budget allocation of €521 million.
- (36)
- Equipped on Rafale jets serving in the Hellenic Air Force.
- (250)
- Operated by the Indian Air Force, which has ordered 250 Meteor missiles for its fleet of Rafale aircraft.
- Employed by the Italian Air Force on their Eurofighter fighters.
- (330)
- Utilizes Meteor missiles on both Rafale and Eurofighter platforms.
- Initial order of 160 missiles placed in 2015 alongside Rafale acquisition.
- Additional purchase of 170 missiles made in 2017 concurrent with Eurofighter contracts.
- (100)
- The Spanish Air Force operates Meteors on its Eurofighter, with an approved procurement of 100 missiles since 2009.
- The Swedish Air Force employs Meteor missiles on both its current Gripen C/D models and future Gripen E/F variants.
- Signed production contracts in September 2010, followed by another order in March 2025.
- Concluded a significant arms deal including acquisition of 300 Meteor missiles alongside French Rafale F4 aircraft, plus an additional purchase of 600 Mica-NG medium- and short-range missiles featuring active radar or infrared seekers.
- Utilized by the Royal Air Force mounted on its fleet of Eurofighter jets.
- Equipped on the Royal Saudi Air Force’s fleet of Eurofighter aircraft.
Future users
- In 2019, the Republic of Korea Air Force opted to equip the KAI KF-21 Boramae fighter jet with the Meteor missile. Initial missile testing on the prototype took place in May 2024. A procurement agreement finalized in November 2024 includes 100 missiles intended for the first set of 20 KF-21 aircraft.[1][2][3]
- , and
- By the late 2020s, the Italian Navy and Royal Navy intend to incorporate the Meteor missile into their F-35B platforms. Additionally, both the Hellenic and Italian Air Forces are outfitting their F-35A squadrons with Meteor missiles.[4][5]
Prospective operators
- MBDA Deutschland is promoting integration of the Meteor missile with the F-35A for the German Air Force.
- The Hungarian Air Force has upgraded its Gripen C/D fleet to be compatible with Meteor missiles. While procurement talks were active in 2022, no definitive acquisition has been made.
- Turkey has expressed interest in obtaining the Meteor missile, contingent upon a Eurofighter Typhoon purchase.
- The Royal Thai Air Force aims to phase out its F-16A/B Block 15 ADF jets in favor of the JAS 39E/F Gripen, with potential inclusion of Meteor missile armament.
See also
- Comparable systems
- (Turkey)
External links
- MBDA: Meteor (MBDA)
- ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
- ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
- ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
- ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
- ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).