Meteor (missile)

From Wikipedia, the free encyclopedia
  (Redirected from MBDA Meteor)
Jump to: navigation, search
Meteor
ILA 2010 Samstag 125.JPG
Type Beyond visual range air-to-air missile
Service history
In service Not yet in service; development to be completed in 2013.
Production history
Manufacturer MBDA
Unit cost GBP 1,000,000 (estimated in 2003)[1]
Specifications
Weight 185 kg (407 lb)[2]
Length 3.65 m (12 ft 0 in)[2]
Diameter 0.178 m (7.0 in)
Warhead High explosive blast-fragmentation
Detonation
mechanism
Proximity/impact

Engine Throttleable ducted rocket
Operational
range
320+ km (200+ mi)[3][4][N 1]
Speed over Mach 4
Guidance
system
Inertial mid-course with datalinked updates, active radar
Launch
platform
Eurofighter Typhoon
Dassault Rafale
Saab JAS 39 Gripen
F-35 (Pending)

Meteor is an active radar guided beyond-visual-range air-to-air missile (BVRAAM) being developed by MBDA. Meteor will offer a multi-shot capability against long range manoeuvring targets in a heavy electronic countermeasures (ECM) environment.

It is intended to equip the Eurofighter Typhoons of the United Kingdom Royal Air Force (RAF), Germany's Luftwaffe, Spain's Ejército del Aire and Italy's Aeronautica Militare Italiana, British and Italian F-35s, French Dassault Rafale, and the Saab JAS 39 Gripen of the Swedish Air Force.

It is scheduled to enter service for with the RAF and with the Swedish Air Force in 2015, possibly with the SwAF as the first operator of the missile due to most testing having been done on the JAS-39.[5] According to MBDA, Meteor has three to six times the kinematic performance of current air-air missiles of its type. The key to Meteor's performance is a throttleable ducted rocket (ramjet) manufactured by Bayern-Chemie of Germany.[6]

History[edit]

From the outset, the Meteor programme has been the main catalyst for the consolidation of the European complex weapons industry. Of the seven European companies who responded to the initial Request for Information (RFI) from the UK Ministry of Defence (MoD), either individually or as part of a team, five are now part of MBDA and the other two are major risk-sharing partners on the programme. The selection of Meteor ended a long-running and hard-fought competition between Europe and the United States (US) and gained Europe a significant foothold in a market sector hitherto dominated by the U.S.

Requirement[edit]

Meteor was selected in competition to meet the UK's Staff Requirement (Air) 1239 (SR(A)1239), for a Future Medium Range Air-to-Air Missile (FMRAAM or FRAAM) to replace the RAF's BAe Dynamics Skyflash semi-active radar guided missiles. As the primary air-to-air armament of Eurofighter, the missile would be used against a range of fixed and rotary wing targets including Unmanned aerial vehicles and cruise missiles.

Although no detailed performance requirements have been publicly released, they were understood to demand launch success and no-escape zones three times greater than those of the then "state-of-the-art" medium-range missile, AMRAAM. The missile external geometry would be constrained by the need for compatibility with Eurofighter's semi-recessed underfuselage launchers which had been designed for AMRAAM.[7] Key features of the requirement included "stealthy launch, enhanced kinematics, which will provide the missile with sufficient energy to chase and destroy a highly agile manoeuvring target, robust performance in countermeasures and the ability for the launch aircraft to fire and disengage at the earliest opportunity thus enhancing aircraft survivability".[8] These requirements were largely shaped by the perceived threat posed by advanced versions of the Russian Sukhoi Su-27 "Flanker" armed with extended range ramjet powered versions of the R-77 missile.

In February 1994 the UK MoD issued an RFI on the possibility of the development of an advanced medium range air-to-air missile. Four concepts were produced in response, all using integrated rocket/ramjet propulsion. A group led by BAe, comprising Alenia Difesa, GEC-Marconi, and Saab Dynamics, proposed the S225XR; Matra proposed a derivative of MICA, although the long-planned merger of BAe Dynamics and Matra's missile division was expected to lead to the removal of this proposal; Daimler-Benz Aerospace and Bayern-Chemie proposed the Advanced Air-to-Air Missile (A3M); and Hughes, supported by the U.S. Government, proposed an AMRAAM derivative based on upgrade work being carried out.[9]

The competition commenced in June 1995 with the endorsement of SR(A)1239 by the Equipment Approvals Committee (EAC). This took place against a backdrop of government and industrial contacts between the UK, France, and Germany aimed at establishing a common requirement and an industrial consortium.[10] Even at this early stage the competition was developing into a straight fight between a European and a U.S. solution.

The U.S. Government agreed to transfer development of the advanced propulsion system to the UK in support of the Hughes bid, although it was not clear how much of the actual work would be allowed across the Atlantic.[11] Hughes' initial offering for SR(A)1239 was powered by a variable-flow ducted rocket (VFDR). This had been under development by an Atlantic Research/Alliant Techsystems team for ten years but the USAF had no plans at that time, to develop an extended range AMRAAM since this could endanger support for the stealthy F-22 Raptor. The team had also provided information to BAe who were considering the VFDR as a powerplant for the S225XR, along with systems from Bayern Chemie and Volvo. Atlantic Research had discussions with Royal Ordnance, the only UK company with the necessary capability following Rolls-Royce's decision to stop work on ramjets.

On 2 October 1995 the Minister for Defence Procurement gave approval for an Invitation to Tender (ITT), which was issued by the MoD in December. Responses were due in June 1996 for a UK contract valued at £800m. By February 1996 the U.S. team was in place whereas the European effort remained fragmented. Matra and DASA's missile division (LFK), were on the brink of a joint bid, which BAe and Alenia were also considering.[12] The Matra/LFK proposal was based on Matra's MICA-Rustique project using a Matra/ONERA designed self-regulating solid fuel ramjet. The merger between BAe and Matra's missile businesses had stalled due to the French Government's reluctance to approve the deal without UK assurances that it would adopt a more European approach to procurement. A joint winning bid for SR(A)1239 was expected to provide renewed impetus to the merger, both companies having had to restart the valuation process due to changing fortunes since the deal was first agreed, over two years previously. This was not the only merger in prospect as DASA and Aérospatiale were conducting due diligence, although Matra had also expressed an interest in Aérospatiale's missile operations. The German government was trying to use the UK and German requirements to forge the consolidation of the European industry into a critical mass capable of engaging the US on more equal terms.[13]

Hughes had assembled a team including Aérospatiale (propulsion), Shorts (integration and final assembly), Thomson-Thorn Missile Electronics (TTME), Fokker Special Projects (fin actuation), and Diehl BGT Defence (warhead). Incidentally, the adoption of FMRAAM as the name of Hughes' proposal forced the UK MoD to change the title of SR(A)1239 to BVRAAM.[14] Hughes would provide the seeker, with electronics from its Scottish subsidiary, based in Glenrothes. The upgraded guidance electronics would be compressed compared to the existing AMRAAM. Other changes included: a new electronic, as opposed to the usual mechanical, safe and arm device, based on Diehl BGT Defence's IRIS-T system; a TTME digital target detection device (a two-way conformal microwave proximity fuze unit); and a shortened control and actuation system. The seeker and warhead were basically unchanged from AMRAAM's.

The European content of Hughes' bid had been bolstered by the replacement of the ARC/ATK VFDR by an Aérospatiale-Celerg liquid-fuel ramjet with an ARC integrated nozzleless booster. This was based on studies conducted during the Simple Regulation Ramjet programme, which began in 1994.[15] The direct-injection design used an inflatable elastomer bladder within the fuel tank to control the fuel flow and was believed to offer a lower cost approach compared to a regulated liquid ramjet requiring a turbopump and associated fuel supply hardware.[16] Eighty percent of FMRAAM production and development would be carried out in Europe, 72% in the UK.[17]

The European team, consisting of BAe Dynamics, Matra Defense, Alenia Difesa, GEC-Marconi, Saab Dynamics, LFK, and BC was finally assembled just six weeks ahead of 11 June 1996 deadline for bids.[18] BAe brokered an agreement whereby it would lead the team.[19] This tie-up avoided a dangerous division in the European attempts to provide a credible alternative to the US Matra and LFK had already teamed and would have bid independently, had BAe's "shuttle diplomacy" failed, seriously denting European credibility and giving Hughes the advantage.

BAe Dynamics' original S225XR proposal was a wingless design. However, during the international discussions the evolving UK and German proposals were found to be near identical in concept apart from the latter's wings. The trade-off between winged and wingless configurations was very closely balanced but the wings offered increased roll damping which was believed to be useful given the asymmetric intake configuration so the German A3M configuration was adopted for the European proposal, called Meteor.

When the bids went in it was anticipated that a contract would be awarded at the end of 1997 with first deliveries by 2005.

Risk reduction[edit]

Following several rounds of bid clarification it was concluded in early 1997 that the risks were too high to proceed directly to development. The UK's Defence Procurement Agency (DPA) and Sweden's Defence Materiel Administration (FMV) therefore launched a Project Definition and Risk Reduction (PDRR) programme. This gave the two teams twelve months in which to refine their designs, and identify and understand the risks and how they would be mitigated. PDRR contracts were placed in August 1997 with a second ITT following in October. The results of the PDRR programme were expected in March 1998 but the procurement became ensnared in the run-up to and aftermath of the UK General Election in May 1997, as the new Labour government conducted its Strategic Defence Review. By 1998 the in-service date (ISD), defined as the first unit equipped with 72 missiles, had slipped to 2007.[20]

The UK MoD hosted a government-to-government level briefing on 14/15 July 1997 with Italy, Germany, and Sweden to discuss the BVRAAM programme and how it might meet their requirements, with the aim of pursuing a collaborative procurement.[21] There were issues at this time over the funding of the risk reduction contracts and some nations were discussing possible financial contributions to the studies in return for access to the data.

The European team hoped that, if chosen by the UK, Meteor would also be adopted by Germany, Italy, Sweden, and France. However, Germany had now formulated an even more demanding requirement.[22] In response, DASA/LFK proposed a modified A3M, called Euraam, using a DASA Ulm K-band active seeker, with a passive receiver for stealthy engagements, and a redesigned Bayern Chemie propulsion system. The high energy of the high frequency radar (compared to the I-band used on AMRAAM) was claimed to provide an ability to "burn-through" most ECM and the shorter wavelength would allow the target's position to be determined more precisely allowing the use of directional warheads. At one stage DASA was pushing their government for a two-year demonstration programme which would culminate in four unguided flight tests.[23] This was presented as a fallback position in case the UK chose Raytheon's proposal. More cynical observers regarded this as a tactic to push the UK towards Meteor.

Revised BVRAAM bids were submitted on 28 May 1998, with final reports in August. The U.S. Secretary of Defense, William Cohen, wrote to his UK counterpart, George Robertson, with assurances that procurement of the Raytheon missile would not leave the UK vulnerable to US export restrictions, which could potentially handicap Eurofighter exports, a major concern highlighted by Meteor supporters.[24] The letter assured "open and complete technology transfer", adding that FMRAAM would be cleared for countries already cleared for AMRAAM and that a joint commission could be set up to consider release to other "sensitive countries".

In July 1998 a formal statement of intent was signed between the governments of the UK, Germany, Italy, Sweden, and Spain which, subject to the UK's selection of Meteor, agreed to work towards joint procurement of the same missile.

In September 1998, Raytheon supplied the UK with estimated costs for AIM-120B AMRAAMs to be fielded on Tornado and as an interim weapon on Eurofighter on initial entry into service while BVRAAM was still in development.[25] The US declined to sell the improved AIM-120C version. This was the first stage in Raytheon's incremental approach to fielding the full capability FMRAAM. The MoD had offered both teams the opportunity to propose alternative acquisition strategies which would have involved reaching the full capability on an incremental basis by initially providing an interim capability which could later be upgraded.[26]

Raytheon's staged approach to meeting the full SR(A)1239 requirement offered an interim weapon with a capability between the AIM-120B AMRAAM and the FMRAAM. The Extended Range Air-to-Air Missile (ERAAM) had the FMRAAM seeker and guidance section mated to a dual-pulse solid propellant rocket motor. Raytheon estimated that ERAAM could be ready by the then Eurofighter ISD of 2004 and provided 80% of the FMRAAM capability but at only half the price. This approach played to perceived MoD budget limitations and a realisation that the main threat on which the SR(A)1239 requirement had been predicated, the advanced R-77 derivatives, did not look like entering development any time soon. An incremental approach would allow any technological advances to be incorporated into future upgrades. These could have included multi-pulse rocket motors, thrust vectoring, hybrid rockets, gel propellants, and ductless external combustion ramjets.

The Meteor team had considered an interim design, also powered by a dual-pulse solid rocket motor,[21] but decided to offer a fully compliant solution, believing that the staged approach was not cost-effective due to concerns that upgrading from one version to the next would be more complicated than Raytheon claimed.

In February 1999 Raytheon added another interim level to their staged approach. The AIM-120B+ would feature the ERAAM/FMRAAM seeker and guidance section but attached to the AIM-120B solid rocket motor.[27] This would be ready for Eurofighter's 2004 ISD and could be updated to the ERAAM or FMRAAM configurations in 2005 and 2007 by swapping the propulsion system and updating the software.

At the 1999 Paris Air Show the French Defence Minister expressed his country's interest in joining the Meteor project, putting further pressure on the UK to use BVRAAM as a focus for the consolidation of the European guided weapons industry.[28] The French offered to fund up to 20% of the development if Meteor won the UK contest. Inter-governmental letters of intent were exchanged between the UK and French defence ministers in advance of signing the official MoU prepared by Germany, Italy, Spain, Sweden, and the UK.[29] The French officially joined the programme in September 1999.

In July 1999 the Swedish Air Force announced that it would not be funding development of Meteor due to a shortfall in the defence budget.[30] However, this decision was not expected to affect Sweden's participation in the programme, with funding being found from other sources.

The political stakes were high. On 4 August 1999, US President Bill Clinton wrote to the UK Prime Minister, Tony Blair.[31] Clinton said that "I believe transatlantic defence industry cooperation is essential to ensuring the continued interoperability of Allied armed forces".[32] Blair also faced lobbying from the French President and Prime Minister, the German Chancellor, and the Spanish Prime Minister. In response, Clinton later wrote a second time to Blair, on 7 February 2000, timed to arrive before the 21 February EAC meeting to discuss the decision. He put the case for Raytheon's bid, underlining the phrase "I feel strongly" about the decision. The direct intervention of the U.S. President emphasised the political and diplomatic significance that the BVRAAM procurement had acquired.

In autumn 1999 Raytheon offered yet another twist to its staged approach with the ERAAM+.[33] If chosen, the U.S. Government, in an unprecedented move, offered to merge the U.S. AMRAAM and UK BVRAAM programmes, under joint control. ERAAM+ would be adopted by both countries, equipping Eurofighter, JSF, and the F-22, allowing economies of scale from large U.S. procurement. ERAAM+ would retain the ERAAM dual-pulse motor but fitted to a front end incorporating all the features of Phase 3 of the U.S. Department of Defense's (DoD) AMRAAM Pre-Planned Product Improvement (P3I) programme, which was planned out to 2015. These included upgraded seeker hardware and software to provide improved performance against advanced threats and replacement of the longitudinally mounted electronics boards with a circular design which reduced the volume occupied by the electronics allowing space for a longer rocket motor. As equal partners the U.S. and UK would jointly specify and develop the new missile. It was estimated that ERAAM+ could be delivered for less than half the budget allocated for BVRAAM with a 2007 ISD. According to Raytheon, the programme would have initially provided the UK with 62% of development, production, and jobs for the MoD BVRAAM procurement and would give the UK 50% of the significantly larger US air-to-air market. The UK would have participated in the production of every AMRAAM-derivative sold around the world, projected at that time to be about 15000 over the following 15 years.[34]

The ARC dual-pulse motor would not enable full compliance with the SR(A)1239 requirement, however it was believed to be adequate to counter the threats expected until 2012-15 when improvements to the warhead, datalink, and propulsion would be available. The slow pace of Russia's ramjet powered R-77 derivative, a mock-up of which had been displayed at the Paris Air Show but which had not progressed past component ground tests and for which the Russian air force had no requirement due to lack of funding,[35] was offered as evidence that the full capability required by SR(A)1239 would not be necessary for some time. At a press conference to launch ERAAM+ Raytheon said that a ramjet powerplant "is not needed today".

Countering Raytheon's proposed transatlantic tie-up, Boeing was added to the European team,[36] to provide expertise on aircraft integration, risk management, lean manufacturing technology and marketing activities in selected markets. Boeing also brought vast experience of dealing with the U.S. DoD, essential in any future attempts to get Meteor on U.S. aircraft. Raytheon were delighted that "MBD has validated our transatlantic approach." Although initially interested in developing a suppression of enemy air defence variant of Meteor as a successor to HARM,[37] Boeing has become less and less an active partner as development has progressed, possibly having served their political purpose.

In late 1999, in advance of December's EAC meeting to discuss the BVRAAM competition Sweden rejoined the programme.[38]

By early 2000 both teams had submitted best and final offers. The Government was expected to announce a decision in March, following a meeting of the EAC on 21 February.[39] The decision was so politically delicate that some believed that the EAC would leave it to the Prime Minister when he chaired the defence and overseas policy committee.[40] MBD announced a proposal to work with Boeing to offer Meteor derived technology to the U.S. MBD and Boeing urged the US to agree to a governmental-level transatlantic cooperation on the Meteor programme. In a last-minute bid to sway the decision Raytheon proposed increased European involvement in its programme.

Last minute intervention by the UK Treasury delayed the decision, after concerns about the cost of Meteor, believed to be the preferred solution, compared to the cheaper incremental approach offered by Raytheon.[41]

Decision[edit]

In May 2000 the UK Secretary of State for Defence, Geoff Hoon, announced that Meteor had been selected to meet SR(A)1239. Fabrice Bregier, then Chief Executive Officer of MBD, said "This decision marks a historic milestone in the establishment of a European defence capability. For the first time, Europe will equip its fighter aircraft with a European air-to-air missile, creating interoperability and independence to export".[42] By this stage the In Service Date was 2008.

The British House of Commons Defence Select Committee summarised the reasons behind the decision in its Tenth Report: "The Meteor missile has some clear advantages over its Raytheon competitor—it appears to offer the more militarily effective solution; it should help rationalise and consolidate the European missile industry, and provide future competitions with a counterweight to U.S. dominance in this field; and it entails a lower risk of constraints on Eurofighter exports. Although the programme is in its early days, it also offers the prospect of avoiding some of the problems that have plagued other European procurement collaborations, without arbitrary workshare divisions and with a clear project leadership role to be provided by the UK. The MoD needs to take advantage of that leadership role to keep momentum behind the project, including an early contract which will lock-in not just the contractor but also the commitments of our international partners. The cautious definition of the missile's target in-service date may be realistic, particularly in view of the technological challenges that will have to be overcome, but in BVRAAM's case it is a date that must be met if Eurofighter is to fulfil its potential."[26]

The selection of Meteor was not a total loss for Raytheon. As a consolation prize[citation needed] the UK ordered a number of AIM-120s to arm Eurofighter on entry into service which was expected before Meteor development was complete.

Pre-contract[edit]

Negotiations to conclude a smart procurement contract continued. At the Paris Air Show 2001 defence ministers from France, Sweden, and the UK signed a Memorandum of Understanding committing their nations to the Meteor programme.[43] The nations of the other industrial partners, Germany, Italy, and Spain, only signalled an intention to sign within a few weeks, claiming procedural delays within their national procurement systems. Following parliamentary approval in August, Italy signed the Memorandum on 26 September 2001, for an anticipated procurement of about 400 missiles.[44] Spain followed on 11 December 2001.

Germany's financial contribution to the programme was considered essential but for more than two years development was hamstrung by the repeated failure of the German defence budget committee to approve funding.[45] Without the German propulsion system, MBDA deemed that Meteor could not realistically proceed. During this gap in the programme MBDA was funding Meteor from its own resources and, by June 2002, had spent around £70m - most of which had gone, ironically, to Bayern-Chemie to reduce technical risk in the propulsion system, the performance of which was critical to meeting the requirements.

Germany had set two conditions for participation in the project: that the UK should place a contract for the weapon; and that MBDA give a guaranteed level of performance, both of which were achieved by 30 April 2002.[46] It was hoped to sign an agreement at that summer's Farnborough Air Show.

However, Meteor was not on the agenda of the German defence budget committee meeting on the 3 July which meant that a decision could not be made until 12 September, after the German Parliament's took its summer recess. This was claimed to have been due to a delay in paperwork being transferred between the defence and finance ministries.[47] However, there were concerns that this meeting might not even happen until after the German elections on 22 September which would push a decision to the last quarter of the year. An article in the German press claimed that the Rechnungshof (independent federal audit division) urgently recommended "to work up an alternative solution in US-European co-operation and to negotiate a solution with the foreseeable partners" because of the "recognisably high risks in all areas".[48] These delays led to high-level diplomatic contacts over the summer with both the UK and Italian Defence ministers writing to their German counterpart stressing the importance of the Meteor programme.[49]

Germany finally approved the funding that would allow development to commence in December 2002 but at the same time cut its planned acquisition, from 1,488 to 600 missiles.[50]

Orders[edit]

In December 2002 full-scale development and production of Meteor was begun.[51] The £1,200 million fixed-price contract only covered production for the RAF – no other nation had signed up at that time.[2]

The percentage share of the programme allocated to each partner nation has changed several times over the years. Germany's decision to reduce its intended acquisition resulted in the UK taking 5% of the programme from Germany, giving the UK 39.6% and Germany 16%. France is funding 12.4%, Italy 12%, and Sweden and Spain 10% each.

An Integrated Project Team (IPT) was established at MoD Abbey Wood with representatives from all partner nations seconded to the team. The programme will be managed by the UK MoD through the IPT on behalf of the partner nations. The IJPO report to the UK Chief of Defence Procurement, the Executive Board of the DPA, and to an International Steering Committee comprising a one or two star representative from each partner nation's air force.

The prime-contractor, MBDA, will manage and execute the programme through its operating companies in France, Italy, and the UK, working with Bayern-Chemie/Protac in Germany, Inmize Sistemas SL in Spain, and Saab Bofors Dynamics in Sweden. It is estimated that over 250 companies across Europe will be involved. Work will be allocated by MBDA to its risk-sharing partners on an "earned value basis" under which work is placed according to best commercial value, taking into account technical excellence, but with a view to aligning "broadly" with the share of development funding provided by each nation. The programme will initially create and sustain 2500 jobs across Europe, 1200 in the UK, but successful exports could double these figures.[citation needed]

The development programme will make large use of computer simulation and so should require a relatively small number of firings, some of which will cover activities more traditionally associated with aircraft-integration trials. The first firing, from Gripen, was expected in 2005 with an in service date of August 2012.

In December 2009 the Spanish government authorized the procurement of 100 Meteor missiles and their corresponding support equipment.[52] In September 2010 the Swedish Defence Materiel Administration, signed a production order contract with the MoD for the Meteor missile; the system is expected to be operational with the Swedish Air Force in 2015.[53]

Key milestones[edit]

The UK MoD stipulated four "tightly defined" contractual milestones that had to be met otherwise the programme would be cancelled with MBDA expected to repay the development funding:[54]

  1. To demonstrate successful transition from boost to sustain propulsion.
  2. To demonstrate control of the asymmetric airframe. There was concern that the intake air flow would be disrupted during manoeuvres resulting in a loss of propulsion performance or even control. The asymmetric configuration also poses unique control problems. Achievement of this milestone was to be demonstrated using computer models validated from the Air Launched Demonstrator (ALD) trials results.
  3. To demonstrate transfer alignment of the missile's inertial measurement system. This process ensures that the missile knows where it is at launch. Good knowledge of initial position is essential to accurate navigation, particularly for long range engagements.
  4. This milestone relates to Meteor's electronic counter-countermeasures(ECCM) capability. This is highly classified work to be conducted in MBDA's hardware-in-the-loop laboratory at Rome.[55]

Achievement of these milestones will be evaluated by QinetiQ acting as an independent auditor.

Development[edit]

At the 2003 Paris Air Show MBDA signed a contract with Bayern-Chemie/Protac worth in excess of EUR250m, for development, first lot production, and integrated logistics for the Meteor PSS.[56] Also at the show, MBDA and Thales formalised their agreement of June 2002 by signing a contract for EUR46m covering development and initial production of seekers for the RAF's missiles.[57]

Over the eight months following contract signature, MBDA had determined the definitive external shape of Meteor. By the summer of 2003 manufacture had commenced of a full-scale model for aircraft fit checks as well as sub-scale models for wind tunnel tests scheduled for the autumn.[58] The mid-mounted wings which had featured in the originally proposed configuration were removed. Following extensive pre-contract wind tunnel testing and MBDA's growing experience with guidance and control technologies for wingless configurations, such as ASRAAM, a wingless design was believed to offer the best solution to meeting the performance requirements. The control fins were also redesigned so that all four fins were now identical.

In August 2003 Saab Bofors Dynamics received a contract worth SEK450m to develop the PFS.[59]

In October 2003 the first trial fit of a geometrically representative model was carried out on Eurofighter.[60] Checks were successfully carried out on the underfuselage semi-recessed, long-stroke Missile Eject Launchers, designed and manufactured by Flight Refuelling plc, and the underwing pylon-mounted rail-launchers. In November 2003 Saab Aerosystems received an order worth 435m Swedish Kronor from the FMV for the integration of Meteor onto Gripen.[59] As prime contractor for the integration task Saab Aerosystems will be supported by Ericsson Microwave Systems, Saab Bofors Dynamics, and MBDA (UK).

In December 2003 MBDA and Saab Bofors Dynamics signed an enabling contract worth 485m kronor covering programme management, system level participation, participation in the development of seeker, guidance, and autopilot algorithms, development of missile software, development of test equipment, system proving activities, and the TBUS.

In April 2004 MBDA carried out fit checks on a Gripen at Saab's Linköping facility.[61] This demonstrated the mechanical interfaces between the missile, the Flight Refuelling designed and manufactured Multi-Missile Launcher (MML) and the aircraft.

Wind tunnel tests had recently been completed at BAE Systems' facility at Warton, UK, and at ONERA in Modane, France. These tests successfully demonstrated the air intake operation and validated the modelled aerodynamic characteristics, confirming the configuration for the first flight trials.

In August 2004 Bayern-Chemie delivered the first inert PSS, to be used for structural testing, amongst other things.[62]

By the summer of 2005 two inert missiles had been delivered to Modane to recommission the facility following major modifications intended to prepare it for the free-jet trials. These were planned to begin with a 'part-firing' before the French summer holidays to be followed by two full-scale firings later in the year. These would comprise a full end-to-end demonstration of the complete propulsion system at representative supersonic free flight conditions as a risk reduction exercise for the ALD firings, scheduled for the last quarter of 2005. During these tests a full-scale missile model fitted with a live PSS would be mounted on a moveable strut in the wind tunnel, allowing a series of incidence and sideslip manoeuvres to be conducted over the full duration of the PSS operation. The tests would demonstrate operation of the air intakes, the transition from boost to sustain propulsion, control of the sustain motor thrust, and provide data on the aerodynamic characteristics.

On 9 September 2005 the first flight of Meteor on board a French Navy F2 standard Rafale M was successfully carried out from the Centre d'Essais en Vol at Istres in southeast France.[63] This was in preparation for a week-long series of trials from the nuclear-powered aircraft carrier Charles de Gaulle which commenced on 11 December 2005 in the Mediterranean.[63] The Meteor trials were conducted at the end of a series of tests of other Rafale weapons including SCALP-EG, ASMP-A and MICA.[64] Tests were carried out with two Ground Handling Training Missiles (GHTM) and an Environmental Data Gathering (EDG) missile fitted alternatively on an underwing rail-launcher or underfuselage eject launchers. The EDG is an instrumented missile representing all the dynamic properties of an operational missile in terms of size, weight, and aerodynamic shape. The trials were designed to measure the shock and vibration levels associated with the severe carrier operational environment. Around twenty catapult launches and full deck arrests were undertaken, along with a number of touch and go landings on the fightdeck to provide a fully comprehensive handling test of the aircraft while fitted with Meteor. The trials went so well that they were concluded a day earlier than planned.[64]

On 13 December a separate campaign commenced in Sweden with flights of the Meteor avionics missile (GMA5) carried on the port wing outboard station of Gripen aircraft 39.101, which had been modified with Meteor-unique software.[59] As with the EDG missile GMA5 represents all the dynamic properties of an operational missile but also interfaces electrically with the launch aircraft.[63] These trials successfully verified mechanical, electrical, and functional interfaces between the missile and aircraft. This was the first in-flight trial of two-way communication between the missile and aircraft and was an important step in clearing the aircraft and missile for the ALD firings which had slipped into Spring 2006, due to the lack of winter daylight hours at the Vidsel Test Range in northern Sweden.

In a separate air-carry trial a Eurofighter of No. 17 (R) squadron RAF flew with two GHTMs on the forward underfuselage stations to assess how the aircraft handled during a series of manoeuvres.

On 21 January 2006 a range work-up was conducted at Vidsel, again with GMA5 mounted on 39.101.[59] This successfully verified system communications and set-up between the aircraft and the test range in advance of the first firing.

The first ALD firing took place on 9 May 2006 from a JAS 39 Gripen flying at an altitude of 7,000 m. The missile was launched from the port underwing MML, separating safely from the launch aircraft as the integrated booster accelerated the missile to over Mach 2.0 in around two seconds.[65] However, after a successful boost the missile failed to transition to the sustain phase of flight. The missile continued under boost impulse, gradually decelerating until broken up, on command from the ground. Despite this problem telemetry was gathered throughout the full duration of the flight. The missile debris was recovered and the air intakes were found to be still closed.[65]

The problem was traced to a timing issue in the gas generator valve control unit software, which was developed by a Bayern-Chemie subcontractor. Following modification a repeat of the first trial took place on 20 May 2006 and was a complete success. During the sustain phase the missile carried out a series of pre-programmed manoeuvres, under autopilot control, representative of the mid-course and endgame phases of an engagement. The flight lasted just under a minute and ended again with the successful operation of the break-up system which destroyed the missile within the range boundary.

The first trial of a flight standard functional seeker was carried out on 30 June 2006.[66] The Seeker Data Gathering (SDG) missile was carried under the wing of Gripen. The SDG missile has no propulsion system or warhead but contains operational missile subsystems and telemetry systems. The flight lasted approximately 1.5 hours, allowing data to be gathered over a variety of different flight conditions. These data will be used in support of the third Key Milestone. This marked the start of a two-year seeker development programme which will conclude with the first guided firing, currently scheduled for 2008 from Gripen.[67] This programme will gather clutter data and demonstrate capabilities such as transfer alignment and target tracking in clear air and in the presence of ECM.

On 5 September 2006 the third and final ALD firing was successfully conducted.[68] The launch conditions were the same as the first two firings but the missile flew a different flight profile.

Flight trials will continue in mid-2008 with control and dispersion firings to be conducted in the Hebrides off northwest Scotland.[55] A series of 10 guided firings will follow in 2008.[65]

The Eurofighter Typhoon was originally scheduled to join the Meteor trials effort in 2006 but no integration contract or funding has yet been agreed.[69] Eurofighter claims that the Block 8 aircraft, scheduled for delivery from 2007, will be fully compatible with Meteor but the CAPTOR radar will not be integrated with Meteor's datalink, requiring an additional processor card. Meteor will be delayed until the final Tranche 3 deliveries, which are scheduled to run from 2012/13 to 2017.[70] Most of the trials effort is already being conducted on Gripen and Saab is keen to take on as much of the work as possible. Consideration is also being given to using Rafale or a modified Tornado F3.[71] MBDA have said that the development plan is completely independent of the launch platform and decisions on allocation of aircraft types are made by the customer.

The UK NAO Major Projects Report 2006[72] reported a 12-month delay in the Meteor programme, pushing the expected in service date back to August 2013. The Chief of Defence Procurement was reported as saying that this was nothing to do with the missile itself, "Meteor is actually going very well."[73] and the lack of Eurofighter aircraft for the integration work was the main reason for the slip. The Minister of Defence Procurement, Lord Drayson, said "I regard this as a Eurofighter Gmbh problem." It was reported by Jane's Information Group that this delay could lead to the RAF operating AMRAAM to a point where stocks of airworthy missiles become low.[74]

Future[edit]

MBDA is planning integration of Meteor on the Lockheed Martin F-35 Lightning II Block 4.[75] The Meteor has already been checked for fit in the internal weapons bays of the JSF. It is compatible with the aircraft's internal air-to-ground stations, but would require modification of the fin span and air intakes to be compatible with the air-to-air stations.[76] In this context 17 July 2014, MBDA has agreed to jointly research a meteor's seeker with Japan.[77]

The U.S. Navy may require a Meteor-class missile to replace the capability lost with the retirement of the AIM-54 Phoenix in 2004. A possible solution may be a ram-powered AMRAAM (ERAAM) carried by the F-18E/F Super Hornet. India has made a request for information about integrating Meteor on their Sukhoi Su-30MKI fleet.[78]

MBDA is also looking to exploit its ongoing investment in the high-speed Meteor airframe and platform integration with derivatives for other roles, including air-to-surface use against targets such as self-propelled Surface-to-air missile systems, self-propelled air-defence radars, mobile command posts, and ballistic-missile transporter/erector/launchers. Studies have shown that the time from detection to engagement of this class of target needs to be less than 10 minutes.

Description[edit]

Seeker[edit]

Terminal guidance is provided by an active radar seeker which is a joint development (June 2003)[79] between MBDA's Seeker Division and Thales Airborne Systems and builds on their co-operation on the 4A (Active Anti-Air Seeker) family of seekers that equip the MICA and ASTER missiles. Thales produces four sub-assemblies representing approximately 35% of the seeker.

Forebody[edit]

Immediately aft of the seeker, the missile forebody which is designed and manufactured by Indra Sistemas, contains the inertial measurement system (IMS), provided by Litef, a German subsidiary of Northrop Grumman. The active radar proximity fuze subsystem (PFS) is provided by Saab Bofors Dynamics (SBD). The PFS detects the target and calculates the optimum time to detonate the warhead in order to achieve the maximum lethal effect.[59] The PFS has four antennae, arranged symmetrically around the forebody. The Impact Sensor is fitted inside the PFS. Behind the PFS is a section containing thermal batteries, provided by ASB, the AC Power Supply Unit, and the Power and Signal Distribution Unit.

Warhead[edit]

The blast-fragmentation warhead is produced by TDW of Germany. The warhead is a structural component of the missile. A Telemetry and Break-Up System (TBUS) replaces the warhead on trials missiles.

Propulsion[edit]

The propulsion sub-system (PSS) is a Throttleable Ducted Rocket (TDR) with an integrated nozzleless booster, designed and manufactured by Bayern-Chemie. TDR propulsion provides a long range, a high average speed, a wide operational envelope from sea level to high altitude, a flexible mission envelope via active thrust control, relatively simple design, and logistics similar to those of conventional solid rocket motors.

The PSS consists of four main components: a ramcombustor with integrated nozzleless booster; the air intakes; the interstage; and the sustain gas generator. The PSS forms a structural component of the missile, the gas generator and ramcombustor having steel cases. The propulsion control unit electronics are mounted in the port intake fairing, ahead of the fin actuation subsystem.

The solid propellant nozzleless booster is integrated within the ramcombustor and accelerates the missile to a velocity where the TDR can take over. The reduced smoke propellant complies with STANAG 6016.

The air intakes and the port covers which seal the intake diffusors from the ramcombustor remain closed during the boost phase. The intakes are manufactured from titanium. The interstage is mounted between the GG and the ramcombustor and contains the Motor Safety Ignition Unit (MSIU), the booster igniter, and the gas generator control valve. The gas generator is ignited by the hot gases from the booster combustion which flow through the open control valve. The gas generator contains an oxygen deficient composite solid propellant which produces a hot, fuel-rich gas which auto-ignites in the air which has been decelerated and compressed by the intakes. The high energy boron-loaded propellant provides a roughly threefold increase in specific impulse compared to conventional solid rocket motors. When it enters service it will yield a no-escape zone more than three times greater than that of the current AMRAAM (AIM-120 C-7) used by Typhoon-equipped airforces.[3]

Thrust is controlled by a valve which varies the throat area of the gas generator nozzle. Reducing the throat area increases the pressure in the gas generator which increases the propellant burn rate, increasing the fuel mass flow into the ramcombustor. The mass flow can be varied continuously over a ratio greater than 10:1.

The Meteor PSS will be able to cope with high incidence and limited sideslip angles during manoeuvres but not negative incidences or large amounts of sideslip.[citation needed]

Control[edit]

The missile trajectory is controlled aerodynamically using four rear-mounted fins. Meteor's control principles are intended to allow high turn rates while maintaining intake and propulsion performance.

The fin actuation subsystem (FAS) was originally designed and manufactured by the Claverham Group (formerly Fairey Hydraulics Limited) a Somerset, UK, based division of the U.S. company Hamilton Sundstrand. Currently the design has been taken onboard by the MBDA UK, at Stevenage. The FAS is mounted at the rear of the intake fairings. The design of the FAS is complicated by the linkages required between the actuators, which are located in the intake fairings, and the body-mounted fins.

Datalink[edit]

Meteor will be 'network-enabled'. A datalink will allow the launch aircraft to provide mid-course target updates or retargeting if required, including data from offboard third parties.

The datalink electronics are mounted in the starboard intake fairing, ahead of the FAS. The antenna is mounted in the rear of the fairing.

On 19 November 1996 Bayern-Chemie completed the latest in a series of tests designed to assess the attenuation of signals by the boron rich exhaust plume of the TDR, a concern highlighted by opponents of this form of ramjet propulsion. Tests were conducted with signals transmitted through the plume at various angles. The initial results suggested that the attenuation was much less than expected.[80]

Eurofighter and Gripen[edit]

With Eurofighter and Gripen, it is a two-way datalink, which will be able to transmit missile information such as functional and kinematic status, information on multiple targets, and notification of target acquisition by the seeker.[81]

Rafale[edit]

It is different with Rafale, which is fitted with a one-way link originally designed for use with its MICA missiles.

  • Mid-course guidance is provided by the fighter until the active seeker acquires the target, the missile then becoming autonomous.
  • Alternatively, the Meteor can be fired without using mid-course update, allowing the Rafale to immediately turn away to deny the enemy aircraft any firing possibility.[79] Like with a "Fire and forget" AASM or MICA or Exocet missile.

Support[edit]

The Integrated Logistics Support concept proposed for Meteor does away with line maintenance. The missiles will be stored in dedicated containers when not in use. If the Built-In Test equipment detects a fault the missile will be returned to MBDA for repair. The Meteor is intended to have an airborne carriage life of 1,000 hours before any maintenance is required.[2]

See also[edit]

Similar missiles

References[edit]

Notes[edit]

  1. ^ More than three times the no escape zone of current AMRAAM (AIM-120 C-7) - AirForces Monthly 20th Anniversary Special - Eurofighter Typhoon: May/June 2014

Citations[edit]

  1. ^ Comptroller and Auditor General (2004-01-23). "Ministry of Defence Major Projects Report 2003" (PDF). National Audit Office. p. 83. Retrieved 2006-11-07. 
  2. ^ a b c d Air Launched Weapons, Jane's, 30 July 2006 .
  3. ^ a b AirForces Monthly: 20 Year Anniversary Special - Eurofighter Typhoon, Issue Date: May/June 2014
  4. ^ http://s25.postimg.org/4qw3vyzov/going_digital_pg_3.jpg
  5. ^ Aviation week, Oct 7, 2012 .
  6. ^ "European Meteor BVRaam Missile Test Fired over Sweden", Defense update 
  7. ^ "No-Escape Zone", Flight International, 16–22 March 1994.
  8. ^ "Beyond Visual Range Air to Air Missile (BVRAAM)". Ministry of Defence. Retrieved 2006-11-07. 
  9. ^ "Seeing double", Flight International, 15 March 1995
  10. ^ "British court Germany and France on FMRAAM project", Flight International, 14–20 June 1995
  11. ^ "USA offers ramjet sweetener", Flight International, 4–10 October 1995
  12. ^ "Matra/DASA poised to make joint RAF missile bid", Flight International, 21–27 February 1996
  13. ^ "Germany presses for joint European missile approach", Flight International, 27 March – 2 April 1996 .
  14. ^ "Minutes of Evidence: Examination of Witnesses", Report (10th), House of Commons Defence Select Committee, 23 May 2000 .
  15. ^ "Terminal velocity", Flight International, 13 November 1996 .
  16. ^ "Hughes homes in on missile pact", Flight International, 11–17 September 1996 .
  17. ^ "Missile makers vie for key UK order", Flight International, 8 September 1998 .
  18. ^ "Ramjet, the Air-breathing Engine with no Serviceable Parts Inside", Armada International (4), 1996 .
  19. ^ "BAe-brokered missile deal heads off European divide", Flight International, 15 May 1996 .
  20. ^ "Rocket's red glare", Flight International, 11–17 March 1998 .
  21. ^ a b "Funding struggle hits Eurofighter missile", Flight International, 23 July 1997 .
  22. ^ "Air Combat Missiles – The Gloves Are Off", Armada International (4), 1998 .
  23. ^ "Dasa asks Germany for approval of EURAAM demonstrator", Flight International, 27 May – 2 June 1998 
  24. ^ "USA smoothes path for UK EF2000 missile selection", Flight International, 3–9 June 1998 .
  25. ^ "Raytheon supplies UK with AMRAAM costs", Flight International, 3–9 June 1998 .
  26. ^ a b Report (10th), UK: Parliament Select Committee on Defence .
  27. ^ "Interim AMRAAM Upgrade offered", Aviation Week & Space Technology, 8 February 1999 .
  28. ^ "Rival Teams Battle for UK BVRAAM order", Missiles & Rockets (Jane's), 1 July 1999 .
  29. ^ "France offers funding for European Meteor", Flight International, 16 June 1999 .
  30. ^ "Sweden's armed forces close purse strings on Meteor", Flight International, 7 July 1999 .
  31. ^ "Clinton offers transatlantic link with BVRAAM", Flight International, 18 August 1999 .
  32. ^ Truscott, Peter (2000), European Defence Meeting the Strategic Challenge, Institute for Public Policy Research .
  33. ^ "ERAAM+ proposed as joint UK/US AMRAAM replacement", Jane's Missiles & Rockets, 1 July 1999
  34. ^ "Missile market milestones", Jane's International Defense Review, Volume Number 33 July 2000
  35. ^ "BVRAAM fight sparks ramjet threat debate", Flight International, 4 August 1999
  36. ^ "Boeing joins Meteor missile group", Flight International, 27 October 1999 .
  37. ^ "Boeing looks at Meteor for SEAD", Flight International, 10 October 2000 .
  38. ^ "Matra BAe makes final Meteor push", Flight International, 1 December 1999 .
  39. ^ "Final BVRAAM bids submitted to UK MoD", Missiles & Rockets (Jane's), 1 February 2000 .
  40. ^ "Hard-fought battle for £1bn Eurofighter missile contract reaches key point today", The Independent, 21 February 2000 .
  41. ^ "Treasury delays RAF winners", Flight International, 28 March 2000 .
  42. ^ "UK selects Meteor for Eurofighter", Jane's Missiles & Rockets, 24 May 2000
  43. ^ "Three nations sign Meteor go-ahead", Jane's Missiles & Rockets, 18 July 2001
  44. ^ "Italian air force signs up to join Meteor development", Flight International, 11 September 2001
  45. ^ "Why we are angry with the Germans", The Daily Telegraph, 22 July 2002
  46. ^ "Meteor awaits German go-ahead", Jane's Missiles & Rockets, 21 June 2002
  47. ^ "Germany puts back Meteor decision", Flight International, 2–8 July 2000
  48. ^ Rough translation of German Financial Times article, 18 June 2002
  49. ^ "Key European Military Projects Await German Decisions", Aviation Week & Space Technology, 9 September 2002
  50. ^ "Berlin Deals Blow To Military Plans", Aviation Week & Space Technology, December 9, 2002
  51. ^ MBDA signs Meteor missile contract (press release), MBDA, 23 December 2002 .
  52. ^ "Cabinet meeting" (Press release). Spanish Government. 2003-06-17. Retrieved 2009-12-23. 
  53. ^ FMV, SE .
  54. ^ "Beyond visual range shoot-out hots up", Flight International, 27 June – 3 July 2000 .
  55. ^ a b "MBDA starts preparations for first Meteor test firings", Missiles & Rockets (Jane's), 12 July 2000 .
  56. ^ "MBDA awards Meteor contract to Bayern-Chemie/Protac" (Press release). MBDA. 2003-06-17. Retrieved 2006-11-07. 
  57. ^ Thales MBDA Meteor seeker contract (press release), MBDA, June 17, 2003 .
  58. ^ "Meteor loses its wings", Missiles & Rockets (Jane's), 23 July 2003 .
  59. ^ a b c d e Meteor (press brief), Farnborough: Saab, 17 July 2006 .
  60. ^ "Meteor fit-tested on Typhoon", Missiles & Rockets (Jane's), 23 July 2003 .
  61. ^ Gripen trials success marks next milestone for Meteor (press release), MBDA, 22 April 2003 .
  62. ^ "Bayern-Chemie Protac delivers Meteor propulsion system", International Defense Review (Jane's), 20 September 2004 .
  63. ^ a b c "Meteor missile takes to the sky with Europe's next generation fighters" (Press release). MBDA. 2005-12-13. Retrieved 2006-11-07. 
  64. ^ a b Rafale flies Meteor trials from Charles de Gaulle", Jane's Missiles & Rockets 2005
  65. ^ a b c "Meteor fizzles, then burns", Aviation Week & Space Technology, 26 June 06
  66. ^ "Meteor missile demonstrates seeker functionality", Missiles and Rockets (Jane's), 28 July 2006 .
  67. ^ "Meteor reaches milestone", Flight International, 25 July 2006 .
  68. ^ "Third Firing Success for Meteor Air Dominance Missile" (Press release). MBDA. 2006-09-14. Retrieved 2006-11-07. 
  69. ^ "Meteor soars but Eurofighter integration lags", Defence Weekly (Jane's), 22 June 2006 .
  70. ^ "Typhoon Transformation", Air Forces Monthly, January 2011 .
  71. ^ "Kingdom Come", Aviation Week and Space Technology, 16 October 2006 .
  72. ^ Comptroller and Auditor General (2006). "Ministry of Defence Major Projects Report" (PDF). National Audit Office. Retrieved 2006-12-13. 
  73. ^ "UK MinDP and Eurofighter Typhoon", Defence Analysis 9 (12), December 2006 .
  74. ^ Richardson, Doug. "Royal Air Force could face BVRAAM shortage". Jane's Information Group. Retrieved 2006-12-09. 
  75. ^ "MBDA pitch a European weapons option for F-35 JSF". indiandefencereview.com. 2014-02-14. Retrieved 2014-09-09. 
  76. ^ "PICTURE: MBDA reveals clipped-fin Meteor for F". Flightglobal. 2010-09-17. Retrieved 2014-09-09. 
  77. ^ "Japan, Britain To Collaborate On Meteor Guidance". Aviation Week & Space Technology. 2014-07-17. Retrieved 2014-09-09. 
  78. ^ Singh, Rahul (16 October 2011). "IAF gets lowdown on the Royal Air Force’s Libya op". Hindustan Times. 
  79. ^ a b "Rafale pushes BVR at extreme" (PDF), Fox Three (Rafale International) (6) 
  80. ^ "Germans to test Meteor ramjet", Flight International, 27 November 1996 .
  81. ^ "MBDA explores Meteor integration and derivatives", Missiles and Rockets (Jane's), 2005-06-15 .

Bibliography[edit]

External links[edit]