Jump to content

Mikoyan MiG-29

From Alfawiki
Mikoyan
IndustryAerospace, Defense
Founded1939
Headquarters
Moscow
,
Russia
ProductsMilitary aircraft, including MiG-29 fighter jet

Overview

The Mikoyan MiG-29 (Russian: Микоян МиГ-29), known by its NATO code name Fulcrum, is a twin-engine fighter aircraft originally developed in the Soviet Union. Created by the Mikoyan design bureau during the 1970s, this jet was intended primarily as an air superiority fighter. Alongside the larger Sukhoi Su-27, it was engineered to challenge American fighters such as the McDonnell Douglas F-15 Eagle and the General Dynamics F-16 Fighting Falcon. The MiG-29 officially entered operational service with the Soviet Air Forces in 1983.

Initially focused on engaging enemy aircraft, many MiG-29s have since been adapted into versatile multirole fighters, capable of executing a wide range of missions. They are commonly equipped to deploy various air-to-surface weapons and precision-guided munitions. The MiG-29 family includes several significant variants, such as the multirole Mikoyan MiG-29M and the carrier-capable Mikoyan MiG-29K. The most advanced iteration currently available is the Mikoyan MiG-35. Newer versions often feature upgraded engines, glass cockpit displays with HOTAS ("hands-on-throttle-and-stick") controls, enhanced radar and infrared search and track (IRST) systems, and substantially increased fuel capacity; some units are also fitted for aerial refueling.

After the collapse of the Soviet Union, numerous former Soviet republics continued operating the MiG-29, with the largest operator being the Russian Aerospace Forces. Russia has aimed to modernize its fleet through the MiG-29SMT upgrade program; however, financial constraints have limited the number of deliveries. The MiG-29 has enjoyed widespread export success, having been operated by over 30 countries worldwide. As of As of 2024, Flight Global reports that approximately 809 MiG-29s across all variants remain active in military service, ranking it as the fifth most prevalent fighter aircraft globally.

Origins

During the mid-1960s, the United States Air Force (USAF) faced significant challenges over Vietnam's airspace. Supersonic fighter-bombers, such as the F-105 Thunderchief, which were optimized for low-altitude strike missions, proved vulnerable against both older MiG-17 models and more advanced, highly maneuverable MiGs. To reestablish limited air dominance, the US shifted focus toward air combat using the F-4 Phantom multirole fighter, while the Soviet Union responded with the development of the MiG-23. By the late 1960s, the USAF initiated the "F-X" program aimed at creating a dedicated air superiority fighter, culminating in the order for production of the McDonnell Douglas F-15 Eagle in 1969.

Amidst Cold War tensions, it became imperative for the Soviet Union to counterbalance potential technological superiority by the United States. Consequently, developing a new air superiority aircraft was prioritized. In 1969, the Soviet General Staff issued a requirement for a Perspektivnyy Frontovoy Istrebitel (PFI, meaning "Advanced Frontline Fighter"). The specifications were notably demanding, calling for extended range, robust short-field capabilities (including operation from rough runways), exceptional maneuverability, speeds exceeding Mach 2, and substantial firepower. The aerodynamics institute TsAGI collaborated closely with the Sukhoi design bureau to refine the aircraft’s aerodynamic profile.

File:Soviet MiG-29 DF-ST-99-04977.JPG
A Soviet Air Forces MiG-29 displayed after a flight demonstration at the Abbotsford Air Show, 1989

By 1971, Soviet assessments revealed a requirement for multiple fighter categories. The PFI initiative was complemented by the Perspektivnyy Lyogkiy Frontovoy Istrebitel (LPFI, or "Advanced Lightweight Tactical Fighter") program; plans projected that approximately one-third of fighters would be PFI and two-thirds LPFI. This division mirrored the USAF’s "Lightweight Fighter" program that produced aircraft like the General Dynamics F-16 Fighting Falcon and Northrop YF-17. The PFI contract was awarded to Sukhoi, resulting in the Sukhoi Su-27, while Mikoyan undertook development of the lightweight fighter. Detailed design efforts for Mikoyan’s Product 9, designated MiG-29A, commenced in 1974, with its maiden flight occurring on 6 October 1977. The pre-production model was first detected by United States reconnaissance satellites in November that year and was codenamed Ram-L due to its location at Zhukovsky flight test center near Ramenskoye.

The distinction between TPFI and LPFI roles became clearer as the MiG-29 entered operational service with the Soviet Air Forces (Russian: Voenno-Vozdushnye Sily [VVS]) during the mid-1980s. While the larger, longer-range Su-27 was assigned to undertake complex and high-risk deep air-to-air missions targeting NATO's strategic assets, the more compact MiG-29 took over from the MiG-23 in frontline tactical aviation duties.

Introduction and Enhancements

In Western countries, the newly introduced fighter received the NATO reporting name "Fulcrum-A" because the pre-production MiG-29A, which logically should have been assigned this code, was not yet known in the West. The Soviet Union typically did not assign formal names to most of its aircraft, although informal nicknames were frequently used. Interestingly, some Soviet aviators regarded the MiG-29's NATO codename, "Fulcrum", as an apt and even complimentary reflection of the aircraft’s mission, and it is occasionally used unofficially within Russian forces.

Export versions of the MiG-29 were widely distributed in downgraded forms, designated as MiG-29 9-12A for Warsaw Pact members and MiG-29 9-12B for countries outside that alliance. These variants featured less advanced avionics and lacked the capability to deploy nuclear weapons.

During the 1980s, Mikoyan introduced the enhanced MiG-29S model designed to carry longer-range R-27E air-to-air missiles. This variant incorporated a dorsal 'hump' on the upper fuselage to accommodate a jamming system along with additional fuel storage. The aircraft’s weapons payload capacity was increased to 4,000 kg (8,800 lb) through structural reinforcement of the airframe. These improvements were implemented both on newly manufactured units and as upgrades to existing MiG-29s.

File:Mig-29 on landing.jpg
A Russian Air Force MiG-29UB trainer touching down

The Soviet Union deployed refined MiG-29 models equipped with upgraded avionics; however, Mikoyan's multirole variants—including a carrier-capable version known as the MiG-29K—never reached large-scale production. Development of the MiG-29K carrier variant was halted for more than ten years before resuming, ultimately entering service with the Indian Navy aboard the INS Vikramaditya and with the Russian Navy on the Admiral Kuznetsov class aircraft carrier. Mikoyan also advanced improved models such as the MiG-29M and its variant MiG-29SMT.

File:Kubinka East Ramp. 23-8-2017 (37434151656).jpg
Various MiG-29s of Russian Naval Aviation stationed at Kubinka, alongside newer and heavier Su-30SM aircraft

Multiple upgrade programs have been carried out on the MiG-29 platform. Typical enhancements include integration of NATO-compatible avionics, extension of service life to 4,000 flight hours, improvements in safety features, increased combat effectiveness, and enhanced reliability.

Replacement

On 11 December 2013, Russian Deputy Prime Minister Dmitry Rogozin announced plans to develop a new fighter aircraft intended to succeed the MiG-29. While the Sukhoi Su-27 and its variants were set to be replaced by the Sukhoi Su-57, a distinct design was necessary for a direct successor to the lighter MiG series. An earlier effort in the 1990s to create a MiG-29 replacement, known as the MiG 1.44 demonstrator, did not come to fruition.Template:Fix/category[citation needed] The idea resurfaced in 2001, drawing interest from India; however, they ultimately chose a Su-57 variant instead. Russian Air Force leadership has suggested the potential development of a single-engine model utilizing the Su-57’s engine, radar, and armament systems primarily for domestic deployment.[1] This concept has since been identified as the Sukhoi Su-75 Checkmate. Concurrently, within Russian service, the MiG-29 has been largely supplanted by the Sukhoi Su-30SM, indicating a decline in market share for the MiG-29 family in favor of heavier Sukhoi platforms.Template:Fix/category[citation needed]

Design

File:Mig-29UB.jpg
MiG-29UB from the Swifts aerobatic team

Originating from the initial PFI specifications formulated by TsAGI, the MiG-29 exhibits many aerodynamic traits similar to those of the Sukhoi Su-27, though with several distinct characteristics. The aircraft features mid-mounted swept wings equipped with blended leading-edge root extensions (LERXs) angled at approximately 40°. It is fitted with swept tailplanes and twin vertical stabilizers positioned on booms located outside the engine nacelles. The wings' leading edges incorporate automatic slats—four segments on early variants and five segments on some later models. On the trailing edges, maneuvering flaps and wingtip ailerons are present.[2]

The MiG-29 employs hydraulic flight controls along with a SAU-451 three-axis autopilot system but lacks a fly-by-wire system found on the Su-27. Nevertheless, it maintains exceptional agility, demonstrating superior instantaneous and sustained turning capabilities, high-alpha maneuvering proficiency, and strong spin resistance. The airframe is predominantly constructed from aluminum combined with select composite materials,[3] designed to withstand maneuvers up to 9 g (88 m/s²). Its control system incorporates "soft" limiters that prevent pilots from exceeding maximum g-forces and angle-of-attack thresholds; however, these restrictions can be manually overridden.[2]

Powerplant, performance and range

File:Klimov RD-33 turbofan engine.JPG
RD-33 exhibited at the Luftwaffenmuseum of the Bundeswehr
File:Bangladesh Air Force MiG-29 (15) (cropped).png
A Bangladesh Air Force MiG-29 airborne, with its Klimov RD-33 turbofan engines operating at full afterburner power

Equipped with two widely spaced Klimov RD-33 turbofan engines, the MiG-29 delivers thrust rated at approximately 50 kilonewtons (11,200 lbf) in dry mode and 81.3 kilonewtons (18,300 lbf) when using afterburners. The gap between these engines contributes to lift generation, effectively lowering the wing loading and enhancing agility. Air intake is managed through variable ramps located beneath the leading-edge extensions (LERXs), designed to support high-Mach velocity flight. The engines' relatively short combustion chambers result in a more pronounced smoke trail compared to similar aircraft of its era. To accommodate operations from unprepared airfields, the primary air inlet can be fully sealed, while an auxiliary intake positioned on the upper fuselage supplies air during takeoff, landing, and low-altitude maneuvers, thereby minimizing the risk of ingesting debris. In this mode, air enters through automatically opening louvers on the LERXs. However, this feature was removed in the latest variant, the MiG-35, which instead employs mesh screens within the main intakes akin to those used on the Su-27.

The MiG-29’s ferry range extends up to 1,500 km (930 mi) without additional fuel tanks and increases to approximately 2,100 km (1,300 mi) when equipped with external tanks. The original MiG-29 (Fulcrum-A) holds an internal fuel volume of 4,300 L (950 imp gal; 1,100 US gal), distributed among six internal tanks—four housed within the fuselage and one in each wing. The MiG-29 (Fulcrum-C) variant features a slightly larger internal fuel capacity of 4,540 L (1,000 imp gal; 1,200 US gal), attributed to an expanded #1 fuselage tank. For extended missions, fuel capacity can be augmented by a 1,500 L (330 imp gal; 400 US gal) centerline drop tank on the Fulcrum-A and two underwing drop tanks each holding 1,150 L (250 imp gal; 300 US gal) on later production models. Additionally, newer versions incorporate a port-side aerial refueling probe compatible with a Probe and drogue system, significantly extending operational endurance through inflight refueling.

Cockpit

File:MiG-29 cockpit 3.jpg
MiG-29 cockpit, 1995

The cockpit is equipped with a traditional centre stick and throttle positioned on the left side. The pilot is seated in a K-36DM ejection seat manufactured by NPP Zvezda.

Instrumentation consists of standard analog gauges complemented by a head-up display (HUD) and a Shchel-3UM helmet mounted display. However, it lacks HOTAS functionality. The design prioritizes similarity to earlier Soviet aircraft such as the MiG-23 to facilitate pilot transition rather than focusing on modern ergonomic principles. Despite this, the MiG-29 provides significantly enhanced visibility compared to prior Soviet jets, largely due to its elevated bubble canopy. Later variants introduce advanced "glass cockpit" configurations featuring contemporary liquid-crystal multi-function displays (MFDs) along with genuine HOTAS controls.Template:Fix/category[citation needed]

Sensors

The standard MiG-29 9.12 model incorporates a Phazotron RLPK-29 fire control system radar suite, which includes the N019 Sapfir 29 coherent pulse-Doppler radar capable of look-down/shoot-down operations, paired with the Ts100.02-02 digital computer.[4]

File:German MIG-29 Nose.jpg
MiG-29 nose showing radome and S-31E2 KOLS IRST

Rather than being an entirely new creation, the N019 radar evolved from the Sapfir-23ML system used on the MiG-23ML. In the mid-1970s design phase, Phazotron NIIR was assigned to develop a modern radar for the MiG-29. To accelerate progress, they adapted technology from NPO Istok’s experimental "Soyuz" radar project. Initially, the plan was for the N019 to utilize a flat planar array antenna combined with full digital signal processing, aiming for a detection and tracking range exceeding 100 km (62 mi) against fighter-sized targets. However, prototype evaluations showed these goals were unattainable within the required development timeline and spatial constraints of the MiG-29’s nose. Consequently, Phazotron reverted to using a modified twisted-polarization cassegrain antenna from the Sapfir-23ML and conventional analog processing, supplemented by a new Ts100 digital computer designed by NII Argon to reduce cost and time. This resulted in an operational radar but retained limitations of its predecessor that hindered effective detection and tracking at distances compatible with missiles like the R-27 and R-77.

File:MiG-29 gun.jpg
MiG-29UB on display, showing gunport

The effectiveness of the N019 radar was further diminished after Phazotron engineer Adolf Tolkachev leaked its design details to the CIA, leading to his execution in 1986. In response to these challenges, Soviet engineers quickly developed an improved variant known as the N019M Topaz radar for the enhanced MiG-29S version. Nonetheless, reports suggest that the VVS remained dissatisfied with its capabilities and requested additional enhancements. The most recent upgrade, embodied in the MiG-29M model, introduced the N010 Zhuk-M radar featuring a planar array antenna instead of a dish, which extends detection range and offers superior processing power. This system supports multiple target engagement and is compatible with advanced missiles such as the Vympel R-77 (RVV-AE).[5]

Armament

File:Bangladesh Air Force MiG-29 (5) (cropped).png
Bangladesh Air Force MiG-29 displaying its complete underside. Notice the six underwing pylons equipped with R-27 and R-73 air-to-air missiles. The centerline fuel tank is visible alongside an APU exhaust vent.

The MiG-29 is armed with a single GSh-30-1 30 mm (1.18 in) cannon located in the port wing root. Initially, this cannon was supplied with a 150-round magazine, but subsequent models reduced this capacity to 100 rounds, limiting firing duration to a few seconds before ammunition depletion. Early production MiG-29s are unable to operate the cannon when a centerline fuel tank is attached, as it obstructs the shell ejection path; this issue was resolved in the MiG-29S and later iterations.

Each wing supports three pylons (with some variants featuring four), resulting in a total of six or eight pylons. The inner pylons can accommodate a 1,150 L (250 imp gal; 300 US gal) fuel tank, one Vympel R-27 (AA-10 "Alamo") medium-range air-to-air missile, or unguided bombs and rockets. Certain Soviet models were capable of carrying a single nuclear bomb on the port inboard station. Outer pylons typically mount R-73 (AA-11 "Archer") close-range air-to-air missiles, though some operators still use the older R-60 (AA-8 "Aphid"). Additionally, a 1,500 L (330 imp gal; 400 US gal) fuel tank can be fitted on the centerline between the engines.Template:Fix/category[citation needed]

The United States has provided Ukraine with AGM-88 HARM missiles, which appear to be launched from MiG-29 aircraft. This information surfaced after Russian forces released footage showing the tail fin of one such missile. U.S. Under Secretary of Defense for Policy Colin Kahl commented: "I would highlight two points. First, considerable attention was given months ago to the MiG-29 issue, but less noticed is the extensive support we've provided through spare parts and other means to enable Ukraine to deploy more of their MiG-29s and maintain those already flying for extended periods. Second, recent Presidential Drawdown Authority packages have included several anti-radiation missiles compatible with Ukrainian aircraft, capable of targeting Russian radar systems."[6] Due to their Soviet-era design, these aircraft lack the onboard computer systems required to integrate NATO-standard armaments directly. Although challenging, with relatively simple adaptations such as an electronic tablet interface, it becomes feasible to operate these weapons.[7]

Operational history

Although the MiG-29's exact performance remained largely speculative from its debut in 1977 until the mid-1980s, ongoing intelligence efforts combined with increased exposure through Soviet export programs eventually revealed its true capabilities. The initial MiG-29 models were highly maneuverable fighters, matching the agility of contemporary aircraft such as the F-18 and F-16. Nevertheless, their limited fuel reserves confined them primarily to short-range air defense roles. Early versions lacked features like HOTAS controls and inter-aircraft data links, requiring pilots to adopt a demanding "heads-down" method to manage cockpit instruments, which reduced their situational awareness compared to pilots flying equivalent Western fighters. Experts and Western aviators who tested the MiG-29 concluded that these limitations likely prevented even skilled pilots from fully exploiting the aircraft’s combat potential. Subsequent upgrades enhanced the MiG-29’s operational effectiveness. The Soviet Union supplied MiG-29s to various nations; however, due to the complexity of fourth-generation fighters—demanding extensive pilot training, robust air-defense systems, and ongoing maintenance—its operational record has varied across different air forces.

Soviet Union and successor states

The MiG-29 was unveiled to Western audiences for the first time on 2 July 1986 during a Soviet display in Finland. Two additional MiG-29s appeared at the Farnborough Airshow in the United Kingdom in September 1988. The following year, the aircraft performed flight demonstrations at the 1989 Paris Air Show, where one experienced a non-fatal accident during the event’s opening weekend. This appearance marked only the second occasion since the 1930s that Soviet fighters were exhibited at an international air show. Observers from the West noted its impressive capabilities and remarkable agility. The MiG-29’s sole combat deployment under Soviet command occurred in 1987–1988 when the 115th GvIAP was stationed at Termez Airfield in Turkmenistan to protect Soviet forces in Afghanistan, particularly around Kabul. This deployment was effective; according to differing accounts placing it in either August or September, four SU-22M3 aircraft from the DRAAF defected and attempted an attack on Kabul but were promptly intercepted and shot down by MiG-29s. After the collapse of the Soviet Union, most MiG-29 units were absorbed into the newly established Russian Air Force.

Russia

File:Pugachev Cobra.svg
Illustration of the MiG-29 executing the super maneuver, known as Pugachev's Cobra

In July 1993, two MiG-29 aircraft from the Russian Air Force collided mid-flight and crashed out of public view during the Royal International Air Tattoo. Fortunately, no serious injuries occurred on the ground, and both pilots successfully ejected and survived.[8]

File:MiG-29SMT on the MAKS-2009 (01).jpg
MiG-29SMT displayed at the 2011 MAKS airshow

Following a crash in Siberia on 17 October 2008, the Russian Air Force temporarily grounded its entire MiG-29 fleet.Template:Fix/category[citation needed] After another MiG-29 accident in eastern Siberia in December 2008,[9] Russian authorities acknowledged that a majority of their MiG-29 fighters were unfit for combat missions due to inadequate maintenance. Additionally, the advanced age of approximately 70% of the fleet rendered many aircraft unairworthy.Template:Fix/category[citation needed] Since the Soviet Union's dissolution, these jets had not undergone modernization. Flight operations with MiG-29s resumed on 4 February 2009.Template:Fix/category[citation needed] Nevertheless, inspections in March 2009 revealed corrosion issues affecting 91 MiG-29s, requiring repairs; around 100 jets were deemed safe to continue flying.[10][11] The Russian Aerospace Forces initiated upgrades converting early MiG-29 models to the more advanced MiG-29SMT variant,[12] but financial constraints limited deliveries to only three upgraded aircraft.Template:Fix/category[citation needed] Instead, Russia acquired the batch of 35 MiG-29SMT/UBTs that Algeria declined.[13]Template:Verify source On April 15, 2014, Russia ordered an additional sixteen newly manufactured MiG-29SMTs, with expected delivery by 2017.[14]

A MiG-29 crashed during a training flight near Astrakhan on June 4, 2015,[15] and another incident occurred a month later near Kushchevskaya village in Krasnodar region where the pilot ejected safely.[16] The surge in accidents within the Russian Aerospace Forces throughout 2015 was largely attributed to increased flight operations and training exercises.[17]

On April 20, 2008, Georgian authorities reported that a Russian MiG-29 had downed a Georgian Hermes 450 unmanned aerial vehicle and released footage showing what appeared to be a MiG-29 firing an air-to-air missile at it. Russia denied ownership of the aircraft and stated no pilots were airborne that day. Meanwhile, Abkhazia's government claimed its forces shot down the drone using an L-39 fighter for violating Abkhaz airspace and ceasefire terms.[18] A United Nations inquiry confirmed the video's authenticity and concluded that either a Russian MiG-29 or Su-27 had destroyed the drone using an R-73 heat-seeking missile.[19]

On July 16, 2014, Ukrainian officials asserted that a Ukrainian Su-25 was shot down by a Russian MiG-29 employing an R-27T missile;[20][21] Russia refuted these claims.[22]

In early September of 2017, the Russian Aerospace Forces deployed several MiG-29SMT multirole fighters to Khmeimim Airbase near Latakia in western Syria—marking the first deployment of this upgraded Fulcrum model in active combat during the Syrian Air War.[23] These aircraft participated in bombing sorties and provided escort for strategic bombers.[24]

Two Russian-operated MiG-29s linked to Wagner Group crashed near Sirte, Libya on June 28 and September 7, 2020 respectively.[25]

Ukraine

File:181009-Z-VM449-513.jpg
A Ukrainian MiG-29, 2018

In April 2014, amid the Russian annexation of Crimea, Russian forces reportedly seized 45 MiG-29 fighters and four L-39 combat trainers from the Ukrainian Air Force at Belbek air base. Most of these aircraft were found to be non-operational. By May, Russian troops had dismantled the planes and transported them back to Ukraine. On 4 August 2014, Ukrainian authorities announced that several of these jets had been restored to operational status to participate in combat operations in eastern Ukraine.[26]

At the onset of the Donbas conflict in April 2014, the Ukrainian Air Force deployed jet fighters over Donetsk for combat air patrols and show-of-force missions. Due to a limited fleet, a MiG-29 from the Ukrainian Falcons aerobatic team was observed flying armed with a full complement of air-to-air missiles during a low-altitude pass.[27] On the evening of 7 August 2014, a Ukrainian MiG-29MU1 bearing the tail number 02 Blue was downed by an anti-aircraft missile launched by pro-Russian insurgents near Yenakievo; the aircraft exploded midair but the pilot ejected safely.[28][29][30] On 17 August 2014, another MiG-29 of the Ukrainian Air Force, identified as tail number 53 White and assigned to air-to-ground missions against separatist targets,[31] was shot down by pro-Russian forces in Luhansk region. The Ukrainian government confirmed this loss; the pilot ejected without injury and was subsequently rescued by allied troops.[32][33]

File:UA signed AGM-88 HARM.jpg
A MiG-29 equipped with an AGM-88 HARM missile

By 2018, the Lviv State Aircraft Repair Plant initiated a domestic modernization program to enhance the MiG-29’s capabilities into a multirole platform designated as MiG-29MU2. This upgrade was projected for completion in 2019, with production slated for commencement in 2020.[34] The initial upgraded MiG-29 was delivered to Ukraine’s Air Force in July 2020.[35] On May 29, 2020, Ukrainian MiG-29s participated alongside American B-1B bombers in the Bomber Task Force mission over the Black Sea region for the first time.[36] In September that year, B‑52 bombers from the 5th Bomb Wing conducted essential integration exercises alongside Ukrainian MiG‑29s and Su‑27s within Ukraine’s airspace.[37][38]

File:MiG-29 (Ghost of Kyiv) 40thTAB.jpg
MiG‑29s from the 40th Tactical Aviation Brigade, photographed in 2023

Throughout the 2022 Russian invasion of Ukraine, both Su‑27 and MiG‑29 fighters served primarily as air superiority platforms. Reports indicate that ten MiG‑29s were lost either on the ground or during flight operations.[39][40][41][42][43][44][45] In August of that year, a senior official from U.S. defense revealed that Ukraine had successfully integrated the AGM-88 HARM missile onto their MiG jets,Cite error: Closing </ref> missing for <ref> tag Subsequently, in 1989, India acquired an additional 20 MiG-29s, followed by another batch of ten in 1994.[46] During the 1999 Kargil War against Pakistan, the IAF deployed MiG-29s extensively, primarily to escort Mirage 2000 jets executing strikes with laser-guided bombs.[47]

Since their induction, these fighters have undergone multiple modernization phases involving upgrades to avionics, subsystems, engines, and radar systems.[48] Between 2005 and 2006, India inked an $888 million contract with Russia to enhance its entire MiG-29 fleet, aiming to prolong their service life by a decade to fifteen years.[49] This upgrade initiative was slated for completion within four years and included retrofitting aircraft with advanced avionics such as replacing the N-019 radar with the Phazatron Zhuk-M variant. The modifications also enabled deployment of R-77 missiles and incorporated mid air refueling capabilities for extended operational range.[50] In 2007, Hindustan Aeronautics Limited (HAL) secured a license to locally manufacture 120 RD-33 series 3 turbofan engines as part of this upgrade program.[51]

File:Mikoyan-Gurevich MiG-29UPG Fulcrum, India - Air Force JP7677166.jpg
An Indian Air Force MiG-29UPG after modernization

In March 2008, India renewed its agreement with Russia, committing $960 million for upgrading its existing fleet of 69 MiG-29s to extend their operational lifespan by an additional 25 to 40 years.[52] The modernization would elevate these aircraft to the MiG-29UPG standard. The first six jets were sent to Russia for refurbishment while HAL was tasked with upgrading the remaining 63 units domestically.[52] Enhancements included a new weapon control system, improved cockpit ergonomics, integration of the DRDO/DARE D-29 electronic warfare suite, and upgraded armaments comprising air-to-ground missiles and precision-guided munitions.[53][54][55] Additionally, India contracted Israel Aircraft Industries to supply avionics and subsystems essential for this upgrade.[52] The initial six aircraft were dispatched to Russia in 2008.[56] The first trio of upgraded jets was delivered back to India in December 2012, experiencing a delay exceeding two years from the original schedule.[57]

In early 2009, concerns arose within the IAF following the grounding of 90 Russian MiG-29s after a crash incident.[58] However, after thorough inspections in March of that year, all Indian MiG-29s were declared safe for operation.[59] The Indian Defence Minister disclosed in Parliament that structural issues had been detected involving potential corrosion-induced cracks in the tail fin. This problem surfaced after a Russian Air Force MiG-29 crash in December 2008. Following Russia’s communication of these findings to India, a comprehensive maintenance and repair program was initiated to address these flaws.[60]

File:A MiG-29K performs a touch and go landing on INS Vikramaditya during Narendra Modi's visit.jpg
An Indian Navy MiG-29K executing a touch-and-go landing on INS Vikramaditya

In 2004, India signed an agreement for procuring an additional 16 MiG-29Ks intended for deployment aboard INS Vikramaditya, the refurbished Russian aircraft carrier acquired by the Indian Navy. Later in January 2010, a $1.2 billion contract was finalized between India and Russia for acquiring another batch of 29 MiG-29Ks, increasing total orders for this naval variant to 45 aircraft.[61] The Indian Navy officially inducted the MiG-29K into service on 19 February 2010.[62]

By 2020, India planned to place an order for an extra 21 MiG-29 fighters. These would be assembled from airframes manufactured in the late 1980s but never previously completed. Prior to delivery to the IAF, these aircraft would undergo modern upgrades.[63][64][65] On August 7, 2024, the IAF issued a Request for proposal aimed at upgrading 24 MiG-29s with integration capabilities for High Speed Low Drag Bombs possessing ranges up to 180 km (110 mi). This enhancement would involve installing hardware such as bomb racks on external hardpoints, alongside necessary software modifications. The upgrade is planned to be executed across the entire MiG-29 fleet progressively.[66][67]

Yugoslavia and Serbia

File:Serbian mig-29 missiles.jpg
MiG-29 of the Serbian Air Force and Air Defence

The SFR Yugoslavia was the earliest European nation outside the Soviet bloc to introduce the MiG-29 into its air force. Between 1987 and 1988, the USSR delivered 14 MiG-29 9.12A models along with two MiG-29UB trainers to Yugoslavia. These fighters were assigned to the 127th Fighter Aviation Squadron, which operated from Batajnica Air Base, located just north of Belgrade, Serbia.

During the dissolution of Yugoslavia, the MiG-29s had limited combat engagement, primarily conducting ground attack missions. In 1991, a Yugoslav MiG-29 destroyed several Croatian-operated Antonov An-2 planes on the ground at the airfield in Čepin, near Osijek, Croatia, without suffering any losses itself. On 7 October 1991, at least two MiG-29s executed an air raid targeting Banski Dvori, the official residence of the Croatian Government.

Following the breakup, the MiG-29s remained operational within the Federal Republic of Yugoslavia. However, due to a United Nations arms embargo, maintenance standards declined significantly. Scheduled overhauls planned for 1996 and 1997 were not performed, resulting in deteriorated aircraft conditions.

During NATO's intervention in the Kosovo War, six MiG-29s were shot down: four by United States Air Force F-15 fighters, one by a USAF F-16, and another by a Royal Netherlands Air Force F-16. One pilot reported that one aircraft was downed by friendly ground fire. Additionally, four MiG-29s were destroyed while on the ground. An Argentine source claims a MiG-29 shot down an F-16 on 26 March 1999; however, this claim is contested since the referenced F-16C reportedly crashed in the United States on that same day.

A MiG-29 9.12A operated by the Yugoslav Air Force during Operation Allied Force in 1999.
A digital depiction of a MiG-29 9.12A serving with the Air Force of Serbia and Montenegro during Operation Allied Force in 1999

Post-conflict, the Air Force of Serbia and Montenegro maintained operations with its remaining five MiG-29s at a minimal tempo. Reports emerged in spring 2004 indicating cessation of flight operations due to maintenance challenges; nevertheless, these five aircraft were subsequently sent to Russia for refurbishment. In July 2009, a Serbian Air Force MiG-29 crashed near Belgrade. During summer 2014, Serbia’s limited MiG-29 fleet was grounded for approximately four months because of difficulties in acquiring replacement batteries.

In November 2016, Russia agreed to donate six MiG-29s at no cost, contingent upon Serbia covering $50 million in refurbishment expenses. By late January 2017, Serbian Defense Minister Zoran Đorđević announced Belarus had also pledged eight MiG-29s as a free donation. Russia completed delivery of its six aircraft in early October 2017 via Antonov An-124 transport planes. Subsequently, on 25 February 2019, Belarus officially transferred four MiG-29s to Serbia during a ceremony at its 558th Aircraft Repair Plant in Baranavichy, increasing Serbia’s total fleet to fourteen jets. Serbia intends to invest approximately €180–230 million in modernizing its entire MiG-29 inventory. As of 2021, the Serbian Air Force operates fourteen MiG-29 fighters.

Germany

East Germany procured 24 MiG-29 aircraft—comprising 20 MiG-29As and four MiG-29UBs—which were introduced into service between 1988 and 1989 with the 1./JG3 "Wladimir Komarow" squadron based at Preschen in Brandenburg. Following the November 1989 collapse of the Berlin Wall and the subsequent German reunification in October 1990, these MiG-29s along with other assets from the East German Air Forces of the National People's Army were incorporated into the West German Luftwaffe. Initially, the 1./JG3 retained its original designation. By April 1991, both MiG-29 squadrons of 1./JG3 were restructured into a dedicated MiG-29 test wing ("Erprobungsgeschwader MiG-29"), which later became JG73 "Steinhoff" and relocated to Laage near Rostock in June 1993.

File:MiG-29 (12196698226).jpg
An East German MiG-29 operating at Preschen in 1990, bearing the GDR emblem.

According to the Federation of American Scientists, the MiG-29 matches or surpasses the F-15C in close-range dogfights, attributed to its Helmet Mounted Weapons Sight (HMS) and superior agility at low speeds. This capability was confirmed during joint DACT exercises where German Air Force MiG-29s operated alongside US fighters. The HMS system provided a significant advantage by enabling pilots to lock onto targets visible within the missile’s field of view, including those nearly 45 degrees off the aircraft’s forward axis. Nevertheless, German pilots acknowledged that while the Fulcrum was more maneuverable at slower velocities than aircraft such as the F-15 Eagle, F-16 Fighting Falcon, F-14 Tomcat, and F/A-18 Hornet, and featured a superior dogfight missile system with its Vympel R-73 compared to contemporaneous AIM-9 Sidewinder missiles, it faced challenges in beyond visual range engagements. Specifically, German crews found it difficult to simultaneously lock and fire the MiG-29's Vympel R-27 missile (as they did not have access to the more advanced Vympel R-77 variant) while countering American fighters’ longer-range radar detection and use of the AIM-120 AMRAAM. Additionally, American aircraft held advantages under night and adverse weather conditions. The Luftwaffe concluded that the MiG-29 was optimally employed as a point defense interceptor for urban areas and military sites rather than for offensive fighter patrols over contested airspace. This evaluation influenced Germany’s decision not to deploy its MiG-29s during the Kosovo War under Operation Allied Force, although Luftwaffe pilots noted that even if authorized, combat missions would have been hampered by a lack of NATO-compatible communication systems and identification friend or foe (IFF) technology.

File:Mikoyan mig29.jpg
A MiG-29 operated by the German Air Force.

From 1993 onward, Germany stationed its MiG fleet with JG73 "Steinhoff" at Laage near Rostock. During their operational tenure within the Luftwaffe, one aircraft ("29+09") was lost on 25 June 1996 due to pilot error. By 2003, German pilots had accumulated more than 30,000 flight hours on these MiGs. In September of that year, 22 out of the remaining 23 aircraft were transferred to the Polish Air Force for a nominal fee of €1 each. The final batch was delivered by August 2004. The last remaining MiG-29 ("29+03") was preserved for static display at Laage.

Libya

In 2020, reports emerged indicating that MiG-29 fighters were operated by factions loyal to Khalifa Haftar within Libya. On 11 September 2020, the United States Africa Command revealed that two MiG-29 jets, piloted by Russian-speaking crews, had crashed in Libya under unclear circumstances—one incident occurred on 28 June 2020, and the other on 7 September 2020. Additionally, announcements were made regarding the planned delivery of MiG-29 and Su-24 aircraft from Russia to the Libyan Air Force.

Peru

File:Peruvian Air Force MiG-29 SDLP.jpg
MiG-29SE operated by the Peruvian Air Force

The Peruvian Air Force procured 21 MiG-29S fighters from Belarus in 1997, as part of a broader acquisition that also included 18 Su-25 ground-attack planes. In the following year, Peru supplemented this fleet with three more MiG-29s purchased directly from Russia. Concurrently, a contract was established with Mikoyan to upgrade eight aircraft to the MiG-29SMP configuration, with provisions to modernize the remaining fleet if desired. These MiG-29s are stationed at FAP Captain José Abelardo Quiñones González International Airport in northern Peru and serve within Escuadrón Aéreo 612 (Fighter Squadron 612 "Fighting Roosters").

Poland

File:U.S. F-16C Fighting Falcon and Polish Mikoyan-Gurevich MiG-29A over Krzesiny air base, Poland - 20050615.jpg
A Polish Air Force MiG-29 alongside a USAF F-16

Between 1989 and 1990, Poland initially received a batch of 12 MiG-29s, comprising nine MiG-29As and three MiG-29UBs. These aircraft were stationed at Mińsk Mazowiecki and operated by the 1st Fighter Aviation Regiment, which was restructured in 2001 into the 1 Eskadra Lotnictwa Taktycznego (1. elt), also known as the 1st Tactical Squadron (TS). During 1995–1996, Poland expanded its fleet by acquiring ten pre-owned MiG-29s from the Czech Republic—nine MiG-29As and one MiG-29UB. Following the phase-out of its MiG-23s in 1999 and MiG-21s in 2004, these 22 MiG-29s remained the sole interceptors in Polish service for a period.

In 2004, Poland received an additional 22 MiG-29s from the German Air Force, of which 14 were refurbished and incorporated into active duty. These aircraft equipped the 41st Tactical Squadron (41. elt), replacing its older MiG-21 fleet. By 2008, Poland held the distinction of being NATO’s largest MiG-29 operator. As of 2017, the country maintained an active inventory of 31 MiG-29s—25 MiG-29As and six MiG-29UBs—deployed between the 1st Tactical Squadron at the 23rd Air Base near Mińsk Mazowiecki and the 41st TS based at the 22nd Air Base near Malbork.

There have been unconfirmed accounts suggesting that Poland temporarily leased one of its MiG-29s to Israel for evaluation purposes; photographic evidence has shown a Polish MiG-29 operating within Israel. Reports indicated that three Polish MiG-29As were present in Israel’s Negev Desert for assessment between April and May 1997. On 7 September 2011, a modernization contract was awarded by the Polish Air Force to WZL 2 to upgrade its MiG-29 fleet, enabling interoperability with Polish F-16 fighters.

Polish MiG-29 units have actively participated in NATO operations: four aircraft from 1. elt took part in the Baltic Air Policing mission in 2006, while the 41. elt contributed in 2008, 2010, and 2012. Additionally, Polish MiG-29s served as aggressor aircraft during NATO’s Tactical Leadership Programme (TLP) joint exercises held in Albacete across 2011, 2012, and 2013.

On 18 December 2017, a MiG-29 experienced a crash landing within a forested area near the 23rd Air Base during an approach maneuver. The pilot remained inside the aircraft without ejecting and sustained only minor injuries. This incident marked the first-ever crash involving a Polish-operated MiG-29 after nearly thirty years of service. Another accident occurred on 6 July 2018 near Pasłęk, resulting in the pilot’s fatality during an attempted ejection; preliminary investigations pointed to possible technical faults as contributing factors. A subsequent crash took place on 4 March 2019; however, on this occasion, the pilot successfully ejected and survived.

On 8 March 2022, Poland declared its readiness to transfer its operational fleet of MiG-29 jets to the United States through Ramstein Air Base. In exchange, Poland sought aircraft with comparable roles and capabilities. The intention behind this arrangement was to facilitate delivery of these MiG-29s to Ukraine amid the ongoing 2022 Russian invasion of Ukraine.

Subsequently, on 16 March 2023, Polish President Andrzej Duda announced that Poland would hand over four operational MiG-29s to Ukraine, with plans for additional deliveries following maintenance and preparation. This action positioned Poland as the first NATO member state to supply fighter jets directly to Ukraine.

On 13 April, German Defence Minister Boris Pistorius confirmed Germany’s approval for transferring five MiG-29s to Ukraine. This consent was essential because these aircraft originally belonged to the former German Democratic Republic, having been transferred to Poland only in 2004.

Iraq

File:Iraqi Air Force MiG-29 Fighter.jpg
Iraqi Air Force MiG-29 fighter

During the latter phase of the Iran–Iraq War, Iraq acquired several MiG-29 fighters which they deployed against Iranian counterparts of similar capability.

By August 1990, coinciding with the Kuwait invasion, the Iraqi Air Force had taken delivery of 37 MiG-29 (9.12B) Fulcrum-As. Reports indicate Iraq was dissatisfied with not receiving the R-73 and R-27T missiles, which Coalition intelligence had identified as significant threats, and instead were supplied with R-60MK missiles. Consequently, Iraq chose not to place further orders for these aircraft. It is also reported that Iraqi forces managed to modify their MiG-29s to accommodate both external fuel tanks and the TMV-002 Remora electronic countermeasure pod.[68]

MiG-29s participated in combat operations during the 1991 Persian Gulf War under Iraqi control. During this conflict, USAF F-15s downed five MiG-29s.[69] Some accounts claim a British Panavia Tornado, designated ZA467, was shot down by a MiG-29 in northwestern Iraq.[70][71] However, UK sources state this Tornado crashed on January 22 during a mission over Ar Rutbah.[72] Another Tornado, an IDS variant from the AMI's 4th or 5th Fighter Squadron, is also claimed to have been downed by an Iraqi MiG-29 using an R-60 missile.[73] Additional Iraqi air-to-air successes are noted in Russian sources, while US accounts attribute other incidents such as a B-52 being damaged by friendly fire when an AGM-88 anti-radiation missile locked onto the bomber's tail gun radar; despite damage, the B-52 returned safely and was nicknamed "In HARM's Way".[74] It is believed that a MiG-29 missile strike hit a F-111 Aardvark, which nevertheless managed to return to base.[75] On January 17, 1991, a MiG-29 from either the 4th or 5th TFS mistakenly downed a friendly MiG-23ML using an R-27R missile. This was not an isolated incident; in April 1988, a MiG-29 from the 5th TFS shot down another MiG-29 of the same squadron with an R-60MK missile under unclear circumstances.[76]

Following the Gulf War, Iraq's initial fleet of 37 MiG-29s dwindled to just twelve operational aircraft. One was damaged, and seven were reportedly flown to Iran.[77] The remaining dozen were retired from service in 1995 due to engine maintenance requirements that Iraq was unable to fulfill abroad.[78]

After the American-led 2003 invasion of Iraq and subsequent dissolution of the Ba'athist Iraqi Army in May of that year,[79] all remaining Soviet and Chinese fighter jets within the Iraqi Air Force were retired from active duty.

Syria

Syria was among the earliest international operators of the MiG-29, acquiring these aircraft even before many members of the Warsaw Pact. Allegedly, Syrian Defence Minister Mustafa Tlass aimed to procure as many as 150 MiG-29s. The initial delivery occurred in June or July 1987, consisting of 16 units, followed by additional shipments throughout the late 1980s. In total, 48 MiG-29A and UB variants were supplied during these initial phases, with an extra 16 reportedly delivered in the mid to late 1990s. These latter airframes were originally manufactured for Iraq between 1990 and 1991 but remained undelivered due to sanctions and the Gulf War; they were later upgraded to an unspecified configuration.

MiG-29s operated by the Syrian Arab Air Force have occasionally engaged with Israeli fighter and reconnaissance planes. On 2 June 1989, two Israeli F-15Cs are said to have downed a pair of Syrian MiG-29As under ambiguous conditions. Reports also suggest that between 1990 and 1991, several aerial clashes took place between Syrian and Israeli forces, resulting in at least one MiG-29 loss for Syria, although claims of Israeli losses during these encounters remain unverified. Further accounts assert that on 14 September 2001, two Syrian MiG-29s were shot down by Israeli F-15Cs while intercepting an Israeli reconnaissance aircraft off Lebanon's coast. Both Syria and Israel officially deny this incident; however, unofficial sources maintain that the engagement occurred. The Syrian pilots involved were identified as Maj. Arshad Midhat Mubarak and Capt. Ahmad al-Khatab, both reportedly rescued from the Mediterranean Sea.

The incident reportedly unfolded when an Israeli Boeing 707 SIGINT aircraft, escorted by two F-15Cs equipped with advanced Python Mk.IV missiles, conducted routine surveillance along Lebanese and Syrian coastlines, monitoring radar and telecommunications near Tripoli and Hamidiyah. Typically, Syrian interceptors—usually MiG-23s or MiG-29s—would shadow such missions at a safe distance without hostile intent. On this occasion, at 09:14 hours, two Syrian MiG-29s aggressively approached the Israeli formation. The F-15s instructed the Boeing 707 to withdraw and activate electronic countermeasures while calling in reinforcements. After warnings broadcast on international distress frequencies were ignored, one F-15 launched a Python Mk.IV missile that destroyed the lead MiG-29; the second MiG was shot down by a close-range AIM-9M Sidewinder as it attempted to retreat. Both aircraft crashed into the Mediterranean.

Syrian MiG-29s re-entered combat during the Syrian Civil War starting in late October 2013, conducting ground attacks against Free Syrian Army forces around Damascus using unguided rockets and bombs. Throughout the conflict, Syria received deliveries of MiG-29SM fighters—an extensively modernized variant developed by Russia. On 5 March 2020, a Syrian MiG-29SM crashed near Shayrat Airbase, marking the first such loss for the Syrian Air Force since 2001. According to avia.pro, this crash may have resulted from being targeted by MANPADS operated by opposition forces.

Following the collapse of the Assad Ba'athist regime, most of the remaining Syrian Air Force assets fell under opposition control. Concerned about instability under the new administration, Israel launched Operation Bashan Arrow, targeting Syrian defense infrastructure including airbases and reportedly destroying at least 30 MiG-29s. The operational status of any surviving aircraft remains unclear.

Malaysia

File:Mikoyan-Gurevich Mig-29 Fulcrum, Malaysia - Air Force JP7323767.jpg
A Malaysian MiG-29 in 2012

The Royal Malaysian Air Force maintained a fleet of 18 MiG-29N/NUB fighters from 1995 until 2017, operating them primarily from the Kuantan air base. These aircraft were customized with enhanced engines and reinforced airframes tailored to Malaysian operational demands.

In 2009, plans were announced to retire the MiG-29s by the close of 2010 due to rising upkeep expenses, aiming to reduce costs by roughly $76 million each year. However, the Malaysian Ministry of Defence later revised this decision, opting to retain ten jets while retiring six. By 2013, an official retirement target was set for 2015. Nevertheless, postponements in the Multi-Role Combat Aircraft (MRCA) procurement program necessitated keeping the MiG-29s active and scheduling upgrades to prolong their service life. Ultimately, these upgrade plans did not come to fruition, and the fleet was fully retired in 2017.

Regarding operational incidents, one MiG-29 was lost in 1998 following hydraulic system and battery malfunctions, while another crashed in 2004 due to an engine fire shortly after takeoff. In both cases, the pilots successfully ejected and survived.

North Korea

File:DPRK MiG-29.jpg
A North Korean MiG-29 intercepting a USAF RC-135S in 2003

The Korean People's Air Force reportedly operates approximately 18 MiG-29 fighters, which are stationed with the 55th Air Regiment at Sunchon Air Base. Besides the 13 MiG-29 (9.12B) Fulcrum As and 2 Fulcrum B trainer variants delivered in 1987, North Korea stands out as the sole Cold War-era export customer and licensed assembler of the Fulcrum-C model.[80]Template:Page needed Known locally as the MiG-29S-13 (9.13B) Fulcrum-C, these aircraft were supplied from the USSR/Russia between 1991 and 1992 in kit form. However, only three units were completed due to Russia’s refusal to provide additional components. The first domestically assembled Fulcrum-C took flight on 15 April 1993.[80]Template:Page needed The USAF first detected and photographed these jets in March 2003 when two KPAF MiG-29s intercepted a USAF RC-135S Cobra Ball reconnaissance plane.[81][82] On 17 May 2025, a North Korean MiG-29 was observed deploying a newly developed active radar homing missile resembling the AIM-120 and PL-12. This missile appears to exceed the range capabilities of the original Soviet-era MiG-29 radar system.[83][84]

Sudan

File:Sudan Air Force Mikoyan-Gurevich MiG-29SE (9-12SE) MTI-2.jpg
Sudanese Air Force MiG-29SE

There have been sporadic reports suggesting that Sudanese Air Force MiG-29s have been deployed against rebel factions in Darfur. Nevertheless, while Mi-24 attack helicopters and Nanchang A-5 or more recently Su-25 ground attack jets have been documented at Darfur airstrips, no evidence has confirmed MiG-29 operations there. On 10 May 2008, during an assault by the Darfur rebel group Justice and Equality Movement (JEM) on Sudan’s capital, a Sudanese MiG-29 was downed by heavy machine gun fire ranging from 12.7 and 14.5 mm (0.500 and 0.571 in) while it targeted a vehicle convoy in Omdurman, a suburb of Khartoum. The jet was piloted by a Russian mercenary who died after ejecting when his parachute failed to deploy.[85][86][87] On 14 November 2008, Sudan’s Ministry of Defence acknowledged receiving twelve MiG-29 fighters from Russia.[88] An unnamed Russian source indicated these aircraft had been delivered prior to 2004.[88]

During the brief conflict known as the 2012 South Sudan–Sudan border conflict, on April 4, 2012, the Sudan People's Liberation Army (SPLA) claimed to have shot down a Sudanese MiG-29 using antiaircraft artillery; however, Khartoum denied this assertion.[89] A subsequent SPLA statement on April 16 reiterated claims of downing another Sudanese MiG-29.[90] It remains unclear whether this second claim referred to the same incident.

On April 15, 2023, footage captured a Sudanese MiG-29 launching missiles over Khartoum amid clashes involving paramilitary groups.[91]

Later, on May 25, 2023, video evidence showed a Sudanese MiG-29 being shot down by the Rapid Support Forces (RSF) above Omdurman.Template:Fix/category[citation needed] The pilot managed to eject safely but sustained injuries and was subsequently captured.[92]

United States

In 1997, the United States acquired 21 MiG-29 fighters from Moldova through the Nunn–Lugar Cooperative Threat Reduction initiative. Among these, fourteen were MiG-29S variants, featuring an active radar jammer located along the spine and capable of carrying nuclear armaments. A significant reason behind this acquisition was to prevent these aircraft from being transferred to Iran. This procurement also offered valuable opportunities for the tactical fighter branches of the USAF, USN, and USMC to conduct operational assessments and gather data on the MiG-29, potentially integrating them into dissimilar air combat training programs. Such insights are beneficial for future combat scenarios and contribute to the development and evaluation of current and forthcoming weapons systems. By late 1997, these MiGs were delivered to the National Air and Space Intelligence Center (NASIC) at Wright-Patterson Air Force Base in Ohio; however, many of the former Moldovan MiG-29s are believed to have been dismantled. Several units are now exhibited openly at locations including Nellis AFB, Nevada; NAS Fallon, Nevada; Goodfellow AFB, Texas; and Wright-Patterson AFB, Ohio.

Others

In 1996, Cuban MiG-29UB fighters shot down two Cessna 337 aircraft operated by the group Brothers to the Rescue after they entered Cuban airspace.

During the 1999 Eritrean-Ethiopian War, reports indicate that Ethiopian Su-27 fighters, piloted by Russian mercenaries, successfully downed several Eritrean MiG-29s. Local pilots reportedly received training from instructors originating from those countries. Additional accounts suggest Eritrean MiG-29s achieved aerial victories by shooting down two Ethiopian MiG-21s and three MiG-23s. The assertion that an Eritrean MiG-29 destroyed an Ethiopian Su-25 was later disproved; the missing Ethiopian Su-25TK was actually damaged in a May 2000 accident and remains stored for spare parts at Bishoftu Air Base.

As of 2022, according to Jane's Information Group, the Bangladesh Air Force (BAF) operated eight MiG-29 aircraft (six 6B models and two UB variants), though their operational readiness is reportedly low.

Following the conclusion of the 1994 civil war, a reunified Yemen inherited several intact MiG-29s originally purchased by South Yemen shortly before unification. Between 1995 and 1996, Yemen also obtained two additional jets from Kazakhstan. In 2001, Yemen signed a significant arms agreement that included acquiring up to 36 upgraded MiG-29s, with deliveries commencing in June 2002. These aircraft were outfitted with N019MP radar and advanced fire control systems, making them the most sophisticated combat jets in Yemen’s air fleet. They are compatible with guided air-to-ground missiles such as the Kh-31P and Kh-29T, as well as air-to-air missiles like the R-77.

Prospective users and unsuccessful proposals

Prior to the collapse of the Soviet Union, Finland adopted a strategy of diversifying its arms procurement among Western, Eastern, and domestic manufacturers. The MiG-29 was intended to succeed the Finnish Air Force's MiG-21 fighters by 1988, with test flights having been conducted.

In the late 1980s, the Soviet Union proposed supplying Libya with MiG-29 aircraft. However, this offer was declined because the MiG-29's weapons systems and radar were considered comparable to those of the MiG-23MLD already operated by the Libyan Arab Air Force. Additionally, the cost of the MiG-29 was viewed as prohibitively expensive.

Between 1989 and 1990, following the Soviet withdrawal from Afghanistan, the Soviet Union delivered 49 helicopters and 125 fixed-wing aircraft to Afghanistan. The Democratic Republic of Afghanistan also requested MiG-29 fighters for its air force, but this request was rejected.

In 1989, Zimbabwe placed an order for a squadron of MiG-29s from the USSR. Some members of the Air Force of Zimbabwe underwent training in Russia to operate these jets; however, by 1992, the transaction was cancelled due to improving regional geopolitical stability.

In December 2008, Russia sought to strengthen its military ties in the Middle East by announcing a donation of 10 fighter jets to Lebanon, marking the most significant enhancement of Lebanon's military capabilities since its civil war ended nearly twenty years earlier. A representative from the Russian defense ministry stated that these secondhand MiG-29s would be provided free of charge as part of a defense cooperation agreement that included training Lebanese military personnel in Russia. Subsequently, on 29 February 2010, Russia agreed to amend this offer to supply Lebanon with 10 Mi-24 attack helicopters at Lebanon’s request.

In 2021, Russia proposed selling the Argentine Air Force a batch of 15 MiG-29 fighters along with another package consisting of 12 Su-30 aircraft. The offer also included potential sales of Yak-130 training jets and Mil Mi-17 helicopters.

Original Soviet versions

File:BAF MiG-29s in flight Garchev.png
A formation of Bulgarian Air Force MiG-29 "Fulcrum-A"
File:MiG-29 Graf Ignatievo 2.jpg
MiG-29UB of the Bulgarian Air Force
MiG-29 (Product 9.12)
The initial production model designed for the Soviet Air Force, entering service in 1983. It carries the NATO codename "Fulcrum-A". This variant was equipped with the Phazotron N019 Rubin radar, OEPS-29 optical-electronic sight system, and a helmet-mounted sight.
MiG-29 (Product 9.12A) 'Fulcrum-A'
An export version of the 9.12 tailored for Warsaw Pact nations, featuring a downgraded RPLK-29E radar, reduced capability OEPrNK-29E optoelectronic and navigation equipment, and older IFF transponders. It was incapable of nuclear weapon delivery. Recipients included East Germany, Czechoslovakia, Poland, Sudan, and Romania.
MiG-29 (Product 9.12B) 'Fulcrum-A'
This export model of the 9.12 was intended for countries outside the Warsaw Pact and incorporated further downgraded radar and avionics systems. It was supplied to India, Iraq, Syria, North Korea, Cuba, Malaysia, Myanmar, and Eritrea.
MiG-29UB (Product 9.51)
A two-seat trainer variant featuring only an infrared sensor without radar capability. The NATO reporting name for this model is "Fulcrum-B".
MiG-29 (Product 9.13) 'Fulcrum-C'
An upgraded iteration of the original production version introduced in 1986 and designated "Fulcrum-C" by NATO. This variant included a larger dorsal spine to house an expanded No.1 fuel tank and incorporated the L-203BE Gardenyia-1 jammer absent from the earlier 9.12 model. The increased size of the dorsal spine earned this version and its successors the nickname "Fatback".
MiG-29 (Product 9.13B) 'Fulcrum-C'
This export version of the 9.13 was assembled in semi-knocked down form at Panghyon between 1991 and 1992 for North Korea. It retained the Gardenyia-1 jammer but featured downgraded avionics and lacked IFF systems. Some reports suggest North Korea did not receive the Gardenyia jammer.
MiG-29S (Product 9.13S)
An enhanced update of the original 9.13 model maintaining the NATO designation "Fulcrum-C". This version incorporated flight control system upgrades with four new computers improving stability augmentation and controllability, allowing an increased angle of attack by 2°. The revised mechanical-hydraulic flight control system permitted greater deflection of control surfaces. The MiG-29S supports carrying 1,150 L (250 imp gal; 300 U.S. gal) drop tanks under each wing as well as a centerline tank. Its inboard underwing hardpoints enable tandem pylons to accommodate a larger payload capacity up to 4,000 kg (8,800 lb). The maximum gross weight rose to 20,000 kg (44,000 lb) overall. New avionics were introduced alongside the Phazotron N019M radar and Built-In Test Equipment (BITE), minimizing reliance on ground support gear. This variant's development was partly driven by security breaches involving Phazotron engineer Adolf Tolkachev compromising multiple systems to Western intelligence. It represents the last MiG-29 model produced before the Soviet Union's dissolution, with only limited quantities manufactured.

Enhanced models derived from the original airframe

MiG-29S (Product 9.12S)
A post-Soviet modernization applied to earlier 9.12 models, integrating improvements developed for the 9.13S variant.
MiG-29SD (Product 9.12SD)
An export version of the upgraded 9.12S featuring downgraded radar and avionics systems.
MiG-29SE (Product 9.13SE)
This export configuration of the 9.13S is equipped with a slightly reduced capability N-019ME radar, capable of tracking multiple targets and supporting RVV-AE (R-77 missile) compatibility. It was the first export MiG-29 to include underwing drop tanks; the inner pylons beneath the wings can carry bombs exceeding 500 kg (1,100 lb) arranged in side-by-side tandem pairs. Its armament includes medium-range missiles such as R-27T1, R-27ER1, and R-27ET1. Additionally, it can be outfitted with active ECM systems, weapons guidance aids, improved built-in test and training systems, and is capable of engaging two aerial targets simultaneously.
MiG-29SM (Product 9.13M)
This variant resembles the 9.13 but adds the capability to deploy guided air-to-surface missiles as well as TV- and laser-guided bombs. Its NATO reporting name is "Fulcrum-C".
MiG-29SM (Syrian Air Force)
Customized for Syria based on the MiG-29SM but utilizing the 9.12 airframe, this special variant was developed by RAC MiG specifically for the Syrian Air Force.
File:MiG-29 Fulcrum B Luftwaffe.jpg
German Air Force MiG-29GT
MiG-29G/MiG-29GT
These are East German MiG-29A / 29UB aircraft upgraded to meet NATO standards through modifications conducted by MiG Aircraft Product Support GmbH (MAPS), a joint venture established in 1993 between MiG Moscow Aviation Production Association and DaimlerChrysler Aerospace.
MiG-29AS/MiG-29UBS
The Slovak Air Force undertook an upgrade program on their MiG-29A/-29UB fleet to ensure NATO interoperability. This initiative, started in 2005 and executed by RAC MiG alongside Western companies, introduced navigation and communication systems from Rockwell Collins, an Identification Friend or Foe (IFF) system from BAE Systems, new glass cockpits featuring multifunction LCD displays and digital processors, and provisions for future integration with Western equipment. The aircraft's weaponry remained unchanged. By late February 2008, twelve out of twenty-one MiG-29s had completed this upgrade.
File:MiG-29Sniper.jpg
MiG-29 Sniper
MiG-29 Sniper
An upgrade project planned for the Romanian Air Force involving collaboration between DaimlerChrysler Aerospace (DASA), Aerostar, and Elbit Systems. DASA managed program oversight, technical support, and flight testing alongside Elbit, which developed the avionics suite; Aerostar handled aircraft modifications. The first upgraded aircraft flew on 5 May 2000. Enhancements encompassed a modular multirole computer based on MIL-STD-1553B data bus architecture, advanced Western avionics, new radio communications equipment, a hybrid navigation system combining inertial navigation with GPS, an identification system, two 152 mm × 203 mm (6.0 in × 8.0 in) multifunction color displays, a Head-Up Display with UFCP front control panel, a new radar warning receiver (RWR), updated HOTAS controls, and an advanced air data computer (ADC). Plans also included fitting a new radar and integrating Western weaponry while retaining Russian armaments. However, this program was discontinued due to various factors including Romania’s decision in 2003 to retire its MiG-29A/UB fleet and focus investments on the MiG-21 LanceR modernization.
File:Mikoyan-Gurevich MiG-29SMT (9-19), Russia - Air Force AN2269907.jpg
A Russian Air Force MiG-29SMT
MiG-29SMT (Product 9.17)
The MiG-29SMT represents an upgrade of first-generation MiG-29s (models 9.12 through 9.13) incorporating improvements derived from the MiG-29M design. It features additional fuel tanks housed within an extended dorsal spine that increase maximum internal range up to 2,100 km (1,300 mi). The cockpit includes an enhanced HOTAS setup with two 152 mm × 203 mm (6.0 in × 8.0 in) color liquid crystal multifunction displays plus two smaller monochrome LCDs. To address the original MiG-29A's limited air-to-ground capability, this upgrade integrates the advanced Zhuk-ME radar with ground mapping functions and supports air-to-ground guided munitions. Powerplants are upgraded RD-33 series 3 engines delivering afterburning thrust rated at approximately 81 kN (18,000 lbf) each. Weapons capacity increases to 4,500 kg (9,900 lb), distributed over six underwing stations plus one ventral hardpoint, compatible with similar armaments as found on the MiG-29M. The platform also allows integration of non-Russian avionics and weapon systems.
File:Mikoyan MiG-29 BM Variant - Jet fighter - 36100 - Bangladesh Air Force - VGHS.jpg
Bangladesh Air Force MiG-29BM
MiG-29BM
The MiG-29BM—likely standing for Belarusian Modernised or Bolyshaya Modernizaciya (large modernization)—is a strike-focused upgrade performed at ARZ-558 repair facility in Baranovichi, Belarus. It serves as Belarus’s counterpart to Russia’s MiG-29SMT by enhancing weapons systems, radar capabilities, and adding fixed air-to-air refueling functionality. These upgraded jets entered operational service circa 2003 with approximately ten units modernized to BM standard. The Bangladesh Air Force has similarly upgraded its MiG-29B fleet following this model.
MiG-29UBT (Product 9.51T)
This is an SMT-standard modernization applied to the twin-seat MiG-29UB variant currently operated by Russia, Algeria, and Yemen.
MiG-29UPG
Designed specifically for upgrading Indian Air Force’s MiG-29B fighters, this variant shares many features with the SMT version but incorporates imported avionics components. It includes the Zhuk-M radar system, updated avionics suite, an inflight refueling probe, DRDO D-29 electronic warfare system, and enhanced RD-33 series 3 engines. The first flight of this configuration occurred on 4 February 2011.
MiG-29SMP / MiG-29UBP
These are tailored upgrades for Peru’s fleet of MiG-29SE aircraft under a US$106 million contract signed in August 2008 with RAC MiG for an initial batch of eight units with options for all Peruvian jets. The single-seat model is designated SMP while the two-seater is UBP. Enhancements include improved electronic countermeasures suites, avionics upgrades, sensor improvements including advanced IRST capabilities for superior passive detection and off-boresight missile launch performance, one multifunction color display (MFCD), HOTAS controls, and a MIL-STD-1553 data bus architecture. The original N010 Zhuk-M radar is replaced by the heavily modified digital N019M1 radar variant offering enhanced performance. Structural life extension programs were implemented alongside engine overhauls and installation of inflight refueling probes.
MiG-29N/NUB
These designations refer to export deliveries comprising sixteen MiG-29SD single-seaters and two MiG-29UB twin-seaters supplied to the Royal Malaysian Air Force.
MiG-29MU1
A Ukrainian modernization effort focused on upgrading the MiG-29A/S variants.
MiG-29MU2
A subsequent Ukrainian modernization concentrating on enhancing air-to-ground munition capabilities for the MiG-29S platform.

Second-generation models featuring altered airframes

File:MiG-29M NTW 7 8 93.jpg
Russian MiG-29M
MiG-29M / MiG-33 (Product 9.15)
This advanced multirole fighter incorporates a revamped airframe, replacing traditional mechanical flight controls with a fly-by-wire system, and is powered by upgraded RD-33 ser.3M engines. Its NATO reporting name is "Fulcrum-E".
MiG-29UBM (Product 9.61)
A two-seat trainer variant derived from the MiG-29M that was never produced. Its role was effectively succeeded by the 'MiG-29M2' designation.
MiG-29M2 / MiG-29MRCA
This version is a two-seat adaptation of the MiG-29M, sharing identical performance with a slightly decreased ferry range of approximately 1,800 km (1,100 mi). RAC MiG has showcased it at multiple airshows including the Fifth China International Aviation and Aerospace Exhibition (CIAAE 2004), Aero India 2005, and MAKS 2005. Initially marketed under the designation MiG-29MRCA, it has since evolved into what is now known as the MiG-35.
File:MiG29-OVT-ENGINE.JPG
Russian MiG-29OVT on display
MiG-29OVT
Originally one of the six pre-production MiG-29Ms built before 1991, this aircraft was later equipped with thrust vectoring engines and fly-by-wire controls. It served as a technology demonstrator and testbed for thrust-vectoring engines at various airshows, highlighting potential advancements for the MiG-29M series. The avionics suite matches that of the MiG-29M, with the cockpit differing only by an added switch to activate thrust vectoring. Powered by two RD-133 engines featuring distinctive 3D rotating nozzles capable of multidirectional thrust deflection, it primarily functions as an aerobatic demonstrator. Despite its thrust-vectoring capabilities, other specifications were not officially emphasized. The aircraft has been exhibited globally alongside the MiG-29M2 to promote export opportunities.
File:MiG-29K at MAKS-2003 airshow.jpg
A Russian Naval Aviation MiG-29K
File:Mikoyan-Gurevich MiG-29K ‘RF-92324 - 48 blue’ (36946836632).jpg
A Russian MiG-29K/KUB displayed with wings folded
MiG-29K (Product 9.31)
This naval version, derived from the MiG-29M, carries the "K" suffix representing "Korabelnogo bazirovaniya" (deck-based). It is equipped with folding wings, arrestor hooks, and reinforced landing gear suitable for carrier operations. Initially designed for deployment on Admiral Kuznetsov class aircraft carriers, the program received production approval from the Russian Ministry of Defence but was halted in 1992 due to changes in military strategy and budget constraints. The project was revived by MiG Corporation in 1999. On 20 January 2004, the Indian Navy contracted for twelve single-seat MiG-29K and four two-seat MiG-29KUB aircraft. Adaptations were made to meet Indian Navy specifications. Both production models share a canopy sized for two seats, with radar absorbent coatings applied to reduce their radar signature. The cockpit features a wide HUD and three colour LCD multi-function displays (seven on the MiG-29KUB), complemented by a Topsight E helmet-mounted targeting system. Its armament compatibility includes the full range available to MiG-29M and MiG-29SMT variants. NATO assigns it the code name "Fulcrum-D".
File:Mig-29K getting ready to launch from INS Vikrant.jpg
An Indian Navy two-seat MiG-29K/KUB aboard INS Vikrant
MiG-29KUB (Product 9.47)
Sharing identical specifications with the MiG-29K but configured with tandem seating for pilot training purposes, this variant remains fully combat-capable. The first Indian Navy-dedicated MiG-29KUB completed its maiden flight at Russia's Zhukovsky test centre on 22 January 2007.[citation needed] Its NATO reporting code is also "Fulcrum-D".
File:712BLUE MG29(M2)(MiG-35) Russian Air Force ZIA UUBW 1 (33847794464).jpg
A Russian Air Force MiG-35UB
MiG-35
An evolution stemming from both the MiG-29M/M2 and MiG-29K/KUB families, this model is designated by NATO as "Fulcrum-F".

Operators

File:Mig-29.operators.png
MiG-29 operators
  Active
  Former
File:Military parade in Baku 2011 (498).jpg
MiG-29 of the Azerbaijani Air Force
File:Rotate! 36501, Bangladesh Air Force Mig-29B (29930367676) (cropped).jpg
Bangladesh Air Force MiG-29SE 9.12SE[lower-alpha 1] Fulcrum departing from Shahjalal International Airport
File:Belarus Air Force Mikoyan-Gurevich MiG-29 (9-13) Pichugin-1.jpg
Belarusian Air Force MiG-29 9.13
File:Bulgarian mig-29 r-27.jpg
MiG-29 operated by the Bulgarian Air Force
File:Chadian Air Force Mikoyan-Gurevich MiG-29 (9-13) at Lviv International Airport.jpeg
MiG-29 9.13 belonging to the Chadian Air Force landing at Lviv International Airport
File:Myanmar Air Force Mikoyan-Gurevich MiG-29B (9-12B) MRD-2.jpg
MiG-29 9.12B from the Myanmar Air Force
File:Flag of Algeria.svg Algeria
  • Algerian Air Force – As of January 2014, 26 MiG-29s were operational.[94] Additionally, 14 MiG-29M/M2 units were on order.[95][96] By 2023, the fleet comprised 39 fighters and one UB trainer, with five additional aircraft pending delivery.[97]
Template:Country data Azerbaijan
File:Flag of Bangladesh.svg Bangladesh
  • Bangladesh Air Force – Held six MiG-29SEs (9.12SE)[93] and two MiG-29UB trainers as of 2021. Four of these MiG-29SEs underwent life extension upgrades in Belarus, while the remaining were modernized between 2021 and 2022.[100][101]
Template:Country data Belarus
File:Flag of Bulgaria.svg Bulgaria
  • Bulgarian Air Force – Operated 11 MiG-29s and three MiG-29UBs dedicated to operational conversion training as of 2025.[102]
Template:Country data Cuba
File:Flag of Egypt.svg Egypt
Template:Country data Eritrea
File:Flag of India.svg India
Template:Country data Iran
  • Islamic Republic of Iran Air Force – Reported operating 19 MiG-29s in 2023 according to Flight Global data.[109] Iran initially acquired 20 MiG-29 (9.12B) and four MiG-29UB units in 1989.[110] A planned purchase of an additional 48 aircraft in 1992 was not completed.[111] Furthermore, Iran obtained nine units from Iraq as per RSK MiG records.[112]
Template:Country data Libya
Template:Country data Mongolia
Template:Country data Myanmar
  • Myanmar Air Force – Recorded inventory included 31 MiG-29 aircraft (6 SE, 20 SM(mod), and five UB) as of January 2015.[117] Ten units have been upgraded to the MiG-29SM(mod) standard.[118] By 2023, the force maintained a total of 28 fighters and five UB trainers.[119]
Template:Country data North Korea
File:Flag of Peru.svg Peru
File:Flag of Poland.svg Poland
  • Polish Air Force – Maintained eleven MiG-29s alongside three UB trainers for conversion training purposes as of 2025.[102] Ten aircraft were transferred to Ukraine during that year.[121]
File:Flag of Russia.svg Russia
  • Russian Aerospace Forces – Totaled eighty-seven aircraft[122] comprising seventy MiG‑29/MiG‑29UB units, fifteen upgraded to the SMT standard, and two UBTs as reported in 2022.[122] According to World Air Forces data for 2025, at least two hundred fifty-six units remain active.[123]
  • Russian Naval Aviation – Operated twenty-four Mikoyan MiG‑29K naval fighters.[102]
Template:Country data Serbia
  • Serbian Air Force and Air Defence – Inventory included fourteen units as of 2025: five MiG‑29As, three MiG‑29Bs (corresponding to models 9.12A and B), three modernized SMT variants, and three UB trainers used for operational conversion training. Eleven fighters have been upgraded to advanced SMT standards.[124]
Template:Country data Sudan
Template:Country data Turkmenistan
File:Ukrainian MiG29 1992.jpg
MiG‑29 operated by Ukraine in the year 1992
Template:Country data Ukraine
  • Ukrainian Air Force – Between thirty-seven and seventy aircraft were reported active by March 2019,[128][129] with an estimated forty-seven fighters and eight UB trainers operational in early 2023.[130] By March 8, 2025, losses amounted to thirty destroyed fighters and three damaged on the ground.[131]
File:Flag of the United States.svg United States
  • Utilized by private defense contractor RAVN Aerospace for adversary air combat training services.[132]
Template:Country data Uzbekistan
Template:Country data Yemen
  • Yemeni Air Force – Recorded twenty-four aircraft in service by January 2017,[125] though all were grounded due to ongoing civil conflict. Numerous units were destroyed on the ground during Saudi-led Operation Decisive Storm in 2015.[134] Twenty-three remained reportedly available by 2023.[133]

Former operators

File:MiG der HuAF.jpg
Hungarian Air Force MiG-29
File:Een MiG–29 van de Slowaakse luchtmacht in de vlucht (2156 018809).jpg
Slovakian MiG–29 in flight circa 1999

Aircraft on exhibit

Czech Republic
Canada
Germany
  • 29+03 – MiG-29G presented at the Luftwaffenmuseum der Bundeswehr in Berlin.[171] This particular aircraft is the sole remaining German MiG-29 within Germany. Previously exhibited in Laage, it was relocated to the Luftwaffenmuseum der Bundeswehr in 2006 as part of the "50 Jahre Luftwaffe" exhibition.[172][173]
Hungary
  • A MiG-29 is exhibited alongside older MiG aircraft and helicopters at The RepTár Museum in Szolnok, Hungary.[174][lower-alpha 2]
India
Latvia
  • 9-52 – MiG-29UB showcased at the Riga Aviation Museum in Riga. This airframe represents the second MiG-29UB prototype. Following 213 test flights conducted around Moscow between 23 August 1982 and 10 April 1986, it was dismantled with wing and tail components reused for prototype (9–16). The remaining parts were transferred to the Riga Military Aviation Engineers High School and subsequently donated to the Riga Aviation Museum in 1994, where it remains on display.[177] The condition of this prototype's remnants is poor, featuring exposed fuselage panels and a partially damaged canopy.Template:Fix/category[citation needed]
Malaysia
Poland
Romania
File:MiG-29 Sniper in Bucharest.JPG
MiG-29 Sniper exhibited
Russia
File:Mikoyan MiG-29 Fulcrum prototype 01 blue (9923238334).jpg
First prototype MiG-29 exhibited at the Central Air Force Museum in Monino
Slovakia
United States
File:Mig 29 Fulcrum.jpeg
MiG‑29 exhibited in McMinnville, Oregon
File:MiG‑29A (At Wright-Patterson).jpg
MiG‑29 model 9.12ATemplate:Sfn \ Gordon \2006 \p=\501 displayed at the National Museum of the United States Air Force in Dayton, Ohio

Airworthy

  • N29UB – This MiG-29UB is currently owned by Jared Isaacman.Cite error: Closing </ref> missing for <ref> tag</ref>
  • N129XXCite error: Invalid <ref> tag; refs with no name must have content – Owned by RAVN Aerospace (previously Air USA), this MiG-29UB is stationed at Quincy Regional Airport in Quincy, Illinois. Don Kirlin purchased the aircraft from Kyrgyzstan.[198] It is utilized for contract flight training and testing purposes.[199]
  • In spring 2009, two MiG-29UBs in operational condition were listed for sale from Eastern Europe. These jets originated from the same source as the flyable N129UB, formerly held by the Historic Flight Foundation[200] and currently owned by Jared Isaacman.[201]Template:Fix/category[needs update]

Specifications (MiG-29)

File:Mikoyan MiG-29 3-view.svg
Three-view schematic of the Mikoyan MiG-29

Template:Aircraft specs

Accidents and incidents

Template:Incomplete list

Between 1989 and 2024, the Indian Air Force and Navy acquired 80 and 45 aircraft of their respective models, experiencing losses of 20 and five aircraft correspondingly during this period.[202]

  • On 8 May 2020, a MiG-29 belonging to the 223 Squadron of the Indian Air Force crashed near Jalandhar in Punjab. The pilot successfully ejected after the aircraft became unresponsive.[203]
  • A MiG-29 (KBU-3112) from the Indian Air Force's 47 Squadron crashed on 2 September 2024 during a nocturnal training exercise near Uttarlai in the Barmer district of Rajasthan. The incident occurred in a sparsely inhabited region due to technical malfunction, with the pilot ejecting without injury.[204][205]
  • On 4 November 2024, a MiG-29 (KBU-711) assigned to the 28 Squadron crashed while flying from Adampur to Agra during a routine training sortie. The aircraft stalled and entered a flat spin before impact due to technical complications; the pilot managed to eject safely.[206][207][208]

In popular culture


See also

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

Notes

  1. ↑ 36501 corresponds to a 9.12SE[93]
  2. ↑ Hungarian AF MiG-29 s/n 2960535148 was a 9.12A[175]

References

  1. ↑ "Russia considers funding MiG-29 successor" Archived 17 December 2013 at the Wayback Machine - Flightglobal.com, 11 December 2013
  2. ↑ 2.0 2.1 Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  3. ↑ Gordon 2006, pp. 55, 57: "Indeed, on the first thirty production aircraft the inlet ducts, engine cowlings, leading-edge flaps, control surfaces, wingtips, fuselage spine, detachable upper fin sections and numerous access panels were made of composites, not to mention the radome and dielectric fin caps concealing communications aerials." Composites failed during testing and service. "In the end only composite fins, radome and access panels remained."
  4. ↑ Gordon 2006, p. 58.
  5. ↑ Gordon 2006, p. 431.
  6. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  7. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  8. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  9. ↑ "Russian MiG-29 fighter crashes in East Siberia: Pilot dead." Archived 27 July 2009 at the Wayback Machine The Journal of the Turkish Weekly, 5 December 2008. Retrieved 28 March 2009.
  10. ↑ "Corrosion issue grounds one-third of Russian air force MiG-29 fleet." Archived 22 March 2009 at the Wayback Machine Flight International, 19 March 2009. Retrieved 14 October 2009.
  11. ↑ Litovkin, Dmitry. "У новых истребителей МиГ-29 выявлена коррозия (MiG-29 pilot did everything to his notice)." Archived 15 March 2009 at the Wayback Machine Izvestia, 23 April 2008. Retrieved 28 March 2009. (English translation). Archived 21 September 2015 at the Wayback Machine Google. Retrieved 14 October 2009.
  12. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named airforce-technology.com
  13. ↑ AirForces Monthly, p. 68.
  14. ↑ Isby, David C. "16 Additional MiG-29SMTs for Russia". Air International, June 2014. Vol. 86, No. 6. p. 8.
  15. ↑ "Op Tempo, Sustainment Flaws Hit Russian Air Force" Archived 12 March 2024 at the Wayback Machine. Defense News, 12 July 2015. Retrieved 2 August 2015.
  16. ↑ "Russian MiG Fighter Crashes in Southern Russia, Pilot Lives" New York Times, 3 July 2015. Retrieved 2 August 2015.
  17. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  18. ↑ Long, Helen. "Russia ‘shot down Georgia drone’." Archived 22 April 2008 at the Wayback Machine BBC, 21 April 2008. Retrieved 10 March 2009.
  19. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value). International Herald Tribune, 26 May 2008. Retrieved 10 March 2009.
  20. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  21. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  22. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  23. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  24. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  25. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  26. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  27. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  28. ↑ 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. ↑ 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. ↑ 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. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named SIPRI
  47. ↑ ...
  48. ↑ ...
  49. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named HT
  50. ↑ ...
  51. ↑ ...
  52. ↑ 52.0 52.1 52.2 Cite error: Invalid <ref> tag; no text was provided for refs named TOI
  53. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named Upgrade
  54. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named DRDO
  55. ↑ ...
  56. ↑ ...
  57. ↑ ...
  58. ↑ ...
  59. ↑ ...
  60. ↑ ...
  61. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named Navy
  62. ↑ ...
  63. ↑ ...
  64. ↑ ...
  65. ↑ ...
  66. ↑ ...
  67. ↑ ...
  68. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  69. ↑ Steve Davies. F-15C Eagle Units in Combat, p. 88. Osprey Combat Aircraft 53.
  70. ↑ [1] один самолет Панавиа «Торнадо» английских ВВС at archive.today (archived 1 July 2012)
  71. ↑ "Iraqi air-air victories during the Gulf War 1991." Archived 17 July 2011 at the Wayback Machine safarikovi.org.com, 2004. Retrieved 7 December 2009.
  72. ↑ "ASN Aircraft accident Panavia Tornado GR1 ZA467." Archived 9 October 2011 at the Wayback Machine Flight Safety Foundation via aviation-safety.net, 21 December 2009.
  73. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  74. ↑ Lake 2004, pp. 47–48.
  75. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  76. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  77. ↑ Gordon, p.483
  78. ↑ Woods, Kevin M. "Iraqi Perspectives Project Phase II, Um Al-Ma'arik (The Mother of All Battles): Operational and Strategic Insights from an Iraqi Perspective, Volume 1 (Revised May 2008)." Archived 22 July 2011 at the Wayback Machine Defense Technical Information Center via oai.dtic.mil. Retrieved 23 October 2010.
  79. ↑ Kaplan, Fred. "Who disbanded the Iraqi army?" Archived 11 December 2011 at the Wayback Machine Slate, 7 September 2007. Retrieved 9 December 2011.
  80. ↑ 80.0 80.1 80.2 Cite error: Invalid <ref> tag; no text was provided for refs named Mitzer-2020
  81. ↑ "MiG-29戦闘機(ファルクラム)(北朝鮮)" (in Japanese). Archived 10 February 2012 at the Wayback Machine Atwiki.jp. Retrieved 5 October 2012.
  82. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  83. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  84. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  85. ↑ "Russian Fighter Pilot Shot Down In Sudan." Archived 1 June 2008 at the Wayback Machine strategypage.com, 30 May 2008. Retrieved 1 August 2010.
  86. ↑ Ali, Wasil. "Russia says fighter pilot shot down in Sudan was an ex-military officer." Archived 13 May 2015 at the Wayback Machine sudantribune.com, 30 May 2008. Retrieved 1 August 2010.
  87. ↑ "Russian pilots fly Sudan MIGs in Darfour missions." Archived 1 June 2008 at the Wayback Machine World Tribune, 29 May 2008. Retrieved 1 August 2010.
  88. ↑ 88.0 88.1 Informacje in "Raport - Wojsko Technika Obronność" Nr. 12/2008, p. 62 (in Polish)
  89. ↑ "South Sudan: Nation Guns Down War Plane, Khartoum Denies." Archived 11 November 2013 at the Wayback Machine Allafrica, 5 April 2012.
  90. ↑ "SPLA shoots down Khartoum jet fighter over Heglig: officials." Archived 7 July 2012 at the Wayback Machine Sudan Tribune, 17 April 2012.
  91. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  92. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  93. ↑ 93.0 93.1 Gordon 2006, p. 459.
  94. ↑ 94.0 94.1 94.2 94.3 94.4 Cite error: Invalid <ref> tag; no text was provided for refs named 2014_Aero
  95. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  96. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  97. ↑ 2024 World Air Forces, Flight Global, p.12
  98. ↑ 98.0 98.1 Cite error: Invalid <ref> tag; no text was provided for refs named World_Air_Forces_2014
  99. ↑ 99.0 99.1 Cite error: Invalid <ref> tag; no text was provided for refs named World Air Forces p.13
  100. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  101. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  102. ↑ 102.0 102.1 102.2 102.3 Cite error: Invalid <ref> tag; no text was provided for refs named IISS212
  103. ↑ 2024 World Air Forces, Flight Global, p.16
  104. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  105. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  106. ↑ 2024 World Air Forces, Flight Global, p.22
  107. ↑ 107.0 107.1 Cite error: Invalid <ref> tag; no text was provided for refs named India Today-2020
  108. ↑ 108.0 108.1 Cite error: Invalid <ref> tag; no text was provided for refs named :0
  109. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named World Air Forces 2023
  110. ↑
  111. ↑
  112. ↑
  113. ↑
  114. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  115. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  116. ↑ 2024 World Air Forces, Flight Global, p.24
  117. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named 2015_Aero
  118. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  119. ↑ 2024 World Air Forces, Flight Global, pp.24–25
  120. ↑ 2024 World Air Forces, Flight Global, p.27
  121. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  122. ↑ 122.0 122.1 Cite error: Invalid <ref> tag; no text was provided for refs named IISS22
  123. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named World Air Forces 2025
  124. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  125. ↑ 125.0 125.1 125.2 Cite error: Invalid <ref> tag; no text was provided for refs named WAF2017
  126. ↑ 126.0 126.1 Cite error: Invalid <ref> tag; no text was provided for refs named World Air Forces p.30
  127. ↑ 2024 World Air Forces, Flight Global, p.32
  128. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named Kyiv Post, 2019
  129. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  130. ↑ 2024 World Air Forces, Flight Global, p.32.
  131. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  132. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  133. ↑ 133.0 133.1 Cite error: Invalid <ref> tag; no text was provided for refs named World Air Forces p.34
  134. ↑ Cooper 2018, p. 43
  135. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  136. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  137. ↑ 2024 World Air Forces, Flight Global, p.15
  138. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  139. ↑ "World Military Aircraft Inventory". 2011 Aerospace: Aviation Week and Space Technology, January 2011.
  140. ↑ 140.0 140.1 140.2 Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  141. ↑ "Vége, ennyi volt... (A MiG-29 és üzemeltetőik emlékére)." Archived 14 January 2011 at the Wayback Machine JETfly Magazin. Retrieved 5 October 2012.
  142. ↑ "MIG-29-est vegyenek!" Archived 5 January 2022 at the Wayback Machine nol.hu. Népszabadság, 12 August 2011.
  143. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  144. ↑ Gordon 2006, p. 483.
  145. ↑ "US buys Su-27 fighters from Ukraine for ‘aggressor’ training." Archived 5 January 2022 at the Wayback Machine defencetalk.com, 13 May 2009. Retrieved 1 August 2010.
  146. ↑ "IAF Magazine: The “Sting” has landed" Archived 1 February 2014 at the Wayback Machine iaf.co.il
  147. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  148. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  149. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  150. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  151. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  152. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  153. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  154. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  155. ↑ DefenseLink News Transcript, DoD News Briefing: Cooperative Threat Reduction Initiative Archived 2 October 2006 at the Wayback Machine
  156. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  157. ↑ "Romanian International Air Show." Template:Webarchive – archived version available. targeta.co.uk. Retrieved 1 August 2010.
  158. ↑ Template:Cite web – archived trade register data.
  159. ↑ Template:Sfn (Gordon 2006) p.497
  160. ↑ 160.0 160.1 {{usurped link [2] acig.org archive }}
  161. ↑ Template:Cite web – archived article on modernization.
  162. ↑ Template:Cite web – archived Flight Global report.
  163. ↑ Template:Cite web – archived Slovak Ministry site.
  164. ↑ Template:Cite web – BBC News report.
  165. ↑ Template:Cite web – Reuters article.
  166. ↑ Template:Cite news – Yahoo! News report.
  167. ↑ Template:Cite news – EurAsian Times commentary.
  168. ↑ Template:Cite web – SME Spectator report.
  169. ↑ Template:Cite book Cooper Tom (Hot Skies Over Yemen), Helion & Company Publishing (Solihull UK), pp.51,53
  170. ↑ Letecké muzeum Kbely láká na unikát. Slavnou sovětskou stíhačku MiG-29, Novinky CZ, Archived 27 May 2016 at the Wayback Machine Retrieved 26 May 2016.
  171. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named Bundeswehr
  172. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  173. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  174. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  175. ↑ Gordon 2006, p. 475.
  176. ↑ 176.0 176.1 Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  177. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  178. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  179. ↑ 179.0 179.1 Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  180. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  181. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  182. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  183. ↑ Gordon 2006, p. 444.
  184. ↑ Gordon 2006, p. 445.
  185. ↑ 185.0 185.1 185.2 Gordon 2006, p. 499.
  186. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  187. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  188. ↑ Gordon   & 2006  .
  189. ↑ {{cite web  url=https://www.valka.cz/MiG‑29A‑5817‑t51607 title="MiG‑29A 5817 : Československo" website Valka place CZ date 30 December 2006 access-date 24 May 2021 archive-date 24 May 2021 archive-url=https://web.archive.org/web/20210524161256/https://www.valka.cz/MiG‑29A‑5817‑t51607 url-status live}}
  190. ↑ {{cite web url=https://www.valka.cz/MiG‑29A‑5515‑t51605 title="MiG‑29A 5515 : Československo" website Valka place CZ date 30 December 2006 access-date 24 May 2021 archive-date 24 May 2021 archive-url=https://web.archive.org/web/20210524161254/https://www.valka.cz/MiG‑29A‑5515‑t51605 url-status live}}
  191. ↑ {{cite news title=MIG‑29 receives a new home url=https://www.goodfellow.af.mil/Newsroom/Article‑Display/Article/373058/mig‑29‑receives‑a‑new‑home/ access-date 23 August 2016 work Goodfellow Air Force Base date 22 May 2013 archive-url=https://web.archive.org/web/20160911104725/http://www.goodfellow.af.mil/News/ArticleDisplay/tabid/322/Article/373058/mig‑29-receives-a-new-home.aspx archive-date 11 September 2016 url-status live df=dmy-all}}
  192. ↑ {{cite web url=http://www.aeroresource.co.uk/operational-reports/nas-fallon title="NAS Fallon" publisher=AeroResource date 2016–03–03 access-date 2019–02–02 archive-url=https://web.archive.org/web/20160411210616/http://www.aeroresource.co.uk/operational-reports/nas-fallon/ archive-date 11 April 2016 url-status live df=dmy-all}}
  193. ↑ {{cite web last1 Seaman first1 Richard title=Nellis AFB Threat Training Facility Aircraft url=http://www.richard-seaman.com/Aircraft/Museums/ThreatTrainingFacility/Aircraft website The Flying Kiwi access-date 23 August 2016 archive-url=https://web.archive.org/web/20070630152434/http://www.richard-seaman.com/Aircraft/Museums/ThreatTrainingFacility/Aircraft/archive-date 30 June 2007 url-status live df=dmy-all}}
  194. ↑ {{cite web title=Mikoyan-Gurevich MiG‑29A url=https://www.nationalmuseum.af.mil/Visit/Museum‑Exhibits/Fact-Sheets/Display/Article/197174/mikoyan-gurevich-mig‑29a website National Museum of the US Air Force access-date 23 August 2016 date 29 May 2015 archive-url=https://web.archive.org/web/20161122192720/http://www.nationalmuseum.af.mil/Visit/MuseumExhibits/FactSheets/Display/tabid/509/article/197174/mikoyan-gurevich-mig‑29a.aspx archive-date 22 November 2016 url-status live df=dmy-all}}
  195. ↑ {{cite web title="Fulcrum-A" url=http://www.pimaair.org/aircraft-by-name/item/mikoyan-gurevich-mig‑29‑fulcrum-a website=Pima Air & Space Museum access-date 23 August 2016 archive-url=https://web.archive.org/web/20160810030857/http://www.pimaair.org/aircraft-by-name/item/mikoyan-gurevich-mig‑29‑fulcrum-a archive-date 10 August 2016 url-status live df=dmy-all}}
  196. ↑ 196.0 196.1 {{cite web title="Aircraft on loan (by Location)" url=https://www.nationalmuseum.af.mil/Portals/7/documents/other/aircraft_on_loan_by_location.pdf website National Museum of the US Air Force access-date 8 November 2016 archive-url=https://web.archive.org/web/20161122040605/http://www.nationalmuseum.af.mil/Portals/7/documents/other/aircraft_on_loan_by_location.pdf archive-date 22 November 2016 url-status live df=dmy-all}}
  197. ↑ {{cite web title="Military Aircraft" url=http://www.evergreenmuseum.org/military-aircrafts website Evergreen Museum Campus publisher Evergreen Museum access-date 23 August 2016 archive-url=https://web.archive.org/web/20160815105616/http://www.evergreenmuseum.org/military-aircrafts archive-date 15 August 2016 url-status live df=dmy-all}}
  198. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named Hoffman
  199. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named Aircraft
  200. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named fhdc20140514
  201. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named faar20210915
  202. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  203. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  204. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  205. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  206. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  207. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  208. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).

Cite error: <ref> tag with name "FOOTNOTEGordon2006481" defined in <references> is not used in prior text.
Cite error: <ref> tag with name "FOOTNOTEGordon2006482" defined in <references> is not used in prior text.

Cite error: <ref> tag with name "FOOTNOTEIISS2024371" defined in <references> is not used in prior text.

Bibliography

  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value)..
  • The time allocated for running scripts has expired..
  • The time allocated for running scripts has expired.
  • The time allocated for running scripts has expired.
  • The time allocated for running scripts has expired.
  • Jenkins, Dennis R. McDonnell Douglas F-15 Eagle, Supreme Heavy-Weight Fighter. Arlington, TX: Aerofax, 1998. The time allocated for running scripts has expired.The time allocated for running scripts has expired.The time allocated for running scripts has expired..
  • Lake, Jon. "Mikoyan MiG-29 'Fulcrum'". World Air power Journal. Volume 4, Winter 1990/91. London: Aerospace Publishing. pp. 44–91. The time allocated for running scripts has expired.The time allocated for running scripts has expired.The time allocated for running scripts has expired.. Template:ISSN.
  • The time allocated for running scripts has expired..
  • The time allocated for running scripts has expired..
  • The time allocated for running scripts has expired..
  • North, David M. MiG-29 Pilot Report, part 1 The time allocated for running scripts has expired. Part 2 The time allocated for running scripts has expired.
  • Spick, Mike, ed. "MiG-29 'Fulcrum'". "The Flanker". Great Book of Modern Warplanes. St. Paul, MN: MBI Publishing, 2000. The time allocated for running scripts has expired.The time allocated for running scripts has expired.The time allocated for running scripts has expired..

External links

Template:Mikoyan aircraft Template:YAF aircraft Template:USAF/DoD reporting names

The time allocated for running scripts has expired.