Unsurprisingly, Belgium has announced that it has chosen the American F-35 fighter.Unsurprisingly, Belgium has announced that it has chosen the American F-35 fighter. Second betrayal of partners by Belgium, "heart of the European Union" since the 1970s. After 48 years, new proof to what extent Belgium's policy is influenced by the Americans, which was also the case in 1970. New proof to what extent European integration can be considered serious. Quo vadis European integration?
Why has Belgium once again turned its back on the European preference?
Thanks to two defining criteria that were insinuated in the specifications for the replacement of the F-16: the ability to carry a US-made nuclear bomb and stealth. Two crucial criteria for the success of the F-35. Belgium has been carrying out the nuclear mission on behalf of NATO for decades. The F-16s stationed at Kleine-Brogel (F-16A) are capable of carrying and dropping an American B-61 nuclear bomb. In any case, Brussels who wishes to keep it, had made it known.
This skewed the competition and favored the American F-35 against its four competitors: F / A-18E / F Super Hornet, Rafale F3R, JAS-39E / F Gripen and Eurofighter Typhoon. Only the F-35 will be able to carry out the mission of nuclear attack by carrying a B-61 American gravitational bomb. It is designed as dual capacity (conventional and nuclear) and should be able to carry a bomb B-61 in a later phase (!) of its development, probably from 2022 (!).
What is not the case for other contenders to Belgian market, with the exception of the Rafale, which already carries a nuclear weapon. However, Germany has also made a formal request to the United States to integrate the B-61 under the Eurofighter. In theory, this ability could also be certified on the European fighter. Not sure if Washington shares with anyone the firing and releasing codes of the B-61s.
"Within the Alliance, Belgium has accepted, five decades ago, that its fighter jets have both conventional and nuclear capabilities, taking into account a joint analysis of the global threat. NATO is asking us to continue to maintain our combat aircraft available for any such missions, and we look forward to meeting all our obligations in this regard, " said Belgian Foreign Minister Didier Reynders.
In addition, the Belgian Air Force is close to that of the Netherlands, which without hesitation bought eight F-35s in March 2015 on a target of 37 aircraft.
Despite the fact that about 38,000 signatures were collected against the idea of equipping the Belgian air force with F-35 stealth fighter jets, the finance committee of the House of Representatives refused to hear the arguments opponents of this project.
The F-35 project is the most expensive project ever seen. The aircraft had several hundred defeats (hardver + software) his "brother" the F-22 Raptor, after it was put in place with the US Army, was less effective in the fight against the Eurofighter and the former F-16 is stealth is also highly doubtful.
According to a leaked test in 2015 also the F-35 Joint Strike Fighter’s demonstrated performance is inferior to the current fighters it is designed to replace. Specifically, the report marked for official use only (FOUO) finds that, in a series of 17 dogfights, the F-35 was consistently outmatched by an aging F-16 :
"One of the significant new issues raised by the report was the F-35’s difficulty in sustaining energy in close-in maneuvering combat—that is, the energy needed to turn and accelerate. The test pilot found this to be “substantially inferior” to older planes like F-15s, F-16s, and F-18s. In the tests, the F-35’s maneuverability against the F-16 was so limited that it could only point quickly enough to achieve a missile shot by executing one specific maneuver. But this move consumed so much energy that if the shot failed the F-35 would “ultimately end up defensive again”—which is to say, at the mercy of any opponent.
The report also homed in on flight control problems in the 20 to 26 degrees angle of attack zone, crucial for hard maneuvering. The pilot described the F-35’s computer-controlled flying qualities as “sluggish” for evasive maneuvering and “not intuitive or favorable.” This echoes information in a recent report from the Director of Operational Test and Evaluation (DOT&E) that described severe flying quality problems in this high angle of attack region—including uncontrollable wing drop and heavy buffeting (shaking) “that degraded the flight control system (two of three flight control channels become disabled), requiring a flight abort.”
Tag: BelgiumF-35RafaleEurofighterTomorrow, on 27 October 2018, Kandahar will vote in the country’s parliamentary election – a week later than the rest of the country. The delay comes after the assassination of, among others, the province’s police chief and strongman Abdul Razeq on 18 October 2018. The IEC has tried to remedy the problems that plagued the rest of the country last week, through additional training. This may not be enough to maintain the integrity of their new anti-fraud measures: voter lists and biometric verification – particularly since Kandahar has a history of mass fraud. AAN’s Martine van Bijlert, with input from Ali Adili and Ali Mohammad Sabawoon, takes a closer look at what we might be able to expect on Afghanistan’s third day of voting.
What can we expect on Afghanistan’s third election day?
Kandahar’s Provincial Electoral Officer Neamatullah Wardag told AAN that the IEC intends to open 173 polling centres on 27 October 2018, with a total of 1,113 polling stations. This is, on average, a little over six polling stations per centre but the variation in size will be wide. Some centres registered only few voters and will have one or two stations only, while other will have to have at least 15 or more. (1)
Some polling centres, particularly in Kandahar city, would be very crowded if all voters did indeed turn up (which is unlikely, even in the city). Nahiya nine in Kandahar, for instance has almost 29,000 voters registered in three polling centres, while three other urban districts have around registered 45,000 voters for six polling centres. Of course there will be many polling stations, but the crowds could still be large. Alternatively, if the centres are captured by strongmen or partisan security forces, as has happened in the past, the opportunity for fraud in these places would be significant.
So far, there have been no signs of a breakdown in the security situation or in discipline in the security forces, since Abdul Razeq’s death (AAN background here). Security in Kandahar city has been tight and there has been a steady stream of high profile visitors who have come to pay their respects, including President Ghani, Chief Executive Abdullah, former president Karzai and several Jamiat leaders.
It is difficult to predict the overall turnout, other than that it will be very low in the remote districts, where Taliban threats warning people not to take part in the election are expected to keep people away from the vote. In Kandahar city, Abdul Razeq’s supporters believe turnout might be buoyed by the wish to honour his memory. They emphasised that he had been killed only minutes after a meeting that focused on election security and had called on the people of Kandahar to come out and vote.
The death of Police Chief Abdul Razeq has the potential to rearrange Kandahar’s political scene. Different groups, both from Kandahar (such as the Karzai and Gul Agha families) and outside (President Ghani and others) may see new opportunities to try to get their own affiliates elected. His absence will also be felt during this vote, even though so far there seems to have been no security vacuum. But he was a looming figure in the elections, controlling security and, sometimes, the vote.
Unpacking Kandahar’s election numbers
There are a total of 112 candidates (13 are women, more by AAN here) competing for Kandahar’s eleven seats, of which three are reserved for women. Five have registered a political party affiliation; the remaining 107 have registered as independents. 99 of the candidates are men, 13 are women (full candidate list here). According to the 2018 population estimate by the Central Statistics Office (CSO), Kandahar has a total population of around 1,3 million.
According to the IEC’s voter lists Kandahar registered a total of 522,984 voters in this year’s new voter registration: 442,512 men and 67,276 women for the vote in the provincial constituency, and 13,196 Kuchis (gender not specified) for the nationwide election of kuchi representatives.(2)
The rate of registration varied greatly across the province. The district with the most registered voters was Spin Boldak, the birthplace and main power base of General Abdul Razeq. In Spin Boldak 86,082 voters registered to vote in 26 polling centres (11,801 of them were women; 2,015 were Kuchis), representing 15 per cent of the province’s total number of votes.
Four urban districts in Kandahar city (nahiya one, two, four and ten) each registered between 45,000 and 55,000 voters, representing a little less than 10 per cent of the total vote each. Three other urban districts registered a fair number of voters, (almost 29,000 in nahiya nine, and around 13,000 in nahiyas seven and eight). The five rural districts closest to the city – Zherai, Panjway, Dand, Arghandab and Daman – each registered around 20,000 to 30,000 voters in 16 or 17 polling centres each.
After that, it starts petering out: Mianeshin (909 voters), Ghorak (564 voters), Khakrez (409 voters), Shorabak (203 voters) and Reg (161 voters) all registered voters in single polling centres – with no women, except a handful in Khakrez. There was no voter registration in two rural districts – Nesh and Maruf – which also means there will be no vote. There are also four urban districts where no voter registration took place (nahiyas 11, 12, 14 and 15), which include the prosperous, largely-gated community of Aino Mina, Kandahar’s most densely-populated neighbourhood of Loya Wala are located and an insecure area bordering on Dand district. (3) Residents of Kandahar city, however, said that voters from these two areas would have easily been able to register in other neighbourhoods close by. [Update 27 October: According to the IEC there is voting in all nahiyasof Kandahar. They said the centres in question may have been listed under other areas.]
Normally, an election would most probably be won or lost in the areas where most votes are cast (in this case likely to be Spin Boldak and areas of Kandahar city). However, in an election like this, with many candidates and relatively small margins, seemingly insignificant areas can swing a vote, particularly if the votes are concentrated on a certain candidate. This is further compounded by the fact that the final results have so far been largely determined afterelection day, when the IEC had to decide which votes could be counted and which must be invalidated. For this reason, candidates and supporters are often incentivised to try to manipulate the vote wherever they can, in the hope that some of it will slip through.
What was the vote like in Kandahar in previous elections?
In the 2009 presidential election, Kandahar became famous for its “industrial scale” ballot stuffing (for an AAN report that raised the issue of mass fraud days after the election, see here). The fraud was particularly concentrated in the border provinces, where the late Abdul Razeq was then Border Police Chief at the time. Out of the around 250,000 votes that were cast that year, around 180,000 were disqualified in the ECC-led sampled audit, leaving only a little over 70,000 votes to be counted (see details here).
In the 2010 parliamentary elections, every single polling station in the province had reported open on election day, despite serious security challenges. 30 per cent of all polling stations were disqualified in full. After the IEC and ECC disqualifications, there were around 75,000 votes left (see here for more details).
The 2014 presidential election saw 270,000 votes counted in the preliminary count. In the various audits (the results of which were never made public) the province appears to have lost around 50,000 votes (see here). In the 2014 provincial council vote, which took place at the same time and was audited by the IECC rather than the IEC, Kandahar lost around 11 per cent of its votes, including all the votes of its top candidate. (4)
Will the new anti-fraud measures work?
In the past, when voters could cast their vote wherever they wanted, Kandahar provided ample opportunity for unmonitored and/or unopposed ballot stuffing that could be explained away with claims of suddenly improved security or surprise high turnouts. This was particularly the case in the province’s remote districts and in the districts that were under the firm control of local strongmen.
With the new registration system, voters have to cast their vote in the centre where they registered. The last-minute addition of biometric verification aims to weed out multiple registrations, multiple votes and the use of fake documents. If implemented properly, it has now become much more difficult to engage in multiple voting, mass proxy voting, ballot stuffing and manipulation of the count and data entry. But only if procedures are actually followed. The scope for (mass) fraud, and the difficulties the IEC will have to deal with this, will therefore depend on how messy the election becomes.
So far, the IEC in its public statements has downplayed the messiness, saying that only in a minority of the polling centres procedures were not followed and that the main problem had been teachers and other staff turning up late. The IEC also said it hope the vote in Kandahar would be an improvement, compared to last week’s two election days (see here and here and here for observation reports). Provincial IEC head, Wardag, told AAN that atechnical team, dispatched from IEC headquarters, trained the district electoral officers (DEOs) and polling centre managers, who in turn trained the polling station staff. The focus was mainly on the use of the new biometric machines.
The IEC initially made it clear it would invalidate all votes that were not cast using both the voter lists and biometric verification, but it has already been wavering. From what happened on 20 and 21 October 2018, it appears that there will be considerable leeway to get votes counted that were not without properly cast. (5)
This could provide an incentive for all forms of fraud, including the very blatant, in the hope that the results will slip through the cracks. Things to watch will thus include implausible high turnouts in both secure and insecure areas, significant numbers of voters turning up without having registered, and the mass malfunction or loss of biometric devices and voter lists.
Edited by Sari Kouvo and Thomas Ruttig
(1) According to the IEC’s lists voter registration earlier this year took place in 172 polling centres. Wardag could not explain why the number of polling centres had now risen from 172 to 173. He thought it might simply be a repetition on the list somewhere.
(2) The English-language summary, which can be found here has slightly different figures for Kandahar’s registration totals: 567,608 registered all together, with 557,344 registered for the vote in the provincial constituency – 483,749 men and 73,595 women (a little over 13 per cent) and – and 10,262 as part of the nationwide kuchi constituency.
The total number of registered kuchi voters nationwide is 168,015. Kandahar, according to this list, comes in fifth and is dwarfed, by far, by Kabul’s largely settled kuchi constituency (71,506 registered kuchi voters, or 43 per cent of the total). The other provinces with significant Kuchi registration have numbers comparable to Kandahar: Kapisa (13,651 or 8 per cent of the total), Nangarhar (11,535 or 7 per cent of the total), Logar (10,298 or 6 per cent of the total).
(3) Voters registered per rural and urban district, as provided by the IEC:
Kandahar’s rural districts
A total of 132 polling centres in rural districts registered voters. Mianeshin, Shorabak and Reg were among 32 districts that could not be accessed due to security problems at the time of the polling centre assessment in the second half of 2017. These three districts, as well as Ghorak, ended up with just one polling centre. Maruf and Nesh have no polling centres at all, even though are not mentioned in the list of 11 districts countrywide which, according to the Afghan Ministry of Interior, are fully under Taleban control.
Kandahar’s urban districts (with a brief description of the nahiyas):
A total of 40 polling centres in urban districts registered voters. The districts that are not on the list are:
(4) In a letter to the IEC, the IECC said it decided to disqualify the candidate after an audit of over 600 polling stations in Kandahar, when they found that “all his votes had problems.” Such problems included ballots not being removed from their stubs, large numbers of ballots with similar tick marks, made with the same markers, which led them to the conclude that there had been systematic fraud.
(5) As reported here, the IEC will need to deal with three types of election results: a) votes from polling stations that used both the voter lists and the biometric verification, b) votes from polling stations that used only the voter lists, without capturing the biometric verification data, and c) votes from polling stations that used neither of the two systems and made new on-the-spot, handwritten voter lists. (see here for background).
NATO response to Vostok 2018 : Trident Juncture 18, abbreviated TRJE18, is a NATO-led military exercise to be held in Norway in October and November 2018 with an Article 5 collective defence scenario.
Trident Juncture 2018 will consist of three main parts:
- A phase of deployment lasting from August to October,
- LIVEX (live field exercise) from 25 October to 7 November. The land battle will take place in the area south of Trondheim and north of Rena Camp in Hedmark County. There will also be sea activity along the Norwegian Coast, the North Sea and limited areas in The Baltic Sea and Skagerrak. There will be air activity in the airspace over Norway, Sweden and Finland.
- CPX ( command post exercise) from 13 to 24 November 2018 at NATO's Joint Warfare Centre in Stavanger, Norway. This is a data simulated desk exercise to train the headquarters. This exercise is also a certification test for Allied Joint Force Command Naples.
The Norwegian Armed Forces have called the exercise the largest to be held in Norway since the 1980s, it will be NATO's largest exercise since 2002. An expected 50,000 participants from 31 nations will take part, including 10,000 vehicles, 250 aircraft and 65 vessels.
The exercise will mainly take place in central and eastern parts of Norway, and air and sea areas in Norway, Sweden and Finland. The main goals of Trident Juncture is to train the NATO Response Force and to test the alliance's defence capability. For Norway, the exercise will test the country's ability to receive and handle allied support.
Tag: Trident Juncture 2018Vostok 2018EDA and Thales Six GTS France SAS have signed a contract within the Agency’s EU Satcom Market project for the provision of secure network and communication services to the Military Planning and Conduct Capability (MPCC) and the EU’s Training Mission (EUTM) in Mali. The contract contains several options which, when triggered, will extend the services also to the EU Training Missions in the Central African Republic and Somalia. The contract has a potential value of €6 million and runs until the end of 2021.
The specific contract was awarded following a reopening of competition between contractors previously awarded the Service Framework Contracts for the Provision of 'Communication and Information System (CIS) Services for Headquarters and Deployed Forces' in the context of the EU SatCom Market Project
Thales Six GTS France SAS will provide network and communication services for both unclassified and EU Classified Information (EUCI). Services provided include a secure WAN with LANs, work stations, printers, VoIP phones, VTC and encrypted mobile phones for EUCI communication, SMART phone communication application, Cyber Defence services, technical support, training, accreditation support and transportation.
The contract signing is the result of a close cooperation between EDA, MPCC and the missions’ CIS personnel to define the requirements and evaluate the most advantageous proposal. EDA has been in the lead of the process up to the signing of the contract and will continue to be fully responsible for its management throughout the implementation.
MPCC, which is responsible at the strategic level for the planning and conduct of non-executive military missions under the political control and strategic guidance of the Political and Security Committee, will be able to exercise its responsibilities in a secured environment. This new capacity will enhance the reactivity of MPCC by speeding up the flow of information not only between MPCC and missions, but evenly between missions. MPCC and CPCC already study the possibility to enlarge this capacity to other CSDP actors.
The overall purpose of the EU SatCom Market project is to provide contributing Member States with an option to efficiently source cost effective commercial Satellite Communications (SatCom) as well as wider Communication and Information Systems (CIS) services. The Satcom services offered include end to end services with transmission links as well as SatCom terminals for all bands (including military). The CIS services offered cover the integration of telecommunications with radio and IT networks and include hardware as well as software. The range of services provided through the EU SatCom Market project enable users to access, store, transmit, receive and manipulate information required to meet a wide range of operational needs, both abroad and at home.
A major component of the B61-12 nuclear bomb will now be produced at the Y-12 National Security Complex in Oak Ridge. The Complex is one of the nation’s most important national security assets. The 811 acre site contains the world’s largest stockpile of highly enriched uranium, enough to build 14.000 nuclear warheads. Y-12 is now qualified to manufacture the B61-12’s canned subassembly, which is the second stage of a modern thermonuclear weapon, and is also part of the nuclear explosives package. Y-12 Site Manager Bill Tindal said, “We are delivering a key contribution to global security through this program. I couldn’t be more proud of how all organizations pulled together to accomplish this difficult task.” The B-61 is currently undergoing a life extension program, which will consolidate four versions of the bomb into one. The nuke can be launched from B-2A, B-21, F-15E, F-16C/D, F-16 MLU, F-35 and PA-200 aircraft. Delivery of the first production unit is scheduled for March 2019.
Colonna’s Shipyard is being contracted to work on the Navy’s first Spearhead-class ship during the ship’s upcoming regular overhaul and dry docking phase. The firm-fixed-price contract is valued at $7.9 million and provides for a 67-calendar day shipyard availability. The contractor will be responsible to conduct structural inspection of the hull, perform a variety of repairs, support the main propulsion engine’s overhaul, replace heater exchangers and perform gear maintenance. The USNS Spearhead is an Expeditionary Fast Transport ship that was launched in 2011, it is designed for the fast, intra-theater transportation of troops, military vehicles and equipment with aviation support. Work will be performed at Colonna’s shipyard in Norfolk, Virginia. The Regular Overhaul availability is expected to be completed by January, 2019.
National Industries for the Blind is being awarded with a contract modification that extends a one-year base contract for the second year in a row. The modification is priced at $13.1 million and allows for the continued production for the advanced combat helmet (ACH) pad suspension system. The ACH is made of a new type of Kevlar to provide improved ballistic and impact protection. The helmets are also designed to allow an unobstructed field of view and increased ambient hearing capabilities for the wearer. Modular, flame-retardant, and moisture-resistant pads act as the suspension system between the wearer’s head and the helmet. This allows a soldier to fight more effectively when wearing body armor. Work will be performed at facilities in Virginia, Pennsylvania and North Carolina. This second option period is set to run through October 26, 2019.
Contitech is being tapped to provide the US Army with vehicle tracks for its M109 Paladin artillery system. The firm-fixed-price contract is valued at $20.1 million and will run through July 8, 2021. The M109 family of systems has been in service since 1962. The latest variant is the BAE produced Paladin M109A7 next-generation artillery system. The new variant incorporates upgrades to hull, turret, engine, and suspension systems that offer increased reliability, survivability and performance over its predecessor. The 155 mm cannon is mounted on the chassis structure common to the Bradley tracked fighting vehicle. Work will be performed at Contitech’s factory in Fairlawn, Ohio.
Middle East & AfricaSaudi Arabia may be blocked from future arms purchases as world leaders are calling on the government to provide more information on the death of journalist Jamal Khashoggi. German chancellor Angela Merkel recently said that future weapon deliveries to the Middle-Eastern nation are highly unlikely until an investigation into the journalist’s death has been carried out. The German parliament approved exports worth $416.4 million to Saudi Arabia in 2018 alone, making it Germany’s second biggest defense customer, right after Algeria. One of the largest deals in recent year included the Saudi purchase of 270 Leopard A2 Main Battle Tanks. Germany is currently calling on other countries to consider setting up bans on the sales of arms to Riyadh.
EuropeBelgian news agency, Belga reports that the country has chosen Lockheed Martin’s F-35 JSF over the Eurofighter Typhoon to replace its old fleet of F-16s. Despite the final deadline being set for October 29, government sources are confident that the US-made fighter jet will make the cut. Lockheed spokeswoman Carolyn Nelson told Reuters that “the F-35 offers transformational capability for the Belgian Air Force and, if selected, will align them with a global coalition operating the world’s most advanced aircraft.” The potential deal could also strengthen Lockheed’s position in forthcoming tenders in Switzerland, Finland and Germany. The order for jets due for delivery from 2023 is estimated to be worth $4.14 billion. European countries that currently fly the F-35 include Britain, the Netherlands, Denmark, Italy and Norway.
Jane’s reports that the Romanian Ministry of Defence is expected to soon make a decision on the procurement of new multirole corvettes. The planned acquisition program sees for the delivery of four corvettes at a cost if $1.85 billion. The new 2.500 ton-class vessels must come with capabilities across the ASW, anti-surface warfare, AAW, EW, SAR and naval gunfire support spectrum. Current bidders include Damen Schelde Naval Shipbuilding of the Netherlands, Italy’s Fincantieri, and France’s Naval Group. All bidders are currently in line with Romanian stipulations for local industry participation. The French Naval Group, has associated with local Constanta Shipyard, Dutch group Damen Shipyards, owns the Galati shipyard and is in the process of acquiring the Mangalia shipyard, Italian group Fincatieri, controls the Tulcea and Braila shipyards. The corvette program is the centrepiece of Romania’s naval modernization process that seeks to mitigate the growing Russian military threat in the Black Sea.
Asia-PacificIndia’s sole operational aircraft carrier will start sea trials by the start of next week. The INS Vikramaditya recently completed its second refitment at Cochin Shipyard, a process which cost close to $96 million. Captain Puruvir Das, the carrier’s commanding officer, told the New Indian Express “soon, we will start the sea trials, which will take place off the Kochi and Goa coasts. We are hopeful of returning to the Western Naval Command without delay.” During the refitment major work was carried out, including an extensive hull survey and repainting, as well as some large scale repair of the ship’s shaft system. “The refitment will enhance the operations of Vikramaditya. It will be ready for sea operations once the trials are completed,” added Captain Das. The Kiev-class former Russian Navy aircraft carrier has been in service since 2013 and upgrade of its infrastructure were started in September 2016.
Today’s VideoWatch: GAO: Flight Test of a B61-12 Nuclear Bomb
When moving whole units, shipping is always the cheaper, higher-capacity option. Slow speed and port access are the big issues, but what if ship transit times could be cut sharply, and full-service ports weren’t necessary? After Australia led the way by using what amounted to fast car ferries for military operations, the US Army and Navy decided to give it a go. Both services leased Incat TSV/HSV wave-piercing catamaran ship designs, while the Marines’ charged ahead with very successful use of Austal’s Westpac Express high-speed catamaran. These Australian-designed ships all give commanders the ability to roll on a company with full gear and equipment (or roll on a full infantry battalion if used only as a troop transport), haul it intra-theater distances at 38 knots, then move their shallow draft safely into austere ports to roll them off.
Their successful use, and continued success on operations, attracted favorable comment and notice from all services. So favorable that the experiments have led to a $3+ billion program called the Joint High Speed Vessel. These designs may even have uses beyond simple ferrying and transport.
The design specifications established for the JHSV described an ocean-going vessel 450 feet in length or less, capable of carrying 600 short tons of cargo up to 1,200 nautical miles at a speed of 35 knots. It must also have seats for at least 312 passengers, and must be able to provide long-term berthing and galley facilities for at least 104 of those passengers in addition to the vessel’s 41 crew.
A single firm was ultimately selected to produce all planned JHSV ships, and Austal beat their rival Incat for the contract. Austal’s design ventured slightly beyond the program’s specifications. Length is just 103.0m/ 337.9 ft, with a Beam of 28.5m/ 93.5 ft, and a miniscule Draught of just 3.83m/ 12.57 ft.
The ship’s 4 Wartsalia WLD-1400-SR waterjets are powered by the same MTU 8000 class diesel engines used on Austal’s Independence Class Littoral Combat Ship, and the Hawaii Superferries. Specifically, JHSVs use 4 MTU 20V8000 M71Ls, rated at a maximum of 9.1 MW each. These engines and waterjets can push the ships to the required 35 knots at full cargo load, or 43 knots unloaded.
Austal’s design offers embarked troop berthing for 150 (104 permanent, 46 temporary) that can support 14 days of operations. Alternatively, airline-style seating for 354 troops, in addition to the crew of 41, allows the ship to support 96 hours of operations. Cargo capacity is up to 700 short tons/ 635 metric tons, in a usable cargo area 1863 m2/ 20,053 ft2, with a clear height of 4.75m and a turning diameter of 26.21m. The cargo area also has 6 ISO TEU (20′ ISO container) interface panels, for containers that need power. The Austere Loading Ramp Arrangement can support vehicles up to 70 ton M1A2 Abrams tanks, per requirements, and a telescoping boom crane can lift 18.2 metric tons at 10m, dropping to 12.3 metric tons at 15m.
The ship is required to be able to transport 600 short tons of troops, supplies, and equipment 1,200 nautical miles at an average speed of 35 knots, through wave height of up to 4 feet. It won’t quite manage that, in part because its 12.5 short tons overweight. Required range will also suffer a bit at 23 knots cruise speed (4,018 nmi vs. 4,700 nmi).
The JHSV’s flight deck can support all current Navy helicopters up to and including the Marines’ current med/heavy CH-53E Super Stallion, and Vertical Replenishment has been tested using a tilt-rotor MV-22 Osprey. Flight operations will be handled by Kongsberg Maritime’s night-capable Helicopter Operations Surveillance System (HOSS).
HSV-2 Swift, frontal“[JHSV] will be capable of transporting Army and Marine Corps company-sized units with their vehicles, or reconfigure to become a troop transport for an infantry battalion. Its 35-45 nautical miles per hour speed allows for rapid deployment and maneuver of conventional or special operations forces.
The JHSV will not be a combatant vessel. Its construction will be similar to high-speed commercial ferries used around the world, and the design will include a flight deck and an off-load ramp which can be lowered on a pier or quay wall – allowing vehicles to quickly drive off the ship.
JHSV testingJHSV’s shallow draft will allow it access to small austere ports common in developing countries. This makes the JHSV an extremely flexible asset ideal for three types of missions: support of relief operations in small or damaged ports; as a flexible logistics support vessel for the Joint Commander; or as the key enabler for rapid transport of a Marine Light Armored Reconnaissance Company or an Army Stryker unit.”
It has taken time, but the US military is beginning to expand its thinking beyond these obvious applications, and begin thinking about ways to employ the JHSV’s vast internal space and mobility in front-line missions. The most dramatic example may involve mounting a 32MJ railgun on USNS Millinocket [JHSV 3] in 2016.
The JHSV Program Incat JHSV concept – lostThe Joint High Speed Vessel’s Initial Capability Document received approval from the Department of Defense Joint Requirements Oversight Council on Nov 1/05, with all 4 military services concurring. The initial goal was 5 Army vessels, and 3 Navy vessels, for a program worth about $1.6 billion, but the Navy’s interest has continued to grow. The contract signed in November 2008 called for up to 10 ships, split evenly between the Army and Navy. An initial Memorandum of Agreement (MOA) allowed the U.S. Navy to use its surface ship acquisition expertise to buy these vessels on the Army’s behalf, with Army participation – until program changes moved all of these ships to the Navy’s procurement budget and operation.
All of the JHSVs were then transferred to Maritime Sealift Command under a May 2011 agreement. The first 4 / 10 projected vessels will be crewed by civil service mariners. JHSV 5-10 are slated to be crewed by contracted civilian mariners working for a private company. Military mission personnel will embark with either set, as required by mission sponsors. The goal was for JHSV to achieve Initial Operational Capability in 2012, and JHSV 1 just made it.
All ordered JHSV ships have been named now, and ships with the USNS listing have been delivered to US Military Sealift Command:
The Pentagon’s April 2011 Selected Acquisition Report placed the program at 18 ships, and its total cost at about $FY08 3.5 billion. That changed as FY 2013 budget plans cut all ships beyond the 10 in the current contract, and the US Navy is negotiating over cancellation of its JHSV 10 contract due to sequestration cuts. Annual budgets to date have included:
FY 2008: $231.9 million, 1 ship funded.
Navy: $18.4M RDT&E
Army: $5M RDT&E, $208.6M production, 1 ship
FY 2009: $364.2 million, 2 ships funded.
Navy: $11.6M RDT&E, $181.3M production, 1 ship
Army: $3.0M RDT&E, $168.3M production, 1 ship
FY 2010: $391.1 million, 2 ships funded
Navy: $8.2M RDT&E, $202.5M production, 1 ship
Army: $3.0M RDT&E, $177.4M production, 1 ship
FY 2011: $390.1 million, 2 ships funded.
Navy: $3.5M RDT&E, $203.9M production, 1 ship
Army: $3.0M RDT&E, $179.7M production, 1 ship
FY 2012: $376.4 million, 2 ships funded.
Navy: $4.1M RDT&E, $372.3M production, 2 ships
FY 2013 request: $376.4 million, 1 ship funded.
Navy: $1.9M RDT&E, $189.2M production, 10th & final ship
Note that advance materials purchases for future years are included in each year’s procurement budgets. After FY 2013, JHSV budgets are very small, reflecting only minor post-shakedown work.
Supplements: From Leased to Bought Hawaii SuperferryAt present, 1 leased vessel remains in military service, following the end of Incat’s HSV-2 Swift lease. Austal’s HSV 4676 Westpac Express catamaran continues to serve in Military Sealift Command in the Pacific around Guam and Japan, working closely with the Marine Corps as a troop and cargo transport.
HSV-2 Swift’s influence lives on in the JHSV concept of operations. The ship had supported relief operations in Indonesia post-tsunami, and in the Gulf Coast region following hurricane Katrina. In both cases, Swift’s high speed and shallow draft combined to make it an ideal platform for the delivery of relief supplies and support of other platforms operating in the area. During operations following Katrina, Swift was able to use ports that were inaccessible to other ships of the logistics force. It has also been a platform for UAV and aerostat experiments.
It’s likely that both charters will soon be replaced, thanks to a recently-purchased alternative with many similarities to the JHSV.
After its ferry service was forced into bankruptcy by environmental lawfare, the Hawaii Superferries Huakai and Alakai were pressed into service by their main creditor: the US Department of Transportation’s Maritime Administration (MARAD). They were called into service in the wake of the 2010 Haiti earthquake, and these Austal-built ships were very successful in that role. Both ferries were ultimately bought by the US Navy in 2011, for just $35 million. Once their $35 million conversions are done, they’re likely to replace Westpac Express and Swift as USNS Guam (ex-Huakai) and USNS Puerto Rico (ex-Alakai, slightly smaller). The superferries will offer more troop-carrying berths than their similar JHSV counterparts, in exchange for less military flexibility.
USNS Guam is expected to relieve Westpac Express in the Pacific some time in FY 2015.
Contracts & Key Events FY 2014-2018JHSV 1 passes trials & deploys; JHSV 3 passes acceptance trials; JHSV 4 launched.
JHSV 1 deploysOctober 24/18: EPF-1 ROH Colonna’s Shipyard is being contracted to work on the Navy’s first Spearhead-class ship during the ship’s upcoming regular overhaul and dry docking phase. The firm-fixed-price contract is valued at $7.9 million and provides for a 67-calendar day shipyard availability. The contractor will be responsible to conduct structural inspection of the hull, perform a variety of repairs, support the main propulsion engine’s overhaul, replace heater exchangers and perform gear maintenance. The USNS Spearhead is an Expeditionary Fast Transport ship that was launched in 2011, it is designed for the fast, intra-theater transportation of troops, military vehicles and equipment with aviation support. Work will be performed at Colonna’s shipyard in Norfolk, Virginia. The Regular Overhaul availability is expected to be completed by January, 2019.
October 22/18: EPF-13 Austal is being tapped to start building the Navy’s next Expeditionary Fast Transport (EPF) ship. The undefinitized contract action is valued at $57.8 million and allows for the procurement of long-lead-time material and production engineering services. The Spearhead-class vessels are designed for the fast, intra-theater transportation of troops, military vehicles and equipment with aviation support. Bridging the gap between low-speed sealift and high-speed airlift, EPFs transport personnel, equipment and supplies over operational distances with access to littoral offload points including austere, minor and degraded ports often found in developing countries. The vessels are able to transport 600 short tons of military equipment to a range of 1.200 nautical miles at speeds of up to 35 knots. Work will be performed at multiple locations, including – but not limited to – Novi, Michigan; Mobile, Alabama and Rhinelander, Wisconsin. The US Navy’s 13th EPF is expected to be completed by November 2021.
February 28/18: Christening Ceremony The US Navy has christened its latest Spearhead-class expeditionary fast transport, the USNS Burlington, during a ceremony in Mobile, Alabama, on Saturday. It is the tenth of 12 Expeditionary Fast Transports being built for the Navy at a cost of $1.9 billion. Overseeing the event were the ship’s primary sponsors US Senator Patrick Leahy and his wife Marcelle Pomerleau. Marcelle Leahy said naming the ship after the Vermont city of Burlington was “fitting because Vermonters have long heeded the nation’s call to service.” Built by Austal USA, the vessel is designed to transport troops and equipment at high-speeds and in shallow waters for rapid deployment. The Navy says it can “carry 600 short tons of military cargo for 1,200 nautical miles, at an average speed of 35 knots.” This equates to the Burlington being able to carry 1,200,000 pounds for 1,380 miles at an average speed of 40 mph. It also has a flight deck for helicopter operations and an off-loading ramp for disembarkment missions.
Sept 26/14: Naming. “Secretary of the Navy Ray Mabus announced the next joint high speed vessel (JHSV) will be named USNS Trenton during a ceremony in Trenton, New Jersey, Sept. 25.” Um, OK. Trenton, which is still under construction, was publicly named by the Secretary of the Navy on April 12/13 (q.v.) Sources: US Navy, “SECNAV Names the Next Joint High Speed Vessel”.
Sept 16/14: #4 delivered. Austal delivers USNS Fall River to US Military Sealift Command. Construction update:
“Preparations are underway for the launch of Trenton (JHSV 5) later this month with construction on Brunswick (JHSV 6) progressing well. Metal cutting began for Carson City (JHSV 7) in early September.”
Sources: Austal, “Austal Delivers Fourth Joint High Speed Vessel”.
USNS Fall River
June 13/14: Aerostat zapped. From US Naval Forces Southern Command:
“During routine testing off the coast of Key West, the Aerostat tethered off the Joint High Speed Vessel USNS Spearhead (JHSV-1) was struck by lightning at 12:21 in the morning, June 12…. The lightning strike caused the Aerostat to deflate and land in the water. Response efforts were delayed as the thunderstorm moved into the area. The Aerostat was subsequently sunk so to pose no hazard to other vessels or navigation.”
Aerostats are tethered blimps, used to dramatically expand a JHSV’s field of view (q.v. April 27/13). This can be very useful for survey and interdict deployments like Operation Martillo (q.v. March 31/14). Sources: US Navy, “USNAVSO/US 4th Fleet Statement regarding AEROSTAT”.
May 20/14: JHSV 3. USNS Millinocket will become the 1st JHSV deployed to the far east, where it will operate alongside the leased ship Westpac Express [HSV-4676] and the former Hawaii Superferry USNS Guam [HST-1].
MSC’s JHSV project officer Mike Souza says that USNS Millinocket is preparing for a move to San Diego, CA. She’ll serve as a display platform for the two EM Railgun prototypes during the May 26/14 International Symposium on Electromagnetic Launch Technology in La Jolla, CA. Some final post-delivery tests and trials will follow, including some interface testing with a Mobile Landing Platform ship. Once the post shakedown availability trials and fixes are done, Millinocket head to an unspecified new homeport in the Far East. Sources: Seapower, “Millinocket Will Be the First JHSV in Westpac”.
April 7/14: Experiment: Railgun. The US Navy plans to use JHSV 3 Millinocket as a test platform for one of its newest weapons in 2016: a 32MJ rail gun that can fire projectiles about 100 miles at Mach 7 speeds. JHSV was picked as the trial platform because it has the space to carry the large system on its deck and in its cargo bay. The gun itself isn’t unusually large, but once you throw in the capacitors for power storage, any additional power needs, extensive maintenance tools and parts, and ammunition, it adds up fast. Rolling and bolting that onto a JHSV is much easier than using any warship, and the trial underscores JHSV’s usefulness as a concept testbed.
On the weapon’s side of the equation, ONR Chief Rear Admiral Matthew Klunder touts the railgun’s economic benefit, as well as its military edge in extending the bombardment range of naval guns and the number of rounds on board. It’s true that $25,000 for a defensive railgun shot against incoming missiles is orders of magnitude better than a RIM-116 RAM ($900,000) or RIM-162 Evolved SeaSparrow Missile ($1.5 million), assuming the unproven assumption of equal effectiveness. One must also compute operating and maintenance costs over the railgun’s lifetime, however, which are going to be far higher than they would be for an All-Up-Round missile in its canister. The JHSV tests will offer some early data re: the gun’s robustness under trial conditions at sea, and that cost data point could end up being as valuable as any performance data. Sources: Reuters, “U.S. Navy to test futuristic, super-fast gun at sea in 2016”.
March 31/14: Operations. USNS Spearhead [JHSV 1] is preparing for a 2nd deployment, this time to the 4th Fleet’s waters around the Caribbean and South America. The US military is taking cautious steps to expand JHSV uses, and is explicitly following in the footsteps of HSV-2 Swift’s 2013 deployment. It’s well short of full innovation toward mothership roles, but still a step forward.
These extensions still have JHSV 1 operating primarily in a ferry capacity, with “adaptive force packages.” They’ll be carrying the USMC’s 4th Law Enforcement Battalion and equipment to the Dominican Republic. After the Marines are ferried back to Florida, a trip to Belize will involve a Navy Seabee explosive ordnance disposal detachment, and a riverine crew. From Belize, a a mobile diving and salvage unit and an explosive ordnance disposal team will be ferried from Guatemala to Colombia, before all of the units that were in Guatemala and Columbia end up ferried to Honduras.
In between, USNS Spearhead will “conduct detection and monitoring activities” in support of the multinational anti-drug Operation Martillo. Spearhead’s exact role isn’t made clear, but Spearhead works well with helicopters, Swift has shown that UAVs can be used from these ships, and it would be possible to have boarding teams embarked. Sources: US Navy, “Plans Finalized for USNS Spearhead’s Deployment to 4th Fleet AOR”.
March 21/14: #3 delivered. Austal delivers USNS Millinocket to US Military Sealift Command. They add that:
“Ships currently under construction are JHSV 4, which was christened in January and is being prepared for sea trials, JHSV 5, which has begun final assembly, and JHSV 6, which commenced construction in January in the module manufacturing facility. Five Independence-variant Littoral Combat Ships are also in construction at Austal’s US shipyard…”
Sources: Austal, “Austal Delivers Third Joint High Speed Vessel” | GD-AIS, “Austal Delivers USNS Millinocket (JHSV 3)”.
USNS Millinocket
March 10/14: JHSV 5. Trenton’s keel is formally laid. Sources: Austal USA, “Austal Commemorates Keel Laying for Trenton (JHSV 5)”.
Jan 28/14: DOT&E Testing Report. The Pentagon releases the FY 2013 Annual Report from its Office of the Director, Operational Test & Evaluation (DOT&E). JHSV will be able to carry 354 passengers for 96 hours, which is better than the required 312, but it’s overweight by 12.5 tons, and will fall short of required ranges at 23 knots (4,018 nmi vs. 4,700) and 35 knots (won’t make 1,200 nmi) transit speed. The extra weight amounts to about 4% fuel load, or 3,565 gallons.
Overall testing results have been positive. Loading tests demonstrated suitability up to M-1A2 tank loading onto a floating causeway. If the ships need replenishment at sea, both USNS Spearhead and USNS Choctaw County have successfully conducted fuel-only underway replenishments. For other supplies, vertical replenishment tests have included an MH-60S helicopter at night, and MV-22 Osprey tilt-rotos by day, and Aircraft Dynamic Interface testing has included MH-53E Minehunting helicopters. DOT&E says that “manning and facilities can accommodate handling of all required helicopters, with the exception of fuel and power.” Finally, DOR&E says that with an embarked security team and weapons, JHSV can engage a moving surface threat. The bad news, aside from ship range?
“The JHSV’s organic container load trailer is not effective for loading 20-foot long metal storage containers. During the IOT&E, the test team took five hours to connect the container load trailer with a storage container and failed to load it…”
Jan 17/14: JHSV 4. Fall River is launched at Austal’s Mobile, AL shipyard, after a side trip to BAE. Instead of moving down a slipway, launches are now float-off affairs from a BAE floating drydock. Getting to the drydock requires a transfer onto a barge, using Berard Transportation rollers. The ship was christened on Jan 11/14, and will be formally delivered to the USN later in 2014, after final fitting out. Austal adds that:
“Three JHSVs and four LCSs are currently under construction in Austal’s Mobile, Alabama shipyard. Austal will begin production of one more ship in each program before the end of January.”
Sources: Austal, “Austal Launches USNS Fall River (JHSV 4)” and “USNS Fall River (JHSV 4) Christened – One of seven Navy vessels currently under construction at Austal USA”.
Jan 16/14: JHSV 1 deploys. Operational use of the JHSV fleet begins with USNS Spearhead’s deployment from NAB Little Creek. She’ll head to “the US 6th Fleet Area of Responsibility” (Africa) until May 2014, then on to the 4th Fleet AOR (Central & South America) until December 2014. Sources: USN, “USNS Spearhead departs on Maiden Deployment”.
1st deployment
Jan 9/14: JHSV 3. USNS Millinocket successfully completes Navy Acceptance Trials in the Gulf of Mexico. Formal delivery is expected in late January. Sources: MarineLog, “JHSV 3 completes Acceptance Trials”.
Oct 8/13: JHSV 1. USNS Spearhead has successfully completed initial operational testing and evaluation with the US Navy. Sources: Austal, “JHSV 1 successfully completes US Navy operational testing”.
FY 2013JHSV 10 bought, but Navy wants to cancel it over sequestration; JHSV 1 & 2 delivered; JHSV 3 launched; Keel-laying for JHSV 4; Aerostat experiment.
JHSV 2 LaunchJuly 31 – Aug 6/13: Testing. USS Spearhead completes Initial Operational Test and Evaluation and Total Ship Survivability Trials, thanks to about 280 Marines from 1st Battalion/ 2nd Marine Regiment/ 2nd Light Armored Reconnaissance Battalion, and 2nd Assault Amphibian Battalion. The Marines embarked Spearhead with their weapons, gear and vehicles and traveled from Morehead City, NC, to Mayport Naval Station, FL and back, while participating in various tests. Sources: US MSC Sealift magazine, October 2013.
June 6/13: Naming. The Secretary of the Navy names the last 3 JHSV ships under contract.
The future USNS Yuma (JHSV 8) honors the city in Arizona near the USMC’s big testing range, and will be the 4th ship to bear this name. JHSV 9 USNS Bismarck is named in honor of North Dakota’s capital city. As one might imagine, it’s a first for the US Navy. JHSV 10 USNS Burlington is also a first, named for the largest city in Vermont. US DoD.
June 6/13: JHSV 2. USNS Choctaw County is accepted into service, after completing acceptance trials in May. Delivery just 6 months after the 1st ship in the class is a very fast pace. US Navy | Austal.
USNS Choctaw County
June 5/13: JHSV 3. Millinocket is launched from the Austal USA shipyard in Mobile, AL. It’s not done, just entering the final phase of construction, test, and activation, followed by preparation for sea trials late in 2013. US NAVSEA | Austal.
May 23/13: JHSV 4. The keel is formally laid for Fall River. Austal.
May 3/13: JHSV 2. USNS Choctaw County successfully completes USN Acceptance Trials. Sources: Austal, “Joint High Speed Vessel USNS Choctaw County (JHSV 2) completes Acceptance Trials”.
April 27/13: Aerostat experiment. The Miami Herald reports that the chartered catamaran HSV 2 Swift is currently testing an interesting combination for the US Navy. An aerostat (tethered blimp) mooring system has been attached to the starboard rear at the helicopter deck, and sailors are deploying hand-launched Aerovironment Puma mini-UAVs to investigate targets cued by the aerostat’s radar and optical sensors. When fully deployed to 2,000 feet, Raven Inc’s TIF-25K gives Swift a sea surveillance radius of 50 miles at almost zero operating cost, roughly doubling a warship’s surveillance radius, and increasing Swift’s by 10x.
The JHSV ships and Hawaii Superferries (esp. USNS Puerto Rico) are natural fits for this configuration, given their similarity to HSV 2. If weight and other issues can be worked out, the USA’s Littoral Combat Ships like the trimaran Independence Class could also be an option, and so could amphibious LSD and LPD ships. Still, Swift needs to work out a coherent concept of operations in these trials, including the question of barrier vs. mobile surveillance approaches.
If all goes well with the operational tests, the US Navy will consult with drug enforcement agencies, including the Key West, FL Joint Interagency Task Force South (JIATF) that oversees Operation Martillo in the Caribbean. If the system is deployed, the biggest losers would probably be expensive-to-operate P-3 quad-turboprop sea control planes. US personnel have also begun promoting the concept to other nations, including Colombia, though those countries would almost certainly use their own ships.
April 20/13: JHSV 3 christened. The Millinocket is christened at Austal’s Alabama shipyard, named after 2 Maine towns. No word on negotiations concerning JHSV 10, though Austal’s release does make a point of noting 10 JHSV vessels under contract. US MSC | Austal.
April 12/13: Naming. 3 JHSV ships are among the 7 named by Secretary of the Navy Ray Mabus, who actually stuck to class naming conventions this time instead of veering into political partisanship.
JHSV 5 will become USNS Trenton, after New Jersey’s capital city. JHSV 6 will become USNS Brunswick, after the seaport in Georgia. JHSV 7 will become USNS Carson City, after Nevada’s capital city. Pentagon, “Secretary of the Navy Names Multiple Ships”.
April 5/13: LCS Council. The CNO adds the JHSV program to the portfolio of the Littoral Combat Ship (LCS) Council, which was set up to manage the logistics, support, training, and concept of operations involved in making LCS a useful part of the fleet. Sources: Gannett’s Navy Times, “LCS council adds new member”.
Added to LCS Council
March 15/13: JHSV 2. Choctaw County completes builder’s trials, reaching speeds of more than 41 knots. Delivery is expected this summer. Austal.
March 2/13: JHSV 10. The US Navy’s guidance regarding sequestration budget cuts involves negotiations to cancel JHSV 10’s contract. They have to hold negotiations, because the contract is already live. The question will be cancellation costs.
Dec 20/12: JHSV 10. Austal USA in Mobile, AL receives a $166.9 million contract modification, exercising the construction option for JHSV 10. All contract funds are committed immediately.
Work will be performed in Mobile, AL (48%); Pittsfield, MA (9%); Franklin, MA (3%); Philadelphia, PA (3%); Henderson, Western Australia (3%); Atlanta, GA (2%); Chicago, IL (2%); Gulfport, MS (2%); Slidell, LA (1%); Iron Mountain, MI (1%); Houston, TX (1%); Dallas, TX (1%); Chesapeake, VA (1%); Milwaukee, WI (1%); Brookfield, WI (1%), and various sites inside and outside the United States each below 1% (21% tl.), and is expected to be complete by June 2017. US Naval Sea Systems Command in Washington, DC manages the contract (N00024-08-C-2217).
JHSV 10 bought
Dec 5/12: #1 delivered. US Military Sealift Command accepts delivery of USNS Spearhead [JHSV 1] at Austal Shipyard in Mobile, AL.
Following delivery to the Navy, Spearhead will participate in operational testing before sailing to its layberth in Little Creek, VA. The Navy says that it expects the ship to begin conducting missions in Q1 of FY 2013. Which is to say, by Dec 31/12. US MSC | US Navy | Austal.
USNS Spearhead
Oct 1/12: JHSV 2 launch. Choctaw County is launched in Mobile, AL.
FY 2011 – 2012JHSV becomes Navy-only; JHSVs 4-9 bought; 2 Superferries bought, re-named; JHSV program to end at 10; JHSV 1 christening, trials; Corrosion controversy.
Austal JHSV conceptSept 15/12: JHSV 2 christened. USNS Choctaw County is christened during a ceremony at Austal USA in Mobile, AL. US MSC | Pentagon.
May 30/12: Secretary of the Navy Ray Mabus announces that the next JHSV will be named the USNS Millinocket. Pentagon.
May 8/12: The US Navy re-names the Hawaiian Superferries, which will becomes USNS Guam and USNS Puerto Rico.
They do not say, but it’s likely that the larger Huakai, tabbed to replace the Westpac Express and move Marines to and from Okinawa and Guam, is the future USNS Guam. The smaller Alakai was being considered for missions in Latin America and/or Africa, so it’s likely that she’ll become USNS Puerto Rico.US DoD.
April 25/12: The first of 43 modules for JHSV 3 have been successfully transported from the Module Manufacturing Facility (MMF), and erected in the final assembly bay on the waterfront, in preparation for the May 3/12 keel-laying ceremony. The 46 tonne, 20.4m x 8.3m x 9.4m module will be part of one of the catamaran akas. Austal.
April 19/12: JHSV-1 trials. The future USNS Spearhead completes builder’s trials of the ship’s propulsion plant, communication and navigational systems, ride control systems, pollution control systems; and first-of-class maneuverability and stability trials. The ship reached speeds of more than 35 knots, exceeding the program’s requirements.
Next steps include INSURV inspection, and commissioning. US Navy acceptance is scheduled by the end of 2012. USN PEO Ships | Austal.
Feb 24/12:JHSV 8-9. Austal USA in Mobile, AL receives a $321.7 million contract modification, exercising construction options for JHSV 8 and JHSV 9.
Work will be performed in Mobile, AL (48%); Pittsfield, MA (9%); Franklin, MA (3%); Philadelphia, PA (3%); Atlanta, GA (2%); Chicago, IL (2%); Gulfport, MS (2%); Slidell, LA (1%); Iron Mountain, MI (1%); Houston, TX (1%); Dallas, TX (1%); Chesapeake, VA (1%); Milwaukee, WI (1%); Brookfield, WI (1%); various sites throughout the United States (5%); and various sites outside of the United States (19%). Work is expected to be complete by April 2016 (N00024-08-C-2217).
Austal’s release offers a snapshot of current progress. USNS Spearhead is scheduled for builder’s sea trials in early March 2012. JHSV 2 is taking shape in Austal’s final assembly bay. Modules for JHSV 3 are being built, and the ship’s official keel laying is scheduled for April 12/12.
JHSV 8 & 9 bought
Jan 26/12: JHSV cut. The Pentagon issues initial guidance for its FY 2013 budget, and next plans. They include lowering planned JHSV buys by 8 ships, leaving only the 10 in the current contract. Pentagon release | “Defense Budget Priorities and Choices” [PDF] | Alabama Press-Register.
Just 10
Jan 20/12: Superferry supplement bought. Inside the Navy reports that the cost for the 2 Hawaii Superferries, plus required modifications, is actually $70 million. The superferries were seen as a better option to move 880 Marines, because JHSV wasn’t designed for maximum passenger seating. Read “Hawaii Superferry’s Bankruptcy = US Navy Opportunity” for full coverage.
Dec 19/11: Superferries. The Defense Authorization Act of 2012, which will soon become law, looks set to buy both of the Austal-built Hawaii Superferries out of the firm’s bankruptcy, then send them to US MSC, alongside the future JHSV vessels. Read “Hawaii Superferry’s Bankruptcy = US Navy Opportunity” for full coverage.
Superferry supplements bought
Oct 10/11: JHSV 3 begun. Austal announces the official beginning of fabrication for JHSV 3 Fortitude. Austal USA President and COO, Joe Rella:
“The race is on… The world is about to learn just how much value Austal’s investments in modular ship fabrication offers our Navy and Military Sealift Command customers. We challenge ourselves every day to build each ship faster and more efficiently than the one before.”
Oct 7/11: JHSV 6 named. Secretary of the Navy Ray Mabus names JHSV 6 as USNS Choctaw County. He grew up in that Mississippi county, though there are also Choctaw counties in Alabama and Oklahoma. Ray Mabus said that “I chose to name JHSV after Choctaw County to honor those men and women who represent rural America.”
The name eventually migrates to JHSV 2. US MSC.
Sept 10/11: JHSV 1 christened. JHSV-1 Spearhead is launched at Austal USA’s yard in Mobile, AL. The formal christening ceremony is held on Sept 17/11. The ship is reported to be slightly over budget, but not badly so – a welcome departure for a USN first ship of class. US MSC | Austal | Alabama Press-Register | Maritime Executive.
June 30/11: JHSV 6-7. Austal USA in Mobile, AL receives a $312.9 million contract modification, exercising options for JHSVs 6 and 7. Note, as usual, that this is not the full price of a ready to serve ship. On the other hand, JHSVs have much lower amounts of “government furnished equipment” beyond the base seaframe and installed gear, so the figure will be much closer than it would for a warship.
Options remain for another 3 ships under the current FY 2009-2013 contract, though the program of record tops out at 18 ships. Spearhead [JHSV 1] is scheduled for launch in August 2011, and delivery in December 2011, with other ships currently in various stages of assembly.
Work will be performed in Mobile, AL (48%); Pittsfield, MA (9%); Franklin, MA (3%); Philadelphia, PA (3%); Henderson, WA (3%); Atlanta, GA (2%); Chicago, IL (2%); Gulfport, MS (2%); Slidell, LA (1%); Iron Mountain, MI (1%); Houston, TX (1%); Dallas, TX (1%); Chesapeake, VA (1%); Milwaukee, WI (1%); and Brookfield, WI (1%), with other efforts performed at various sites throughout the United States (5%) and outside the United States (16%). Work is expected to be complete by June 2014. US Naval Sea Systems Command in Washington, DC manages the contract (N00024-08-C-2217). See also US NAVSEA | Austal.
JHSV 10 bought
June 20-22/11: Corrosion issues? After USS Independence [LCS-2] corrosion reports hit Austal’s share price, a company release addresses the issue. It notes the complete lack of such problems on all of Austal’s commercial and military ships to date, and suggests that the US Navy may have failed to follow basic procedures. Information Dissemination has a different take, and wonders if Austal’s JHSV, which may not have a cathodic protection system either, could also be at risk due to the military’s added electronics:
“In the case of LCS-2, the problem was apparently accelerated by stray currents in the hull from the electrical distribution system problems the ship has been having since it was turned over to the Navy. LCS-4 doesn’t have [a cathodic protection system] either, but apparently CPS is part of the lessons learned process and was included in the fixed-price contracts for Austal versions of the LCS beginning with LCS-6. LCS-2 will have the CPS installed at the next drydock period, while Austal has said a CPS will be added to LCS-4 before the ship is turned over to the Navy. The question everyone seems to be asking is whether the JHSV could suffer the same issue… I’d be curious to know if Westpac Express has a CPS installed, or some other form of prevention is used at all.”
MarineLog’s report says that yes, cathodic protection is used on Westpac Express. See: Austal | Alabama Press-Register | Information Dissemination | MarineLog | WIRED Danger Room.
June 17/11: Corrosion issues? The US Navy has told Congressional appropriations committees that “aggressive” corrosion was found in the propulsion areas of the Littoral Combat Ship USS Independence, which rely on Wartsila waterjets. The ship has been given temporary repairs, but permanent repairs will require dry-docking and removal of the water-jet propulsion system. The strong Australian dollar has hurt Austal’s commercial exports, so this blow to its defense business has added impetus. Bloomberg | Alabama Press-Register | Sydney Morning Herald.
Corrosion in new ships isn’t unheard of, though it’s never a good sign. Norway’s Fridtjof Nansen Class AEGIS frigates had this problem, for instance. The Independence Class runs some risks that are specific to its all-aluminum construction, however, as key subsystems with different metals create risks of galvanic corrosion.
Corrosion controversy
June 11/11: Industrial accident. A 50-ton block from JHSV Vigilant, containing the ship’s service diesel generators, breaks loose while the module is being lifted and repositioned for further work. One source reported that pad eyes tore loose from the module, causing it to fall about 3 feet and tip over.
The extent of the damage to the module, and the cost of repairs, are still being assessed. The good news is that modular construction ensures less schedule impact. Defense News.
Accident
June 9/11: Inside the Navy reports that a June 14/11 Defense Acquisition Board meeting will determine the Navy’s readiness to procure JHSV ships 6-10. Defense officials may opt to fast-track the decision as a “paper DAB,” granting approval without requiring a meeting.
June 2/11: Sub-contract. Taber Extrusions LLC announces contracts to supply extruded aluminum products for JHSV 3 Fortitude, and LCS 6 Jackson, from its facilities in Russellville, AR and Gulfport, MS. Some structural extrusions for both ships will also be manufactured by Taber and supplied to Austal through a contract with O’Neal Steel Corp.
Taber has an 8,600 ton extrusion press with a rectangular container and billet configuration. The firm says that compared with smaller presses and round containers, their tool gives superior metal flow patterns with much tighter tolerances for flatness, straightness and twist; and better assurance of critical thickness dimensions. The resulting wide multi-void extrusions are friction stir welded into panels, and tight tolerances improve productivity while reducing downstream scrap. When finished, they make up some of the ship’s decking, superstructure and bulkheads.
May 2/11: Army Out. The US Army signs a memorandum of agreement to transfer custody of all 5 of its JHSVs to US Military Sealift Command. Army watercraft personnel who had been training to operate the ships have been reassigned. Instead, JHSVs will be operated by the US Navy’s Military Sealift Command, and crewed by civil service (JHSV 1-4) or civilian contract (JHSV 5-10) sailors. The transfer was approved in principle in December 2010, during Army-Navy talks.
MSC has been slated to operate the Navy JHSVs since August 2008, and in May 2010, MSC announced that the vessels would each have a core crew of 21 mariners (vid. May 13/10 entry). That template will now apply to all ships of class, which will carry a USNS designation instead of the Navy’s USS. US DoD | US MSC | Gannett’s Navy Times.
Navy-only now
Oct 12/10: #4 & 5 bought. Austal USA in Mobile, AL receives a $204.7 million contract modification, exercising options to build JHSV 4 and 5. Work will be performed in Mobile, AL, and is expected to be complete by December 2013. US Naval Sea Systems Command in Washington, DC manages the contract (N00024-08-C-2217).
The $204.7 million is on top of the earlier $99.6 million long-lead materials contract, bringing the total so far to $304.3 million for the 2 ships. See also Austal.
JHSV 4 & 5 bought
FY 2009 – 2010Program baseline set; Austal wins; JHSVs #1-3 bought; Long-lead items for #4-5; JHSV 1 keel-laying; Austal opens new manufacturing facility; Hawaii Superferries in Haiti; JHSV program to reach 23 ships?
JHSV 1 constructionSept 28/10: JHSV 2 begins. Austal announces that they’ve begun construction of JHSV 2 Vigilant for Maritime Sealift Command. A subsequent release fixes the start date at Sept 13/10.
July 22/10: JHSV 1 keel-laying. Keel-laying for the first JHSV ship, Spearhead, at Austal’s Mobile, AL facility. Austal | Press-Register advance report.
June 3/10: #4-5 lead-in. Austal USA in Mobile, AL receives a $99.6 million modification to a previously awarded contract (N00024-08-C-2217) for JHSV 4 and 5 long lead time materials, including main propulsion engines, aluminum, waterjets, reduction gears, generators and other components, beginning in fall 2010.
Work will be performed in Detroit, MI (38%); Chesapeake, VA (18%); Henderson, Australia (13%); Gulfport, MS (10%); Ravenswood, WVA (9%); Ft. Lauderdale, FL (4%); Mobile, AL (3%); Auburn, IN (2.6%); Winter Haven, FL (1%); Gardena, CA (1%); and Davenport, IA (0.4%), and is expected to be complete by December 2011. The Naval Sea Systems Command in Washington, DC manages this contract. See also Austal release.
May 26/10: Sub-contract. Kongsberg Maritime has successfully delivered the first JHSV Helicopter Operations Surveillance System (HOSS) to General Dynamics Advanced Information Systems. The sub-contract was awarded in November 2009.
The JHSV HOSS system will provide comprehensive flight deck coverage for helicopter operations, even in very low light conditions, on a MIL-S-901D shock qualified 19″ SXGA liquid crystal display (LCD) monitor in the JHSV control room. The monitor’s Night Vision Device (NVD) optical filter makes it suitable for night operations in ship compartments directly overlooking the flight deck. defpro.
March 25/10: JHSV 4 named. US Navy Secretary Ray Mabus officially names the 2nd US Navy ship under the JHSV program: USNS Fall River [JHSV 4]. US Navy | Gannett’s Navy Times.
March 16/10: Support. Reuters reports on a recent US Navy SBIR research solicitation, aimed at more quickly and cheaply diagnosing cracking in aluminum ship structures. From US Navy SBIR N10A-T041: “Fracture Evaluation and Design Tool for Welded Aluminum Ship Structures Subjected to Impulsive Dynamic Loading” :
“A new analysis tool combined with an experimental validation protocol is needed to accurately characterize the dynamic response and fracture behavior of welded aluminum ship structures subjected to extreme loading events. The goal of this effort is to develop an explicit dynamic failure prediction toolkit for fracture assessment of welded thin-walled aluminum structures. To efficiently characterize a large size ship structure, innovative modeling techniques using fractured shell elements are needed along with a mesh independent crack insertion and propagation capability. In addition to innovative crack simulation in a shell structure, advanced constitutive models have to be implemented in the toolkit to capture the rate dependence and anisotropy in strength, plastic flow and ductility. Developing and demonstrating novel damage simulation and fracture prediction methods has significant potential impact on design and operation of current and future Navy welded aluminum, ship structural systems.”
US Navy Commander Victor Chen reiterated the Navy’s confidence in the JHSV and Littoral Combat Ships; the JHSV is aluminum construction, as is the LCS-2 Independence Class, and the LCS-1 Freedom Class uses an aluminum superstructure on a steel hull. He adds that:
“We already have a level of confidence in how to work with aluminum. The Office of Naval Research is trying to expand the knowledge base and build on what we already know.”
May 13/10: Crewing plans. The US Navy and Military Sealift Command announce the crewing plan for USN JHSVs (even numbers, JHSVs 2-10). Because the ships are new and could conduct a wide variety of missions, MSC determined that the best course of action is to institute a pilot program where JHSV 2 Vigilant and JHSV 4 Fall River will be crewed by 21 civil service mariners each, in order to create a base of experience and knowledge. Delivery as USNS Vigilant is scheduled for FY 2013, but the crews arrive beforehand; while USNS Fall River’s delivery is scheduled for FY 2014. JHSVs 6, 8 and 10 will be crewed with 21 civilian contract mariners each, with specifications developed based on experience with the first 2 ships.
The Army Transportation Corps officers have apparently won their argument to crew the Army’s JHSVs as USAV ships, involving larger crews of soldiers. Within a year, however, that victory would be undone. US MSC.
April 2/10: SAR baseline. The Pentagon adds [PDF] the JHSV program to its Selected Acquisition Reports. The program’s baseline is $3.9355 billion, and subsequent SARs set the number of ships at 18. The program is listed under the US Navy.
Baseline
Feb 11/10: Superferries. The former Hawaii superferries Huakai and Alakai are pressed into service by the USA’s Maritime Administration (MARAD), in the wake of the disaster in Haiti. The ships are managed by Hornblower Marine Services (HMS), and the deployment is seen as an earl concept test of the similar JHSV design’s operations. Haiti’s lack of port infrastructure has not, to date, been a major problem for these ships.
Maritime Executive magazine has the full report, and see also July 30/08 entry.
Feb 3/10: JHSV Boost? Defense News reports that the JHSV program may be about to get a very big boost. Navy Undersecretary Bob Work:
“There was a big debate within the [Navy] department on patrol craft, PCs… People said these are very good for irregular warfare. But when we looked at it we said we wanted to have self-deployable platforms that have a lot of payload space that you can take to the fight whatever you need – SEALs, Marines, riverine squadrons. So we decided to increase the Joint High Speed Vessel program.” Work said the Navy now envisions buying up to 23 of the ships for its own use, in addition to five being built for the Army. “We like their self-deployability aspects,” Work said. “They can be a sea base, they can be an Africa Partnership Station, they’re extremely flexible.”
Jan 28/10: JHSV 2 & 3. Austal USA in Mobile AL receives a $204.2 million modification to a previously awarded contract (N00024-08-C-2217), exercising options for JHSV ships 2 and 3. Work will be performed in Mobile, AL, and is expected to be complete by July 2012. The Naval Sea Systems Command in Washington, DC issued the contract. See also the June 19/09 entry for related advance materials purchases.
The accompanying Austal release, adds that the similar (ex-)Hawaii Superferry ships, “Alakai” and “Huakai,” have been mobilized by the US Maritime Administration, and are currently supporting the ongoing relief operation in Haiti.
JHSV 2 & 3 bought
Dec 18/09: Industrial. Austal announces success in the US Navy’s Production Readiness Review (PRR), which allows their Mobile, AL facility to immediately begin construction of Fortitude [JHSV 1]. US Navy Program Manager George Sutton referred in part to Austal’s recently-competed Module Manufacturing Facility (MMF) when he said that:
“Considerable investments in the Austal shipyard coupled with the implementation of proven commercial technology gives me high levels of confidence in the shipyard’s ability to execute the program.”
Nov 10/09: Industrial. Austal officially opens its new $88 million state-of-the-art Modular Manufacturing Facility (MMF) in Mobile, AL, equipping its US shipyard with the ability to build up to three 100 metre-plus vessels each year. Phase 1 facility boasts 35,000 m2 of manufacturing space under one roof, including a 7,900 m2 warehouse, as well as paved parking for more than 2,000 vehicles.
The MMF will increase Austal USA’s capacity to assemble and outfit unit modules before consolidating them into the full vessel, automating component manufacture, including pipe runs, from a 3D model. This approach is widely used in advanced European and Asian shipyards, but is less common in the USA. Austal’s MMF is equipped with routers for the precise cutting of aluminum plate, as well as automated pipe and plate benders. Test constructions are currently underway at the new facility, with work on the first 103 meter JHSV scheduled to commence before the end of 2009. The facility will also build LCS-2 Independence class trimarans for the Littoral Combat Ship program. Austal release.
July 17/09: Ship names 1-3. The Pentagon announces names for the first 3 JHSV ships. The Army will field Fortitude [JHSV 1] and Spearhead [JHSV 3], while the Navy’s first JHSV will be named Vigilant [JHSV 2]. The names for JHSV 2 and 3 eventually change.
Spearhead would later become the name for JHSV 1 instead. US Navy Team Ships | MarineLog.
June 19/09: #2-3 lead in. Austal USA in Mobile AL receives a $99.6 million modification to their JHSV contract (N00024-08-C-2217), covering long lead time materials needed for JHSV 2 and JHSV 3. These materials include items like aluminum for the hulls, main propulsion engines, waterjets, reduction gears, generators, and other components that need to be on hand before construction begins in June 2010.
Work will be performed in Detroit, MI (38%); Chesapeake, VA (18%); Henderson, Australia, (13%); Gulfport, MS (10%); Ravenswood, WVA (9%); and Ft. Lauderdale, FL (4%); Mobile, AL (3%); Auburn, IN (2.6%); Winter Haven, FL (1%); Gardena, CA (1%); and Davenport, IA (0.4%), and is expected to be complete by July 2013. US Naval Sea Systems Command manages the contract
Once construction contracts are awarded for the 2 ships later in FY 2009, these materials will be moved with their associated costs into their respective ship construction line items.
April 6/09: US Secretary of Defense Robert M. Gates takes the unusual but approved step of making his FY 2010 defense budget recommendations public. They include another 2 high speed ship charters from 2009-2011, until JHSV ships begin arriving.
Nov 13/08: Austal wins. Austal USA in Mobile AL received a $185.4 million Phase II modification to previously awarded contract (N00024-08-C-2217) for 1 (one) JHSV, and for associated shore-based spares. The firm also has options for up to 9 additional ships by 2013, which could raise the contract’s total value to about $1.6 billion. The Naval Sea Systems Command, in Washington Navy Yard, DC manages this contract, which eliminates fellow Phase I winners Bollinger/Incat and General Dynamics Bath Iron Works. The 103m JHSV design appears to be based on Austal’s Westpac Express catamaran, which is currently under long term charter to the US Marines.
Work on this initial contract will be performed at the firm’s American facility in Mobile, AL and is expected to be complete by November 2010. Austal is teamed with General Dynamics Advanced Information Systems, who will design, integrate, and test the JHSV’s electronic systems, including an Open Architecture Computing Infrastructure, internal and external communications, electronic navigation, aviation, and armament systems.
Austal already produces ships in Mobile, AL, which has about 1,000 employees and will now grow to about 1,500 employees. Ships produced at this location include some similar civilian designs like the Hawaii Superferry, as well as the Independence Class trimaran Littoral Combat Ship produced in partnership with General Dynamics Bath Iron Works. Austal USA is growing the Alabama facility, and phase one of what will ultimately be a $170 million expansion should be complete by summer 2009. The assembly-line style manufacturing building will allow construction of 3 LCS/ JHSV/ Hawaii superferry scale vessels per year, rising to a capacity of 6 ships per year at full build out. Austal | General Dynamics | Marinelog | Alabama Press-Register | Biloxi-Gulfport Sun-Herald | Western Australia Today | Maine’s Brunswick Times-Record re: union lobbying in Congress to scrutinize the deal.
Austal Wins! JHSV 1 bought
FY 2005 – 2008From initial requirements draft, to 3-team preliminary design contracts, to final RFP submissions.
Westpac express,July 30/08: Austal announces its final Phase II JHSV submission to the US Navy, following an extensive detailed design and review process. The firm expects that a single Phase II contract for up to 10 JHSV ships will be awarded in late 2008.
Austal’s release adds the interesting tidbit that the firm was recently awarded a new contract to provide additional features and equipment on Hawaii Superferry’s second commercial 107 meter catamaran, in order to allow its use by the military if required.
Jan 31/08: Preliminary design. The US Department of Defense awards a trio of $3 million Phase I preliminary design contracts for the JHSV. Winners include:
Team Austal: Austal USA, Austal Ships (Australia), and General Dynamics Advanced Information Systems (GDAIS). This is sort of the same Austal/GD core team building the trimaran LCS 2 Independence design for the USA’s Littoral Combat Ship competition – but note competitor #3…
Team Incat: Louisiana-based Bollinger Shipyards, Inc., Incat of Australia, and its design arm Revolution Design, Nichols Brothers Boat Builders and Kvichak Marine in Washington State, and Gladding-Hearn (Duclos Corp) in Massachusetts. Their design will be based on Incat’s 112 meter wave-piercing catamaran, currently in commercial service. Consortium source.
General Dynamics’ Bath Iron Works. No information.
See: US NAVSEA release [PDF] | Incat Australia release | Austal release | UPI re: Bath Iron Works | Springbored’s blog commentary re: Austal-GD dynamics.
Preliminary design contracts
April 23-27/07: Representatives of the US Army, Navy, Marine Corps and the shipbuilding industry meet at at Quantico Marine Corps Base, VA, to discuss the JHSV’s current status of the Joint High Speed Vessel and update prospective contractors on the vessel’s design requirements. US Army release.
November 2005: Initial Draft. The JHSV program office’s Initial Capability Document received approval from the Department of Defense Joint Requirements Oversight Council in early November. All four military services concurred with the decision. The Analysis of Alternatives for this program is scheduled to report out before the end of the 2005 calendar year, and procurement of the lead ship is planned for FY 2008. NAVSEA release
Appendix A: The US Military’s HSV/TSV Experience Westpac ExpressInstead of arising from a drawing board or a notional requirements sheet, the JHSV’s requirements were based on 7 years of experience operating similar leased vessels, from 2001-2008. The core concept is based on an Australian innovation: fast catamaran ferries from Austal and Incat that are in widespread civilian use. Each ship has a carrying capacity equal to about 20 C-17 heavy airlifters, and their waterjets can power these aluminum catamarans through the water at a consistent 35-40 knots in calm seas. Robert Kaplan, in “Hog Pilot and Blue Water Grunts“:
“Who thought up the idea of using car ferries to get Marines to a combat zone and then link up with pre-positioning ships?” I asked a Marine chief warrant officer. “No-one at the Pentagon. Just a bunch of guys brainstorming here,” the chief replied.”
It was more than just brainstorming. Incat’s HMAS Jervis Bay had been used very effectively by Australia during East Timor’s 1999 independence referendum and subsequent operations, and its demonstrated capabilities attracted American interest.
The chartered vessels quickly lived up to their billing. Normal transit for a Marine battalion from Okinawa, Japan to South Korea aboard ferry or amphibious shipping is about 2-3 days, and moving it by air would take 14-17 “lifts” from C-17 aircraft, a process that might require several trips unless that many planes were available. The same deployment could be carried out by Austal’s chartered WestPac Express catamaran in 24-30 hours; which is to say, at about half the time of conventional naval options, and at about 25% of airlift’s costs. One ship can carry a complete battalion of up to 970 Marines, along with 663 tons of vehicles and equipment. If the Marines must deploy from Guam, where many are being moved from Okinawa, the added distance makes JHSV an even more timely and cost efficient option.
“I Serve With HSV-2!”Austal’s ships weren’t the only high speed vessels in operation. The Army operated Incat’s HSVX-1 Joint Venture in conjunction with the Navy, and TSV-1X Spearhead was under sole Army control until its 2005 return to commercial service. Both ships saw extensive Army use in operations Enduring Freedom and Iraqi Freedom, as well as supporting operations in the Pacific, Atlantic, Mediterranean, Horn of Africa, Persian Gulf and Southeast Asia.
In one operation, TSV-1X Spearhead moved the 101st Airborne Division’s military police and their equipment from Djibouti, Africa to Kuwait in the Persian Gulf. The fast catamaran made the 2,000 mile trip in just 2.5 days. Its naval LSV predecessor would have needed 10 days to make the voyage, and would only have carried the equipment, forcing the troops to fly separately.
HSVX-1 Joint Venture was even used by Special Operations Command as a proof-of-concept platform for a special operations force afloat in the western Pacific. Its modifications included a helicopter landing deck and hangar, along with a small military command, control and communications suite. Modifications to its complement also included ScanEagle UAVs, letting US Navy experiment with UAVs, blimps and related vehicles in a persistent surveillance role. The combination of high speed transport, persistent surveillance, and advanced communications may prove to be very complementary.
A 3rd Incat ship, the 112m HSV-2 Swift, was contracted to serve as an interim Mine Warfare Command and Support Ship (MCS), supporting R&D into new mine warfare modular payloads. From 2004 onward, its scope of use became far broader, and Swift’s geographic range expanded to include Africa, Asia, and recovery efforts in the USA after Hurricane Katrina. It remains in American service as of 2013, and continues to trial new approaches like aerostats and UAVs.
If HSVX-1 and HSV-2’s experiences sound a lot like the USA’s forthcoming Littoral Combat Ships, the similarity is no accident. Experience with these high-speed catamarans has played an important role in developing the LCS concept of operations, though the US Navy may not have taken the experiments to their logical conclusion. Given the emergence of naval unmanned vehicles, some observers believe that JHSV’s size and lower cost make it a better choice than the smaller LCS as a “robotic swarm mothership”.
Additional Readings & SourcesThanks to DID reader and long-serving US MSC vet Lee Wahler for his assistance with this article.
JHSV and its RelativesThe USA’s 155mm M109 self-propelled howitzers (SPH) were first introduced in 1962, as a form of armored mobile artillery that could stand up to the massed fire tactics of Soviet heavy artillery and rockets. They and their companion M992 Armored Ammunition Resupply Vehicles (AARV) have been rebuilt and upgraded several times, most recently via the M109A6 Paladin upgrade.
In the meantime, the Army has re-learned a few home truths. Artillery arrives in seconds rather than minutes or hours, is never unavailable due to bad weather, and cheaply delivers a volume of explosive destruction that would otherwise require hundreds of millions of dollars worth of bombers and precision weapons. Most combat casualties in the gunpowder age have come from artillery fire, and the US Army will need its mobile fleet for some time to come. So, too, will the many countries that have bought the M109 and still use it, unless BAE wishes to cede that market to South Korea’s modern K9/K10 system, or new concept candidates like the KMW/GDLS DONAR. What to do? Enter the Paladin PIM program.
While the M109 was technically mobile, in practice it was only semi-mobile. The need to string communications wire in order to physically connect the battery’s howitzers and their fire-control center fixed the vehicles in position. Surveyors were used to calculate the battery’s location as part of this process, and the entire emplacement and readying procedure could easily take 15-20 minutes. So, too, could the process of taking this setup down so the battery could move to another location. It didn’t take a genius to figure out that spending so much time outside of any protective armor was going to get a lot of people killed in any serious conflict involving tools like attack helicopters, massed artillery and rocket fire, and nifty toys like artillery-locating radars that backtrack the origin point of incoming shells.
The M109A6 Paladin addressed these issues via computerization and communications upgrades. Secure SINCGARS radios replaced the wires. Inertial navigation systems and sensors attached to the gun automatically tell the crew where they are, and where their shells are likely to land. Finally, automatic gun-laying translates the fire co-ordinates to a specific gun position. No aiming circles. No surveyed fire points. No wire lines. Just move into the assigned position area somewhere, calculate data, receive orders from the platoon operations center, use FBCB2 (aka “Blue Force Tracker”) to verify the location of “friendlies,” use the automatic PDFCS (Paladin Digital Fire Control System) to aim the gun and send the shell on its way. Once the fire mission is over, the vehicle can move off, receive another target, then quickly lay and fire again.
Improved armor added even more protection to the new system, and an upgraded engine and transmission made the M109A6 speedier. On-board prognostics and diagnostics were installed to improve the vehicles’ readiness and maintainability. Finally, ammunition stowage was made safer, and the load was increased from 36 rounds to 39 rounds of 155mm shells. Some of which can be M982 Excalibur GPS-guided shells.
The M992 Field Artillery Ammunition Support Vehicle (FAASV) vehicle is the M019’s companion. The M992A2 is also referred to as “Carrier Ammunition Tracked” by the US Army, which is an apt name because it holds up to 90 shells on 2 racks (up to 12,000 pounds total), plus an hydraulic conveyor belt to help with loading the M109. In practice, the duo’s crews often handle that task manually. The Paladin PIM program will enhance the FAASV/CAT to M992A3.
M109A7 PIM: The Weapon M109, firingThe Paladin Integrated Management partnership builds on the A6’s advances, but there are so many changes that it’s almost a new-build program.
The BAE/Army partnership will re-use the turret structure and the main 155/39 mm gun. As such, additional range and accuracy depends on using new projectiles like the rocket-boosted & GPS-guided M982 Excalibur, or ATK’s non-boosted PGK screw-in guidance system. Both are explicitly contemplated in the Paladin PIM’s loading systems. Maximum rate of fire also remains unchanged, because tube structure and temperature remain the limiting factor for sustained rates of fire.
The Paladin Digital Fire Control System is somewhere between old and new. The system has continued to receive upgrades, and is being produced by BAE and Northrop Grumman. GPS is currently provided via older PLGR systems, with data sent to the Dynamic Reference Unit – Hybrid (DRU-H inertial navigator), but the obsolescence of electronic components within this box means that DRU-H and possibly PLGR are on the future replacement list.
M109A7 PIMWhat will be new? Two big advances:
Chassis. Previous M109 upgrades hadn’t altered the M109’s 1950s configuration. The new chassis are being fabricated & assembled with components from the M2/M3 Bradley IFV (e.g. engine, transmission, final drives, etc.), in order to create more commonality across America’s Heavy Brigade Combat teams. BAE Systems expects a growth in overall weight of less than 5%, but the combined effects of the new chassis and more robust drive components give Paladin PIM the ability to operate at higher weights than its current GVW maximum of about 39 tons/ 35.4 tonnes. That will be tested, given the expected weight of the T2 add-on armor and separate underbelly armor add-on kits.
All-Electric. The M109A7 PIM also incorporates select technologies from the Future Combat Systems 155mm NLOS-C (Non-Line-of-Sight Cannon), including modern electric gun drive systems to replace the current 1960s-era hydraulically-operated elevation and azimuth drives. The removal of the hydraulic systems saves the crew a tremendous amount of maintenance, and they retain manual backups for gun laying just in case.
The shift to an electric turret included a major redesign of the vehicle’s power system, converting the 600 hp engine’s work into up to 70 kW of 600 volt/ 28 volt direct current for use by various on-board systems. The power system’s modularity means that if any one of the motors inside fails, it can be replaced in the field within less than 15 minutes, using the same single part type. In concrete terms, it means the howitzer crew can handle the problem themselves and continue the mission, instead of withdrawing for repairs.
Paladin PIM: The ProgramAdam Zarfoss, BAE Systems’ director of artillery programs:
“Artillery is playing an important role in operations in Iraq, with the Paladin providing critical fire support with both standard and precision munitions… The M109A6-PIM is the next step in Paladin development to ensure this essential fire support system remains ready and sustainable for soldiers in the HBCT [Heavy Brigade Combat Teams] through its projected life beyond the year 2050.”
Even with the previous-generation Paladin’s computerization and fast, safe set-up and take-down, a noticeable capability gap existed between the M109A6 used in Iraq, and newer self-propelled guns. At the same time, America’s comparable XM2001 Crusader/ XM2002 ARRV was canceled as an $11 billion Cold War relic in 2002, and the light 155mm NLOS-C died with the 2009 removal of the Future Combat Systems ground vehicle program.
The Paladin Integrated Management Program is designed to handle America’s future needs in the absence of Crusader and NLOS-C, and close some of the M109A6’s technological gaps. The initial goal was 600 M109A7 / M992A3 vehicle sets, but that has been lowered slightly to 558.
BAE Systems and the U.S. Army have signed a 2007 memorandum of understanding (MoU), establishing a Public-Private Partnership (P3) to develop and sustain the Army’s M109A6 vehicles throughout their life cycle. The establishment of a P3 will capitalize on the strengths and capabilities of each organization to ensure the cost-effective and on-time reset of the current fleet of M109A6 Paladin self-propelled howitzers (SPHs) and M992A2 Field Artillery Ammunition Supply Vehicles (FAASV), as well as the planned production of the M109A7/M992A3 Paladin Integrated Management (PIM) systems.
PIM prototypes were originally slated to be delivered to the US Army for test and evaluation in 2009, but changes to the program meant that the prototype contract wasn’t even issued until October 2009. That moved prototype delivery back to May 2011.
By January 2012, BAE had completed Phase I of the Army’s formal Developmental Test Program, with 5 vehicles returning for refurbishment, and 2 remaining at Aberdeen Proving Grounds for further tests. Full testing of all vehicles was set to resume in June 2012, and the Milestone C approval to proceed with Low-Rate-Initial-Production (LRIP) was scheduled for June 2013. In practice LRIP approval by the Defense Acquisition Board slipped to October 2013, and formal induction didn’t take place until May 2014.
Industrial Team M992 cutawayParties to the memorandum signing include BAE Systems leaders, US Army TACOM (Tank, automotive & Armaments COMmand), The Army’s PEO-GCS (Program Executive Office for Ground Combat Systems), the Army’s PKM-HBCT (Project Manager – Heavy Brigade Combat Team), and the Anniston Army Depot in Alabama. The MoU was signed during the AUSA 2007 conference in Washington, DC.
BAE Systems has significant experience with public-private partnerships thanks to Britain’s “future contracting for availability” innovations. In the USA, meanwhile, it has a long standing and successful partnership with the Red River Army Depot in Texas to remanufacture and upgrade the USA’s M2/M3 Bradley fighting vehicles.
The Army’s PM-HBCT will manage the M109 RESET activities. Anniston Army Depot will retain labor and lead the majority of the program, including the M109A6-PIM production process, through the public-private partnership. They will be integrated into the PIM Integrated Product Development Teams (IPDTs) structure during the design phase, and will support the manufacture of the prototype vehicles.
During the production phase, Anniston Army Depot will be responsible for induction of vehicles, overhaul of critical components like the gun system, and modification/ upgrade of the cab structure. BAE Systems will be responsible for materials management. The partially assembled cabs, along with overhauled components, will be provided to BAE Systems for integration with the new M109A7 PIM chassis. Areas involved in production will include York, PA; Aiken, SC; and Elgin, OK where final assembly will take place.
Export Potential PzH-2000A total of 975 M109A6 Paladins were produced for the US Army, and another 225 or so were produced for Taiwan. Full rate production ceased in 1999. BAE built a small final batch to fill out an Army National Guard request, which finished in 2001.
Most other countries who use the M109 (Belgium, Brazil, Chile, Denmark, Egypt, Greece, Israel, Kuwait, Morocco, Norway, Oman, Pakistan, Portugal, Saudi Arabia, South Korea, Spain, Thailand, Tunisia, Iran on its own, soon Iraq with US support) employ previous versions, ranging from M109A1s to M109A5s.
That’s a lot of potential upgrades.
So far, the most popular upgrade abroad is the M109A5+, which adds independent position location via GPS/INS, and radio transmission of co-ordinates. It’s a budget-conscious upgrade that omits the M109A6’s automatic gun-laying, which would require a tear-down and rebuild of the turret. It also omits the PIM upgrades, which make very substantial changes to every part of the vehicle.
On the other hand, countries that do decide to field fully modern armored artillery systems will find that Paladin PIM is still generally cheaper than buying new heavy systems. That’s enough to succeed in America. What about the rest of the world?
Abroad, Paladin PIM will be competing against options like KMW’s PzH-2000, Denel’s G6, and Samsung’s K9/K10 on the heavy side, some of which offer more advanced features. It will also have to deal with substitution threats from lightly-armored truck-mounted 155mm artillery like BAE/Saab’s Archer, Elbit’s Atmos, and Nexter’s Caesar. It’s still early days, but the M109A7 Paladin PIM system has yet to find an export customer.
Contracts and Key EventsUnless otherwise noted, US Army TACOM in Warren, MI issues the contracts to BAE Systems Land & Armaments’ Ground Systems Division in York, PA.
FY 2018At Fort Sill
October 24/18: Tracks Contitech is being tapped to provide the US Army with vehicle tracks for its M109 Paladin artillery system. The firm-fixed-price contract is valued at $20.1 million and will run through July 8, 2021. The M109 family of systems has been in service since 1962. The latest variant is the BAE produced Paladin M109A7 next-generation artillery system. The new variant incorporates upgrades to hull, turret, engine, and suspension systems that offer increased reliability, survivability and performance over its predecessor. The 155 mm cannon is mounted on the chassis structure common to the Bradley tracked fighting vehicle. Work will be performed at Contitech’s factory in Fairlawn, Ohio.
FY 2016August 11/16: Howitzers in the Paladin Integrated Management (PIM) program are being questioned over deficiencies with the weapon’s maximum rate of fire and problems with the automatic fire extinguisher that could potentially endanger the crew. The DoD’s inspector general raised the queries in a report released last week. 2012 and 2013 tests saw the howitzer fail the test for maximum rate of fire which led to a redesign of hardware, software and firing procedures but still failed a total of four out of eight attempts following the fixes “under non-stressful firing conditions.”
November 2/15: The Army announced on Friday that they have awarded a $245.3 million contract modification for 30 M109A7 Paladin self-propelled howitzers, along with 30 M992A3 Armored Ammunition Resupply Vehicles. This low rate initial production-2 (LRIP-2) modification (Option 2) follows a similar award (Option 1) in October 2014 for 18 of each vehicle, with the two options scheduled for deliveries by February 2017 and June 2018 respectively.
FY 2015
Oct 31/14: LRIP-2. A $141.8 million fixed-price-incentive contract modification exercises Option 1 for 18 M109A7 Self-Propelled Howitzers and 18 M992A3 Carrier Ammunition Tracked vehicles. All funds are committed immediately, using FY 2014 and 2015 Army budgets. This raises the contract’s total value (q.v. Oct 30/13) to $386.7 million so far.
Estimated completion date is Feb 28/17. Work will be performed in Elgin, OK (18%), and York, PA (82%) (W56HZV-14-C-0002, PO 0011).
LRIP-2 order: 18 SPH, 18 CAT
FY 2014Milestone C approval; LRIP contract; GAO and DOT&E reports highlight remaining issues.
M109A7: Fire!July 18/14: EMD. An $88.3 million modification to contract to extend the existing M109A7 and M992A3 engineering and manufacturing development contract to incorporate low rate initial production test support. $14.1 million in FY 2013 and 2014 US Army RDT&E funding is committed immediately.
This raises announced Paladin PIM EMD contracts (q.v. Jan 17/12) to $401.6 million. Estimated completion date is March 31/17. Work will be performed in York, PA (W56HZV-09-C-0550, PO 0081).
May 19/14: Inducted. The US Army formally inducts the Paladin PIM system, and gives the systems new designations. It’s now the M109A7 self-propelled howitzer, with its companion M992A3 ammunition carrier. Low-rate initial production will begin in summer 2014, as M109A6s and M992A2s are shipped the Anniston Army Depot for disassembly. Some of those parts, especially the cab and cannon assembly, will be used along with new components like the chassis, engine, transmission, suspension, steering system, and power system.
US Army PM self-propelled howitzer systems Lt. Col. Michael Zahuranic is especially pleased by the fact that the upgrade creates more space, saves weight, and improves power and cooling, making it much easier to add new capabilities until its planned phase-out in 2050. BAE Systems VP and GM Mark Signorelli was also happy today, both for the milestone it represents for his company and because he had commanded a M109A3 when he was in the US Army. Sources: US Army, “Army inducts self-propelled howitzer into low-rate initial production”.
Inducted as M109A7 / M992A3
May 14/14: Engines. BAE Systems Land & Armaments LP in York, PA receives a $16.1 million contract modification for an advance buy of V903 engines, to equip PIM low rate initial production vehicles.
All funds are committed immediately, using FY 2014 budgets. Work will be performed in Columbus, IN (77%), and York, PA (23%), with an estimated completion date of Dec 31/18. US Army Contracting Command-Tank and Automotive in Warren, MI manages the contract (W56HZV-14-C-0002, PO 0003).
March 31/14: GAO Report. The US GAO tables its “Assessments of Selected Weapon Programs“. Which is actually a review for 2013, plus time to compile and publish. For the PIM program, its design is mature. So are its 2 critical new technologies: power pack integration, and the ceramic bearing of the generator assembly. On the other hand, weight limits are a concern, and testing had better go right, because the program’s schedule leaves very little time for fixes if tests show problems.
The largest single technology risk involves the current contractor for the engine and transmission, who may cease production due to lack of orders. That could force a vendor switch and even a redesign of the engine compartment, raising costs between $32 – $100 million and adding a “significant” schedule delay.
The Milestone C delay from June – October 2013 was staff-driven due to sequestration. Other delays to the start of developmental testing stemmed from changes to protection and survivability requirements, which led to a new ballistic hull and turret and new armor kits.
Jan 28/14: DOT&E Testing Report. The Pentagon releases the FY 2013 Annual Report from its Office of the Director, Operational Test & Evaluation (DOT&E). The revised program schedule reduces the program’s planned low-rate (LRIP) production run from 72 sets – 66 sets, while cutting the LRIP period from 4 years – 3 years.
The new M109A6 PIM has done well in tests with GPS-guided shells, with a CEP of less than 10m for rocket-boosted M982 Ia-2 Excalibur shells out to 35 miles, and average CEP of 24m out to 15 miles for ATK’s screw-in Precision Guidance Kit. The bad news is that ordinary shells are a problem. In 2012 Limited User Tests, the PIM failed to meet accuracy requirements at short (4-6 km) ranges, offered a timeliness downgrade from M109A6 standards by meeting less than 20% of fire mission time standards, and displayed deformation and jamming of the M82 primer when firing when firing M232A1 Modular Artillery Charge System (MACS) Charge 5 propellant.
The Army has begun using some very innovative approaches in its effort to fix the defects (q.v. July 30/12), and in January 2013, the program began installing and testing a series of Corrective Actions, Producibility, and Obsolescence (CPO) changes for the SPH and CAT. The Army intends to fix the timeliness problem using hardware and software changes, and there have been some positive indicators in subsequent tests. Meanwhile, they intend to continue testing upgraded suspension and transmission components in light of increased weight from the underbelly and T2 up-armoring kits.
A special research team is looking at the MACS problems. They’re considering a wide range of options: propellant changes, breech & firing mechanism redesigns, alternative ignition systems, or even restricting the PIM to 4 MACS charges and taking the range penalty.
Oct 30/13: LRIP. BAE Systems Land & Armaments LP in York, PA receives a $195.4 million fixed-price-plus-incentive contract for Low-Rate Initial Production of 19 Paladin PIM self-propelled Howitzers (SPH), 13 SPH Threshold 2 (T2) armor kits as up-armoring options, 18 Carrier Ammunition Tracked (CAT, formerly FAASV reloader) vehicles, 11 CAT T2 armor kits, and 37 lots of basic issue items. All funds are committed immediately, using FY 2013 RDT&E ($14.6 million) and “other” ($180.8 million) budgets.
Work will be performed at York, PA; Elgin, OK; and 24 locations throughout the United States until Feb 29/16. One bid was solicited and one received by US Army TACOM in Warren, MI.
The 1st production vehicle is expected to roll out of the depot in mid-2015. BAE says that this contract could rise to $688 million for about 66 vehicle sets (likely 67 SPH and 66 CAT), plus spares, kits and technical documentation (W56HZV-14-C-0002). Note that this is slightly less than envisioned before (q.v. Dec 6/12). See also: BAE, Oct 31/13 release.
LRIP-1 order: 19 SPH, 18 CAT
October 2013. The Defense Acquisition Board green-lights the Paladin Integrated Management program for low rate initial production. To that effect, the FY 2014 budget submitted by the Army in April 2013 asked for $260.2 million in base procurement to field a lot of 18 SPHs and CATs (Carrier Ammunition, Tracked) at a unit cost of about $14.45 million. A LRIP award is expected soon so that production can begin next year.
The Initial Operational Test & Evaluation (IOT&E) milestone had been scheduled for Q4 FY2016, back when Milestone C was expected in June 2013. Meeting that deadline will depend on whether corrective actions to address deficiencies found in tests (q.v. December 2012) can be made fast enough.
LRIP decision / Milestone C
FY 2012 – 2013EMD contract finalized; Production moves to Elgin, OK; What videogames have to teach the PIM program.
PIM LUTDecember 2012: Test results. The Pentagon’s Operational Test & Evaluation Office publishes its 1st report [PDF] on PIM. The Test and Evaluation Master Plan (TEMP) was approved in March 2012, and prototypes refurbished in June 2012 had gone through Phase II development testing by October 2012, following Phase I tests a year earlier.
Vehicle discrepancies after repeated gun shock were higher than with legacy subsystems, including PDFCS. A software issue between the Muzzle Velocity Radar System (MVRS) and PDFCS led to frequent failures. The SPH also failed to meet its climbing requirement, though DOTE doesn’t say whether that’s a problem with meeting a paper spec or a more serious mobility issue.
The report notes that the program’s tight schedule means corrective actions will have to wait until the LRIP phase. This leads DOTE to conclude that “the schedule for development, test, and implementation of those [corrective action, producibility, and obsolescence (CPO)] changes is high-risk and challenging.”
Dec 6/12: BAE Systems announces that they’ve picked the Elgin, OK facility in the Fort Sill Industrial Park for M109A6 Paladin PIM Low Rate Initial Production. This will move those jobs to Elgin about 2-3 years sooner than the original plan. BAE, in turn, wants to be next to the Army’s Artillery Center of Excellence and its experienced personnel.
The PIM LRIP award is expected in Q3 2013, and will involve just 72 PIM systems. Key components of the PIM production vehicles, including the chassis, will be sent to the Elgin facility from BAE Systems manufacturing facilities and suppliers. As part of final assembly and checkout, BAE Systems will use Fort Sill for mobility and firing verification.
July 30/12: Videogames & Telemetry. David Musgrave is the Army’s project lead for fire control software development on the M109A6 PIM, and he’s having a problem:
“We were encountering some problems with firing tests. I started asking questions looking for objective use data. How often does subsystem X fail? When it does fail, what was the user trying to do at the time? How often does a user perform Y task? The truth was I couldn’t get any decent answers. I was frustrated that there was a very limited information channel from our system back to us while it was being used.”
He thinks the solution might involve taking a tip from the videogame industry, which uses “telemetry” to track how people are interacting with the games, and what they’re using or not using. A presentation from BioWare’s Georg Zoller was especially inspirational, and Musgrave has a good head on his shoulders when it comes to the reality of implementation in the Army. He sees huge potential benefits for program managers, units, and soldiers alike, but only if the system doesn’t interfere with the weapon in any way, and the program doesn’t try to do too much. The biggest technical challenge will be finding a reasonable method to reliably get the tracking data back to a central server. See also US Army Article | Full RDECOM PowerPoint Presentation [PDF].
Jan 17/12: EMD. A $313.1 million cost-plus-incentive-fee contract modification for PIM engineering design, logistics and test and evaluation services, which will complete the Engineering, Manufacturing & Design phase. Work will be performed in York, PA, with an estimated completion date of Jan 31/15. One bid was solicited, with 1 bid received (W56HZV-09-C-0550). Additional EMD contracts bring the total to $401.6 million, and include:
In discussions, BAE representatives added that the 7 prototype PIM vehicles (5 howitzers, 2 resupply vehicles) delivered in May 2011 have logged over 7,500 miles, fired over 2,600 rounds, and come through extreme temperature testing to complete Phase I of the Army’s Reliability, Availability and Maintainability (RAM) tests. Testing will resume in June 2012, and the next step after that is a June 2013 Milestone C decision, which would begin low-rate initial production. BAE release.
EMD Contract
Oct 24/11: EMD. A $9 million cost-plus-fixed-fee contract to provide refurbishment and analysis services for the PIM Bridge 3 effort. Work will be performed in York, PA, with an estimated completion date of Nov 30/12. One bid was solicited, with one bid received (W56HZV-09-C-0550).
Oct 5/11: EMD. A $9.8 million cost-plus-fixed-fee contract for the PIM Bridge 1 effort. Work will be performed in York, PA, with an estimated completion date of Nov 30/11. One bid was solicited, with 1 bid received by the U.S. Army Contracting Command in Warren, MI (W56HZV-09-C-0550).
Oct 5/11: T2. A $7.9 million cost-plus-fixed-fee contract to buy the PIM’s T-2 Armor Kits. Work will be performed in York, PA, with an estimated completion date of Sept 30/12. One bid was solicited, with 1 bid received by the U.S. Army Contracting Command in Warren, MI (W56HZV-09-C-0550).
Oct 5/11: Transmission. L3 Communications Corp. in Muskegon, MI receives a $7.9 million firm-fixed-price and cost-plus-fixed-fee contract, to develop a common transmission for the Bradley Family IFV/CFVs, and the Paladin Integrated Management vehicles. Work will be performed in Muskegon, MI, with an estimated completion date of Nov 15/13. One bid was solicited, with one bid received by the U.S. Army Contracting Command in Warren, MI (W56HZV-09-C-0098).
FY 2007 – 2011From MoU to delivery on initial prototypes.
M109A6 PIMJune 7/11: An $11.6 million cost-plus-fixed-fee contract modification, to buy PIM ballistic hulls and turrets. Recall that the new PIM chassis are being fabricated & assembled with Bradley common components.
Work will be performed in York, PA, with an estimated completion date of April 30/12. One bid was solicited, with one bid received (W56HZV-09-C-0550).
May 2011: Delivery. The 7 PIM prototypes are delivered to the U.S. Army, on schedule. Source.
Prototypes delivered
Oct 28/10: BAE Systems announces that they are on track to deliver 7 Paladin/FAASV Integrated Management (PIM) prototype vehicles to the U.S. Army on schedule, under the $63.9 million August 2009 research and development contract, announced in October 2009 (5 M109s, 2 FAASVs).
The initial PIM vehicles are conducting contractor testing in Yuma, AZ and Aberdeen, MD before they are delivered for government testing in January 2011.
June 15/10: An $8.7 million cost-plus-fixed-fee contract, for Paladin PIM line replaceable units. Work is to be performed in York, PA, with an estimated completion date of June 30/12. One bid was solicited with one bid received (W56HZV-09-0550).
Jan 20/10: Rollout. BAE Systems unveils its upgraded PIM (Paladin Integrated Management) vehicle to military customers, Congressional representatives, community leaders and employees at a ceremony held at its York facility. This is the 1st vehicle built under the Oct 5/09 contract. BAE Systems release.
Oct 5/09: Prototypes. BAE Systems announces a $63.9 million contract from the U.S. Army Tank Automotive & Armaments Command for 5 prototype M109A6 PIM self-propelled howitzer vehicles, and 2 prototype M992A2 Field Artillery Ammunition Support Vehicles (FAASV).
Development contract
Nov 4/08: PDFCS. BAE systems announces a $20 million contract from the US Army’s TACOM Life Cycle Management Command, to purchase and deliver 140 Paladin Digital Fire Control Systems (PDFCS) kits, and more than 60 spare components to support the system. They will be added to the 450 or so kits that have already been ordered under this contract.
Some of the kits under this contract will be installed on vehicles at fielding sites across the world, while others will be shipped to an Army Depot where they will be used on the Paladin reset line. Work will be performed by the existing workforce at BAE Systems facilities in York, PA; Sterling Heights, MI; and Anniston, AL beginning in September 2009. Deliveries are scheduled to be complete by January 2010.
Oct 9/07: MoU. BAE Systems and the US Army sign a memorandum of understanding (MoU), establishing a Public-Private Partnership to develop and sustain the Army’s M109 Family of Vehicles throughout their life cycle. BAE Systems release.
Oct 8/07: BAE Systems unveils the M109A6-PIM Paladin upgrade at the AUSA 2007 show in Washington DC. BAE Systems release.
Unveiling & Partnership
Additional ReadingsReaders with corrections, comments, or information to contribute are encouraged to contact DID’s Founding Editor, Joe Katzman. We understand the industry – you will only be publicly recognized if you tell us that it’s OK to do so.
Background: Artillery & ShellsThis free-to-view DID Spotlight article offers an in-depth look at India’s troubled attempt to convert and field a full-size aircraft carrier, before time and wear force it to retire its existing naval aviation and ships.
India faced 2 major challenges. One was slipping timelines, which risked leaving them with no aircraft carriers at all. The other challenge involved Vikramaditya’s 3-fold cost increase, as Russia demanded a re-negotiated contract once India was deeper into the commitment trap. The carrier purchase has now become the subject of high level diplomacy, involving a shipyard that can’t even execute on commercial contracts. A revised deal was finally signed in March 2010, even as deliveries of India’s new MiG-29K naval fighters got underway – but now Russia still has to make good. This article tracks the changes India is making to its new aircraft carrier, key characteristics, and a full history of contracts and events affecting this carrier and its planned aircraft contingent.
Russian naval doctrine saw the 45,000t Admiral Gorshkov as a missile cruiser with a complement of aircraft. India wanted a full-fledged aircraft carrier. Getting there required extensive modifications.
The cruiser-carrier’s guns, anti-shipping and air defense missile launchers on the front deck were removed. In their place, India installed a full runway and ski jump, widened the deck in numerous places, and installed a bigger and stronger rear aircraft elevator.
Core ship systems were also slated for modernization. New boilers were installed to run on diesel fuel, for instance, and communications were improved. One nasty surprise that might have been expected was the need to replace most of the ship’s old wiring. Adding more reliable, higher capacity wiring will help make Gorshkov a fully modern ship, but it has been very labor intensive and expensive.
INS Vikramaditya’s weakness will be defensive. An official Indian CAG report says that INS Vikramadirya will have no aerial defenses until 2017. When it does, those weapons will need to integrate with the Russian LESORUB-E combat system, which means that weapon installation won’t take place until the carrier’s initial refit. The Navy would like to field the Barak-8/ MR-SAM missile for medium-long range defense, but integration could be challenging. They also want a close-in weapon system or 2, and intend to hold a competition rather than adopting the gun/missile Kashtan CIWS system carried by Russia’s own Admiral Kuznetsov carrier, or buying Russia’s lower-end 30mm AK-630.
Anti-submarine defenses are equally concerning. The Indian Navy only has 10 Ka-28s, and only 4 of those are operational. That deficit, plus a Sea King fleet that is small, old, and needs improvements, makes anti-submarine defense a big concern. India may end up outfitting its own Dhruv light helicopter with 1st-generation locally-designed ASW gear, and basing some on the carrier. That’s a fine stopgap solution, but a questionable medium-term option for defending their fleet flagship. A global tender for larger and more advanced ASW helicopters has been delayed since 2008.
Failure to add a modern towed sonar to its surface combatant ships juts makes things worse. Anti-submarine defenses will have to be improved within the fleet as a whole, if India intends to field a viable carrier force.
Gorshkov-Vikramaditya: Aerial Complement Ka-31 AEWMany of Gorshkov’s key modifications are aircraft-related, including the new arrester gear and ski jump. That’s just the down-payment on the final cost of an operational carrier, because the aircraft are bought separately.
The original cruiser-carrier’s complement was 12 Yak-38 Forger V/STOL(Vertical/Short Take Off and Landing) fighters, 12 Ka-28 helicopters, and 2 Ka-31 airborne early warning helicopters. The removal of the Gorshkov’s forward missiles, addition of the ski ramp, and other modifications will improve the ship’s air complement, but the nature of its original design means that INS Vikramaditya will still fall short of comparably-sized western counterparts. Carriage ranges given for the refitted Vikramaditya seem to converge around 16-24 fighters, and 10 compact Ka-28/31 or Dhruv helicopters.
In contrast, the 43,000t FNS Charles de Gaulle nuclear-powered aircraft carrier is about the same size, with a 40-plane complement that leans heavily to fighter jets. The FS Charles de Gaulle will also have an advantage in surveillance coverage, thanks to catapults that let her operate E-2C Hawkeye 2000 airborne early warning planes. INS Vikramaditya won’t have that option, because it doesn’t have a launch catapult.
The carrier’s AEW complement, if any, is almost certain to use India’s Ka-31 helicopters instead. That means a smaller radar, on a slower platform, offering much less coverage.
MiG-29K 3-viewVikramaditya’s fighters will also be Russian. Its air wing will draw on a fleet of 45 Indian MiG-29Ks, thanks to about $1.95 billion in contracts. The initial $740 million contract for 16 MiG-29K (12 MiG-29K, 4 two-seat MiG-29KUB) aircraft plus training and maintenance was confirmed on Dec 22/04. The contract’s option for another 29 planes, rumored to be worth another $1.2 billion, was signed in March 2010. The MiGs would be operated in STOBAR (Short Take-Off via the ski ramp, But Assisted Recovery via arresting wires) mode.
MiG’s design was reportedly selected over the larger and more-capable SU-33 naval fighter for several reasons. One is that India already operates a large fleet of MiG-29s, and has been improving its ability to maintain them in country. Another reason is that India also wants to operate naval fighters from its locally-built 37,500t – 40,000t “Project-71 Air Defence Ship” (Vikrant Class) STOBAR carriers. The SU-33s wouldn’t be an ideal choice for a carrier that size, Britain hadn’t yet put its Harrier feet up for sale, and India’s own Tejas Naval fighter project remained a high-risk option. That left the MiG-29K as India’s only rational choice, and Russia followed with an order to equip their own carrier.
Waiting for Gorshkov – A HistoryOn Jan 20/04 India and Russia signed a $947 million deal to refurbish and convert the Soviet/Russian Admiral Gorshkov into a full carrier, to be re-named INS Vikramaditya. The announced delivery date for INS Vikramaditya was August 2008 – an ambitious schedule, but one that would allow the carrier to enter service in 2009, around the time as their 29,000t light carrier INS Viraat (formerly HMS Hermes, last of the Centaur class) was scheduled to retire. The new carrier would berth at the new Indian Navy facility in Karwar, on India’s west coast.
That was the plan. Unfortunately, the Vikramaditya story is sadly typical of both Indian defense procurement, and of Russia’s defense industry.
Denial, Delay & Disagreement Now what?Initial reports of delays sparked controversy and denials in India, but subsequent events more than justified them. Slow negotiations and steadily-lengthening delivery times quickly pushed delivery of the Gorshkov back to 2010, and then to 2012 or later, even as Russia’s asking price more than doubled. India’s sunk construction costs, Russian possession of the Gorshkov, the difficulty in finding a substitute carrier to replace the Gorshkov sooner than 2013, and the Chinese push with the Varyag, have all combined to give the Russians substantial leverage in their negotiations.
They exploited that leverage to the fullest. Cost estimates and reports concerning the Gorshkov’s final total now hover in the $2.9 billion range, following the revised project agreement of March 2010.
As is customary with Indian defense procurement, transparency arrived only after all other alternatives had been exhausted.
When reports first surfaced that this delivery date would not be met, India’s Ministry of Defence initially tried to deflect the issue with denials and obfuscation. In May 2007, Chief of Naval Staff Admiral Sureesh Mehta said the ships will be delivered:
“…by late 2008 or early 2009… Our officials, who are stationed at the spot, have said that the work is going on as per schedule and we can have a month long delay once the work is completed as that part of Russia is frozen for a long time.”
Later comments on this issue included this May 1/07 quote:
“The work is only three to four months behind schedule and we can expect the aircraft carrier to be delivered by late 2008 or early 2009”
Neither assessment turned out to be true, and subsequent updates proved the critics to be correct. After the delivery delays could no longer be denied, the initial approach was to minimize their length. February 2008 news reports, however, began to give figures of up to 3-4 years before refurbishment and testing could allow the ship to enter service. Subsequent reports by Indian and Russian sources stressed 2012, or even later.
Those estimates, at least, turned out to be true. The carrier didn’t see operational service of any kind until May 2014, and it will take even longer before it’s fully ready to fight.
India’s Carrier Collapses INS ViraatThe delays have left India’s Navy with a serious scheduling problem, and created periods with no significant carrier force.
INS Viraat’s retirement was scheduled for 2009, but Vikramaditya’s delays forced India into another refit, leaving the country without a carrier for 18 months until August 2009. Even with the refit, Viraat is nearing the limits of her mechanical life, and shortages of flyable Sea Harrier fighters are creating issues of their own. Subsequent refits and overhauls will try to keep the carrier, whose keel was laid in 1944, running until 2018. When she did return after an unexpectedly long refit, she had just 11 flyable Sea Harrier fighters available.
India’s other option was the locally-built Vikrant Class “Air Defence Ship” escort carrier project, which received formal government approval in January 2003. It was supposed to field a 37,500t – 40,000t carrier by 2013-2014; instead, Vikrant’s operational acceptance into the fleet slipped to 2018, then 2019.
To the east, China bought the engineless hulk of the 58,000t ex-Russian carrier Varyag in 1998, towed her to China, and worked hard to refurbish her. The ship began trials in 2012. By September 2012, reports surfaced that the ship had been re-named “Liaoning,” in honor of the province where it was retrofitted. She began sailing before the end of the 2012, and the ship has launched and recovered J-15 (SU-33 derivative) naval fighters. In May 2013, China declared an official naval aviation capability. Reports have China aiming for 4 carriers in the medium term.
Contracts & Key Events 2014 – 2018Arrival in India; Competition for air defense systems; Maintenance agreement with Russia.
Two again 2018October 24/18: Sea trials India’s sole operational aircraft carrier will start sea trials by the start of next week. The INS Vikramaditya recently completed its second refitment at Cochin Shipyard, a process which cost close to $96 million. Captain Puruvir Das, the carrier’s commanding officer, told the New Indian Express “soon, we will start the sea trials, which will take place off the Kochi and Goa coasts. We are hopeful of returning to the Western Naval Command without delay.” During the refitment major work was carried out, including an extensive hull survey and repainting, as well as some large scale repair of the ship’s shaft system. “The refitment will enhance the operations of Vikramaditya. It will be ready for sea operations once the trials are completed,” added Captain Das. The Kiev-class former Russian Navy aircraft carrier has been in service since 2013 and upgrade of its infrastructure were started in September 2016.
July 12/18: India’s plan to build and commission its second indigenous aircraft carrier has been postponed again. Steadily declining budgets, technological hurdles and prolonged delays by the Ministry of Defense in approving the program make it very unlikely that the Vishal will enter service by 2030-2032. The proposed 65,000–70,000 ton conventionally powered ‘flat top’ carrier would be capable of embarking 50–60 fixed- and rotary-wing platforms and cruise at 30 knots, but it would also cost between $12 – 13 billion. India’s Navy has currently one carrier in operation the refurbished Soviet-era Kiev-class Vikramaditya. By 2018–19, Vikramaditya was to have been supplemented by INS Vikrant, the 37,000-tonne Project 71 carrier with a short take-off but arrested recovery (STOBAR) configuration that has been under construction since 2009 at Cochin Shipyard Limited, southern India. At this point the Vikrant is scheduled to enter service by October 2020. The Indian Navy plans to field three carrier battle groups under its Maritime Capability Perspective Plan.
2015December 10/15: The INS Vikramaditya is set to get its first overhaul, the Indian Navy has announced. The Kiev-class former Russian Navy aircraft carrier has been in service since 2013 and upgrade of its infrastructure is set to be under way by September 2016. Works will be undertaken by Cochin Shipyards (CSL), who recently released India’s first indigenously built aircraft carrier, the INS Vikrant, to the Navy. CSL will no doubt be utilizing the experiences learned during the Vikrant’s construction during the refit.
December 8/15: India’s first indigenous aircraft carrier will be delivered to the Indian Navy by December 2018. The INS Vikrant was undocked in June by Cochin Shipyard (CSL) who are anxious to start construction of a second vessel, although no formal agreements have been made. Some minor delays have been experienced due to lack of availability of warship grade steel, and delays in Russian approval over designs and equipment supply. When commissioned, the INS Vikrant will become the third aircraft carrier in service in the Indian Navy, which has been increasing its fleet size to boost India’s presence in the Indian Ocean.
July 16/15: India’s INS Vikramaditya is scheduled to leave Karwar next week after a recent refit. As per previous reports, the carrier has been updated with new air defense systems, including the Barak-1 missile system and the Russian AK-630 close-in weapon system (CIWS). The Indian Navy carried out feasibility studies for the integration of the two systems in June 2014, with the original plan being to fit the vessel with the Barak-8 missile system, jointly developed with Israel; however, development delays led to the carrier being fitted with the older Barak-1 system.
Dec 4/14: Vikrant Schedule. Vice Admiral Anil Chopra, Commander-in-Chief of the Western Naval Command since last June and the 2nd most senior officer in India’s navy, tells reporters that INS Vikrant is now to be commissioned in 2019, months later than the previous already-postponed deadline. Plans to build a second carrier in the class will be “initiated soon.” Source: Free Press Journal.
Aug 25/14: Infrastructure. Defense World claims that India is preparing to field a 2nd MiG-29K squadron in the east, as part of a major upgrade that will grow INS Dega in Vishakapatnam from 1100 to 1500 acres. An initial outlay of INR 4.5 billion (about $75 million) was reportedly approved this month to build MiG-29 fighter and Hawk trainer support and infrastructure there, in preparation for MiG-29K arrival some time in 2015. The Navy is also looking at reactivating Bobilli, a disused, World War II airfield about 45 nautical miles away, as a secondary divert base. The Business Standard:
“The volume of naval aviation that the airbase is slated to handle will bring it almost at par with the largest naval airbase INS Hansa [on the western coast, in Goa]. The workload will include accommodating the full squadron of MiG29K/KUBs as well as the [Navy’s] Advanced Jet Trainer (AJT) Hawks, nine of which are already operational and eight more will arrive by June 2016, along with their required infrastructure and support set up. INS Dega will also field a large chunk of aircraft which form a part of future acquisitions like Multi Role Helicopter (MRH), 56 Naval Utility Helicopters, Naval Multi Role Helicopters (NMRH) as well as Unmanned Aerial Vehicles (UAVs).”
Some reports characterize this move as preparation for the new Vikrant Class carriers under construction. INS Dega will eventually be used that way, but the carriers aren’t going to arrive before 2019. Until then, INS Vikramaditya will have squadrons available on 2 coasts. A parallel ‘Project Varsha’ program would add a major new naval base near Rambilli, 50 km south-west of Visakhapatnam, which will be able to house aircraft carriers and nuclear submarines. Indian history strongly suggests that Project Varsha won’t be ready in time to welcome INS Vikrant. Sources: India Today, “EXCLUSIVE: Navy initiates ‘Look East’ for lethal MiG29K” | Economic Times, “Navy to deploy MiG 29Ks in Vishakhapatnam; move aimed to strengthen eastern coast” | Business Standard, “New naval base coming up near Visakhapatnam”.
June 16/14: Dhruv ASW? India is reportedly looking to outfit their locally-designed HAL Dhruv helicopter with some anti-submarine equipment from the state’s DRDO research agency:
“The Hindustan Aeronautics Limited-built ALH Dhruv is undergoing trials for carrying out role of detecting hostile submarines using systems developed by the DRDO, Defence officials said…. The system was put under trial at Vishakhapatnam and would be tried further before any final decision is taken on deploying the twin-engine chopper on board the carrier, they said.”
The Dhruv is in the same size and weight class as AgustaWestland’s Lynx, but the final result of this program is likely to fall rather short of capabilities possessed by the AW159 Wildcat, or of larger machines like the NH90 NFH or MH-60R Seahawk. On the one hand, adapting an existing HAL platform circumvents India’s broken foreign procurement system, creating a second-rate but deployable near-term solution for their astonishing weakness in this area (q.v. March 31/14). It also creates a platform that can be improved over time, which is good for India and its industry.
On the other hand, providing sub-standard protection to the flagship of one’s naval force is a terrible idea if it’s the only proposed solution. The question is whether the long-discussed foreign tender (q.v. Feb 25/14) for helicopters like the NH90 will also go forward, in order to equip platforms like India’s high-end destroyers (q.v. Oct 15/13) and add a higher tier of shipborne ASW protection for key assets. Sources: IBD Live, “Dhruv chopper likely to be deployed on-board INS Vikramaditya”.
June 4/14: “Slammer”. Welcome to the world of assisted carrier landings. A 2-seat MiG-29KUB pilot just found out the hard way, after flying in from INS Hansa’s shore base. He was going to miss R33’s first 2 arrester wires, but as he throttled up for a bolter takeoff, his jet caught the 3rd wire with the arrester hook. The MiG’s nose reportedly pointed skyward before slamming back to the deck.
Everyone is fine, but the nose wheel is going to need repair or replacement, and the pilot may wind up with a new nickname. We recommend “Slammer,” in the long and proud tradition of handles that sounds cool but refer to something embarrassing.
There will be more incidents like this, as Indian aviators become more familiar with this new landing mode. Sea Harriers will absolutely kill you for a misstep during vertical landings, so it isn’t like this is some new frontier of required professionalism. It’s just that a full-speed trap is a very different animal, with its own skills and dangers. Sources: Calcutta Telegraph, “Safety scare on Gorshkov”.
May 16/14: ASW weakness. Ajai Shulka says the reason that operational safety was the reason that Vikramaditya was joined by an armada of Indian warships for the last leg of its journey to Karwar. The problem is the lack of an effective towed sonar on Indian surface combatants, due to obstruction by the defense bureaucracy. Coming as it does on top of the MoD derelict performance with respect to anti-submarine helicopters, it creates a huge naval weakness that would doom India’s carriers in a shooting war. Read “Anti-Submarine Weakness: India Has a Problem” for full coverage.
ASW weakness
May 7/14: Navy chief Admiral Robin Dhowan says that:
“The navy has inducted aircraft carrier INS Vikramaditya which is now operationally deployed with MiG 29K aircraft embarked and being flown by Indian naval pilots…”
Looks like India has made real progress since the 1st all-Indian flight (q.v. Feb 7/14), and reports also indicate that the carrier has taken part in a recent war game with India’s Western Navy. INS Vikramaditya will remain India’s core carrier option for some time, as Vikrant isn’t expected to be ready until the end of 2018. Sources: India’s Business Standard, “INS Vikramaditya is operationally deployed with MiG- 29K aircraft: Navy Chief”.
Accepted into fleet
March 31/14: ASW weakness. Not only will India’s carrier sail without onboard air defenses, it and its escorts can’t field an effective set of anti-submarine helicopters.
“The Navy is today being asked to make do with four Ka28 helicopters that have the technology of mid-80s for training pilots, doing ASW roles against modern submarines for the five Rajput Class destroyers as well as the aircraft carrier Vikramaditya,” said a source.”
The other 6 Ka-28s have been mothballed for spares, while a mid-life upgrade that would restore the 10 to flying condition and give them modern sensors has been trying to get underway since 2008. Bids were finally opened in 2012, and a combination of Russia’s Kamov and Italy’s Finmeccanica won the INR 20 billion project. Contracts are set, and both the Cabinet Committee of Security and India’s CBI investigators cleared the deal. Defence Minister Antony’s office has been sitting on that for over a month, however, while playing extreme hardball with AgustaWestland over the VVIP helicopter deal.
Meanwhile, the Sea King fleet has problems of its own, and a proposal to buy up to 16 modern naval helicopters from foreign sources remains stalled (q.v. Feb 25/14, Oct 15/13, Aug 17/12). Sources: Daily Mail India, “Navy left ‘defenceless’ after being forced to ‘make do’ with outdated Soviet hardware”.
ASW weakness
March 13/14: Support. India has decided to stick with Sevmash shipyard in Russia’s northern Arkhangelsk region for long-term post-warranty servicing of INS Vikramaditya. The relevant protocol was signed in Goa on Wednesday, March 12, at the 23rd Indo-Russian Inter Governmental Commission on Military Technical Cooperation’s (IRIGC-MTC) naval subgroup meeting. The full 20-year contract is expected in May 2014.
Sevmash engineers and specialists are already providing warranty maintenance services for the 1st year of operation, and there was no question that India would have to extend the relationship. Even an aggressive indigenization program would take a few years to gear up and provide adequate service. Still, 20 years is a puzzle. Given India’s past problems with Sevmash specifically, and with Russian maintenance and support generally, their flagship aircraft carrier appears to be an odd exception to the government’s recent indigenization push. Sources: India & Russia Report, “Sevmash chosen for INS Vikramaditya post-warranty servicing”.
Nyet, SpassibaMarch 12/14: Weapons. India reportedly rejected Russian offers to mount their Kashtan gun/missile close-in air defense system on INS Vikramaditya, which were reportedly made during a recent meeting of the India-Russia Inter-Governmental Commission on Military Technical Cooperation. It’s not a final rejection, but their experience with Russian maintenance is reportedly pushing them to hold an open competition. That could be a fine opportunity for a range of systems. KBP’s Kashtan would be eligible to bid, but so would bolt-on, independently-operated options like Raytheon’s SeaRAM missiles or Phalanx 20mm gun, or systems like MBDA’s Mistral-based Simbad/Tetral.
INS Vikramaditya is eventually supposed to use the medium range LR-SAM/ Barak-8 as its main air defense weapon. A close-in defensive option will be needed until India tests and fields it, and it will remain a good idea even after LR-SAM has been installed. Sources: Defense Radar, “Indian Navy To Open Search for Carrier Air Defense System.”
Feb 25/14: Helicopters. India’s Ministry of Defence clears a whole series of defense projects: upgrades for 37 airbases, modernization of 5 ordnance depots, 4,000 hand-held thermal imagers for soldiers, 5,000 thermal imaging sights for tanks and infantry combat vehicles, 44,000 light-machine guns, 702 light armoured multi-purpose vehicles, and 250 RAFAEL Spice IIR/GPS guided smart bombs. The deal’s not done?
A program to buy M777 howitzers, 56 transport aircraft to replace the ageing Avro fleet, produce 4 amphibious LPDs – and 16 naval multi-role helicopters to restore an effective anti-submarine capability. With elections looming, it will take some time before any of them are restarted. Sources: Times of India, “Decision on four key defence deals put off”.
Feb 7/14: Indian landing. A MIG-29KUB fighter lands on Vikramaditya. That has happened before, but it’s the 1st time with an Indian naval officer at the controls. Indian naval aviation has relied on Sea Harrier vertical-landing jets for decades, which makes this arrested landing a milestone for the Navy as a whole, as well as for the ship.
While the 303 Sqn. Black Panthers were commissioned in 2013, the ship will take another 3-4 months before they’re fully ready. It might even take longer, but reports of troubles on the ship’s journeys are probably exaggerated. The complaints amount to postponing refueling with INS Deepak in rough seas off of Portugal, and a reported boiler breakdown. The first complaint is trivial, but the boiler issue could be a problem, given past issues with that machinery. Even India’s Navy won’t know how big an issue this is, until debriefings are done and the report is in.
As the local beachgoers already know (q.v. Jan 14/14), a team of Russian specialists have arrived on board, and will stay in India for a year as technical backup. Itar-Tass, “First Indian-piloted MiG safely lands on Vikramaditya aircraft carrier” | RIA Novosti, “First Indian MiG-29 Fighter Jet Lands on Vikramaditya” | Hindustan Times, “Choppy first ride home for INS Vikramaditya”.
Black Panthers MiG-29KUB lands
Jan 21/14: The UK’s Daily Mail reports that Karwar’s new shore-based test facility (SBTF) replica of Vikramaditya’s flight deck on the ground has now become fully operational, adding that Indian pilots will begin flying operations from the ship very soon. Landings will take place at the SBTF, before working up to full ship-based operations. Sources: “Navy gets ready to start Vikramaditya flying ops”
Jan 14/14: Culture shock. Some Russian support personnel who are in town to help keep INS Vikramaditya ship-shape end up having a close encounter with the local police, after they leave the ship to have a few drinks and spend time on the beach. Public nakedness and carriage of alcohol doesn’t go over very well in Karwar, apparently, though a local resident suggests that Goa might be more into that sort of thing. Good to know. Indian Express, “Vikramaditya Brings Russian Culture to Karwar, Irks Locals”.
Jan 5/14: Arrival. INS Vikramaditya arrives in the Indian Navy’s Area of Operation in the Arabian Sea, marking the 1st time in over 20 years that India has 2 carriers at sea. The ship quickly gains an escort flotilla that includes the existing carrier INS Viraat, 2 Delhi Class destroyers, 3 Trishul Class frigates, a Godavari Class frigate, and “a couple of offshore [patrol] vessels.”
The carrier pulls into Karwar by Jan 8/14. Sources: Economic Times photo page, “INS Vikramaditya arrives: Navy operates two aircraft carriers after 20 years” NDTV, “INS Vikramaditya, India’s biggest warship, finally arrives” | Defense Update, “India’s Largest Carrier INS Vikramaditya Arrives at Karwar Home Port”.
20131st MiG-29K squadron commissioned; INS vikramaditya handed over and begins her long sail home.
MiG-29KUB on carrierNov 27/13: Sailing home. INS Vikramaditya sets sail for India under the command of Captain Suraj Berry, without any operational aircraft on board. After bunkering and completing customs papers, India’s new carrier will head for the Russian port of Murmansk 215 km away, to join the frigate INS Trikhand and fleet tanker INS Deepak. The flotilla is expected to reach India by the end of January 2014, where it will homeport at the new Karwar base. Even then, the Indian Navy admitted that the ship would take at least 2 years to be ready for full-scale operational deployment – without weapons.
India is still finalizing the proposed weapon fit-out. The Navy would like to field the Barak-8/ MR-SAM missile for medium-long range defense, along with a close-in weapon system or 2. Russia’s Kashtan, which equips Russia’s own Admiral Kuznetsov, would be a high-end gun/missile CIWS option. The AK-630/ A-213-Vympel-A would offer a lower-end, gun-only option. Those weapons will need to integrate with the Russian combat system, and the priority placed on fighter pilot qualification means that weapon installation won’t take place until the carrier’s initial refit. Which is to say, around 2017 at the earliest.
A team of Sevmash specialists remain on board the ship to help with the voyage, and the shipyard hopes to sign a 20-40 year support contract with India after the initial 1-year guarantee period is done. Sources: The Hindu, “INS Vikramaditya sets sail for India” | RIA Novosti, “Refitted Aircraft Carrier Sails Out From Russia to India”.
Nov 16/13: Handover. INS Vikramaditya is handed over to the Indian Navy at Sevmash shipyard, in Russia. That was supposed to happen in 2008. Sources: Indian Navy, “Navy’s largest ship ‘INS Vikramaditya’ Commissioned” | RIA Novosti, “Russia Passes Refitted Aircraft Carrier to India After 5-Year Delay”.
Ship transferred and sets sail for Karwar
Nov 7/13: MiG-29K. India will soon move its 2nd MiG-29K squadron to Naval Air Station INS Dega, on the eastern seaboard in Vishakhapatnam. The Indian Navy’s Hawk Mk.132 advanced jet trainers are already based there, and so is the Maritime Naval Academy. India’s semi-indigenous Vikrant Class carrier will homeport in Vishakhapatnam once it’s complete, but that isn’t expected until at least 2017. Source: Times of India, “MiG 29K squadron base at Vizag soon, says Navy chief Joshi”.
Oct 15/13: Helicopters. India’s anti-submarine issues continue to surface, which is a serious weakness for a fleet air arm and for a carrier. How serious is it?
“The Navy has given an insight into how it is placed during its ongoing exercise with the Royal Navy off the Goa coast. The Royal Navy’s HMS Westminster – a type-23 frigate known for its advanced anti-submarine capability – is taking part in the exercise Konkan. The frigate is equipped with Merlin helicopters – the maritime version of triple-engine AgustaWestland EH-101 that is used extensively by the Royal Navy… The Indian Navy has pitched a Delhi class destroyer, which is a formidable platform, but it carries only one helicopter although it is capable of operating two. The only helicopter on the destroyer is Chetak, which has a limited role in search, rescue and communication. It cannot carry out advanced anti-submarine or anti-surface operation.”
That isn’t what you want defending your carrier. Sources: Daily Mail India, “Chopper shortage rattles Indian Navy during joint exercise with British fleet”.
Oct 14/13: Delays. After the September 2012 blowout (q.v. Sept 17/12), the program expected a handover delay until October 2013. Russian media report that Vikramaditya’s handover to India will take place on Nov 15/13, and the ship will sail out of Russian waters by Nov 30/13.
Russian Deputy Prime Minister Dmitry Rogozin says that: “The problems revealed during sea trials last year have been fixed.” Assuming that he’s correct, and that no new problems surface, the ship is now expected to arrive in Mumbai sometime in February 2014.
Aug 1/13: INS Viraat. Livefist reports that India has decided to keep the 1950s-era INS Viraat in service until 2018. Viraat isn’t really equipped for MiG-29Ks, and there’s some question whether its Sea Harrier contingent will last that long.
May 11/13: MiG-29K. India formally commissions the MiG-29K into the Indian Navy, beginning with the 303 Black Panthers Squadron at INS Hansa, near Goa. The squadron has 16 fighters and full on site training infrastructure now, as opposed to the 4 planes on hand when the MiG-29K was inducted for trials in February 2010.
The announcement comes 1 day after the Chinese formally announced the beginning of their own carrier aviation capability, on May 10. The Chinese fly larger and longer-range J-15 fighters, which are based on Sukhoi’s SU-33 design. The Diplomat | Business Standard | Economic Times | Hindustan Times | Times of India.
MiG-29K inducted
2012Sea trials – and boiler blowout; Delivery delayed another year; 1st MiG-29K operations from the carrier deck; Russia adds itself to the MiG-29K customer list.
Sea trials beginDec 24/12: The 2012 Russian-Indian summit in New Delhi features a number of military and civilian deals, but problems with the Vikramaditya also force their way onto the agenda. The statement itself doesn’t mean much; the meaning is contained in the fact that this statement was included at all. Over $4 billion in defense purchases weren’t specifically mentioned in paragraph 21 of their joint statement, which did find time to say that:
“Both sides discussed measures required to ensure expeditious delivery of the aircraft carrier «Vikramaditya» to India. The Russian side assured that requisite measures would be taken in this regard.”
Nov 3/12: INS Viraat. India’s lone aircraft carrier arrives for a refit at the Cochin Shipyard (CSL). The work is expected to last at least 3 months, and by March 2013, the projection for its return to service is July 2013 (9 months) – or later. India won’t have an operational carrier while the refit takes place, and at the end, they’re left with the carrier and just 11 Sea Harrier fighters. The Hindu | Economic Times | NDTV | Rediff | CDR Salamander.
Oct 10/12: Penalties? Russian Defence Minister Anatoly Serdyukov confirms a 1-year delivery delay, as he arrives in New Delhi for high level talks.
Under the contract, India can impose a penalty of up to 5%, and Ministry of Defence officials have been quoted using a figure of Rs 600 crore (currently about $113.8 million). Russia’s argument is that India didn’t impose a penalty on DCNS for the 3-year delay in delivering Scorpene submarines, but India has acknowledged that its own industry was largely at fault in that case. Unless Russia successfully pushes India into citing required ship design changes as a similar “fault,” the 2 situations are distinct. India Today | Zee News.
Sept 17/12: Blowout. The Vikramadiya has to take 7 of its 8 boilers offline when it tries to go to maximum speed of 30 knots in trials. This is an important ability for a carrier, which needs to generate airflow under its aircraft wings during launch. What the heck happened? Well, India didn’t want to use asbestos as heat protection for the boilers. It’s a definite safety hazard to crews. Instead, the boilers’ designer had to use firebrick ceramics. Which, as we see, didn’t work so well. Especially on a ship that Russia put up for sale in 1994, after a boiler room explosion.
They’ll have to cut the ship open to replace the boilers, which can’t happen until spring. Specialists from the Baltisky Shipyard and boiler design bureau are already at Sevmash shipyard, and the worst case would be damage to the pipes carrying steam from the boilers. The pipes are made from a special steel which is no longer made in Russia, and would need to be bought from the Ukraine. Meanwhile, reports are conflicting. Some say that Vikramaditya can still operate at reduced power, which could allow MiG-29K and systems testing when the weather cooperates, until the ship has to go in for repairs.
The operation is expected to cost Sevmash at least $30 million, and it will be interesting to see if they try to pass the cost on to India, on the grounds that Indian specifications caused the problem. That’s true, but asbestos isn’t a reasonable option, and another re-negotiation attempt isn’t likely to improve relations. The new date for a handover is October 2013, a 10-11 month delay. Business Standard | The Hindu | Livemint | Russia’s RIA Novosti.
Boiler blowout
Aug 17/12: Helicopters. India’s Mk.42B Sea King utility/ASW helicopters have readiness issues, which is a problem because India has a shortage of working anti-submarine helicopters. Upgrades have been delayed, and India is considering packages from AgustaWestland and an Israeli consortium. Upgrades to the 20 or so helicopters would include new avionics, electronic warfare suites, new communication kits, and an all-new weapons suite with anti-ship and anti-submarine ordnance. Sources: SP’s Naval Forces, “Indian Navy Sea Kings upgrade process soon”.
July 28/12: MiG-29K. The first carrier landings and takeoff take place on Vikramaditya, in a MiG-29KUB piloted by RAC MiG test pilots Mikhail Belyaev and Nikolai Diorditsa. RAC MiG.
1st Landing & Takeoff
July 16/12: ADS Watch. Vikramaditya and its air complement had better work well, and mesh swiftly, because there is no backup option. India’s Economic times reports that the 40,000 tonne Vikrant Class (aka. Indigenous Aircraft Carrier or Air Defense Ship project), being built at Cochin Shipyard has “slipped another three years.” The keel was laid in 2009, and it was prematurely floated out of drydock in December 2011, due to delays involving gearboxes and other systems. An anonymous MoD source is quoted as saying that:
“The fact is IAC will not be ready anytime before 2017. In a recent high-level meeting, the Cochin Shipyard was sharply pulled up for this huge delay… IAC is just about 14,000 tonnes at present [instead of the 25,000 tonnes it was supposed to be at launch].”
The original 2002-2003 period contract is already over its Rs 3,261 crore budget, and the follow-on contract to take it from “launch to completion” hasn’t been signed yet. The question isn’t whether the Navy will have 2 carrier strike groups by 2015, as planned; now it’s whether they’ll have that by 2020. Innovative thinking might be able to turn the existing INS Viraat into a useful helicopter and UAV carrier by 2015, if India moved swiftly – but that has never been the MoD’s forte. India’s Economic Times.
July 23/12: MiG-29K. A 2-seat MiG-29KUB naval fighter flown by Russian test pilots jet makes the 1st touch-and-go landings on Vikramaditya, during sea trials in the frigid Barents Sea. A touch-and-go isn’t really a landing, since the jet doesn’t stop. It comes in on approach, touches down on the flight deck, then revs the engines to full power and flies off the front. RIA Novosti.
June 8/12: Sea trials. Vikramaditya leaves the Sevmash shipyard, and heads out for naval trials in the White Sea. Defense News.
Sea trials
May 24/12: The Sevmash shipyard says they’ll have to postpone the Vikramaditya’s naval trials in the White Sea and Barents Sea. The date is now early June – or later, if the weather continues to be bad. That far north, poor conditions means more than just rain and waves. Times of India.
May 14/12: Project update. Minister of Defence Shri A.K. Antony’s written reply to Shri Purnmasi Ram in Lok Sabha, adds nothing new about India’s upgraded Sea Harriers, but says that India has now inducted 15 MiG-29Ks, and plans to induct INS Vikramaditya in December 2012.
Feb 29/12: MiG-29K. India won’t be the type’s only customer, now that Russia has ordered 24 planes for its own naval aviation squadrons.
2011MiG-29K deliveries continue; Eurofighter MMRCA contender offers naval STOBAR option; Sea trials delayed.
Navalized Typhoon conceptOct 16/11: Indian media report that Vikramaditya’s sea trials will be delayed 5-6 months, to February or March 2012, because open sea trials aren’t possible from Severodvinsk in northern Russia during the winters. Instead, the ship will do everything they can in the harbor, then hold sea trials when the ice is out.
PTI was told by “senior Defence Ministry sources” said the change in trial plans will not affect the delivery schedule of the aircraft carrier – but then, they have been wrong and even misleading before. The more puzzling question is why it took until October 2011 to realize that conducting sea trials in northern Russia, in November, is unworkable. PTI | Voice of Russia.
Aug 3/11: MiG-29K. RAC MiG CEO Sergei Korotkov places the number of MiG-29Ks delivered to date at 11, with the initial order’s other 5 slated to arrive by the end of 2011. Work of the 2nd MiG-29K order of 29 planes is just beginning. AFP | domain-b | Hindustan Times | Voice of Russia.
Aug 2/11: The Indian MoD offers an official update of progress on the Vikramaditya – and its smaller cousins:
“Consequent to signing of Supplementary Agreements in March, 2010, the Russian side has increased the manpower and material resources considerably for the Project. A majority of the equipment/systems have been installed on board the ship. The delivery of ship is scheduled in December, 2012.
Regarding the ‘Air Defence Ship’ [DID: 35,000t carrier] being constructed at Cochin Shipyard Limited (CSL), 75% of hull work has been completed and is expected to be launched in December 2011, after which further works will be undertaken prior to commissioning… indigenous Aircraft Carrier-sized ships can [now] be built at CSL. Additionally, Indian-manufactures warship quality steel is now available, which will reduce dependence on foreign countries.”
June 23/11: MiG-29K. A prototype MiG-29KUB trainer crashes in Russia. The plane was a test aircraft belonging to RAC MiG, and the company advised the Indian Navy to temporarily suspend MiG-29K operations until the crash’s causes were known.
India asked for a detailed report, and according to the MoD, the crash wasn’t because of a structural failure in the air, engine failure, or avionics/ systems failure. By June 28/11, RAC MiG advised that MiG-29K flights could resume if India wished. India MoD.
MiG-29K crash
May 30/11: MiG-29K. RAC MiG announces that they delivered a new batch of 5 MiG-29K/KUB carrier-based fighters to the Indian Navy in May, along with a flight training simulator and other technical equipment. That’s on top of the first 4 aircraft, \r
The March 2010 contract for 29 more MiG-29K Fulcrum-Ds won’t begin delivery until 2012. Economic Times of India.
April 4/11: The Admiral Gorshkov is expected is to reach Murmansk in November 2011, as it heads to Murmansk ship-repair yard # 35 from Sevmash. The carrier is expected to undergo further upgrades and performance testing. Barents Nova.
Feb 21/11: Naval Eurofighter? Aero India 2011 sees Eurofighter and BAE unveil an interesting wrinkle: an initial design for a navalized Eurofighter than can operate from aircraft carriers, based on an internally-funded set of studies and simulations. In a direct nod to potential Indian sales, they tout the plane as being able to take off from “ski jump” carriers without catapults – a design that describes all of India’s current and planned carriers, but not the French carriers that launch the Rafale fighter.
Eurofighter GmbH describes the goal as 95% commonality with land-based aircraft, and required changes as “limited… include a new, stronger landing gear, a modified arrestor hook and localised strengthening on some fuselage sections near the landing gear, as well as updates the EJ200 engines,” which could include thrust-vectoring in flight.
The Eurofighter and Rafale are later picked as India’s 2 finalists for its M-MRCA fighter competition. Eurofighter GmbH | India Defence.
2010Carrier agreement raises refit costs to $2.33 billion; India inducts MiG-29K, orders 29 more; Russian affair by program chief.
MiG-29K flight testAug 9/10: Scandal. Indian Commodore Sukhjinder Singh, who was a key person in the Gorshkov refit program from 2005-2009, has reportedly handed in his resignation after reports of his illicit affair with a Russian woman (vid. April 12/10 entry). The inquiry by Indian naval HQ established the relationship with the woman, but ruled out court martial as they couldn’t establish the woman’s status as an agent, or anything untoward beyond a romantic relationship.
The findings of the Board of Inquiry will have to be acted upon by chief of naval staff Admiral Nirmal Verma, who must also decide whether and how to accept the Commodore’s resignation. On the bright side, at least he didn’t hire Jodie Fisher. See: DNA India.
Aug 3/10: MiG-29K. A CAG (Indian comptroller and auditor general) report says that Indian naval aviation has suffered in recent years, and the current state of the Sea Harrier fleet makes it clear that on-time induction of MiG-29Ks into the fleet will be critical. Read “India’s Sea Harrier Shortage” for more.
April 12/10: Scandal. The inquiry against Commodore Sukhjinder Singh has established his ‘amorous relationship’ with a Russian woman, and India’s naval brass are considering punishments. Meanwhile, he has been relieved of his current posting in the defence ministry’s directorate-general of quality assurance.
Singh oversaw the Gorshkov refit project in Russia from 2005-2007, and was the project’s principal director in India from 2007-2009. That gave him no role in price negotiations, but there is more than casual concern that he may have been “honey trapped” by an FSB agent to give details of India’s negotiating position. Explicit photographs with this Russian woman surfaced recently in the media, and formed part of the “clinching evidence” in the just-concluded naval Board of Inquiry (BoI). Defence minister A K Antony said that:
“Nothing beyond [a romantic relationship] has been proved so far. I do not want to jump the gun. I have asked Navy to finish (the inquiry report) as quickly as possible. I do not want to draw any conclusions prematurely. Once the Navy completes everything, we will take a decision.”
See: Current Affairs (incl. Times Now video) | DNA India | India Server | India TV | Kalyugikalki | The Times of India | Hindustan Times.
Honey trap?
March 11-13/10: India’s Cabinet Committee on Security approves a new $2.33 billion price for the Gorshkov refit, a rise of over 140%.
Russian President Vladimir Putin is currently visiting India, and is expected to sign a number of defense contracts, including the revised Gorshkov pact, and a $1.2 billion contract for another 29 MiG-29Ks. The Gorshkov agreement is signed on March 13/10, and the carrier’s delivery date is now 2013. Indian Express | Russia’s RIA Novosti | Sify | Zee News || Putin visit: Calcutta Telegraph | DNA | Economic Times of India | Sify || Post-Signing: Indian government PIB release | DNA India | Times of India.
Revised agreement, 29 more MiG-29Ks
Feb 19/10: MiG-29K. India inducts its first 4 MiG-29Ks into service at INS Hansa in Goa, as an Intensive Flying and Trials Unit. The government also apologizes to Goa’s citizen’s for the unannounced sonic booms they’ve experienced over the past few days.
During the ceremony, Defence Minister Antony confirms India’s intent to buy another 29 fighters, raising the Navy’s MiG-29K fleet to 45. ANI | Economic Times of India | Indian Express | Sify | Times of India | NDTV video – note that aerial footage is of India’s Kiran trainers instead.
MiG-29K inducted
Feb 15/10: Russian deputy service director Alexander Fomin is quoted as saying that Russia and India will sign a supplementary agreement to finish upgrading the Admiral Gorshkov “in February-March this year.” Time will tell. RIA Novosti.
Jan 17/10: Reports surface that India will “soon” finalize a $1.2 billion deal with Russia to buy 29 more MiG-29K jets, which would bring India’s order total for the carrier capable STOBAR (Short Take-Off But Assisted Recovery) fighters to 45. Russia’s RIA Novosti | domain-b | India’s Economic Times | Press Trust of India | Times of India | UPI | Associated Press of Pakistan.
Jan 16/10: Admiral Nirmal Verma tells the media that there is still no final deal:
“I cannot speak anything about the final pricing till the government’s approval is announced. But, yes, for any of these major induction programs, we have a price negotiation committee, which has done its job and a mutually agreed price has been arrived at.”
See: Press Trust of India | Times of India | Barents Observer | China’s Xinhua.
2009Scathing CAG program report; India adds a bridging payment, but still no deal; MiG-29 training & infrastructure; British CVF carrier as a Plan B?; INS Viraat is unavailable, and India’s ADS carriers won’t arrive until 2015.
MiG-29KUB: early flightDec 5/09: Reports surface once again that India and Russia have reached an agreement on the Vikramaditya’s price. This time, they may even be true. Indian Foreign Secretary Nirupama Rao said that during summit-level talks between Indian Prime Minister Manmohan Singh and Russian President Dmitry Medvedev:
“Both the leaders discussed the [Vikramaditya] issue and noted excellent progress on negotiations on price and technical issues which have been brought to a successful conclusion.”
The actual price in question is not discussed, and that political rapprochement may not be shared by the Navy. Defence Minister AK Antony has publicly distanced the Government from Naval Chief Admiral Sureesh Mehta’s recent public hard line regarding the Gorshkov’s price, and suggestions that India reassess its defense ties with Russia owing to quality issues. Adm. Arum Prakash also issued a warning, saying that: “The long-term price that we pay for 25 years of mischief, of twisting our arm will be much more than what we pay now.”
See: domain-b | Economic Times | Hindustan Times | IANS re: Rao quote | IANS re: Adm. Verma || Naval Spat: IBN Live | IBN Live quotes Adm. Mehta & Prakash.
Dec 4/09: MiG-29K. Ending a year-long wait, the first batch of MiG-29K naval fighter jets, purchased from Russia for the Admiral Gorshkov aircraft carrier, arrive in Goa in a “knocked down condition” packed in containers on board an AN-124 cargo aircraft. Press Trust of India.
Nov 30/09: Defence Minister Shri AK Antony, in a written reply to the Lok Sabha (India’s Parliament):
“The Russian side had submitted a revised Master Schedule indicating delay and increase in prices for repair and re-equipping of aircraft carrier ex-Admiral Gorshkov. The Government has agreed to conduct negotiations for finalizing a revised Repair and Re-equipping contract. Negotiations are in progress with the Russian side. Details of final prices would be known only after completion of these negotiations.
An exhaustive list of equipment to be fitted on the ship was included in the original contract. The Aircraft Carrier is scheduled to be inducted in December, 2012.”
Nov 16/09: Plan B from the UK? Amidst rumors of major British defense budget cuts, The Guardian reports that India has expressed formal interest in the 65,000t CVF/Queen Elizabeth class carrier program. The UK MoD is desperately looking for long-term budget savings, but canceling either of its full-size carriers at this point would be rival the cost of finishing them:
“According to senior defence sources, Whitehall officials are examining the feasibility of selling one of the carriers. It is understood they are planning to put forward the option as part of the government’s strategic defence review, which will start early next year… “Selling a carrier is one very serious option,” a defence source said this weekend, although the government is a long way from committing to any sale. It could take between six and 12 months to reach a decision, he added.”
Each Queen Elizabeth carrier costs about $3.5 billion, and the negotiating difference around the Admiral Gorshkov is currently around $2.2+ billion. The question is whether India would be able to buy one of the CVF carriers for less than the UK paid, in order to offer the Treasury monies that it could not otherwise obtain from the CVF program. If a refund could be forthcoming from the Russians, and a deal done with the British, investing the Vikramaditya’s $3 billion could net India a completely new ship rather than an old and refurbished one, with double the Gorshkov’s aerial complement. Key questions include whether those deals could be secured, and whether India is prepared to wait until 2016 for the British carrier, as opposed to 2013 (and sliding…) for Gorshkov.
Then again, $2.2 – $2.5 billion could also secure India an America class light carrier from Northrop Grumman, with a similar tonnage and aerial complement to the Gorshkov, but markedly better electronics and defensive systems. If India begins to look beyond Russia for options, Britain’s CVF program is not its sole alternative.
Nov 1/09: INS Viraat Watch. The Times of India reports that INS Viraat is now on the verge of completing its sea-acceptance trials and work-up phase, after an 18-month-long comprehensive refit and upgrade program in Mumbai and Kochi. This will give India an aircraft carrier again. The 28,000-tonne carrier will complete its 50th year as an operational warship in November 2009, having serves as both HMS Hermes and INS Viraat.
Oct 23/09: A British BBC report explains some of the hurdles on the road to Vikramaditya’s delivery:
“In this hurry [on both sides to sign a deal], fine points including the ones relating to what was expected of Russia were overlooked… India agreed to buy and get a ship refurbished without Gorshkov’s design [presumably means a detail design blueprint]… When the ship was ripped open, it was found that the wiring was ageing and needed to be redone. A Japanese contractor awarded the rewiring contract found the job overwhelming – given the costs involved – and left. Now a new contractor has been found for the purpose. Gorshkov’s steel plates and machinery, too, needed to be pulled apart and new ones fitted… With Gorshkov’s induction delayed, the government decided to refit its only aircraft carrier, INS Viraat, but it will not be operational till 2015. That leaves the Indian navy with no aircraft carrier for some time.”
Oct 15/09: Despite prior reports that an agreement on the Vikramaditya’s final cost would be reached during Defence Minister A.K. Antony’s 2-day visit to Moscow, India and Russia have failed to reach agreement. Negotiations will continue. India MoD | Indo-Asian News Service.
Sept 24/09: MiG-29K. Russia’s Vedemosti newspaper reports that the Russian Navy may decide to replace its 19 larger and longer-range SU-33 fighters on its Admiral Kuznetsov carrier with 24 MiG-29Ks, when the SU-33’s must be retired in 2015. Caution is advised, since the article is based on a source who sees a contract as possible in 2 years; that’s not exactly a rock-solid basis for concluding that India will avoid the potential trap of being the MiG-29K’s only operator. Vedemosti [in Russian] | Barents Observer.
Sept 3/09: Indian media report that a deal to finish the Vikramaditya refit is expected by mid-October 2009. Some caution is advised, as past reports and predictions in this area have later been proven false by events. India’s Business Standard | The Hindu | Hindustan Times.
Aug 16/09: Bridging payment. Indian media report that the government has cleared a $122 million bridging payment for continued modification work on the Gorshkov, while negotiations continue. The payment was sanctioned in early August, following demands by Rosoboronexport. domain-b | Economic Times of India.
Bridging payment
July 31/09: India’s Business Standard conducts an interview with Russia’s outgoing ambassador to India, Vyacheslav Trubnikov. Excerpts:
“[VT] Not changing [the Gorshkov order], but the Indian Navy was eager to get the best, the most modern equipment [to insert into the hull].
[IBS] So the Navy’s appetite kept increasing, they wanted more and more..
[VT] Yes.
[BS] Reports are that it will cost around $2.2 billion?
[VT] It would be irresponsible of me to comment. Price negotiations are now entering the final stage. What is important for India is also the time of delivery. But the point is that if India wants additional equipment, the carrier will cost even more. So if both sides stop and decide, okay no request from India and no increase in price from our side, then we can finalise price and delivery.”
July 29/09: The CAG report begins to generate political opposition to the Gorshkov deal, as well as media op/ed calls for a re-think. In the course of one such op-ed, The Hindustan Times offers a report on the negotiating spread:
“The Russians now want $2.9 billion (Rs 14,500 crore) for the warship, while the defence ministry is bargaining for $2.2 billion (Rs 11,000 crore). [Defence Minister Antony said that] “The Russians have demanded a substantially huge amount. We are still negotiating the deal. No final decision has been taken.”
July 25/09: CAG Criticism. India’s Comptroller and Auditor General (CAG) issues a scathing report, saying that:
“The objective of inducting an aircraft carrier in time to fill the gap in the Indian Navy has not been achieved. The cost of acquisition has more than doubled [from $875 million] to $1.82 billion (Rs. 7,207 crore) in four years. At best, the Indian Navy would be acquiring, belatedly, a second-hand ship with a limited life span, by paying significantly more than what it would have paid for a new ship…”
The largest cost escalation is in sea trials, which have risen from $27 million to $500 million, and the CAG report sharply criticizes the Navy for poor project supervision practices. The report adds that planning failures will leave the warship with no air defense upon delivery, and only a Close-In Weapon System (CIWS) when one is retrofitted in 2017. Risks are also cited with respect to the aircraft arresting gear, which has not been finalized due to development problems. India CAG – they do not archive reports | DNA India | The Hindu | Indian Express | Rediff | Times of India | Agence France Presse.
CAG criticism
May 25/09: Indian media report that the government has decided to speed up renegotiation with Russia, after a recent Moscow trip undertaken by defence secretary Vijay Singh failed to break the long-standing deadlock. The government has reportedly scheduled 3 visits to Russia by Indian officials, in hopes of sealing the deal by the end of July 2009. During those visits, they will also discuss the larger subject of Indian-Russian defense relations.
Another senior official of the Controller of Warship Production and Acquisition will reportedly visit Russia in the middle of June 2009, to work out the warship’s hoped-for 2011 trials in Barents Sea. Assuming that a deal can in fact be reached this time. Times of India.
April 6/09: MiG-29K. India inaugurates the first phase of the MiG-29K maintenance and training facility at the INS Hansa naval base in Goa. Vice-Admiral J. J. Bedi, Commander-in-Chief of India’s Western Naval command, is quoted as saying that:
“This is the first time in my service career of 40 years that I witness construction and availability of major infrastructure project prior to the induction of hardware in the Indian Navy.”
He expects the first batch of 4 aircraft to be “with us by middle of this year.” The Hindu.
March 16/09: MiG-29K. Still no agreement on the Gorshkov refit. Meanwhile, The Times of India reports a Russian decision to ground its MiG-29 fleet, following accidents caused by the disintegration of the planes’ tail fins. It quoted an unidentified “senior officer,” who said that:
“We continue to fly our MiG-29s… Our checks are stringent since we operate our MiG-29s also from coastal airbases (Jamnagar) and Russian metallurgy is susceptible to salinity.”
That’s a somewhat worrying assertion, in light of the MiG-29K naval buy. India is scheduled to finish its MiG-29A upgrades to MiG-29SMT status in 2014, thanks to a contract signed in March 2008. That effort will not be delayed by the news from Russia, but the news will reportedly delay delivery of the new MiG-29Ks to the Indian Navy.
Feb 28/09: ADS Watch. The keel for India’s first “Project-71” 37.5t-40t indigenous carrier project is laid at the Cochin Shipyard in Kerala. The new carrier will be named INS Vikrant, after the 20,000t World War 2 era carrier HMS Herculaeus that was sold to the Indian Navy, and served as the Vikrant (from Sanskrit vikranta, “courageous/ victorious”) from 1961-1997. Ptoject-71 currently has a budget of INR 32.6 billion (currently about $650 million), but few observers believe that the final cost will remain on budget.
Delivery is scheduled for 2014-2015, and these carriers are expected to carry their own complement of MiG-29K fighters. Plans exist for a naval variant of India’s LCA Tejas lightweight fighters, but India’s history of extremely late and failed weapons projects suggests caution. Even a successful project is unlikely to induct a naval Tejas before 2016-2018, leaving both of India’s future carrier classes strongly dependent on Russian goodwill. The Hindu | Indian Express | Sindh Today.
Feb 23/09: Indian media report that Russia has demanded another $700 million, on top of their demand for an additional $1.2 billion which had been approved by India’s cabinet, on top of the original $947 million contract. The shipyard is also demanding $190 million immediately, in order to continue work. Delivery is still scheduled for 2012, but this assumes the schedule promises are kept, and that there are no work stoppages or other production delays owning to contract negotiations.
Assuming that this is in fact Russia’s final demand, it would bring the asking price for the Gorshkov to $2.85 billion. That figure could buy a similar 45.7t new-build America Class LHA-R medium carrier with funds left over, and might even buy one of Britain’s new 65t CVF Class carriers. Hindustan Times | Indian Express | Forecast International report/op-ed | Indian Express op-ed.
Feb 22/09: MiG-29K. The Hindu quotes UAC VP and RAC MiG Director-General Mikhail Aslanovich Pogosyan, who says that Indian naval pilots have been training in Russia since October 2008. The theory portion of the course is done, and:
“Indian pilots are already training to fly the MiG-29Ks from a shore-based facility. They have been doing even 15 sorties in a day during the winter. We expect the first four MiG-29Ks to arrive in India later this year, with the other 12 being delivered by 2010.”
So far, 4 certified MiG-29Ks have been transferred to the Indian project team in Russia, after Russian test pilots have conducted carrier landing check-outs. After the course is complete, India’s Navy hopes to continue their own pilots’ training by using a Shore-based Test Facility (SBTF), built with Russian help at INS Hansa in Goa.
Feb 12/09: RIA Novosti reports that Russia has delivered the first 4 MiG-29 naval fighters to India. Oddly, they use the designation “MiG-29 Fulcrum D,” which is the NATO reporting code and not Russian or RAC MiG nomenclature.
2008Russia wants more money to complete the contract; Reality – delivery in 2012, maybe; Sevmash shipyard not exactly ship-shape; USA’s retiring CV-63 to India?
USS Vikramaditya?Dec 3/08: Indian Express reports that India’s Cabinet Committee on Security (CCS) on Tuesday “gave in to Moscow’s demands,” and will renegotiate the Vikramaditya upgrade on terms acceptable to Moscow.
Nov 22/08: Australia’s the Age newspaper reports that Russian President Dmitry Medvedev has cut his December 2008 India visit to a single day, a signal usually associated with a strained geo-strategic relationship. The visit will now take place on Dec 5/08.
Nov 13/08: As negotiations regarding the Gorshkov continue to drag on, pressure for timely resolution is building on the Russian side, as well. Sevmash (Severodvinsk Machine Building Enterprise) shipyard Deputy General-Director Sergey Novoselov tells RIA Novosti new agency that:
“We are essentially constructing a new aircraft carrier at the open assembly berth of Sevmash. In the last two years, work has only proceeded thanks to internal loans…”
That cannot continue indefinitely – but Sevmash is not backlogged with projects, which means it needs to hang on to the Admiral Gorshkov refit. So, what if India proves unwilling to pay? Novoselov pointed out that even at $2 billion, a refitted Gorshkov costs only 50-67% of the $3-4 billion involved in building a medium sized carrier. Novoselov would not be pinned down to any firm figure, of course, but some Russian defense planners are either taking him seriously, or willing to help him put added pressure on India. RIA Novosti, via Forecast International:
“If India won’t pay the money [over the agreed $617 million], we will keep the aircraft carrier ourselves. It will be very useful to us, because the situation in the world is complicated. Vessels like that are needed to patrol the waters of the Atlantic and the Mediterranean,” noted a Russian defense industry official.”
If Russia did make that move, India would need compensation for costs incurred to date – reportedly about $400 million.
Nov 11/08: Russia now says that the delivery of Admiral Gorshkov aircraft carrier to the Indian Navy will be delayed till 2012. The shipyard also claims that New Delhi has not made any payments since last year, although extra work to the tune of $1.7 billion has been done by the shipyard. ITAR-TASS reportedly quoted a shipyard representative as saying that:
“At this juncture, the completion of work in 2010 would be realistic. Two more years would be required to complete the vessel’s sailing trials, including testing its aircraft in the severe conditions of Barents Sea.”
DID isn’t quite sure why arctic operations would matter to India. India Defence.
Nov 2/08: India’s finance ministry has for the second time rejected a proposal from the MoD to approve an additional $1.2 billion in funds, in order to complete the INS Vikramaditya retrofit project. The article reports that India has already paid Russia about 67% of the original program cost, but has made no further payments since January 2007. The India Defence report adds, cryptically:
“The finance ministry’s latest decision also stemmed from a request to allocate $60 million to perform sea trials of the refurbished vessel during 2011.”
Oct 18/08: The Hindu newspaper quotes Sevmash Shipyard’s deputy director for foreign defence contracts Sergei Novosyolov, who says that Gorshkov will be taken out of dry dock by the end of the month.
“The ship’s hull has been fully done and painted and scaffolding will be dismantled by the end of October…”
Sept 21/08: Still no firm deal on the Gorshkov refit, but India’s Defence Acquisition Committee (DAC) has given approval in principle to add another 29 MiG-29Ks to the original 16-plane, $1.5 billion deal.
No price negotiations have taken place, but the contract is expected to be worth close to $2 billion when it is signed. The Navy is reported to have set its sights on a 3-squadron goal for its MiG-29K/KUB force. Indian Express report.
Sept 19/08: Indian Express reports that after Indian officials expressed concern over the slow progress in overhauling Gorshkov at the Sevmash shipyard in North Sea, Russian asked South Block to immediately pay the cash-strapped shipyard $200 million, “without prejudice to the on-going price negotiations,” in order to speed up work.
The report adds that Russian Defence Minister A Serdyukov’s visit to Delhi later in September 2008 is expected to result in a revised price for the Gorshkov refit, which must then receive political approval in India.
June 3/08: Press Trust of India reports that Russia’s Sevmash shipyard has promised readiness by 2012 – maybe. RIA Novosti quotes Sevmash officials as saying that:
“The successful solution of all the financial issues will enable the shipbuilders to sail the aircraft carrier out into the Barents Sea for trials. In the winter of 2012, the ship is expected to be finally refitted and trials will continue in the summer of that year… At the end of 2012, the aircraft carrier is expected to be fully prepared for its transfer to the Indian navy in accordance with the schedule approved by the Russian Navy.”
Negotiations and maneuvering around the contract’s final details continue, and Sevmash’s history of delivery, detailed below, must also be considered when evaluating such statements.
June 2/08: MiG-29K. Defense News reports that India’s MiG-29Ks will be based on land, because the country has no operational carriers. With INS Viraat unavailable due to upgrades and Vikramaditya badly behind schedule, the MiG-29Ks will go to the Naval Aviation Centre at INS Hansa in Goa instead. Hansa is the base used to train naval pilots. Deliveries of all 16 MiG-29Ks are expected to be complete by 2009.
May 30/08: USS Kitty Hawk? Reuters reports that American Secretary of Defense Robert Gates was asked about rumors that the USS Kitty Hawk might be sold to India at the at the Shangri-La Dialogue forum of regional analysts, defense and security officials. “I am aware of no such plans,” Gates replied.
May 9/08: ADS Watch. News Post India’s “Indian Navy To Order Another Aircraft Carrier” claims that the Indian Navy will supplement the Vikramaditya with 2 of its 37,500t indigenous “Air Defence Ship” carriers, instead of just one. The article also includes additional information about the Vikramaditya’s schedule and the potential risks.
April 9/08: Despite an agreement that was supposed to be finalized in March, Indian Defence Secretary Vijay Singh describes the parties as still “locked in intense negotiations over the price details,” adding that “technical assessment of the work needed on the carrier is still on…” The expected responses re: the deal being on track, and having a final price proposal to bring to the Cabinet “soon,” were also voiced. Zee News.
March 18/08: MiG-29KUB flies. During Chief of Naval Staff Sureesh Mehta’s visit to Russia, the first serially produced MiG-29KUB (tail number 113) performs its maiden flight at the RAC MiG test airfield in Lukhovitsy near Moscow. The MiG-29KUB is the 2-seat variant of the carrier-capable MiG-29K. RAC MiG release.
March 10/08: The Indian government’s DDI News reports that “India has reconciled to a price hike for procurement of Russian carrier Admiral Gorshkov and the government has constituted an experts committee to work out the increase.”
Naval Chief Sureesh Mehta, who had opposed additional payments under the contract, said that: “There will be some price hike. We need to pay extra amount and whatever amount is due as per contracts we will pay.” This does not sound like an encouraging report from ongoing negotiations.
March 3/08: India caves. India opts to pay Russia more, in hopes of getting the Gorshkov ready in time. Figures given vary between $500 million and $1.2 billion; exactly how much more India will agree to pay will reportedly be decided later in March 2008, after 2 more rounds of negotiations. India’s Defence Secretary Vijay Singh is quoted as saying that:
“It should be completed by mid-2010. After that, it will undergo 18 months of extensive sea trials by the Russian navy to ensure all systems are working properly.”
Retired Admiral Arun Prakash was head of the Indian Navy in 2004 when the original deal was “laboriously and painstakingly negotiated for 11 months, and the contract sealed and signed.” He told BusinessWeek that he is disappointed by Russia “reneging on the deal” and says Russia “gifted” the Gorshkov to India in exchange for a $1.5 billion contract to buy planes and helicopters and “revive their terminally ill shipbuilding and aircraft manufacturing industries.”
India will also reportedly send 500 shipyard workers, technicians and managers to Russia, to take direct charge of the work, cover Russia’s labor shortage, and keep an eye on quality control so that it’s caught immediately. Whether this will suffice, in the wake of Sevmash shipyard disasters like the Odfjell contract (q.v. Feb 21/08), remains to be seen.
What also remains to be seen at this point is whether India’s MiG-29K contract becomes the next bottleneck. India remains the only customer for this substantially different aircraft, and MiG will need to make production line changes that the existing contract may not adequately finance. Indian MoD, March 12/08 | Calcutta Telegraph | NDTV | Pravda | StrategyPage | Times of India
Meanwhile, BusinessWeek has its own speculation re: “Why India Talked Up A US Carrier Deal.” As an interesting second perspective on the larger Russia-India relationship, see also the Navhind Times March 4/08 article “India’s Defence: Looking Beyond Russia“.
March 3/08: Sea Harriers. India’s Defence Minister Shri A K Antony confesses that India’s Sea Harrier fleet has an availability problem, due to the rotation of aircraft through the current upgrade program.
“India’s Sea Harrier Shortage” looks at numbers and planned upgrades for India’s legacy naval aircraft, as the Navy prepares for future operations with MiG-29Ks. Given the amount of trouble the Harriers are in, it seems unlikely that they will be able to provide a Plan B if the MiGs have problems.
Feb 27/08: India’s Minister of Defence Shri A K Antony, asked about this issue, says:
“The overall progress of repair and re-equipping of the ship, ex-Admiral Gorshkov, in Russia is behind schedule. Execution of contract for construction of three ships of Project 1135.6 (follow-on-ships of Talwar Class) is on schedule. Russia has indicated an increase in price for repair and re-equipping of ex-Admiral Gorshkov. There is no proposal under the active consideration of the Government to contact some other country in this regard. The need for contacting other country does not arise as the existing contract with Russia is still valid.”
A fine politician’s reply. If another country contacted India instead, his denial would still be “true” in the strict sense of the term…
Feb 23/08: Progress on Gorshkov? According to the India Times’ Economic Times, Indian Defence Secretary Vijay Singh’s 5-day delegation visit to Sevmash Shipyard, and talks with Russian Energy and Industries Minister Viktor Khristenko, may have made progress. Russian senior officials reportedly assured Singh that the Russian government was making strenuous efforts to improve the situation.
F/A-18F over CV-63Feb 19-23/08: Crazy Sam’s Carrier Clearance Sale? As reports begin to suggest that Russia and India are too far apart to agree on the Gorshkov refit, speculation grows that the USA intends to solve India’s problem with a stunning offer during Defense Secretary Gates’ imminent visit to India. instead of retiring and decommissioning its last conventionally-powered carrier, the 81,800 ton/ 74,200t USS Kitty Hawk [CV-63, commissioned 1961], would be handed over to India when its current tour in Japan ends in 2008. The procedure would resemble the January 2007 “hot transfer” of the amphibious landing ship USS Trenton [LPD-14], which become INS Jalashva. The cost? This time, it would be free. As in, $0.
Naturally, there is a quid pro quo that accompanies these rumors. In return for an aircraft carrier that would be larger than its counterparts in every navy other than the US Navy, India would select at least 60 F/A-18 E/F Super Hornets in its MMRCA fighter competition, to serve as the carrier’s air wing. Unlike the Gorshkov, the Kitty Hawk is a purpose-built carrier whose full air complement is a whopping “75+” aircraft and helicopters. India has also expressed interest in the USA’s E-2 Hawkeye carrier AWACS aircraft, which would be a natural fit for its new ship.
As a number of sources point out, this is a multi-pronged move that would achieve several objectives at once. First, the offer removes all Russian negotiating leverage over India by removing the issues of sunk costs, foreign possession of the Vikramaditya, and any danger of being left without a carrier. The Indian Navy would be greatly strengthened, and its ability to police the Indian Ocean from the Straits of Malacca to South Africa would take a huge leap forward. Any additional work to upgrade or refurbish the carrier could be undertaken in India, providing jobs and expertise while maintaining full national control over the refit. The USA gains financial benefits of its own, as the Navy avoids the expensive task of steaming the Kitty Hawk home and decommissioning it. Americans would almost certainly receive maintenance contracts for the steam catapults, and possibly for some new electronics, but those economic benefits pale in comparison to the multi-billion dollar follow-on wins for Boeing (Super Hornet), Northrop Grumman (E-2 Hawkeye), and possibly even Lockheed Martin (F-16 E/F, F-35B). All of which works to cement a growing strategic alliance between the two countries, and creates deep defense industrial ties as well.
Then there’s the effect on Russia, whose relations with the USA currently border on outright hostility. With the MiG-29Ks no longer necessary for India, that contract would almost certainly be canceled. At which point, the commonality value of choosing the MiG-35 as a lower-cost secondary MMRCA buy drops sharply, opening the door for other MMRCA split-buy options that could include the Saab/BAE JAS-39 Gripen, or a complementary American offer of F-16E/Fs and/or F-35Bs. The combined effect of these blows would be a severe setback for Russia’s arms industry, though rising oil & gas revenues in Russia and other export opportunities may lead to less shrinkage and civilian re-purposing than publications like the Weekly Standard believe. The question now is: will this happen? Barents Observer | Weekly Standard | Information Dissemination: Feb 20th/ 23rd.
Feb 21/08: Sevmash screwups. “Galrahn” of the respected blog Information Dissemination passes a key tip along to DID. First, recall that the Sevmash shipyard in Severodvinsk, Archangel Oblast is responsible for the Gorshkov refit. Until recently, they also had a $544 million contract to build up to 12 tankers for the Norwegian shipping form Odfjell. When it was signed in 2004, it was promoted as “a historic deal in Norwegian-Russian industrial relations.”
Now it has been canceled, and Odfjell CEO Terje Storeng has used terms like “no will to try to understand that this is a commercial project,” “deliberately sabotaged and delayed the project” et. al. to Dagens Næringsliv. He adds:
“Following serious delays in the construction process, combined with demands for further price increases from the Yard, continuous cooperation problems as well as protracted negotiations, Odfjell decided today to serve formal notice of cancellation to Sevmash. The instalments already paid are covered by standard refund guarantees from international banks. Odfjell will further claim full compensation for its costs and losses caused, on account of wilful misconduct and massive contract breaches by the Yard. Unless the matter is solved amicably between the parties, the issue will be solved by arbitration in Sweden, as provided for in the contract.”
Note the Russian official’s comments in the Feb 7/08 entry. Closure may once again become a very real possibility for Sevmash. Worse, Odfjell’s experience has to give India serious pause re: the reliability of Russia’s new refit cost estimates, and the likelihood of further extortion to ‘adjust’ the deal down the road. Barents Observer | Dagens Naeringsliv report [Norwegian] | Odjfell.NO release
Sevmash has wider problems
Feb 7/08: Russia – Let’s Change a Deal! Zeenews quotes an unnamed “Russian official” with interesting and somewhat unsettling arguments, in advance of a high-level delegation’s arrival led by Indian Defence Secretary Vijay Singh:
“Moscow feels that the agreement for supply of the 45,000 tonne warship was signed at a time when the Russian ship-building company was in bad shape and India “used” the situation to sign the contract at lower price. The ship-building company was facing closure and was ready to sign any kind of contract when the contract was signed.”
Defense Industry Daily needs to look up the exact definitions to be certain, but we believe this process is known as “shrewd negotiation,” followed by “a deal.” Indian Naval Chief Admiral Sureesh Mehta appears to be using the same lexicon, and has publicly said that there should be no revision to the Goshkov contract. Still, India cannot receive the carrier she wants if the shipyard goes bankrupt, and Russia is holding the carrier. This gives the Russians considerable leverage in negotiations, unless India can find an alternate provider. There may be a way out, however:
“But Russia is willing to “compensate” for the cost of Gorshkov if it gets more military orders, which Moscow insists is not linked to 126 fighter planes that India is planning to buy but other defence purchases.”
2007India’s navy and politicians in denial – but the carrier is late.
Ka-28Nov 19/07: India’s MoD confirms delays in the Gorshkov’s delivery and slow progress, without really answering any questions. It acknowledges that the Russian side has submitted a revised Master Schedule, attributing the delays to “Growth of Work.” In response, an apex level Indian committee under the Defence Secretary, and a Steering Committee under a Vice Admiral, have been set up. A team has also been stationed at the shipyard.
No word on the timelines or costs suggested; indeed, these are likely to remain under negotiation. Indian MoD release.
Nov 6/07: A top-level Indian Navy delegation is heading for Moscow to discuss the delay and price escalation in the Admiral Gorshkov aircraft carrier deal. A detailed financial and technical plan outlining the specific justifications and amounts will be presented to the Indian side, who is there to listen rather than to negotiate.
The report pegs the original price quoted for refurbishing the carrier was just under $980 million, adding that the Russians are insisting on cost increases of at least $350 million. Indian officials reportedly fear that the final escalation may end up being much more once they are deep enough into the commitment trap of having paid for work. The report also adds that the Navy “had reconciled itself to the fact that the delivery of the ship would be delayed from the original deadline of August 2008 by a few years,” a surprising development given the limited service life of India’s remaining carrier. If the government is indeed prioritizing cost containment over delivery dates, reconciliation of the INS Viraat’s service life with Gorshkov’s entry may prove difficult. IDRW.
Oct 18/07: India’s MoD finally admits the obvious, as part of an announcement concerning an Indo-Russia fighter development deal. India MoD release:
“The Defence Minister described the Agreement on FGFA as a ‘major landmark’ and said that the Indo-Russian relationship is on a trajectory to reach new heights… Mr. Antony expressed satisfaction at the outcome of discussions on other important projects e.g., supply and licensed production of T-90 tanks, SU-30 MKI aircraft and other strategic issues. He admitted that there has been a delay in the delivery of the repaired and refurbished aircraft carrier Admiral Gorshkov [emphasis ours] along with supply of deck-based fighter aircraft MiG-29-K and said it was decided that some more studies by technical groups would be done to go through the details. He appreciated the efforts made by the Russian side to resolve issues relating to life cycle support of equipment of Russian origin.”
June 16/07: India Defence: High Level Indian Delegation In Russia To Re-Negotiate Defense Deals Pricing:
“With differences over prices delaying the delivery of upgraded Sukhoi multi-role fighters and Gorshkov aircraft carrier, India today rushed a high-level defence team to Russia with fresh proposals to break the logjam… The visit of the team assumes significance with Defence Minister AK Antony admitting that New Delhi was facing “problems” in acquisition of the carrier Gorshkov as well as in negotiating a new deal to buy 40 more upgraded Sukhoi-30 fighters for the Indian Air Force.”
May 17/07: India Defence: “No Delays in INS Vikramaditya Acquisition from Russia: Defence Minister.” With that said…
“However, sources from the Indian Navy had earlier confirmed reports being circulated in the Indian and Russian media regarding a possible two year delay in the acquisition of the Aircraft Carrier.”
Additional Readings Equipment Profiles