Jump to content

Mikoyan MiG-29K

From Alfawiki
Mikoyan
Company typeDesign bureau
IndustryAerospace, Defense
FoundedLate 1970s
Headquarters
Russia
ProductsMiG-29K fighter aircraft

Overview

The Mikoyan MiG-29K (Russian: Микоян МиГ-29K; NATO reporting name: Fulcrum-D) represents a Russian all-weather, carrier-capable multirole fighter designed by the Mikoyan Design Bureau. Originating in the late 1980s as an evolution of the MiG-29M, the MiG-29K is classified by Mikoyan as a 4+ generation jet fighter.

Production models of the MiG-29K incorporate advancements over initial prototypes, including an advanced multifunction radar system and updated cockpit instrumentation. These aircraft are equipped to deploy RVV-AE (also called R-77) air-to-air missiles, alongside armaments suited for anti-ship and anti-radar missions, as well as various precision-guided munitions for ground attack roles.

During the early 1990s, development was limited to only two prototypes due to the Russian Navy’s preference for the Su-27K (later known as the Su-33). Despite funding challenges from 1992 onward, Mikoyan persisted with the MiG-29K project. The program gained momentum in the late 1990s when India sought a carrier-based fighter following its acquisition of a former Soviet aircraft carrier. The Indian Naval Air Arm received its initial MiG-29K units in 2009. Meanwhile, with their Su-33 fleet approaching obsolescence around 2010, the Russian Navy also procured the MiG-29K to serve as a replacement fighter.

Origins

The MiG-29K initiative began in the late 1970s when the Soviet Navy identified the need for a supersonic fighter capable of carrier operations. To address this, the Mikoyan design bureau created a "proof of concept" variant of the MiG-29, incorporating a reinforced undercarriage and strengthened tail section equipped with an arrestor hook. This prototype was known as the MiG-29KVP (Korotkii Vzlet i Posadka, meaning "short takeoff and landing").[1] The KVP’s maiden flight took place on 21 August 1982, followed by extensive testing that confirmed its capability to operate safely from a ski-jump ramp. However, it became clear that a production model would require enhanced engine power and increased wing surface area.[2][3] Consequently, the decision was made to base the final naval fighter on the then-developing advanced MiG-29M (izdeliye "Product" 9.15), modified with a new undercarriage and larger folding wings. This variant was designated MiG-29K (Korabelniy, meaning "ship-based") or Project 9–31.[4][5]

Compared to the standard MiG-29 production version, the MiG-29K incorporated significant upgrades including a new multi-function Zhuk radar; a cockpit outfitted with monochrome displays and adhering to the HOTAS (hands-on-throttle-and-stick) control concept; RVV-AE active homing air-to-air missiles; as well as anti-ship and anti-radar missile capabilities alongside precision-guided air-to-ground munitions. To mitigate foreign object damage (FOD) risks, its engine intakes featured retractable grills for airflow instead of metal doors and leading-edge extension auxiliary intake louvres commonly found on land-based MiG-29s.[6]

File:MiG-29M NTW 7 8 93.jpg
A MiG-29M exhibited publicly. The MiG-29M served as the foundation for the navalized MiG-29K.

The first flight of the MiG-29K occurred on 23 July 1988 at Saky, piloted by test pilot Toktar Aubakirov.[7] On 1 November 1989—the same day the Sukhoi Su-27K made its debut—Aubakirov successfully completed both the inaugural carrier landing and takeoff of the MiG-29K from the aircraft-carrying cruiser Tbilisi (now known as Admiral Kuznetsov).[8] Between 1989 and 1991, further evaluations were conducted aboard Admiral Kuznetsov. However, following the collapse of the Soviet Union, development was suspended while the Russian Navy opted to focus on the competing Su-33 program.[9][N 1] Despite limited funding, Mikoyan persisted in advancing the MiG-29K project.[13]Template:Verify source[14]

During trials aboard Admiral Kuznetsov, takeoffs were assisted by springboards from runways measuring approximately 195 metres (640 ft) in length with 95 m (312 ft) ramps. Test results indicated excellent landing precision, enabling later transition to a three-cable arrestor system on Admiral Gorshkov. This landing accuracy was further improved by integrating an autothrottle system. Takeoff performance allowed most sorties to be conducted under tropical conditions with ship speeds around 10 knots (19 km/h; 12 mph).[13][14]

Revival

File:Indian Navy MiG-29K climb.JPG
An Indian Navy MiG-29K executes a rapid ascent

The MiG-29K initiative was reinstated following the Indian Navy's 2004 acquisition of the former Soviet naval aircraft carrier Admiral Gorshkov. Originally serving in the Soviet fleet as a hybrid cruiser/aircraft carrier designed for vertical/short take-off and landing (V/STOL) aircraft, the vessel underwent deck modifications to accommodate MiG-29K operations, including installation of a ski-jump ramp and arrestor wires.Template:Fix/category[citation needed] Enhancements to the aircraft itself feature enlarged folding wings, an arrestor hook, and a reinforced fuselage treated for corrosion resistance.[15]

A decisive factor influencing India's preference for the MiG-29K over the Su-33 was the Su-33’s larger dimensions, which would further restrict deck capacity.[16][17] Tailored modifications for Indian specifications include the integration of Zhuk-ME radar, RD-33MK engines, an increased combat payload capability up to 5,500 kilograms (12,100 lb), 13 hardpoints for weapons, and an advanced four-channel digital fly-by-wire control system. The platform supports the entire arsenal compatible with MiG-29M and MiG-29SMT variants.[18]

Addressing the absence of an aircraft carrier-based AWACS platform might be feasible through further advancement of the dual-seat MiG-29KUB variant. Theoretically, equipping the MiG-29KUB with a high-performance radar system and secure data links could enable coordinated network operations among multiple MiG-29KUBs to provide airborne early warning coverage. Additionally, enhancements could focus on electronic warfare capabilities and extended-range strike missions.[13][14]

The inaugural flight of the two-seat MiG-29KUB occurred on 20 January 2007, followed by the single-seat MiG-29K's maiden flight on 25 June 2007.[19]

Design

File:МАКС-2007-ЗВГ-016.jpg
MiG-29K fighter stationed at Zhukovskiy LII airfield

Derived from the Mikoyan MiG-29M, the MiG-29K has been specifically adapted for naval use.[4] Structural reinforcements to the airframe and landing gear accommodate the increased stresses encountered during carrier landings. Modifications for carrier compatibility include folding wings, an arrestor hook, and catapult launch fittings; additionally, the landing gear track has been broadened. Unlike earlier MiG-29 models, the MiG-29K supports both receiving aerial refueling and acting as a "buddy" tanker to refuel other aircraft.Template:Fix/category[citation needed]

File:Mikoyan-Gurevich MiG-29K (9-31) - 1.jpg
MiG-29K performing as a buddy refueling tanker

Equipped with two RD-33MK engines mounted widely apart, early prototypes utilized two RD-33K turbofans, each delivering an afterburner thrust of 86.3 kN (19,800 lb) and a potential takeoff thrust of 92.2 kN (20,723 lbf) optimized for carrier operations.[20][21] The RD-33MK variant offers a 7% increase in power compared to the standard RD-33, achieved through advanced turbine blade materials.[22][23]

Internal fuel capacity was expanded from 3,340 to 4,560 kg (7,360 to 10,100 lb), extending the combat radius to approximately 850 km (531 mi). This radius can be further extended to around 1,300 km (810 mi) when equipped with three external drop tanks under the wings. The maximum takeoff weight increased from 19.5 to 22.4 t (43,000 to 49,400 lb), supporting greater payload capability.Template:Fix/category[citation needed] The two-seat MiG-29KUB trainer variant is capable of executing combat missions identical to those of the single-seat model.[24]Template:Verify source

Cockpit and avionics

File:MAKS-2007-Radar.jpg
File:AESA JUK AE.jpg
Side-by-side comparison of Zhuk-ME (left) and Zhuk-AE (right)

The cockpit incorporates three multifunctional color liquid-crystal display screens (expanded to seven on the MiG-29KUB), a four-channel digital fly-by-wire control system, passive anti-radar missile homing capabilities, Sigma-95 GPS navigation, TopGun helmet-mounted targeting system, and integrated electronic countermeasures (ECM). An onboard oxygen generation system eliminates reliance on heavy oxygen tanks.[24]Template:Verify source Mission versatility is enhanced through optional optronic/infrared reconnaissance pods.[13][14]

The Zhuk-ME radar represents an evolution of the N010 Zhuk series, adding terrain mapping and tracking features. Weighing approximately 220 kilograms (490 lb), it offers enhanced signal processing and can detect a target with a radar cross-section of 5 m2 at distances up to 120 km (75 mi) in its export configuration.[25] In air-to-air mode, it can track up to ten targets concurrently and engage four simultaneously.[26] When operating in air-to-surface mode, it can identify a tank from as far as 25 kilometres (16 mi), detect bridges at ranges up to 120 kilometres (75 mi), and locate naval destroyers at distances reaching 300 kilometres (190 mi); it can track two surface targets simultaneously. The radar’s scanning coverage spans ±85 degrees azimuthally and +56/-40 degrees in elevation.[26]

The Zhuk-AE model was developed using a modular design approach that allows upgrading existing Zhuk ME radars on MiG-29 platforms to an active electronically scanned array (AESA) standard. India operates the Bars phased array radar on its Su-30MKI fleet and has identified AESA technology as essential for its MRCA contenders.Cite error: The opening <ref> tag is malformed or has a bad name The MiG-29K can also be equipped with an integrated infrared search and track (IRST) system combining optical and laser sensors.[24]Template:Verify source This IRST provides targeting data for both aerial and ground threats within a range of up to 15 km (9.3 mi), offering full 360-degree coverage along with detailed missile trajectory analysis at closer distances.

Armament and Defensive Systems

File:MiG-29K on the MAKS-2009 (02).jpg
A MiG-29K and its weaponry displayed at the MAKS Airshow. The wings are folded to optimize limited space aboard an aircraft carrier.

The MiG-29K is equipped with a GSh-30-1 30 mm cannon mounted in the port wing root. It supports deployment of laser-guided and electro-optical bombs, alongside various air-to-surface missiles such as Kh-25ML/25MP, Kh-29T, Kh-31G/31A, Kh-35U, and rocket pods. For anti-radiation missions, it utilizes Kh-31P missiles featuring passive radar seekers. The aircraft also carries anti-ship missiles including Kh-35 and Kh-31A variants, while air-to-air combat capabilities are provided by missiles like RVV-AE, R-27ER/ET, and R-73E. Additionally, the platform is compatible with a range of foreign armaments.Template:Fix/category[citation needed]

To boost survivability, the MiG-29K incorporates low-observable design elements, sophisticated electronic warfare systems, minimized ballistic vulnerability, and standoff weapon options.[18] Mikoyan states that extensive application of radar-absorbent materials reduces its radar cross-section by approximately four to five times compared to the baseline MiG-29 model.[18] The RD-33MK turbofan engine developed by Klimov contributes to lowering the infrared signature and enhancing camouflage effectiveness.[22][23]

India

File:A MiG-29K performs a touch and go landing on INS Vikramaditya during Narendra Modi's visit.jpg
MiG-29K from INAS 303 performs a low pass over the aircraft carrier Vikramaditya in 2014.

In January 2004, the Indian Navy placed an order for 12 single-seat MiG-29Ks and 4 two-seat MiG-29KUBs.[27] These aircraft were intended to fulfill dual roles of fleet air defense and surface strike missions. Deliveries commenced in December 2009.[28] Prior to arrival in India, the MiG-29Ks underwent trials aboard the Russian carrier Error: {{Ship}} missing name (help).[29] In January 2010, India and Russia finalized a contract valued at US$1.2 billion for an additional 29 MiG-29Ks for the Indian Navy.[30] The MiG-29K officially entered service with India in February 2010.[28] By the end of that year, six units had been delivered, followed by five more aircraft and a flight simulator supplied in May 2011. Additional deliveries were scheduled through 2012.[31][32] Initially stationed at INS Hansa near Goa on India's western coast, these fighters transitioned to operate from INS Vikramaditya, formerly the Soviet carrier Error: {{Ship}} missing name (help), after its induction into service in late 2013. The Vikramaditya can accommodate up to 24 MiG-29K/KUB fighters. India's first indigenously built carrier, INS Vikrant, also deploys this aircraft type but plans to transition to Rafale M jets starting from 2030.[31]

File:An Indian navy MIG-29K Fulcrum aircraft flies over USS Nimitz during Exercise Malabar 2017. (35174458953).jpg
MiG-29K of the Indian Navy flying over USS Nimitz during Exercise Malabar in 2017

Following a crash involving a MiG-29KUB during pre-delivery testing in Russia, further procurement by India was temporarily halted; the Defence Ministry expressed concerns over the aircraft's reliability.[33] Subsequently, Russian authorities attributed the accident to pilot error and assured there was no requirement to ground the fleet.[34] In August 2011, Mikoyan’s General Director Sergei Korotkov confirmed that the last five units from the initial contract would be delivered before year-end and that deliveries for a second batch of 29 aircraft would begin in 2012.Template:Fix/category[citation needed] By November 2012, sea trials for the MiG-29K/KUB with the Indian Navy were completed.[35] However, due to Western and Ukrainian sanctions impacting Russian manufacturers, Mikoyan faced difficulties importing components for assembly; consequently, many parts were installed directly on India's flightline.[36]

A report released in 2016 by India's Comptroller and Auditor General (CAG) highlighted multiple issues affecting engines, airframes, and fly-by-wire systems of the MiG fleet. Serviceability rates for MiG-29Ks were recorded at approximately 37.63%, while two-seat KUB variants ranged between roughly 21.30% and 47.14%. Furthermore, about 62% of engines (40 units) were withdrawn or rejected due to design flaws that potentially reduce operational lifespan below the specified 6000 flight hours.[37][38][39][40] Nonetheless, subsequent collaborative efforts between India and Russia reportedly improved fleet serviceability levels to near seventy percent by late 2018.[41] In early 2017, plans were announced by India’s government to replace its current MiGs with a new batch of fifty-seven carrier-capable fighters; contenders included France’s Dassault Rafale and America’s Boeing F/A‑18E/F Super Hornet.[42][43] Following evaluation trials conducted in2022,the Rafale M was selected by2025,but only26 units were procured.[44]

File:An Indian Navy MiG‑29K firing an R‑77‑1 BVR Air‑to‑Air Missile.jpg
MiG‑29K launching an R‑77 missile

During a press briefing ahead of Navy Day in December 2018,CNS Admiral Lanba stated that "currently there are no supply issues concerning spare parts from Russia... The MiG‑29K fleet is now performing satisfactorily." The Indian Navy intends to operate these fighters aboard its first domestically built carrier INS Vikrant, while procuring upgraded combat jets tailored for this platform. Admiral Sunil Lanba further confirmed that prior challenges related to maintenance and spare parts availability—which had impacted readiness—have been resolved. On May26 ,2023,a MiG‑29K successfully completed a night landing on INS Vikrant during sea trials.[45]

Throughout the 2025 India–Pakistan conflict, fifteen MiG‑29Ks were deployed aboard the INS Vikrant Carrier Battle Group operating in the Arabian Sea.Template:Fix/category[citation needed]

The Indian Navy has reportedly experienced multiple failures with the Zhuk-ME radar system installed on both MiG‑29K and KUB variants; their operational reliability dropped significantly with mean time between failures reducing to approximately sixty hours before malfunction.[46] This issue was corroborated by leaked documentation released by Black Mirror Hackers,a Ukrainian cyber group.[47]

Russia

File:Mikoyan-Gurevich MiG-29K ‘RF-92324 - 48 blue’ (36928677816).jpg
MiG-29KR of the Russian Navy displayed at Kubinka Airbase

The Russian Navy’s 279th Shipborne Fighter Aviation Regiment operates a squadron of 21 Su-33 fighters whose operational lifespan was projected to conclude by 2015. Approximately 10 to 12 of these aircraft are slated for upgrades, including the installation of the Gefest SVP-24 bombsight system, enhancing their capability for precision free-fall bombing and limited ground attack roles. However, the existing number of aircraft was insufficient. Restarting Su-33 production for a small batch proved less economical than leveraging the Indian Navy’s MiG-29K procurement. India invested $730 million for development and delivery of 16 MiG-29Ks, whereas equipping the Russian Navy with 24 units would amount to roughly $1 billion.

In late 2009, Russia placed an order for 24 MiG-29Ks intended for deployment on Admiral Kuznetsov. Deliveries commenced in 2010. By August 2011, final discussions were underway between MiG and Russian officials regarding an additional acquisition of MiG-29K/KUB aircraft. In February 2012, an official announcement confirmed an order comprising 20 MiG-29KR fighter-bombers and four MiG-29KUBR operational trainers to replace the Sukhoi Su-33 aboard Admiral Kuznetsov. In 2015, Major-General Igor Kozhin, commander of the Navy’s Air and Air Defence Forces, revealed plans to establish a second fighter regiment to supplement the current force. This new unit was expected to operate MiG-29s while some Su-33s would undergo refurbishment for continued service.

During October 2016, four MiG-29KR/KUBR aircraft from the 100th Independent Shipborne Fighter Aviation Regiment were part of the air wing aboard Admiral Kuznetsov as it deployed with its battle group to the Mediterranean Sea in support of Russia’s military operations in Syria. On 13 November 2016, one MiG-29KUBR crashed while returning to Admiral Kuznetsov during this Mediterranean deployment.

Variants

MiG-29K
Single-seat version operated by India.[24][48]
MiG-29KR
Russian single-seat model featuring replacement of Ukrainian and Indian components with Russian-made equipment.[36]
MiG-29KUB
Two-seat tandem operational trainer variant used by India.[24][48]
MiG-29KUBR
Russian two-seat tandem operational trainer version.[49]
MiG-29KVP
(KVP stands for Korotkaya Vzlet Posadka meaning Short Take-Off and Landing, STOL) A limited number of aircraft modified to article 9–12 standard (or possibly 9–18), equipped with enhanced high-lift devices, reinforced landing gear, and arrestor hook, intended for deck landing research and pilot instruction.[50]

Operators

File:Mikoyan MiG-29K Operators.png
Operators of the MiG-29K as of 2010
Template:IND
Template:RUS

Accidents

  • On 23 June 2011, a MiG-29KUB crashed during pre-delivery testing in Russia, resulting in the deaths of both pilots.[57][58]
  • A MiG-29KUBR went down on 13 November 2016 in the Mediterranean Sea while returning to the aircraft carrier Admiral Kuznetsov after completing a mission over Syria. The pilot was reportedly rescued.[49][59]
  • On 3 January 2018, an Indian Navy MiG-29K veered off the runway at Goa and caught fire; the pilot successfully ejected.[60]
  • An Indian Navy MiG-29KUB trainer crashed on 16 November 2019 following a bird strike and subsequent engine failure; both pilots managed to eject safely.[61][52]
  • A MiG-29K belonging to the Indian Navy crashed on 23 February 2020; fortunately, the pilot ejected without injury.[62][52]
  • On 26 November 2020, an Indian Navy MiG-29KUB trainer aircraft crashed into the sea resulting in one fatality; one pilot was rescued while another was missing.[63]
  • An Indian Navy MiG-29K crashed off the coast of Goa near INS Hansa on 12 October 2022; the pilot was successfully rescued.[51][64]

Specifications (MiG-29K - Izdeliye 9.41)

Three-view illustration of MiG-29
Three-view illustration of MiG-29
File:RD33MK MAKS2009.jpg
Klimov RD-33MK engine showcased at MAKS 2009
File:Mikoyan and Gurevich MiG-29K navy fighter (3968610670).jpg
Mechanism for wing folding
File:Mikoyan and Gurevich MiG-29K navy fighter (3967836277).jpg
Aerial refuelling probe

Template:Aircraft specs

See also

Lua error in mw.title.lua at line 359: bad argument #2 to 'title.new' (unrecognized namespace name 'Portal'). Template:Aircontent

References

Notes
  1. ↑ Aviation experts Bill Gunston and Yefim Gordon described this preference for the Su-33 over the MiG-29K as "astonishing," highlighting that the Su-33 was costlier and lacked surface strike missile capabilities.[10] Some analysts argue that the MiG-29K was considered only as a backup should the Su-33 prove too heavy for carrier operations, noting that Soviet naval priorities centered on fleet air defense rather than strike roles.[3] Others attribute this decision to political influence, pointing out that Sukhoi’s chief designer, Mikhail Simonov, held a position within the Committee of the Supreme Soviet overseeing aircraft manufacturing.[11][12]
Citations
  1. ↑ Belyakov & Marmain 1994, pp. 446–449.
  2. ↑ Belyakov & Marmain 1994, p. 449.
  3. ↑ 3.0 3.1 Bangash 2008, p. 281.
  4. ↑ 4.0 4.1 Gordon & Davison 2005, p. 40.
  5. ↑ Belyakov & Marmain 1994, pp. 449–450.
  6. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  7. ↑ Belyakov & Marmain 1994, p. 452.
  8. ↑ Williams 2002, p. 129.
  9. ↑ Donald and March 2001, pp. 152–153.
  10. ↑ Gunston and Gordon 1998, p. 254.
  11. ↑ Williams 2002, p. 177.
  12. ↑ Eden 2004, p. 462.
  13. ↑ 13.0 13.1 13.2 13.3 Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  14. ↑ 14.0 14.1 14.2 14.3 Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  15. ↑ Rininger 2006, p. 124.
  16. ↑ Conley 2001, p. 69.
  17. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  18. ↑ 18.0 18.1 18.2 Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  19. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  20. ↑ Williams 2002, p. 128
  21. ↑ Gordon & Davison 2005, pp. 46, 92.
  22. ↑ 22.0 22.1 Cite error: Invalid <ref> tag; no text was provided for refs named Ref01
  23. ↑ 23.0 23.1 Cite error: Invalid <ref> tag; no text was provided for refs named Ref02
  24. ↑ 24.0 24.1 24.2 24.3 24.4 Cite error: Invalid <ref> tag; no text was provided for refs named deagel
  25. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named Bharat
  26. ↑ 26.0 26.1 Cite error: Invalid <ref> tag; no text was provided for refs named Rosoboronexport Catalogue
  27. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  28. ↑ 28.0 28.1 Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  29. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  30. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  31. ↑ 31.0 31.1 Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  32. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  33. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  34. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  35. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  36. ↑ 36.0 36.1 Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  37. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  38. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  39. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  40. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  41. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  42. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  43. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  44. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  45. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  46. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  47. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  48. ↑ 48.0 48.1 48.2 Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  49. ↑ 49.0 49.1 Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  50. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  51. ↑ 51.0 51.1 Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  52. ↑ 52.0 52.1 52.2 Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  53. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  54. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  55. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  56. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  57. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  58. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  59. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  60. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  61. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  62. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  63. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  64. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
Bibliography
  • Bangash, M.Y.H. Shock, Impact and Explosion: Structural Analysis and Design. Springer, 2008. ISBN 3-540-77067-4.
  • Belyakov, R.A. and Marmain, J. MiG: Fifty Years of Secret Aircraft Design. Shrewsbury, UK: Airlife, 1994. ISBN 1-85310-488-4.
  • Conley, Jerome M. Indo-Russian military and nuclear cooperation: lessons and options for U.S. policy in South Asia. Lexington Books, 2001. ISBN 0-7391-0217-6.
  • Day, Jerry. "Hot Hot Hot!" Air Classics, Vol. 45, No. 4, April 2009.
  • Donald, David and March, Daniel J. Carrier Aviation Air Power Directory. Norwalk, CT: AIRtime Publishing, 2001. pp. 152–153. ISBN 1-880588-43-9.
  • Eden, Paul (ed.). The Encyclopedia of Modern Military Aircraft. London: Amber Books, 2004. ISBN 1-904687-84-9.
  • Gordon, Yefim and Davison, Peter. Mikoyan Gurevich MiG-29 Fulcrum. North Branch, Minnesota: Specialty Press, 2005. ISBN 1-58007-085-X.
  • Gordon, Yefim. Mikoyan MiG-29. Hinckley, UK: Midland Publishing, 2006. ISBN 978-1-85780-231-3.
  • Gunston, Bill and Gordon, Yefim. MiG Aircraft Since 1937. North Branch, Minnesota: Naval Institute Press, 1998. ISBN 1-55750-541-1.
  • Lake, Jon. Jane's How to Fly and Fight in the Mikoyan MiG-29. New York: HarperCollins, 1997. ISBN 0-00-472144-6.
  • Rininger, Tyson V. Red Flag: Air Combat for the 21st Century. Grand Rapids, Michigan: Zenith Imprint, 2006. ISBN 0-7603-2530-8.
  • Williams, Mel (ed.). Superfighters: The Next Generation of Combat Aircraft, chapter on Sukhoi 'Super Flankers'. Norwalk, Connecticut: AIRtime Publishing Inc., 2002. ISBN 1-880588-53-6.

External links

File:Commons-logo.svg
Wikimedia Commons has media related to Mikoyan-Gurevich MiG-29K (Russian navy).Template:Preview warning

Template:External media

Template:Mikoyan aircraft

Retrieved from "https://www.alfawiki.org/index.php?title=Mikoyan_MiG-29K&oldid=75063"