INS Vikramaditya

From Infogalactic: the planetary knowledge core
(Redirected from INS Vikramaditya (R33))
Jump to: navigation, search
INS Vikramaditya (R33)
INS Vikramaditya during trials
History
India
Name: INS Vikramaditya
Namesake: Vikramāditya
Builder: Black Sea Shipyard, USSR, and Sevmash, Russia
Cost: $2.35 billion[1]
Commissioned: 16 November 2013[2]
Homeport: INS Kadamba, Karwar
Identification: Pennant number: R33[3]
Motto: Strike Far, Strike Sure[4]
Status: in active service, as of 2024
Badge: INS Vikramaditya Crest
General characteristics
Class & type: Modified Kiev-class aircraft carrier
Displacement: 45,400 tons of loaded displacement[5][6]
Length: 283.5 metres (930 ft) (overall)
Beam: 59.8 metres (196 ft)[7]
Draught: 10.2 metres (33 ft)
Decks: 22[8]
Installed power: 6 turbo alternators and 6 diesel alternators which generate 18 MWe[8]
Propulsion: 8 turbo-pressurised boilers, 4 shafts, 4 geared steam turbines, generating 180,000 horsepower (134,226 kW)[8][9]
Speed: 32 knots (59 km/h)[10]
Range: 13,500 nautical miles (25,000 km) at 18 knots (33 km/h)[11]
Endurance: 45 days[8]
Complement: 110 officers and 1500 sailors[9]
Sensors and
processing systems:
Long range Air Surveillance Radars, LESORUB-E, Resistor-E radar complex, CCS MK II communication complex and Link II tactical data system[8]
Armament:
Aircraft carried:
Aviation facilities:

INS Vikramaditya (Sanskrit, Vikramāditya ( भा नौ पो विक्रमादित्य) meaning "Brave as the Sun"[note 1]) is a modified Kiev-class aircraft carrier which entered into service with the Indian Navy in 2013. She has been renamed in honour of Vikramaditya, a legendary 1st century BCE emperor of Ujjain, India.

Originally built as Baku and commissioned in 1987, the carrier served with the Soviet and later with the Russian Navies (as Admiral Gorshkov) before being decommissioned in 1996 as she was too expensive to operate on a post-Cold War budget.[19][20][21] The carrier was purchased by India on 20 January 2004 after years of negotiations at a final price of $2.35 billion.[1] The ship successfully completed her sea trials in July 2013[22] and aviation trials in September 2013.[23]

She was commissioned on 16 November 2013 at a ceremony held at Severodvinsk, Russia.[24][25] On 14 June 2014, Prime Minister of India Narendra Modi formally inducted INS Vikramaditya into the Indian Navy and dedicated it to the nation.[26][27]

History

Purchase

Baku entered service in 1987, and was renamed Admiral Gorshkov in 1991, but was deactivated in 1996 because she was too expensive to operate on a post-Cold War budget. This attracted the attention of India, which was looking for a way to expand its carrier aviation capabilities.[28] On 20 January 2004, after years of negotiations, Russia and India signed a deal for the sale of the ship. The ship would be free, while India would pay US$800 million for the upgrade and refit of the ship, as well as an additional US$1 billion for the aircraft and weapons systems. The navy looked at equipping the carrier with the E-2C Hawkeye, but decided not to.[29] In 2009, Northrop Grumman offered the advanced E-2D Hawkeye to the Indian Navy.[30]

Baku in 1988

The deal also included the purchase of 12 single-seat Mikoyan MiG-29K 'Fulcrum-D' (Product 9.41) and four dual-seat MiG-29KUB aircraft (with an option for 14 more aircraft) at US$1 billion, six Kamov Ka-31 "Helix" reconnaissance and anti-submarine helicopters, torpedo tubes, missile systems and artillery units. Facilities and procedures for training pilots and technical staff, delivery of simulators, spare parts, and establishment maintenance on Indian Navy facilities were also part of the contract.

The upgrade involved stripping all the weaponry and missile launcher tubes from the ship's foredeck to make way for a "short take-off but arrested recovery" (STOBAR) configuration,[31] converting the Gorshkov from a hybrid carrier/cruiser to a pure carrier.

The announced delivery date for INS Vikramaditya was August 2008, which would allow the carrier to enter service just as the Indian Navy's only light carrier INS Viraat retired. While Viraat's retirement had been pushed out to 2010–2012,[32] it underwent a final refit which will enable her to serve through 2016.[33]

The issue with the delays was compounded by ongoing cost overruns, resulting in high-level diplomatic exchanges to get these issues resolved. India finally agreed to pay an additional US$1.2 billion for the project, more than doubling the original cost.[34] However, ongoing delays with the Vikramaditya's delivery schedule, pushed the delivery to 2013. The indigenous Vikrant-class aircraft carrier was delayed by at least a year and was expected to be commissioned at the earliest in 2013 from the proposed 2012.[35]

File:SS-N-12 missile launchers.JPEG
The conversion of the ship saw all the armament removed from the foredeck, including the P-500 Bazalt cruise missile launchers and the four Antey Kinzhal surface-to-air missile launchers, to make way for a 14.3° bow ski-jump ramp.

In July 2008, it was reported that Russia wanted to increase the price by $2bn, blaming unexpected cost overruns on the deteriorated condition of the ship and citing a "market price" for a new carrier of $3-4bn.[36] India has paid US$400 million as of November 2008. However, Russia even threatened to scrap the deal altogether if India did not pay the amount.[37] In December 2008, government sources in India stated that the Cabinet Committee on Security (CCS) had finally decided in favour of purchasing Admiral Gorshkov as the best option available.[38] The Comptroller and Auditor General of India (CAG) criticised the fact that Vikramaditya would be a second-hand warship with a limited life span, which would be 60% costlier than a new one, and there was a risk of further delay in its delivery.[39] The Indian Navy Chief of Naval Staff Admiral Sureesh Mehta defended the price for the warship saying:

"I can't comment on the CAG. But you all are defence analysts, can you get me an aircraft carrier for less than USD two billion? If you can, I am going to sign a cheque right now".

The statement from the Chief of Naval Staff possibly indicates that the final deal could be in excess of US$2 billion. When asked about CAG's finding that the navy had not done its risk analysis before going in for the ship, he said,

"I can ensure you that there is no such thing. There is no question, we have been looking at the ship since the late 90s."[40]

On 2 July 2009, Russian President Dmitry Medvedev said that the refit of the carrier should be completed as soon as possible so she could be delivered to India in 2012.[41] On 7 December 2009, Russian sources indicated that final terms had been agreed on, but no delivery date was set.[42] On 8 December 2009, it was reported that India and Russia ended the stalemate over Admiral Gorshkov price deal by agreeing on a price of US$2.2 billion. Moscow was asking for US$2.9 billion for the aircraft carrier, nearly three times the price that was originally agreed between the two sides in 2004. On the other hand, New Delhi wanted the price to be scaled back to US$2.1 billion.[43][44] Both governments finalsed the price of Admiral Gorshkov at US$2.35 billion on 10 March, a day ahead of Russian Prime Minister Vladimir Putin's two-day visit to India.[1]

In April 2010, a scandal over the project emerged when it was announced that a senior Indian Navy officer had probably been blackmailed in order to influence the negotiations over the cost of Admiral Gorshkov to India.[45] Commodore Sukhjinder Singh had been a senior figure supervising the refit of the carrier, working as the principal director for the project. He was discharged from service due to this incident.[46]

Refurbishment

File:Two aircraft carriers in the closed city of Severomorsk.jpg
Vikramaditya (left) alongside the Russian aircraft carrier Admiral Kuznetsov in the port of Severomorsk in 2012

The hull work was completed by 2008[47] and Vikramaditya was launched on 4 December 2008.[48] Around 99% of the structural work and almost 50% of the cabling work had been completed by June 2010. Almost all of the large equipment, including engines and diesel generators, was installed.[49] A naval MiG-29K prototype aircraft was used to test the deck systems of Vikramaditya in 2010.[50]

All reconfiguration work was completed at Severodvinsk, Russia; however it was delayed by three years due to underestimation of the amount of cabling needed.[51] An expert level discussion on technical and financial matters was held between India and Russia to sort out the issues.[52] The MiG-29K entered operational service with India in February 2010. A compromise was finalised and India was to pay an extra undisclosed amount. Russia was to install new systems instead of repairing the old ones.[53]

On 1 June 2010, the Times of India reported a naval officer saying: "With India earlier this year agreeing to the revised refit cost of $2.33 billion for Gorshkov after three years of bitter wrangling since the earlier agreement inked in January 2004 had earmarked only $974 million for it, Russia has appointed a high-level apex committee to oversee the work on the carrier." The ship was to go for harbour trials by early 2011 to ensure it could be handed over to India by December 2012 or so.[49][54] Dock trials began on 1 March 2011. The focus of these trials was on the main power generation units and the radio-electronic armament systems, manufactured in India.[55][56] Indian Navy personnel began training on Vikramaditya in April 2011.[57] On 19 April 2012, it was announced that all internal systems were functioning, and the ship was entirely self-contained. Measurement of the ship's magnetic field and centre of gravity were performed before sea trials began.[58]

Design

The hull design is based on the Admiral Gorshkov launched in 1982, but has a larger full load displacement. 1750 out of 2500 compartments of the ship were re-fabricated, and extensive re-cabling was done to support new radars and sensors. The elevators were upgraded, and two restraining stands were fitted, allowing combat aircraft to reach full power before making a ski jump-assisted short take-off. Three arresting gears were fitted on the aft part of the angled deck, and navigation and carrier-landing aids were added to support fixed-wing "short take-off but arrested recovery" (STOBAR) operations.[8][59][60]

Structural modifications

Construction of the 900 tonne ski-jump in place on Vikramaditya at Sevmash Shipyard in Russia

The most intricate modification was the conversion of the VTOL carrier to a STOBAR carrier. This involved removal of all the armament, including the P-500 Bazalt cruise missile launchers and the four Antey Kinzhal surface-to-air missile launchers fitted on the front, to make way for a 14.3° bow ski-jump ramp. The 20-ton capacity elevator beside the ship's island superstructure was unchanged, but the aft lift was enlarged and its lift capacity increased to 30 tons. For STOBAR operations, three 30 m arrestor wires and three restraining gears on the stern of the angled deck were fitted. Sponsons were installed to increase the breadth at the flight deck, for fitment of the ski-jump, for strengthening of arresting gear and runway area, and for elongation of the aft end to increase the length of the landing strip aft of the arresting gear. 234 new hull sections were installed to achieve the desired shape, and the total steel added to carry out these modifications amounted to 2500 tons.[8][59][60]

The superstructure profile of the Admiral Gorshkov platform could accommodate powerful planar or phased array radar systems with the "billboard style" antennae, which was first observed on the United States Navy's USS Long Beach, along with extensive command and control facilities to conduct an aerial campaign. Extensive revamp of sensors was carried out, and long range air-surveillance radars and advanced electronic warfare suites were fitted, which enable the maintenance of a surveillance bubble of over 500 km around the ship. An aft mast was installed to accommodate various communication antennae. These changes needed 2300 km of new cables, and 3,000 km of new pipes.[8][60][61]

The eight boilers were replaced by new generation boilers, converted to take diesel fuel utilising LSHSD instead of furnace fuel oil, each providing a steam capacity of 100 tonnes per hour.[62] The new high-pressure boilers are highly efficient and have high levels of automation. They power four propellers in four shaft configuration, producing a total thrust of 180,000 horsepower (134,226 kW) at the shaft, and a top speed of over 30 knots. Six turbo alternators and six diesel alternators generate 18 MW of electricity to power various equipment. Modern oil-water separators as well as a sewage treatment plant were incorporated to meet international standards. Six new Italian Wärtsilä 1.5 MW diesel generators, a Global Marine communications system, Sperry Bridgemaster navigation radar, a new telephone exchange, new data link and an IFF Mk XI system were added. Hotel services were improved with the addition of two reverse osmosis plants producing 400 tons of fresh water per day, as well as York International refrigeration and air conditioning, and a new galley together with improved domestic services and accommodation for 10 female officers.[59][60][63]

Combat systems

Kamov Ka-31 "Helix" performs the airborne early warning role.
File:Mikoyan MiG-29K of the Indian Navy.jpg
The MiG-29Ks are the main offensive platform of the carrier.

The combat systems on board the carrier are controlled by LESORUB-E, the computer-aided action information system. It gathers data from the ship’s sensors and data links and creates comprehensive situation awareness. The CCS Mk II communication complex is installed for external communications and the Link II tactical data system enables integration into the Indian Navy’s network-centric operations. Modern launch and recovery systems are installed for handling different aircraft - the LUNA landing system for MiG-29Ks and the DAPS Landing system for Sea Harriers. The Resistor-E automated air-traffic control system has been installed, which provides assistance during approach, landing and short range navigation down to a distance of 30 metres short of flight deck to the pilots. Along with various other sub-systems, it provides navigation and flight data to ship-borne aircraft operating at long distances from the carrier.[8][64]

As of December 2014 INS Vikramaditya was yet to be fitted with a close in weapon system (CIWS),[65] which will be added during April–June 2015 at the Karwar naval base. The systems being evaluated are Barak and Shtil. Until an air-defence system is installed, the carrier will depend on its accompanying battle group for air defence and long range missile firing.[66][67][68] During the first scheduled refit in 2017, the carrier will be armed with the Barak 8 long-range air-defence system (LR-SAM), which is currently being tested. It is launched from vertical launch cells, and has a strike range of 6–70 km. The carrier will carry up to 48 missiles.[64][66]

The official expected life span of the ship is 40 years, and is unlikely to require any major repair work for at least a decade.[61][69] Over 70% of the ship and her equipment is new and the remainder has been refurbished.[59] Sevmash Shipyard, which upgraded the carrier, will provide warranty servicing including maintenance for the next 20 years.[70]

Air Group

Vikramaditya has been designed as a STOBAR carrier capable of operating both conventional fixed-wing aircraft and helicopters, with up to 30 aircraft capable of being accommodated. Its primary embarked aircraft type is the Mikoyan MiG-29K, a navalised version of the Mikoyan MiG-29M. The MiG-29K is an advanced, all weather multirole fighter capable of undertaking both the fleet air defence, low level strike and anti-shipping roles. The primary ASW platform is the venerable Westland Sea King, while AEW is undertaken by the Kamov Ka-31. Utility and plane guard duties are undertaken by the HAL Chetak (or HAL Dhruv).[8]

Sea trials and commissioning

First sea trials

Vikramaditya in the White Sea during Sea trials in 2013

Russia was scheduled to hand over Vikramaditya to India on 4 December 2012,[71] with sea trials scheduled to begin on 29 May 2012.[72] The sea trials in fact began on 8 June. The ship sailed out for pre-delivery trials from the berth of the Sevmash shipyard in Russia's northern city of Severodvinsk. These trials were to include landing and take-off of fighter jets from the deck of the carrier.[73][74][75]

On 17 September 2012, malfunctions were detected during trials. According to official report, seven out of eight steam boilers of the propulsion machinery were out of order. Due to this, the deadline of the hand over this ship to the Indian Navy was postponed again until October 2013.[76] Later investigation has determined that the cause for the engine failure was due to poor workmanship and supervision.[77] The Gorshkov and other ships of the 1143.4 class had a history of multiple boiler failures,[78] however Russian shipbuilders claimed that the source of the problem was the low-grade Chinese-made firebricks that were used in the boiler insulation instead of asbestos.[79]

Second sea trials

On 3 July 2013, Igor Sevastyanov, deputy head of Russia's state arms exporter Rosoboronexport, announced that the warship had departed for sea trials with a mix of Russian and Indian crew.[80] On 28 July 2013, it was reported that Vikramaditya had successfully completed her sea trials and was able to reach her maximum speed of 32 knots. She then proceeded to the White Sea for aviation trials,[22] which were carried out by Russia's Northern Fleet aviation and completed in September 2013.[23][81] Aircraft and helicopters flew around and over the ship to check the performance of its radar, air defence, communication and control systems, and MiG specialists praised the ski-jump ramp.[82]

The sea trials lasted three months, and the ship demonstrated excellent seaworthiness and manoeuvrability. The carrier’s electronic warfare and jamming capability was demonstrated when Sukhoi-33s, Kamovs, MiG-29s and A-50 early warning aircraft failed to "paint" the carrier using their radars, whereas the incoming aircraft were detected by the ship at a distance of 350–400 km. In total, the ship sailed for 19,500 miles during both the trials, controlled 778 aircraft and helicopter flights, and conducted 88 landings by Russian pilots.[61][82] During the second sea trial, it sailed for 8,600 miles, of which 1,700 miles were under the command of the ship's Indian captain Commodore Suraj Berry.[83]

The Indian Navy flag is hoisted aboard Vikramaditya as it is commissioned at Sevmash Shipyard in Russia.

Surveillance by NATO

When the trials were ongoing, a Norwegian P-3 Orion aircraft observed Vikramaditya. While in international waters,[84] it flew close to the ship to take photographs, and also dropped sonobuoys to record the ship's acoustic signature. The Norwegian aircraft left the area when a Russian MiG-29 arrived. A Norwegian ship was also seen to observe Vikramaditya.[84]

Commissioning

She was formally commissioned on 16 November 2013 at a ceremony held at Severodvinsk, Russia.[24] The ceremony was attended by Indian defence minister A K Antony and the Russian deputy prime minister Dmitry Rogozin. The ship is now patrolling the Indian ocean.[85]

Service history

Vikramaditya being escorted by INS Viraat and other ships of the Western Fleet in the Arabian Sea.
Prime Minister Narendra Modi in cockpit of a MiG-29K, on board INS Vikramaditya. The Prime Minister dedicated the vessel to the nation in June 2014.

After commissioning, the carrier began a continuous 26-day journey of 10,212 nautical miles to its homeport at INS Kadamba, Karwar, from Severodvinsk on 27 November 2013, with a short stopover in Lisbon.[17][86] It is under the command of Commodore Suraj Berry, who is her first Indian captain.[82] Apart from her Indian crew, she also carried 177 Russian specialists from Sevmash, who will remain on board for one year, as part of the 20-year post-warranty services contract with the shipyard. During the journey, it encountered a storm in the Barents Sea where she linked up with her escorts frigate INS Trikand and fleet tanker INS Deepak.[87] The group was escorted by the Royal Navy frigate Monmouth while passing through the English Channel,[88] and was joined by destroyer INS Delhi near Gibraltar.[17] The flotilla sailed in the Mediterranean sea, crossed the Suez Canal[83][89] and entered the Arabian Sea near the Gulf of Aden on 1 January 2014. It was received nearly 1,200 nautical miles (2,200 km) away from Indian shores by a large flotilla of the Western fleet,[90] which was composed of the aircraft carrier INS Viraat, two Delhi-class destroyers including INS Mumbai, three Talwar-class frigates, the frigate INS Godavari, and a couple of offshore patrol vessels including INS Subhadra.[17] The event was significant as the Indian Navy was operating two aircraft carriers simultaneously for the first time in 20 years.[91] After conducting basic sea exercises with the fleet,[92] Vikramaditya reached Karwar on 7 January 2014.[93][94][95]

Navy pilots of INAS 303 "Black Panthers" operating the MiG-29K practiced carrier operations at the Shore Based Test Facility (SBTF) in INS Hansa, Dabolim, Vasco-da-Gama. The first aircraft piloted by an Indian Navy pilot landed on the carrier on 8 February 2014.[96] Since then, the pilots and air controllers have been certified for operating the MiG-29K fighters from the carrier deck, including night landings. The carrier's air wing will consist of 16 MiG-29Ks including four KUB trainers, six airborne early warning and control (AEW&C) Kamov Ka-31 and Kamov Ka-28 anti-submarine warfare (ASW) helicopters.[64]

In May 2014, the carrier was declared operationally deployed along with its embarked air group comprising MiG-29Ks and had taken part in a war game conducted by the Western Naval Command.[97][98] On 14 June 2014, Prime Minister of India, Narendra Modi dedicated the carrier to the country.[99]

On 8 December 2015, Indian Defense-Ministry sources stated that the INS Vikramaditya would receive the CVA's first major overhaul as part of the 'Made In India' initiative. The state-owned Cochin Shipyards and the Pipavav shipyards will overhaul the carrier once it is in dry dock. [100]

See also

Notes

  1. Literally Vikramaditya translates as being "Sun (Aditya) of valour" (Vikram). The component "āditya" (sun) literally means "he who belongs to Aditi". It was the title of some of the most famous kings in Indian history, such as the Vikramaditya of Ujjain, famed as a noble ruler and a mighty warrior. It is also a title that was used by the Indian emperor Chandragupta II who ruled between 375-413/15 AD. This title was again used by the Hindu king Hemu who ruled Delhi from 7 October to 5 November 1556.

References

  1. 1.0 1.1 1.2 Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. 8.00 8.01 8.02 8.03 8.04 8.05 8.06 8.07 8.08 8.09 8.10 Lua error in package.lua at line 80: module 'strict' not found.
  9. 9.0 9.1 9.2 Lua error in package.lua at line 80: module 'strict' not found.
  10. "INS Vikramaditya fully operational- Admiral Dhowan." Russia & India Report, 2 June 2014. Retrieved: 27 June 2014.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. 17.0 17.1 17.2 17.3 Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Bharat Verma 2011, pp. 45–46.
  20. Terry Brien 2012, p. 1145.
  21. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  22. 22.0 22.1 Lua error in package.lua at line 80: module 'strict' not found.
  23. 23.0 23.1 Lua error in package.lua at line 80: module 'strict' not found.
  24. 24.0 24.1 Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. IndiaDefence.com – WHAT'S HOT? ANALYSIS OF RECENT HAPPENINGS – Aero India 2005 – Naval Interests – An IDC Report
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Defence Talk – Pictures of the Gorshkov being worked on in dry docks
  32. Defense Industry Daily INS Vikramaditya Hits Delay, Cost Increases
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. NDTV News clip on price increase
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. Lua error in package.lua at line 80: module 'strict' not found.
  45. Lua error in package.lua at line 80: module 'strict' not found.
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. 49.0 49.1 Lua error in package.lua at line 80: module 'strict' not found.
  50. Lua error in package.lua at line 80: module 'strict' not found.
  51. Lua error in package.lua at line 80: module 'strict' not found.
  52. Only few technical, financial issues pending on Gorshkov deal[dead link]
  53. Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. Lua error in package.lua at line 80: module 'strict' not found.
  57. Lua error in package.lua at line 80: module 'strict' not found.
  58. Lua error in package.lua at line 80: module 'strict' not found.
  59. 59.0 59.1 59.2 59.3 Lua error in package.lua at line 80: module 'strict' not found.
  60. 60.0 60.1 60.2 60.3 Lua error in package.lua at line 80: module 'strict' not found.
  61. 61.0 61.1 61.2 Lua error in package.lua at line 80: module 'strict' not found.
  62. Lua error in package.lua at line 80: module 'strict' not found.
  63. Lua error in package.lua at line 80: module 'strict' not found.
  64. 64.0 64.1 64.2 Lua error in package.lua at line 80: module 'strict' not found.
  65. Lua error in package.lua at line 80: module 'strict' not found.
  66. 66.0 66.1 Lua error in package.lua at line 80: module 'strict' not found.
  67. Lua error in package.lua at line 80: module 'strict' not found.
  68. Lua error in package.lua at line 80: module 'strict' not found.
  69. Lua error in package.lua at line 80: module 'strict' not found.
  70. Lua error in package.lua at line 80: module 'strict' not found.
  71. Lua error in package.lua at line 80: module 'strict' not found.
  72. Lua error in package.lua at line 80: module 'strict' not found.
  73. Lua error in package.lua at line 80: module 'strict' not found.
  74. Lua error in package.lua at line 80: module 'strict' not found.
  75. Lua error in package.lua at line 80: module 'strict' not found.
  76. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  77. Russia Copes With The Vikramaditya Disaster – Strategypage.com, 14 October 2012
  78. Lua error in package.lua at line 80: module 'strict' not found.
  79. Lua error in package.lua at line 80: module 'strict' not found.
  80. Lua error in package.lua at line 80: module 'strict' not found.
  81. Lua error in package.lua at line 80: module 'strict' not found.
  82. 82.0 82.1 82.2 Lua error in package.lua at line 80: module 'strict' not found.
  83. 83.0 83.1 Lua error in package.lua at line 80: module 'strict' not found.
  84. 84.0 84.1 Lua error in package.lua at line 80: module 'strict' not found.
  85. [1]. Retrieved 17 November 2013.
  86. Lua error in package.lua at line 80: module 'strict' not found.
  87. Lua error in package.lua at line 80: module 'strict' not found.
  88. Lua error in package.lua at line 80: module 'strict' not found.
  89. Lua error in package.lua at line 80: module 'strict' not found.
  90. Lua error in package.lua at line 80: module 'strict' not found.
  91. Lua error in package.lua at line 80: module 'strict' not found.
  92. Lua error in package.lua at line 80: module 'strict' not found.
  93. Lua error in package.lua at line 80: module 'strict' not found.
  94. Lua error in package.lua at line 80: module 'strict' not found.
  95. Lua error in package.lua at line 80: module 'strict' not found.
  96. Lua error in package.lua at line 80: module 'strict' not found.
  97. Lua error in package.lua at line 80: module 'strict' not found.
  98. Naval exercises off Goa coast today
  99. Lua error in package.lua at line 80: module 'strict' not found.
  100. Lua error in package.lua at line 80: module 'strict' not found.

Bibliography

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

External links