Friday, July 18, 2014

News roundup: from airshows and elsewhere

HMS Queen Elizabeth undocked

After being named, the aircraft carrier has now been carefully eased out of No 1 Dock in Rosyth, to be berthed in the shipyard’s basin, where the ship will be completed. The dock will not stay empty for long: the LB03 superblock for HMS Prince of Wales has already been loaded onto a barge for the travel to Rosyth, planned for next week. LB01 (the bow) is already in Rosyth, ready to be craned down into the dock. CB02 has been loaded on another barge itself.
Progress on Prince of Wales will be rapid: it is expected that the assembly phase of the second carrier will take 12 months less thanks to a more efficient process and to the experience made with the first-in-class.  

Moving the carrier out of the dock required a flottilla of tugs. One of them had to be lifted whole via Goliath crane, to be then lowered in the dock, ahead of QE's bow!

F-35 visit to the UK is cancelled even as flight resumes

The June 23 fire on the USAF F-35A AF-27 in Eglin has ultimately, as was to be feared, proven to be a big enough issue to prevent the planned international debut of the F-35. The investigation that followed the incident has located the problem in the F-135 engine, specifically identifying excessive friction between the third-stage integrally bladed rotor and an abradable strip lining the engine casing as the cause for the engine failure, which cut a fuel line and sparked the fire. A general inspection, fleet-wide, has been made on all the engines in the fleet, and it seems that the problem is an isolated anomaly. However, the F-35 fleet has for now only been allowed to flight within strict restrictions which include mandatory engine inspections. The investigation, in fact, is not yet complete and it has so far not been possible to isolate the root cause, a fundamental passage to clear in order to safely determine if other engines are at risk or not.

The restrictions put an end to the hope of seeing the F-35 cross the Atlantic to debut abroad for the first time. It must be noted however that F-35Bs of the USMC have actually flown long-endurance flights across the USA twice after the June 23 fire, as three aircraft were flown from Yuma to Patuxent River on July 27, and they yesterday flew back to Yuma, trailed by tankers.

Other F-35 news include the signing of the contract between AIM Norway and Pratt & Whitney for the standing up of an F-135 engine Maintenance, Repair and Overhaul (MRO) centre in Norway. This is the first such centre selected, and is of special relevance to the UK as well, since cooperation agreements between Britain and Norway have all included the plan to eventually have british F-135 engines maintained by AIM Norway.
Two more engine MRO centres are expected to stand up in Europe on the back of other Pratt & Whitney agreements: one MRO line is expected to open in the Netherlands, at the Fokker Woensdrecht centre. This facility, yet to be contractualized, is a key component of wider multinational F-35 agreements, as the Netherlands expect to maintain Italian F-135 engines in exchange for the assembly of their F-35 jets in Italy’s FACO in Cameri.
Finally, Pratt & Whitney has signed a LOI on May 22, 2014, to help Turkey stand up not just a MRO centre but a true engine-FACO which will also be able to assemble engines in support of the F-35 program. However, while Norway and the Netherlands already have a clear path to achieve at least one major client outside of their own airforces, Turkey has yet to find its place in the enterprise.

Meanwhile, the first third generation Helmed Mounted Display systems for the F-35 program have been delivered for testing. They have been trialed in flight to the satisfaction of test pilots, but so far only on substitutive flying-lab aircrafts. Trials will now be made using F-35A AF-3, a test aircraft fitted with Block 3I software and TR2 processors (both appearing starting with LRIP 6 aircraft). It is expected that the third generation helmet will be delivered as part of the LRIP 7.

Later this year, it is expected that negotiations will be concluded and a contract signed for LRIP 8 production, expected to include 4 F-35B for the United Kingdom.

The United Kingdom is preparing to move personnel and aircraft out of Eglin towards the next destinations: 13 engineers and one pilot will follow the USMC training squadron 501 as it moves from Eglin to its intended permanent base in Beaufort. The USMC move is underway, with the first aircraft having transferred yesterday, following the early move of part of the personnel. The first training courses in Beaufort are expected to begin in the fall (October most likely), with the full transfer completed in 2015. Beaufort is where 617 Sqn RAF will stand up, train and grow before moving to Marham in the UK in the summer (july/august) 2018. By December 2018, land IOC is expected to be declared. The same year, HMS Queen Elizabeth is expected to sail across the Atlantic to have her first aviation trials embarking F-35Bs in the US East Coast area.  

The rest of the current british F-35B personnel (3 pilots and 16 to 20 engineers) will move to Edwards AFB, where they will, later this year, stand up 17(R) Sqn as the OEU unit.

Lockheed Martin, Northrop Grumman and BAE Systems are due to invest 140 million dollars between 2014 and 2016 to fund affordability and cost reduction approaches in order to reduce the Unit Recurring Fly-away Cost to “4th Generation levels”.
Another measure being studied to achieve affordability is the project for a “block buy” which would see international partners committing firmly to substantial number of aircraft in the next few years, in exchange for a “discount price”. This is meant to encourage partners to help the US ramp up yearly production numbers ahead of the passage to full rate production and Multi-Year Procurement, so to achieve the cost reduction that everyone is hoping for.

On the testing front, there are good news. Structure durability testing has concluded in Brough, UK, on the horizontal tail surfaces for all three F-35 variants. They have survived the 24.000 hours of simulated flying, equivalent to three design lives (the F-35 has a design life of 8000 hours, against the 6000 of aircraft such as Typhoon).
Next year, the same kind of testing should be completed on the vertical surfaces as well. Brough is also doing the durability testing on the F-35A fuselage, and by next year it will clear the second of the three lives in testing.  

The F-35B remains on track to achieve the intended USMC IOC. The final version of the Block 2B software is flying, and testing is progressing, including on complex features such as four-aircraft situational awareness sharing via MADL secure link.
In October and out to early November, 2 F-35C will embark on USS Nimitz for the first sea trials of the type.
Block 3I software testing in flight is also on the way. This is important because Block 3I is needed for acceptance of the LRIP 6 jets.
Block 3I is the Block 2B software hosted on new, more powerful TR-2 processors introduced on the aircraft from LRIP 6 onwards. TR-2 processors are needed to eventually receive the complete Block 3F software, and will be retrofitted to early production aircraft going ahead.  

HMS Illustrious close to retirement

HMS Illustrious will soon decommission. On July 22 she will make her last entry into Portsmouth. Just days ago speculation had made the rounds about her Out of Service Date being pushed back by the delay of 3 months suffered by HMS Ocean’s big refit. It was suggested that Illustrious might have to deploy once more, as part of the Response Force Task Group for Ex Cougar 14, due to HMS Ocean not being ready.
It won’t be the case. HMS Ocean is now busy in post-refit sea trials, and is starting aviation trials: it looks like the trials will be speeded up to allow her to take her place at the centre of the task group, as originally planned. 

HMS Illustrious seen during her last big adventure, ex Deep Blue, with a full ASW team of 9 Merlin HM2

CBRN reactivation goes ahead

A further step has been moved to restore CBRN wide area recce capability, putting out a tender notice for the regeneration of the Fuchs armored vehicles. The tender covers 9 vehicles, down from 11, but is a key advancement in the story. The regeneration will include spares, logistic support and support for future updates. 3 years of support, plus two 1-year extension options are envisaged. The cost range is between 7 and 11 million pounds.

Sentinel, Shadow and Reaper to stay

Despite providing little actual detail along with the announcement, David Cameron’s much publicized address at Farnborough confirmed the unlocking of funding meant to keep Sentinel and Shadow serving at least out to 2018, reversing the decisions outlined in the 2010 SDSR.
Reaper was not mentioned in the announcement, but it is understood that it will be brought into core and funded for at least five years. A formal confirmation of the plan to retain the RPASs has not yet come as the Royal Air Force is still firming up a decision on where to base the aircraft when it comes back from Afghanistan. It must also be noted that, as of now, personnel from 39 RAF Sqn remains based in Creech AFB, USA, with one Ground Control Station, to maintain the direct ties with the USAF’s own RPAS force. A british pilot is embedded in the 556th Test and Evaluation Squadron, which stood up in march 2008 as the first UAV operational test squadron in the USAF.
39 Sqn had been originally planned to move into Waddington, alongside XIII Sqn which stood up there in 2012 when the other two british Ground Control Stations were transported from Creech to the british base. The two GCS have been housed inside one of Waddington’s hangars to ensure maximum security.
Meanwhile, the last five british Reapers have begun to operate in Afghanistan, after several months of delay due to the challenge of validating the changes and upgrades present in these more recent RPASs. 

The Sentinel R1 will not just be retained, but it will actually receive significant upgrades over which the RAF and Raytheon are already working. It is likely that one of the five aircraft will be devoted to a program of assessment of the upgrade program in the next months: the development paths being considered involve introducing a maritime search mode for the radar; adding long-range EO/IR optics, probably derived from the sensor employed by the DB-110 RAPTOR reconnaissance pod, primarily for high definition, visual validation of radar tracks; and a SIGINT sensor fit.
A maritime radar mode won’t be an MPA replacement, but it will help to fill the gap somewhat, by restoring a wide area surface surveillance capability.

Tornado GR4’s last upgrades

Despite being planned to leave service in March 2019, the Tornado GR4 is still receiving upgrades. 59 aircraft will receive the full package of upgrades (once planned for 96 aircraft) by the end of March 2016, in order to stay relevant until their very last day of service. The remaining Tornado aircraft will be used as a source for spare parts for the forward fleet.

The upgrades include the Tactical Integrated Exchange Capability (TIEC) Data Link 16 and Improved Data Modem capability, which fills a gap which was badly felt in 2011 over Libya. The TIEC program had been in the works from well before operation Ellamy, however (dating back easily to 2004), and had been working to introduce Data Link 16 on the Harrier GR9 first.
The upgrade program includes secure communications fit by Cassidian, and full integration of the Paveway IV guided bomb.

Tornado has received substantial improvements in recent times. For operations in Afghanistan, it was fitted under UOR with the Advanced IR Counter Measures (AIRCM) pod (a customised version of Terma's Modular Countermeasures Pod/MCP) and a CAGNET multi-band transceiver (based on a Rohde & Schwarz MR6000L software radio) which embodies the Have Quick II waveform used for air-ground communications with JTACs.
CAGNET was a stop-gap measure on the way to SCOT (Secure Communications On Tornado), a program started in 2005 and rolled out from 2010 that uses the same transceiver but opens up additional waveforms including SATURN for satcoms.

Tornado also received an Helmet Mounted Display fit for target cueing purpose. At least twelve HMD sets have been procured, and the fleet has been progressively fitted for but not with, so that deploying aircraft can bring the system to bear.

A Honeywell TCAS II anti-collision system has been fitted to two aircraft for development and demonstration, and trialed on a third. It will be rolled onto the whole fleet later this year, in a much delayed answer to the risk of in-flight collisions: 3 RAF crewmen from Lossiemouth died in a collision between two Tornado in 2012, and further collisions had happened in the past, including a tragic impact with a Cessna which caused 4 deaths in 1999.  

The AIRCM gave the Tornado GR4 increased protection against IR missiles, and a new contract is due to completely renew the Skyshield 2 pod, carried on the other wing, to massively enhance protection against enemy radars.
Selex ES will take the existing Skyshield 2 pods and rework their internal structure completely, replacing the entire receiver chain, introducing a digital control unit and a digital techniques generator as well as updating to the TWT transmitters. Two Towed Radar Decoys (TRDs) identical to those currently in service with the Eurofighter Typhoon will be incorporated into the rear of the pod. Flight trials are expected by the end of the year, with IOC in late 2015. 

Skyshield 2 pods have not quite kept up with enemy radar developments. In Afghanistan, the lack of radar-guided threats has lead to Tornado often flying with a BOZ simulacre (with the only purpose of keeping the aircraft balanced) instead of a Skyshield pod (unlike the Tornado in this picture, which has it under the left wing)

This Tornado carrying RAPTOR is equipped with an AIRCM (to the right, in the picture) and a simulacre (on the left). No Skyshield 2
The TERMA AIRCM was introduced as UOR to protect Tornado against possible IR-guided threats. The AIRCM combines missile warning sensors and flare dispensers, slaved to an Electronic Warfare
Management System, AN/ALQ-213(V) which automatically reacts to a threat by deploying the adequate countermeasure while giving the pilot video and audio warnings as suitable.

Selex ES has received a final  support contract for Tornado, which will carry it towards OSD.

Typhoon AESA and Storm Shadow

The E-Scan Radar Development Programme for Typhoon is currently still within the Assessment Phase, prior to its main investment decision. In fact, despite the fanfare at Farnborough, a go-ahead contract has yet to be signed. United Kingdom and Italy appear to be ready to sign, but Germany is known to still have to secure parliamentary approval, and until the contract is signed, we are still stuck at the hopes level, like it has already happened many times in the past years. The Typhoon AESA story has been a long and so far disappointing tale.

The contract, once it will be signed, is expected to be worth a billion pounds, spread on the partner nations, but there are no confirmations. The signing of the deal is expected before year’s end.

At Farnborough, as announced by David Cameron, a british-only £72 million Extended Assessment Phase contract has been awarded to BAE Systems, to de-risk UK specific requirements as part of the pre-main investment decision work. It has long been known that the RAF has set ambitious and extensive requirements for the Typhoon’s AESA, to include electronic war functions. This is not the first work that is authorized into developing those additional features, with the most well known earlier project known as Bright Adder.
The RAF hopes to install the AESA radar on its Tranche 3 aircraft, and have the system operational in the early 2020s.

A final contract has instead been signed for the integration of Storm Shadow on Typhoon. Earlier, the first study contract for integration of Brimstone 2 had been announced. The RAF wants to have both weapons integrated on Tranche 2 and 3 Typhoons by 2018, in order to be ready when Tornado GR4 is withdrawn in March 2019.

Ongoing work is evaluating how to add a collision avoidance system to RAF Typhoons, as well.

The RAF is also probably in talks with BAE regarding their Striker II Helmet system. The Typhoon currently employs the Striker I, but BAE has already developed a follow-on thanks to the work made into the F-35 program to provide an alternative HMD.
Striker II is a fully digitally integrated helmet display which removes the need for the pilot to wear Night Vision goggles at night as it comes with an integrated ISIE-11 sensor camera. The night vision is then projected binocularly onto the visor.

Striker II will be flown on a Typhoon already later this year. BAE won’t disclose who it is talking to, but it reasonable to assume that the RAF will be interested.

The RAF is also considering its options regarding recce capabilities beyond Tornado GR4 and RAPTOR pod. Rafael is said to be offering the new TopLite MHD (Multi-High Definition) for Typhoon integration: the pod offers visual, near infrared, medium-wave infrared, short-wave infrared and laser units integrated in the same stabilized package. It can also cover the targeting role currently performed by the Litening III, also by Rafael.  


On the complex weapons front, MBDA has announced that Brimstone 2 series production has now started at Henlow, and the missile will be operational on Tornado GR4 next year. Typhoon will hopefully follow by 2018. Brimstone 2 is the solution for the SPEAR Capability 2 Block 1 program. Future evolutions of the missile are expected, which could see it being adopted on British Army Apache helicopters from around 2021 as a replacement for the Hellfire as it goes out of service. Successful firing trials on a Reaper have been concluded, and integration could follow pretty soon.

Paveway IV

Raytheon provided an update regarding the development of new capabilities for Paveway IV under the SPEAR Capability 1 program.
SPEAR Capability 1 is, as always, further broken down in blocks. Block 1 is about the development of a low-collateral damage warhead option. Tests on the ground have already been carried out.
Block 2 is about developing a capable bunker-buster warhead. The challenge is achieving good penetration and lethality while maintaining the external shape and the current 500 lbs mass of the warhead, to avoid costly trials and integration procedures. The bunker-buster warhead has an external shroud which makes it look like a base warhead, but the shroud is shredded on impact as the special, hardened core penetrates deep into the target. The objective is developing a suitable replacement for the much larger 2000 lbs Paveway III BLU-109, which is not expected to be integrated on Typhoon and F-35B and thus looks set to end its career together with Tornado.

On its own, outside of SPEAR, Raytheon is developing a new digital seeker with high off-boresight field of view and proportional navigation to enhance the capability to hit moving targets running at up to 70 mph.
Raytheon is also working to offer enhanced, active anti-jamming GPS guidance. All capabilities should be available by 2018.
Improvements have been rolled out onto the Paveway IV already several times: the over 4000 bombs produced for the UK MOD have in fact actually been delivered in at least three marks (MK 0, MK 1 and MK 2).

In the next few years, it can be anticipated that Paveway IV, with its various new warhead options, will replace all other, earlier Paveway iterations in the british arsenal, with obvious logistic advantages.


Development of SPEAR 3 continues, and at Farnborough a mock-up gives us a first vision of the Common Weapon Launcher option that MBDA has been asked to come up with to ease SPEAR 3 integration on Typhoon. The Common Weapon Launcher has the same general shape and mass of the current triple rail Brimstone launcher, so that the two different weapons can capitalize on the same flight trials, with the savings that this enables. It is worth remembering that SPEAR 3 actually sees light with a SDB-like quadruple rack especially meant to maximize internal carry capability on the F-35. 

SPEAR 3 on the Common Launcher, with Brimstone in background, to the right. Note the folded wings and the air intake on SPEAR.
SPEAR 3 has many points of contact with the American Small Diameter Bomb II by Raytheon, and indeed Angus Batey writes from Farnborough about the drive of Raytheon to try and sway the MOD away from the MBDA product.
Despite all the points of contact, however, it must be noted that SPEAR 3 is a powered weapon, while SDB II only glides. SPEAR 3 has two small side intakes for its Hamilton Sundstrand TJ-150 turbojet, and the engine opens up a whole range of unique capabilities for a weapon so small. This 80 kg mini-cruise missile can be launched even when not facing the target (differently from SDB) and with more freedom regardless of launch height and weather conditions that affect gliding. The weapon is to be able to engage fixed and mobile targets alike, with a data link enabling post-launch control and retargeting. The propulsion is also fundamental in order to achieve the range of at least 100 km that the MOD wants. SDB is a 45 nautical miles glide weapon, while MOD and MBDA believe they can achieve north of 62 nautical miles for SPEAR. 

SPEAR 3 comes with a quadruple rack, but for ease of integration, the triple launcher could be used on Typhoon.
The proposed VL SPEAR in quadpack
MBDA is also offering a vertical launch SPEAR 3 development for future use ashore and on warships. Four SPEAR 3 rounds could be fitted inside a single MK41 cell, for example on Type 26 frigates.


After many delays, FASGW is finally on the move, with all contracts signed. 48 million pounds are going to Thales to complete development and validation of LMM and of the five-round launcher, the FASGW(H) contract has been signed time ago with France, and at Farnborough a 90 million deal has been signed with AgustaWestland to integrate both weapons on Wildcat. 

Sea Venom integration contract is signed
The FASGW(H) has also a name, finally: according to Jane’s, the MOD has chosen the name Sea Venom. 

Thales has also showcased for the first time one LMM derivative that was known to be in development: the Free Fall mini munition, primarily meant to arm UAVs. The FFLMM is a gliding mini-bomb obtained by removing the LMM rocket motor and adding redesigned wings. The weapon is 70 cm long, 7.6 cm in diameter and weights just 6 kg while retaining the LMM's dual-effect shaped charge and pre-fragmented blast warhead

Thales has added INS and GPS navigation as well as a semi-active laser guidance that replaces the beam-riding system currently used on the LMM. An airburst fuze is a possible development for the near future. The weapon will glide 4 kilometers if dropped from 10.000 feet, and 3 munitions can be carried on an Hellfire rail. 

The british MOD so far has not committed to this variant, but has been involved in its development. Development launches were made from a Lynx AH7, for example.

FCAS and Storm Shadow MLU

Two Memorandum of Understanding documents have been signed with France at the Farnborough airshow: one sets out the course of the next phase of joint studies for the Future Combat Air System (FCAS), the UCAV to be jointly developed for the 2030s.
The other MOU covers the next phase of joint activities aimed at the incoming Mid Life Upgrade for the Storm Shadow missile.

More Merlin HM2 might still be within reach

After the successful exercise Deep Blue, which saw Illustrious deploying in the Atlantic with 9 Merlin HM2 and two Type 23 frigate escorts to stage a full-size ASW war against four between british and French nuclear submarines and dutch diesel-electrics, the RN has achieved IOC with the first 15 Merlin helicopters upgraded to HM2 status.

Flight trials of the two systems in the race for CROWSNEST will soon be ongoing, beginning with the Lockheed Martin VIGILANCE podded solution “in the coming weeks”. The THALES solution based on the current, well known Searchwater “bag” will follow.

The key development emerged at Farnborough is that the Royal Navy has obtained a re-evaluation of the case for upgrading some more helicopters. The original HM2 plan was for 30 helicopters and 8 options, but at one point the option was dropped and it seemed to become more or less official that the 8 HM1 remaining would be shelved.
The Royal Navy is now trying to flesh out a plan for the upgrade of some more helicopters, up to 8 of them, in recognition of how high in demand the Merlin is and is going to be. The current assumption is that the 30 Merlin HM2 will have to deliver a forward fleet of 25, 14 of which would be committed to the aircraft carrier when it deploys at sea. The 14 helicopters would cover the requirement for an ASW force of 9 (to ensure 24 hours coverage) and an AEW group of 4 to 5 helicopter swith CROWSNEST kit.
Add to this training needs, the unexpected and the need for frigate small ship flights, and it becomes evident how hard worked the fleet would be.
Obtaining more HM2s would be a massive boost.

UAVs at sea

The Scan Eagle contract for the Royal Navy has been extended out to June 30, 2017. The earlier contract would have ended in April 2015.
Meanwhile, AgustaWestland is continuing to develop the optionally manned SW-4 SOLO helicopter. It has showcased it in unmanned flight to the Italian ministry of defence, the company announced, and later this year or early in 2015 the system will be used for the Royal Navy’s RWUAS demonstration campaign which is expected to include operations at sea on a Type 23 frigate.

RAF A400M deliveries to be accelerated by 3 years  

The A400M has received around 80 tons of fuel in air to air refueling trials which used the Voyager tanker that the RAF is providing for the Atlas program in Getafe. Parachute launch trials have also been cleared, and will continue with expansion of airdrop capability to include low-level, high-weight load extractions.

Program-wise, the RAF now expects to receive its full fleet of 22 aircraft by March 2018. Until last year, the 22nd unit would have not been delivered before 2021.
The deliveries have been reprogrammed thanks to a swap of production slots with France. This year, starting with MSN 15 in September, the RAF will receive four aircraft. Six more will follow by the end of next year, with the balance spread over 2016, 2017 and early 2018. 


  1. Where are you sources for SPEAR 3? Google info is 2 years old


    Did you spot this one too Gabriele ?


    1. Yeah, but i want to wait until we'll see something more substantial on that front... or perhaps write a new post specifically on how i see the MPA situation.

  3. Typhoon AESA not until the "early" 2020's? So probably 2021-2023?

    For gods sake, this is beyond a joke. We should have just went solo on that plane years ago and did what the French do for the Rafale, develop only for ourselves. No time wasted on munitions we don't need, no time wasted on arguing over who gets to put in the 3rd screw on every second pylon and absolutely none of this being held back from upgrading our OWN planes because whatever country can't be bothered.

    We'd likely have had a thrust-vectoring, conformal carrying, omniroling, AESA equipped and soon Meteor carrying plane by now.

    1. I agree with Anonymous. I prefer UK only to multi national with its delays.

      Also, why will QE be conducting its trials over the Atlantic at the US?? We did once carry out far more complex carrier ops through decades in our own waters! The 1970's HMS Ark Royal for example with her Phantoms and Buccanears. Is this a case of the US wanting a good look like with Astute?

      Good write up otherwise Gabriele, and nice that the Atlas force will build up quickly.

    2. As fantastic as it would have been to go solo, i doubt there would have been enough money for it. The UK went solo with the Austere ground attack capability for Tranche 1, but it was a less than 100 million investment. It is quite unlikely that AESA and other things could be funded solo, unless everything else take a big blow.

      For the Typhoon delays, i understand the frustration. I find it unaccaptable that it took so long to get here, but that's unfortunately how it is.

      As for trials for QE, she will sail to the US because that's where there will be available F-35Bs and available USMC expertise that can be used to begin trials on time. Waiting for british aircraft and personnel to be fully ready would impose a delay on the beginning of the trials.

      And the trials of Astute had nothing to do with the US wanting to look good. With over 40 SSNs, frankly, they don't need that. Over there they have the best equipped underwater test range in the world, available nuclear subs to train against, a firing range huge enough to fire 2 Tomahawaks and test the retargeting function as well, etcetera: things that can't be done in UK waters.

    3. I didn't say "the US looking good" I said " a good look " as Sub ops is one area of the Special Relationship where UK/USA are very close so doubtless they would be interested in our latest effort, use AUTEC etc.

      I take your points on the other stuff though. :-) Makes sense to save time on the trials.

  4. Not all good news but it's nice to see at least some for a change!

    Queen Elizabeth hasn't even been fitted out yet and she already looks magnificent! A basic air-group of 12 F35 and 14 Merlin's sounds all things considered pretty good from where i'm standing. Let's just hope she does occasionally go to sea with a 'surge' air-group of 24 F35 for some high intensity training and the chance to show off a crowded deck!

    Seems like the conformation of the long expected with Sentinel, Shadow and Reaper. Slightly concerning that they have only been granted an extension in service until 2018 but frankly they prove to be so dam useful time and time again that i think everyone will be quietly confident that they will continue past this point. Or perhaps if an MPA solution is getting off the ground around then it might also be factored in as an eventual Sentinel replacement?

    A relief to see some movement on Typhoon's weapon/sensor integration but it's only a case of making up for the criminally slow lack of progress so far. At least it looks like Brimstone/Storm-Shadow will be on-line in time for Tornado's retirement, the possibility of gaps in this area would have been very worrying.

    It's nice to see Brimstone being increasingly developed with the Americans taking a renewed interest and 'Sea Brimstone' emerging as well as Brimstone 2 reaching service. Fingers crossed we see it head onto Apache.

    Sea Venom....good choice! Now we just need to rename the awful 'Sea Ceptor' Shot in the dark which may be a complete no-go for various reasons but if we shop around for an air-launched ASM for the F35 at some-point would some sort of Sea Venom variant be at all attractive?

    Potentially excellent news with the Merlin HM2, the commonly held belief for quite a while has been that the spare 8 air-frames had been cannibalized for the HC3/4 conversion but the fact that they are even considering such a move must mean they are still in reasonable condition. I've come around to the idea of Crowsnest being a bolt-on system across the Merlin HM2 fleet but with 14 air-frames allocated to CVF and a whole host of other commitments factored in alongside the training/maintenance cycle it seems to be dawning on TPTB that 30, however good, just isn't enough. Any extra air-frames thrown into the mix will be a major boost. I'm guessing we will see a decision come fairly soon so that potential additions can be tagged on-to the end of the current program?

    Great news on the A400m delivery dates. Now we can hope (although i won't hold my breath) that by 2018 it will have more than met expectations and sufficient money will exist for us to take up the option on the remaining 3 cut from the original order!

  5. A merge of the Sentinel R1 and MPA requirement is something i've thought about for a long time, and probably the best option to pursue.

    A decision on more Merlin HM2 is most likely needed soon. Maybe next year. I really hope it can be done, because it would be very helpful.
    The 8 HM1 which were to be options have not been cannibalized (4 other airframes from the original 44 have; 2 Merlin were lost in accidents early in their service life) but have been kept separated from the initial HM2 contract exactly because they were needed to ensure the HM1 fleet had enough machines to keep working while many of the helicopters were handed back to factory for the upgrade.

    A Sea Venom version for use on the F-35B... well, i guess it is a possibility, but not a very attractive one.

    1. Providing the basic platform accommodates the varying specifications then perhaps whatever is selected for a MPA could not only replace Sentinel but also in time Sentry as well.

      I think we really should be looking to very belatedly replace Sea Eagle with something new and resurrect an air-launched ASM capability. Now that I've looked at the relative specifications of Sea Skua and the new Sea Venom i can see that we would need something with a lot more punch!

      I still think the NSM could be a goer.

  6. Hi Gabriele, I'm a new fan of your blog and have been enjoying reading through your posts, as they're a great source of detailed information on the Royal Navy. I have a question about the QE class carriers which you might know the answer to. The MOD has stated that each ship will be capable of carrying up to 40 aircraft. However, from looking at diagrams of the internal hangar it appears that it only has space for 24 F35s, and that's if they're packed in like sardines without any space to move aircraft around, perform maintenance etc. So I'm wondering whether the remaining 16 aircraft will be stored on deck, or if the diagrams are simply wrong. I ask because I've heard several people say that the Royal Navy has a policy with its carriers of only carrying as many aircraft as can be stored in the hangar, and does not store aircraft on deck, but I'm not sure if that's true. Cheers.

    1. The correct number of F-35 in the hangar is 20. 24 was in a previous design, which was scaled down somewhat before finally being firmed.
      Anyway, there is deck parking space for some 24 aircraft and helicopters, and while the Royal Navy probably still places much greater importance on the hangar than the USN does, deck parking is definitely on, and part of the equation.

      QE's maximum optimised air wing is 36 F-35B and some 4 Merlin in AEW role. More than that can almost certainly be carried, but it starts being a non-optimal fit which requires more moves and more attention to shift parking arrangements and make everything fit.

  7. Gaby

    I keep on hearing different dates for the entry into full service of "HMS Queen Elizabeth". By "full service" I mean having passed its sea trials and having been equipped with F35s, Crowsnest and ASW Merlins etc., the whole complement of aircraft it's supposed to finally be equipped with, all of them ready for action.

    What's the earliest you estimate that to be? If is as late as mid-2019, that means almost five years when the only flattop we shall have (given the de-commissioning of "Invincible") will be "HMS Ocean", and that only a helicopter carrier. Not a very happy state to be in! One would have to cross fingers another Falklands does not arise in that five-year window!

    1. HMS Queen Elizabeth should be available to complement Ocean as helicopter / commando carrier already in late 2017, possibly. With Ocean to bow out soon afterwards, very possibly, in exchange for the commissioning (and hopefully the use) of Prince of Wales.
      But i'd say a "full" carrier capability will probably take until late 2019, or early 2020 to be achieved.

  8. Gaby - great work as ever! One interesting piece of news youv'e not mentioned is the report by Richard Scott (usually very reliable with excellent contacts) in Warship World that the MoD has selected the mk41 for the T26 vls requirement. This all but rules out MBDA products and makes it almost certain that the RN will fall in step with the USN. This is not a bad thing. The choices - both of which would be a dual land attack / anti-ship weapon - are either LRASM or possibly the refreshed Tomahawk that Raytheon is furiously peddling (with new seeker and warhead). Either of these would be a huge step forward in capability for the RN. Aligning with the USN reduces risk and price and guarantees support and development for decades. Smart. Also, Scott says 24 cells. He's very well informed. So, fingers crossed!


    1. I have heard the news of MK41 from a couple of sources, already. But, as reliable as these may be, i do not quite feel confident enough to splice the mainbrace myself. I prefer to be careful and wait for some more evidence myself.

      Anyway, MK41 is not going to rule out MBDA products: look at CAMM integration ongoing. That is only the beginning of the story, i'd think, even just for the (very good) reason that MK41 is in widespread use globally, and MBDA will want a chance to tap in to that market. The success of CAMM in MK41 in New Zealand is hopefully going to be just the first success of many.

      Again, one key factor is that MK41 compatibility measures exist, that allow integration of foreign systems in it. The same isn't true of Sylver, at this date.

      Even at the physical level, the Sylver cells are 22 inches in diameter, versus 25 inches for MK41: it'll be always much easier to migrate MBDA products "born for Sylver" to MK41 than doing the opposite.
      I don't think the door would be closed for SPEAR 3 and/or the Future Cruise and Anti Ship missile in the longer term. Quite the opposite, actually.

      Type 26 is always on my radar, and i will write about it as soon as something comes out that i can more confidently verify by myself.

  9. So it looks like the US decision to go with Pratt and Whitney alone for the F35 has come back to bite them, UK and everyone else with an interest. What a mess.

    1. Is someone willing to pay for an alternative engine as of today? No. Everyone, US included, has other uses for the billions required for such a project, so it is a non starter to keep banging on that nail.

      Maybe in the future a second engine will re-appear, but i don't expect it anytime soon. It should also be noted that aircraft with a single engine option are the norm, not the exception. The Typhoon initially had a RB199 option, but that never really went anywhere. Many others go with the single engine type, including F-22.

      As for the engine issue, engines occasionally fail.
      I suggest you make a research on Hornet and Super Hornets lost to engine failures even just in the last few years. Out of my mind, i can think of one crash last June, one in January, one in april 2013, one in april 2012, and a USMC Hornet in august 2011.

      Yet, nobody thinks the Super Hornet is doomed, no one thinks its engine is unreliable or not adequate.
      Then the first class A failure develops on a F-35, and the world falls over backwards thinking it should have two engines installed, two different engines to choose from etcetera.

      "What a mess" is what i think of what media overexposure, hostile lobbying and unrealistic claims have done to the F-35 program, causing every little issue to be reported like it is doomsday.

  10. Gabby - recent announcements and hints seem to be making future weapons integration on fast jets, and the thinking behind it, clearer.

    Typhoon takes over Brimstone and Storm Shadow role from Tornado; on F35, priority will be given to SPEAR 3, which is being designed specifically for it. Despite earlier announcements about aspiration for Brimstone and Storm Shadow integration, everything now points to priority to SPEAR 3, which fingers crossed will be a superbly versatile weapon and one capable of carriage internally in numbers that are greater than any present combination on RAF jets bar full Brimstone load out. All for the weight of two 1,000lb bombs!

    With this in mind it is possible to envisage the following roles for a Typhoon / Lightening force:

    First Day:
    Typhoon - Storm Shadow against command and control + counter air
    Lightening - destroy anti-aircraft batteries with SPEAR; hit bunkers with PAveway IV bunker buster variant

    Typhoon: Air to air; CAS with Brimstone and Paveway IV
    Lightening: whatever you want air support with SPEAR 3 / Paveway IV

    In addition, at sea, Lightening also of course takes on fleet air defence, counter air and anti-surface with SPEAR 3.



  11. Gabby- Was wonderin if we do re-engine the apaches, are the RTM engines interchangeable with the merlin engines? Enabling a life extending 'pool' of common engines that the merlin force can draw upon extending the OSD of the current fleet of engines?
    just a thought

    1. Not at all sure if it would be possible to actually swap Apache and Merlin engines. The engine type is the same, but i wouldn't be surprised if there were differences making the two engines sub-variants perhaps not completely common.

  12. Gaby

    I see that the UK Government has not dismissed the possibility of a new-build manned aircraft sometime in the future. In an article on “Defense News” about how the Reapers will join the U.K’s Core Equipment programme, mention is made of how a national program being undertaken to look at the mix of future combat air requirements from 2030 could include a “new-build manned aircraft.”

    A two-year FCAS programme has been launched to inform the SDSR of the most appropriate force mix to meet future combat air programmes from 2030. The options include an unmanned air combat vehicle along the lines of Taranis, an additional buy of Lightning II (F-35), a Typhoon life extension and an alternative new build manned aircraft.”

    Perhaps rather unexpected?

    1. I wouldn't say it is unexpected. A life-extension for Typhoon to carry on beyond 2030 has long been assumed to be almost certain, and a possible further manned aircraft has never been ruled out.
      Finally, the idea is definitely to try and purchase more than just 48 F-35s, and over time the balance is expected to probably see more F-35s than Typhoon.

      But it is all in a quite distant future, so all sort of things can happen in the meanwhile.

  13. Gaby

    I don't know whether you consider this to be a matter of relatively minor interest but the same report mentions how the Government apparently does not intend to retain T-Hawk in future. '"Of the existing UAS currently used on operations in Afghanistan by the Army [Hermes 450, Desert Hawk 3, T-Hawk and Black Hornet] it is our intention that the Desert Hawk 3 and Black Hornet are retained,” said the government.'

    Hermes 450 will of course be replaced by Watchkeeper but I thought that T-Hawk was an essential part of the Talisman system. I hope it does not mean there is some doubt over the retention of Talisman itself.

    1. I did notice that passage, but i'm not sure if we should be worried or not. Earlier indications suggested that the whole TALISMAN system would be retained, including T-Hawk.

      Funding for Talisman into core was announced a while ago, and should in theory not be in discussion.
      Losing T-Hawk would impact search capability negatively, but it would not be a death blow in itself. Talisman is definitely being retained, and the Army hopes to improve the system in the next decade. The non-mention of T-Hawk there might be a mistake.

  14. Gaby

    Many thanks for your prompt and invariably polite reply.



Everybody can comment on this blog without needing a Blogger account. It is meant to keep the discussion free and open to everyone. Unfortunately, anonymous accounts keep the door open for spammers and trolls, so i'm forced to moderate comments and approve them before they appear. Apologies for the inconvenience.