Jump to content

Sukhoi Su-27

From Alfawiki
Sukhoi Su-27
Company typeFighter aircraft
IndustryAerospace
Founded1985
FounderSukhoi Design Bureau
Headquarters
Soviet Union
ProductsSu-27 and variants (Su-30, Su-33, Su-34, Su-35, Su-37)

Overview

The Sukhoi Su-27 (Russian: Сухой Су-27; NATO reporting name: Flanker) is a twin-engine, supersonic fighter aircraft originating from the Soviet Union, engineered by Sukhoi to exhibit exceptional supermaneuverability. It was developed to rival prominent American fourth-generation jet fighters such as the Grumman F-14 Tomcat and McDonnell Douglas F-15 Eagle. Boasting a combat radius of approximately 3,530-kilometre (1,910 nmi), substantial weapons payload capacity, advanced avionics systems, and superior agility, the Su-27 was primarily designed for air superiority roles. Its design complements the Mikoyan MiG-29, fulfilling different operational niches.

Introduced into service with the Soviet Air Forces in 1985, the Su-27’s main function was long-range air defense aimed at countering American strategic bombers such as the Rockwell B-1B Lancer and Boeing B-52G and H Stratofortress. It also played a critical role in securing Soviet maritime borders against carrier-based aircraft and provided extended fighter escort for heavy bombers including the Tupolev Tu-95, Tupolev Tu-22M, and Tupolev Tu-160.

Development and Variants

The Su-27 platform evolved into a diverse family of aircraft tailored for various combat roles. Among these is the Sukhoi Su-30, a two-seat multirole fighter capable of all-weather operations, combining air-to-air and air-to-surface interdiction capabilities. The naval variant, Sukhoi Su-33, serves as a fleet defense interceptor optimized for deployment from aircraft carrier decks. Additional models include the side-by-side two-seat strike/fighter-bomber version known as the Sukhoi Su-34, and the enhanced air superiority multirole fighter, the Sukhoi Su-35. A specialized thrust-vectoring model, designated Sukhoi Su-37, was also developed. Furthermore, the Chinese-produced Shenyang J-11 is a licensed copy of the original Su-27 design.

Development

Template:More citations needed section

File:Sukhoi T-10 Flanker-A 10 blue (9987131666).jpg
Prototype Sukhoi T-10

In 1969, the Soviet Union became aware of the United States Air Force's "F-X" initiative, which led to the creation of the F-15 Eagle. Soviet authorities quickly recognized that this new American fighter would provide a significant technological edge over their current aircraft. The need arose for a more balanced fighter featuring both superior maneuverability and advanced systems. Consequently, the Soviet General Staff issued a requirement for a Perspektivnyy Frontovoy Istrebitel (PFI, translated as "Prospective Frontline Fighter" or "Advanced Frontline Fighter").[1] The specifications were highly demanding, calling for extended range, strong short-field capabilities—including operation from rudimentary airstrips—exceptional agility, speeds exceeding Mach 2, and substantial firepower. The aerodynamic layout was primarily developed by TsAGI in partnership with the Sukhoi design bureau.[1]

Due to the complexity and expense of fulfilling the PFI requirements with a single model in sufficient quantities, the specification was divided into two categories: LPFI (Lyogkyi PFI, Lightweight PFI) and TPFI (Tyazholyi PFI, Heavy PFI). The LPFI effort produced the Mikoyan MiG-29, a tactical fighter with relatively limited range, while Sukhoi OKB took on the TPFI program, resulting in the Su-27 and its derivatives.

Sukhoi's design, continuously refined based on Soviet intelligence regarding the F-15's capabilities, was designated as the T-10 (Sukhoi’s tenth design) and made its maiden flight on 20 May 1977. This aircraft featured a large, clipped wing, twin podded engines mounted separately, and a twin-tail configuration. The space or 'tunnel' between the engines—similar to that seen on the F-14 Tomcat—served dual purposes: providing additional lift and concealing weaponry from radar detection.

The development of the T-10 incorporated insights from the Sukhoi Aircraft Design Bureau (Su-ADB), TsAGI, and the Siberian Aviation Research Institute (SibNIA). They pioneered an aerodynamic concept termed the 'integral scheme', which optimized performance under a longitudinal instability of approximately 3–5% mean aerodynamic chord during subsonic flight regimes. This approach also anticipated fly-by-wire (FBW) control systems for future heavy fighters. Stability challenges encountered in developing airframes with similar performance goals—such as those in the YF-22 and JAS-39 Gripen—were addressed during FBW system development by limiting normal load factor and angle of attack. Emphasis on controlled high-angle-of-attack maneuvering, known as supermaneuverability, was reinforced following research in the 1980s by Su-ADB and TsAGI teams demonstrating its tactical advantage in close-range combat.[2]

Air Force

File:Su-27 05.jpg
Soviet Su-27 in flight
File:P-42 at Ramenskoye.jpg
P-42 at Ramenskoye airfield

The initial flying prototypes, designated T-10-1 and T-10-2, were equipped with Lyulka AL-21 turbojet engines and featured ogival wing designs. During their construction, the aerodynamic configuration proved inadequate, a fact confirmed by the maiden flight of T-10-1 on 20 May 1977.[3] After completing testing in November 1983, T-10-1 was transferred to the Soviet Air Force Museum by late 1985. T-10-2 took to the skies for the first time on 16 May 1978 but tragically crashed on 7 July 1978, resulting in the pilot’s death; this accident occurred after the aircraft surpassed its G limit and disintegrated mid-flight following erratic behavior when the control stick was pulled rearward. Initially, Western intelligence referred to these prototypes as "Ram-K", having detected them via satellite imagery at the Flight Research Institute (LII) located at "Ramenskoye" airfield near Zhukovsky. They were subsequently assigned the NATO codename "Flanker-A".[4] The second series, T-10-3 and T-10-4, were produced by Komsomolsk-on-Amur Aircraft Plant (KnAAPO) beginning in 1978 and marked the first use of the intended powerplant, the Lyulka AL-31 turbofan, with redesigned engine nacelles to accommodate it.[5] After delays caused by engine issues, T-10-3 conducted its initial flight on 23 August 1979 and later performed land-based STOBAR trials for naval aviation during 1982 and 1983.[6] Meanwhile, T-10-4 was dedicated to testing avionics and armaments equipped with the Mech radar.[7] However, evaluations involving both T-10-4 and the subsequent T-10-10 highlighted significant shortcomings in the Mech radar system.[8] KnAAPO then constructed a third group of "type T-10-5" aircraft powered by AL-21 engines—namely T-10-5, T-10-6, T-10-9, T-10-10, and T-10-11—primarily for avionics experimentation.[9] Notably, T-10-6 was lost in October 1980 due to a ground fire triggered by a leaking fuel line.[10] The models T-10-10 and T-10-11 undertook radar, weapons control, and targeting system tests.[11] These prototype trials revealed that avionics weight, AL-31 fuel efficiency, and aerodynamic performance did not fulfill design criteria.[12]

Consequently, a comprehensive redesign was initiated. Sukhoi increased collaboration with SibNIA, which carried out extensive wind tunnel analyses. Insights were also drawn from contemporary Western aircraft designs. The resulting new model—designated T-10S—bore only superficial similarity to the original T-10; its design was finalized in 1980 and served as the foundation for the production Su-27.[13] The initial flying prototypes of this series were T-10-7 (also known as T-10S-1) and T-10-12 (or T-10S-2). The T-10-7 focused on handling characteristics, maneuverability, and AL-31 engine trials; it lacked radar or combat avionics. Its maiden flight occurred on 20 April 1981 but ended with a crash on 3 September 1981 due to a critical in-flight failure; the pilot successfully ejected. Following this incident, the project’s chief was replaced and the flight engineer dismissed.[14] KnAAPO completed T-10-12 in March 1981 to conduct fire control system testing; however, it disintegrated during flight on 23 December 1981, resulting in pilot fatality and leading to dismissal of Sukhoi’s general designer.[15] Further production batches were assembled by KnAAPO throughout 1982—comprising T-10-15, and T-10-17 through T-10-22[16]—and continued into 1983 with models from T-10-23 to T-10–27.[17] The aircraft designated T‑10‑17 was notable as the first built to full production standards; it completed its first flight on 26 May 1982.[16] In one instance during 1983, this aircraft managed to land safely despite losing part of a wing and tail fin due to structural failure.[18] Another prototype, T‑10‑21, crashed on 25 May 1984 caused by failure of a leading edge flap; fortunately, its pilot ejected safely.[18]

The modified version of T‑10S‑3, officially named P‑42, established multiple world records for time-to-height,[19] surpassing records set in 1975 by a similarly modified McDonnell Douglas F‑15 Eagle nicknamed "The Streak Eagle".[20] Known as the "Streak Flanker," this aircraft had all armament, radar systems, and operational equipment removed. Additionally, fin tips, tail-boom sections, and wingtip launch rails were eliminated; its composite radome was substituted with a lighter metal variant. The airframe was stripped of paint, polished meticulously, and all gaps or joints causing drag were sealed. Engine modifications increased thrust output by approximately 1,000 kg (2,200 lb), achieving a thrust-to-weight ratio nearing two-to-one (refer to Specifications for standard configuration comparison).[21][22]

File:Sukhoi Su‑27UB ’17 red’ (37514194274).jpg
Twin-seat combat trainer Su‑27UB of the Russian Aerospace Forces

Production of the operational Su‑27 model (occasionally called Su‑27S, NATO reporting name 'Flanker-B') commenced entering service with the Soviet Air Forces (VVS) from 1985 onward; however, manufacturing challenges delayed its widespread deployment until approximately 1990.[23] The Su‑27 served within both the Soviet Air Defence Forces (V-PVO) and Frontal Aviation branches. Conversion training for operational units utilized the twin-seat trainer variant known as Su‑27UB (Russian: Uchebno Boevoy, meaning "combat trainer"; NATO designation 'Flanker-C'), which featured tandem seating arrangements.[24]

During development of a naval Flanker trainer variant, Soviet Air Force planners were simultaneously assessing replacements for the Sukhoi Su‑24 strike aircraft ("Fencer"). It became clear that any successor would need capabilities sufficient to contend with contemporary American fighters such as the F‑15 and F‑16. Sukhoi concentrated efforts on modifications derived from the standard Su‑27UB tandem-seat trainer platform; however, Soviet preferences leaned toward side-by-side crew seating—as employed in the Su‑24—for enhanced workload management during extended strike missions. Consequently, a conceptual naval side-by-side trainer served as a basis for developing the Su‑27IB (Russian: Istrebityel Bombardirovshchik, meaning "fighter bomber") intended as an Su‑24 replacement starting in 1983. The first production unit flew in early 1994 under its updated designation: Su‑34 (NATO reporting name 'Fullback').[25]

Navy

File:The 279th separate naval fighter regiment (Murmansk Region) (26).jpg
A Su-33 on approach

Shortly after the primary land-based model was developed, work began on a naval variant for the Soviet Navy, known as the Su-27K (derived from Korabyelny, meaning "shipborne", with NATO reporting name 'Flanker-D'). Several T-10 demonstrators were adapted to evaluate features necessary for carrier operations, which subsequently resulted in specialized prototypes named "T-10K" for naval use. These T-10Ks incorporated canards, an arrestor hook, avionics tailored for carrier landings, and a retractable in-flight refueling probe. However, they lacked the reinforced landing gear for carrier touchdowns and did not have folding wings. The inaugural flight of a T-10K occurred in August 1987, piloted by renowned Soviet test pilot Viktor Pugachev—who later showcased the Cobra maneuver with an Su-27 in 1989—conducting test takeoffs from a land-based ski-jump platform located on the Black Sea coast near Saky in the Ukrainian SSR. Unfortunately, this aircraft was lost in a 1988 accident.

During the period when the naval Flanker was under development, the Soviets were constructing their initial class of aircraft carriers but lacked experience with steam catapults and wished to avoid postponing carrier deployment. Consequently, they adopted a catapult-free launch technique whereby full engine thrust was applied against a blast deflector until release restraints disengaged, allowing the fighter to accelerate along the deck and launch off a ski jump ramp.[26]

The production model Su-27K included reinforced landing gear featuring a dual-wheel nose assembly, folding stabilators and wings, extended outer ailerons combined with inner double-slotted flaps, and enlarged leading-edge slats to facilitate low-speed approaches to carriers. It also had modified leading edge root extensions (LERX) equipped with canards, an adjusted ejection seat angle, enhanced fly-by-wire systems, upgraded hydraulic components, an arrestor hook, and a retractable aerial refueling probe accompanied by two deployable floodlights in the nose designed to illuminate the tanker during nighttime operations. Carrier trials for the Su-27K commenced in November 1989 with Pugachev at the controls aboard the Soviet Union’s first aircraft carrier—then named Tbilisi. Formal carrier operations started in September 1991.[27][28]

Initiated in 1989, development of the naval trainer variant dubbed Su-27KUB (from Korabyelny Uchebno-Boyevoy, meaning "shipborne trainer-combat") aimed to create a dual-role airframe serving both Navy and Air Force requirements. This design was intended to support various missions including reconnaissance, aerial refueling, maritime strike, and electronic jamming. This concept eventually evolved into the Su-27IB (Su-34 "Fullback") for Soviet Air Force service. The naval trainer featured a redesigned forward fuselage housing a side-by-side cockpit layout with crew access via a ladder located within the nose-wheel bay. It also incorporated larger canards, stabilizers, fins, and rudders. The wings were equipped with additional hardpoints for ordnance and had folding mechanisms relocated further outward. The air intakes were fixed and lacked foreign object damage protection systems. Structural reinforcements increased maximum gross weight capacity to 45 tonnes (99,000 pounds), while internal volume was expanded by approximately 30%. The first prototype, designated T-10V-1, took flight in April 1990 and conducted aerial refueling tests along with simulated carrier landing approaches aboard the Tbilisi. A second prototype, T-10V-2, followed in 1993 featuring larger internal fuel tanks, an extended dorsal spine, lengthened tail section, and tandem dual-wheel main landing gear.[25]

Export and post-Soviet evolution

In 1991, KnAAPO and Irkutsk manufacturing plants introduced export-oriented versions of the Su-27: the single-seat fighter Su-27SK and the two-seat trainer Su-27UBK (with "K" standing for the Russian word "Kommercheskiy," meaning "Commercial"). These models have been sold to countries including China, Vietnam, Ethiopia, and Indonesia. Following the fall of the USSR in 1991, Russia, as the successor state, began advancing various Su-27 derivatives such as the Su-30, Su-33, Su-34, Su-35, and Su-37.

Since 1998, China has produced the export Su-27SK under license as the Shenyang J-11. The initial licensed aircraft was assembled in Shenyang from Russian-supplied kits and took its maiden flight on 16 December 1998. These license-built jets, totaling around 100 units, were designated J-11A. The subsequent J-11B variant incorporated a significant number of Chinese-developed components within the original Su-27SK airframe.

Beginning in 2004, the Russian Air Force initiated a comprehensive modernization program for its original Soviet-era Su-27 ('Flanker-B') fleet. The updated models were named Su-27SM (an abbreviation of the Russian "Seriyniy Modernizovanniy," meaning "Serial Modernized"). Enhancements included improved air-to-air combat capabilities through integration of the R-77 missile equipped with an active radar seeker. These upgraded Su-27SM fighters are classified within the 4+ generation. Their strike potential was also augmented by adding air-to-surface weapons such as the Kh-29T/TE/L and Kh-31P/Kh-31A missiles along with precision-guided bombs like the KAB-500KR/KAB-1500KR. Avionics systems received significant upgrades as well. Currently, the Russian Air Force is acquiring aircraft modernized to the SM3 standard, which demonstrates a twofold increase in air target engagement efficiency and a threefold improvement against ground targets compared to the baseline Su-27. The Su-27SM3 features two extra underwing hardpoints and a reinforced airframe. It is outfitted with advanced onboard electronic systems and supports a broader array of air-launched weaponry. The cockpit incorporates multifunctional display units.

The two-seat multi-role variant derived from the Su-27UBK is known as the Su-30, designed primarily for export and developed into two principal versions. The Chinese export model, designated SU-30MKK ('Flanker-G'), first flew in 1999. Meanwhile, the Indian export variant, called Su-30MKI ('Flanker-H'), was delivered starting in 2002 and includes at least five different configurations.

The Su-33 serves as the naval adaptation of the Soviet Su-27K, which was renamed by Sukhoi Design Bureau after 1991. Both variants carry the NATO codename 'Flanker-D'.

The Su-34 evolved from the Soviet-era Su-27IB, itself developed from the naval Su-27KUB operational conversion trainer. This model was formerly identified as the Su-32MF.

The most recent and sophisticated iteration of the Su-27 family is the Su-35S ("Serial"). This aircraft was previously known under several designations including Su-27M, Su-27SM2, and Su-35BM.

Derived from prototypes of the Su-35, the Su-37 was an advanced technology demonstrator featuring thrust vectoring nozzles constructed from titanium instead of steel, alongside an updated airframe incorporating substantial amounts of carbon-fiber and Al-Li alloy. Only two units were produced; one crashed in 2002, effectively terminating this program. Nonetheless, many improvements pioneered by the Su-37 were integrated into later Flanker variants such as the Su-35S and Su-30MKI.

Design

File:Cockpit of Sukhoi Su-27 (2).jpg
Cockpit

The Su-27's fundamental aerodynamic layout bears resemblance to the MiG-29, yet it is markedly larger in scale. Its wings are mounted mid-fuselage at the leading edge extensions and exhibit a semi-delta wing shape, with truncated tips designed to accommodate missile launch rails or ECM pods. This aircraft exemplifies a tailed delta wing arrangement, maintaining traditional horizontal tailplanes despite its delta wing form.[29]

File:Su-27 Cobra 2b.png
Diagram showing the Su-27 executing a Cobra maneuver

The Su-27 was the Soviet Union's first fighter to feature an operational fly-by-wire system, developed drawing on Sukhoi OKB's prior work with the T-4 bomber. The combination of this advanced control system, low wing loading, and robust flight control surfaces results in outstanding agility, allowing precise handling even at very low speeds and extreme angle of attack. At airshows, the aircraft has showcased its exceptional maneuverability by performing the Cobra maneuver, temporarily maintaining level flight at an angle of attack near 120°.

File:Su-27 armament.jpg
Su-27 equipped with Vympel R-27 missiles

The naval variant known as the Su-27K (or Su-33) includes canards that provide additional lift, thereby shortening takeoff runs. These canard surfaces have also been integrated into select models such as the Su-30, Su-35, and Su-37.

For detection and targeting, the Su-27 is fitted with a Phazotron N001 Myech coherent Pulse-Doppler radar system capable of track while scan functionality and look-down/shoot-down engagement. Additionally, an OLS-27 IRST sensor is positioned in the nose section ahead of the cockpit, offering detection ranges between 80–100 km (50–62 mi).Cite error: The opening <ref> tag is malformed or has a bad name

Armament includes a single 30 millimetres (1.2 in) Gryazev-Shipunov GSh-30-1 cannon installed in the starboard wing root, complemented by up to 10 external hardpoints for various ordnance. Its typical air-to-air missile loadout consists of a combination of short-range R-73 (AA-11 Archer) and medium-range R-27 (AA-10 'Alamo') missiles, with the latter available in both extended range and infrared homing variants.

Soviet Union and Russia

File:Su-27SM3 flight, Celebration of the 100th anniversary of Russian Air Force.jpg
Russian Su-27SM3

The introduction of Su-27s into the Soviet Air Force inventory commenced in June 1985.[23] The first operational unit to be equipped was the 831st Fighter Aviation Regiment, stationed at Myrhorod Air Base, Ukrainian SSR, receiving aircraft in November 1985.[30][31] Official induction into service occurred in August 1990.[23]

On 13 September 1987, a Soviet Su-27 identified as Red 36, fully armed, intercepted a Norwegian Lockheed P-3 Orion maritime patrol aircraft over the Barents Sea. The Soviet jet conducted multiple close passes and collided with the P-3 during its third approach. Both aircraft subsequently disengaged safely and returned to their respective bases.Cite error: The opening <ref> tag is malformed or has a bad name

During the conflict in Abkhazia from 1992 to 1993, Russian Su-27s were deployed against Georgian forces. On 19 March 1993, Major Vatslav Aleksandrovich Shipko was reportedly killed when his fighter was mistakenly downed by an S-75M Dvina surface-to-air missile while intercepting Georgian Su-25 close air support jets.Cite error: The opening <ref> tag is malformed or has a bad nameCite error: The opening <ref> tag is malformed or has a bad name

In the 2008 South Ossetia War, Russian forces utilized Su-27s to establish air superiority over Tskhinvali, South Ossetia’s capital.[32][33]

On 7 February 2013, two Su-27 fighters briefly entered Japanese sovereign airspace near Rishiri Island off Hokkaido. They proceeded southward over the Sea of Japan before returning north. In response, four Mitsubishi F-2 fighters were scrambled for visual identification and radio warnings were issued to vacate Japanese airspace.[34][35][36] The Japan Ministry of Defense released photographs captured by a JASDF pilot showing one of these Su-27s. Russia denied any violation, asserting that their aircraft were conducting routine patrols near the disputed Kuril Islands.[37][34]

File:Russian SU-27 Flanker with RAF Typhoon MOD 45157730.jpg
A Russian Su-27 alongside a British Eurofighter Typhoon over the Baltic Sea, June 2014

Russia intends to phase out both the Su-27 and Mikoyan MiG-29 fleets in favor of introducing the fifth-generation twin-engine multi-role Sukhoi Su-57 fighter aircraft.Cite error: The opening <ref> tag is malformed or has a bad name

In November 2015, a squadron of Su-27SM3 variants was deployed to Syria as part of Russia’s military intervention in the Syrian Civil War.Cite error: The opening <ref> tag is malformed or has a bad nameCite error: The opening <ref> tag is malformed or has a bad name

On 25 March 2020, a Russian Su-27 crashed under unclear circumstances over the Black Sea. Despite extensive search operations involving helicopters, naval vessels, and drones amid adverse weather conditions, the pilot was not recovered. The last known position was approximately 50 kilometers from Feodosia city.[38][39]

China

File:PLAAF J-11BS - 1.jpg
PLAAF J-11BS

China was the initial foreign buyer of the Su-27, acquiring a total of 76 aircraft constructed in the Soviet Union and Russia—comprising 36 Su-27SKs and 40 Su-27UBKs.

Discussions with the Soviet Union began in June 1990 regarding the potential acquisition of MiG-29s and Su-24s; by October of that year, China had shifted its focus to the more advanced Su-27. This procurement initiative was designated as the "906 Project" by China. In February 1991, a Su-27 conducted a demonstration flight at Beijing's Nanyuan Airport.

In May 1991, China placed an order for 24 Su-27 fighters, accompanying armaments, and a flight simulator. Approximately 70% of the payment was made through barter arrangements involving primarily low-grade light industrial products and foodstuffs. The weakened condition of the Soviet economy at that time enhanced China's leverage during negotiations. By 1995, estimates placed the cost between $1.3 billion and $1.5 billion. The initial delivery included 12 aircraft—eight Su-27SKs and four Su-27UBKs—in late 1991, followed by an additional 12 in 1992. These first deliveries were assigned to Wuhu Air Base during the early 1990s. These units featured N001E radar systems capable of tracking a single target simultaneously; subsequent batches were equipped with N001P radars allowing engagement of two targets concurrently.

By the end of 1992, two additional aircraft—likely Su-27UB trainers—were either ordered or received.

In 1995, modifications were made to both payment terms and contract scope: China agreed to settle payments exclusively in US dollars, while Russia consented to permit licensed production of the Su-27 under the designation J-11. However, Russian negotiators lacked official authorization from their government to approve this licensing arrangement. Between 1995 and 1996, China took delivery of 18 Su-27SKs and six Su-27UBKs.

In December 1999, China placed an order for 28 Su-27UBK trainer aircraft; the first batch of 12 arrived in December 2000, with the remaining units delivered by September 2009.

As of 2012, Chinese-operated Su-27s were unable to deploy the R-77 air-to-air missile due to constraints within their fire control systems.

Ethiopia

Ethiopian Su-27 fighters successfully downed two Eritrean MiG-29 aircraft and inflicted damage on a third during the Eritrean-Ethiopian War in February 1999, later destroying an additional two in May 2000. These Su-27s were also deployed for roles such as combat air patrol (CAP), suppression of enemy air defenses, and escorting fighter jets on bombing and reconnaissance sorties. The introduction of the Su-27 marked the replacement of the older Mikoyan-Gurevich MiG-21, which had served as the primary air superiority fighter for the Ethiopian Air Force from 1977 until 1999.

During the Tigray War, Ethiopian forces utilized their Su-27s in bombing operations, with aircraft observed carrying OFAB-250 unguided bombs over the skies of Mekelle. On 25 August 2022, Ethiopian officials reported that an ETAF Su-27 intercepted and subsequently shot down an An-26 aircraft after it violated airspace originating from Sudan.

Angola

The Su-27 was introduced into Angolan military service around mid-2000 during the period of the Angolan Civil War. Reports indicate that on 19 November 2000, a Su-27 was shot down by 9K34 Strela-3 MANPADS launched by UNITA forces while attempting to land.[40][41]

Indonesia

File:Indonesian Air Force Sukhoi Su-27SKM Flanker.jpg
Sukhoi Su-27SKM Flanker of the Indonesian Air Force

In a notable deployment, four Indonesian Flanker-class fighters, including Su-27s, took part in the biennial Exercise Pitch Black held in Australia for the first time on 27 July 2012. Upon arrival at Darwin in the Northern Territory, the two Su-27s alongside two Sukhoi Su-30s were escorted by a pair of Australian F/A-18 Hornet jets from No. 77 Squadron, Royal Australian Air Force.[42] Exercise Pitch Black 2012 ran from 27 July to 17 August, involving approximately 2,200 personnel and up to 94 aircraft representing Australia, Indonesia, Singapore, Thailand, New Zealand, and the United States.Cite error: The opening <ref> tag is malformed or has a bad name</ref>

North Korea

Admiral Samuel Paparo, head of the United States Indo-Pacific Command, has indicated that North Korea is expected to receive an unspecified quantity of Su-27 and MiG-29 fighters from Russia. This transfer is reportedly linked to Pyongyang’s deployment of troops in support of Russia’s conflict in Ukraine. However, The War Zone notes that such deliveries are unlikely to occur in the near future.Cite error: The opening <ref> tag is malformed or has a bad name</ref>

Ukraine

File:Ukrainian Air Force Sukhoi Su-27P Flanker (29583343448).jpg
A Su-27P of the Ukrainian Air Force arriving at the 2018 RIAT in England
File:Ukrainian Su-27s during a Bomber Task Force Europe mission.jpg
During a Bomber Task Force Europe mission on 23 September 2020, a B-52H from the 5th Bomb Wing operates alongside Ukrainian Su-27s
File:President took part in the festive Parade of Troops on the occasion of the 30th anniversary of Ukraine's independence. (51716068356).jpg
Ukrainian Su-27s performing a flypast at the Kyiv Independence Day Parade on 24 August 2021

Following the dissolution of the Soviet Union, the Ukrainian Air Force came into possession of approximately 66 to 70 Su-27 fighters. Due to financial constraints combined with the aircraft’s demanding maintenance needs, spare parts became scarce and servicing was insufficient, resulting in only about 34 operational aircraft by 2019. Years without adequate funding meant no new Su-27 deliveries were made since 1991. Between 2007 and 2017, Ukraine sold up to 65 combat jets internationally, which included nine Su-27s. Starting in 2009, as relations with Russia deteriorated amid the 2009 Russia–Ukraine gas dispute, obtaining spare parts for Sukhoi jets became increasingly difficult. At the time of Russia’s annexation of Crimea and the onset of the War in Donbas (2014–2022), only 19 Su-27s remained serviceable. However, after the escalation into full-scale conflict with Russia, Ukraine boosted its military budget, enabling stored Su-27s to be restored to active duty.

The Zaporizhzhya Aircraft Repair Plant "MiGremont" in Zaporizhzhia initiated modernization efforts for the Su-27 platform starting in 2012, aiming to upgrade systems to meet NATO standards. This upgrade involved modest improvements to radar, navigation, and communication equipment. The updated variants were designated Su-27P1M and Su-27UB1M. The Ukrainian Ministry of Defence officially approved this project on 5 August 2014, with the first two modernized aircraft delivered to the 831st Tactical Aviation Brigade by October 2015. Despite these enhancements, Ukrainian Su-27 avionics and missile technology remained considerably behind Russian counterparts by two technological generations.

During the 2014 annexation of Crimea, a Ukrainian Su-27 was scrambled on 3 March to intercept Russian fighter jets violating Ukrainian airspace over the Black Sea. Throughout the conflict in Donbas prior to February 2022, Ukrainian Su-27s had a limited combat role due to minimal aerial opposition and other aircraft being assigned ground attack missions. They were observed conducting low-altitude flyovers, providing top cover, performing combat air patrols, and escorting or intercepting civilian flights over Eastern Ukraine. Footage from this period shows these fighters armed with R-27 and R-73 air-to-air missiles.

Two fatal accidents involving Ukrainian Su-27s occurred in 2018. On 16 October, Colonel Ivan Petrenko piloting a Su-27UB1M crashed during the "Clear Sky 2018" exercise near Starokostiantyniv Air Base. Lieutenant Colonel Seth Nehring of the 144th Fighter Wing, California Air National Guard, occupied the second seat; both perished in this incident within western Ukraine's Khmelnytskyi Oblast. Later that year on 15 December, another Su-27 went down during final approach roughly 2 km (1 mi) from Ozerne Air Base, following a training sortie; Major Fomenko Alexander Vasilyevich lost his life.

On 29 May 2020, Ukrainian Su-27s participated alongside B-1B bombers in a Bomber Task Force mission over the Black Sea region for the first time. Subsequently, on 4 September 2020, three B-52 bombers from the 5th Bomb Wing, based at Minot Air Force Base, North Dakota, conducted critical integration training exercises with Ukrainian MiG-29s and Su-27s within Ukraine’s airspace.

Russian invasion of Ukraine

During the Russian invasion of Ukraine, the Su-27 fighter jet was operated by forces on both sides.[43] On the initial day of the conflict, 24 February 2022, a Ukrainian Su-27 along with a refueling vehicle at Ozerne Air Base in Zhytomyr District were destroyed by fire following a Russian assault.[44] The subsequent day saw another Ukrainian Su-27 being downed over Kyiv by a Russian S-400 missile system.[45] This event was captured on video by local witnesses and shared on Twitter.[46] The pilot of this aircraft, Colonel Oleksandr Oksanchenko, lost his life.[47] Ukrainian authorities later confirmed the loss of a third Su-27 near Kropyvnytskyi in central Ukraine, with the pilot also perishing.[48]

On 7 May 2022, two Ukrainian Su-27 jets executed a rapid, low-altitude bombing mission against Russian forces occupying Snake Island; this strike was documented by a Bayraktar TB2 drone.[49]

A Ukrainian Su-27 bearing bort number 38 blue was downed on 7 June 2022 while operating at low altitude near Orikhiv in Zaporizhzhia Oblast. Reports suggest the aircraft was destroyed either by an adversary air-to-air missile or due to friendly fire.[50][51]

On 21 August 2022, combat operations resulted in the loss of another Ukrainian Su-27; the pilot did not survive.[52][53]

In September 2022, observations indicated that Ukrainian Su-27s were equipped with American AGM-88 HARM anti-radiation missiles.[54]

A Ukrainian Su-27 from the 39th Tactical Aviation Brigade was lost during a mission over Poltava Oblast on 13 October 2022; the pilot was killed in action.[55][56]

On 10 March 2023, a Russian Su-27 sustained damage during a partisan attack at Uglovoye airfield located in Primorsky Krai, Russia. Footage showing the aircraft ablaze was released by the Freedom of Russia Legion.[57]

A notable incident occurred on 14 March 2023 when a Russian Su-27 intercepted an American MQ-9 Reaper drone over the Black Sea. The fighter made several passes while releasing fuel onto the drone before colliding with it and causing it to crash into the sea.[58]

By August 2023, it became public knowledge that Ukrainian Su-27s had begun deploying JDAM-ER precision-guided bombs.[59]

During the 2024 Kharkiv offensive, specifically on 17 May 2024 near Metalivka in Chuhuiv Raion, a Ukrainian Su-27 was shot down. The pilot, Lieutenant Colonel Denys Vasyliuk, died in this engagement.[60][61][62][63] This particular aircraft was an upgraded Su-27UP2M model that had been undergoing testing prior to the outbreak of hostilities.[64]

As of 24 October 2025, official tallies indicate Ukraine has lost seventeen Su-27s during combat operations while Russia has suffered losses of three Su-27 aircraft.[65]

On 28 April 2025, a Ukrainian Su-27 was lost amid efforts to repel a drone assault; fortunately, the pilot successfully ejected. An investigative commission has been formed to determine the circumstances surrounding this incident.[66]

Soviet era

File:Т-10-1 VVS museum.jpg
Prototype of the original T-10
File:Su-27 Red 36.jpg
Left profile paint scheme of a first-series Sukhoi Su-27 Flanker B
File:Su27K (Su33) DD-SD-99-06153.jpg
Russian Su-27K fighter (later designated Su-33) aboard the Admiral Kuznetsov flight deck
T-10 ("Flanker-A")
The earliest prototype design.[67]
T-10S ("Flanker-A")
Enhanced prototype model, closer to the finalized production standard.[67]
P-42
A specialized variant created to set climb performance records, stripped of all weapons, radar systems, and paint to reduce its weight to approximately 14,100 kg (31,100 lb). It also featured upgraded engines. This project was analogous to the US F-15 Streak Eagle program. Between 1986 and 1988, it surpassed several climb time records previously held by the Streak Eagle. Many records, including times to ascend to 3,000 m, 6,000 m, 9,000 m, and 12,000 m, remain unbroken as of 2019.Cite error: The opening <ref> tag is malformed or has a bad nameCite error: The opening <ref> tag is malformed or has a bad name
Su-27 ("Flanker-A")
[67] Early pre-production units powered by AL-31 engines.
Su-27S (Su-27 / "Flanker-B")
[67][68] First mass-produced single-seat variant equipped with improved AL-31F engines. Also known as "T-10P".
Su-27P (Su-27 / "Flanker-B")
[67][68] Standard interceptor version lacking air-to-ground weapon control systems and wiring; assigned primarily to Soviet Air Defence Forces units. Commonly referred to simply as Su-27 without the "-P" suffix.Cite error: The opening <ref> tag is malformed or has a bad name
Su-27UB ("Flanker-C")
[67][68] Initial two-seat operational conversion trainer model.
Su-27K (Su-33 / "Flanker-D")
[67][68] Carrier-capable single-seat fighter featuring folding wings, high-lift devices, and arresting gear, produced in limited quantities. These were developed following the "T-10K" prototypes and demonstrators.
Su-27KUB (Su-33UB)
A two-seat combat and training derivative based on the Su-27K and Su-27KU designs, incorporating side-by-side seating similar to that of the Su-34. Only one prototype was constructed.
Su-27KM
A conceptual carrier-based fighter derived from the Su-27 platform that incorporated reverse-swept wings—a feature later integrated into the related Su-47.Cite error: The opening <ref> tag is malformed or has a bad name
Su-27M (Su-35/Su-37 / "Flanker-E/F")
[69][70] Advanced demonstrator variants representing a modernized single-seat multi-role evolution of the Su-27S. Included a two-seat "Su-35UB" demonstrator as well.
Su-27PU (Su-30 / "Flanker-C")
[67][68] Two-seat interceptor variant developed from the Su-27P to provide tactical data support for other single-seat interceptors such as the Su-27P and MiG-31 in PVO operations. This model was later rebranded as the Su-30 and adapted into a multi-role fighter primarily aimed at export markets, diverging from its original interceptor role.
Su-32 (Su-27IB)
Two-seat long-range strike aircraft featuring side-by-side seating within a distinctive "platypus" nose design. Served as the prototype for both the Su-32FN and Su-34 models.

Post-Soviet period

File:Su-27UBK number 8521 Jan-2014.jpg
Vietnam People's Air Force Su-27UBK equipped with a drogue parachute
Su-27PD ("Flanker-B")
A single-seat prototype featuring enhancements such as an in-flight refueling probe.
Su-30M/MK/MKK/MK2 ("Flanker-G")
A modernized, multi-role, two-seat fighter. Several Su-30Ms were produced during the mid-1990s for evaluation by Russia, though the program saw limited progress. The Su-30MK export model was developed as two demonstrators with varying capabilities. This family includes the Su-30MKK tailored for the PLAAF (China), and the Su-30MK2 variant delivered to Uganda, Vietnam, and other countries.
Su-30MKI/MKM/MKA/SM/SME/SM2 ("Flanker-H")
Significantly enhanced versions featuring new Saturn AL-31FP engines with 3D thrust-vectoring capabilities and added canards, drawing inspiration from the Sukhoi Su-34 "Fullback" and Sukhoi Su-37 "Terminator". Variants include the Su-30MKI for India, Su-30MKA for Algeria, and Su-30MKM for Malaysia. The newer Su-30SM was developed specifically for the Russian Aerospace Force (RuAF), with export versions like the Su-30SME and the advanced Su-30SM2 featuring upgraded avionics and more powerful Saturn AL-41F1S engines offering 3D thrust vectoring and approximately 20% greater thrust.
Su-27SK ("Flanker-B")
Export variant of the Su-27S featuring reinforced landing gear to support a maximum takeoff weight of 33 tonnes, meeting Chinese requirements for air-to-ground mission capability. The electronic jamming pod was downgraded to L203/L204. This model was exported to China during the 1990s and later to Indonesia in 2003. China further developed this version into the Shenyang J-11.
Su-30KI
A proposed single-seat air superiority fighter based on the Su-27SMK, equipped with N001E radar, an inflight refueling probe, and R-77 missiles. Intended for the Indonesian Air Force under a 1997 letter of intent for 12 units but canceled due to the 1997 Asian financial crisis.
Shenyang J-11
Chinese-produced derivative based on the Su-27SK.
Su-27UBK ("Flanker-C")
Export two-seat trainer version of the Su-27UB.
Su-27SKM
Single-seat multi-role export fighter derived from the Su-27SK but incorporating upgrades such as an advanced cockpit, enhanced self-defense electronic countermeasures (ECM), and an inflight refueling system.
Su-27UBM
Upgraded two-seat version comparable to the Su-27UB.
Su-27SM ("Flanker-E")
Mid-life modernization of Russia’s Su-27 fleet including new digital multi-function displays replacing analog instruments, improved navigation systems, a new fire-control system with enhanced radar and electro-optical targeting capabilities, plus an advanced mission computer. This upgrade enables synthetic-aperture radar terrain mapping and maritime target detection. Unlike earlier Su-27 models, the SM variant can deploy guided air-to-ground munitions such as Kh-29 and Kh-31 missiles along with laser-guided bombs and R-77 air-to-air missiles. The older SPO-15 Beryoza radar warning receiver is replaced by Pastel, while Sorbtsiya wingtip jamming pods are substituted with modern Khibiny pods. Twenty-four units also received slightly improved engines.
Su-27SM2 ("Flanker-J")
Proposed fourth-generation-plus upgrade incorporating technologies from the Su-35BM including Irbis-E radar, enhanced engines, and avionics. This variant did not enter service due to budgetary constraints.
Su-27SM3 ("Flanker-J Mod")
An upgrade package for existing Su-27SMs that updates airframe features and integrates fire-control system compatibility with the modern R-77-1 Adder beyond visual range missile. It also increases maximum takeoff weight by 3 tonnes and installs AL-31F-M1 engines.
Su-27UBM2
Modernized two-seat variant adapted by Kazakhstan based on the Su-27UB.
Su-27M2
Kazakhstan’s upgraded version of the Su-27P.
Su-27BM2
Belarusian modernization of the Su-27P operated by Kazakhstan’s Air Force.
Su-27UB1M
Ukrainian modernization of the two-seat Su-27UB variant.
Su-27S1M
Ukrainian modernized single-seat version of the Su-27S.
Su-27P1M
Ukrainian upgraded version of the Su-27P.
Su-27UP1M
Ukrainian modernized variant of the two-seat Su-27UP.
Su-35BM/Su-35S ("Flanker-M")
Also referred to as the "Last Flanker," this represents the most recent advancement within Sukhoi’s Flanker series. It incorporates improved thrust-vectoring AL-41F1S engines, updated avionics suite, advanced N035 Irbis-E radar system, and a reduced radar cross-section design.

Operators

File:All Sukhoi Su-27 operators.png
Nations operating the Su-27
  Active
  Former

Active

Template:ANG
People's Air and Air Defence Force of Angola – As of January 2013, Angola operated seven Su-27 aircraft.[71] Three units were acquired from Belarus in 1998, with a total of eight delivered overall.[72] One Su-27 was reportedly downed by a 9K34 Strela-3 MANPADS on 19 November 2000 during the Angolan Civil War.[73]
Template:CHN
People's Liberation Army Air Force (PLAAF) – Between 1990 and 2010, China received 78 Su-27s. As of 2022, the fleet includes 32 Su-27UBK aircraft.[74]
Template:ERI
Eritrean Air Force[75] procured two aircraft during the Ethiopian-Eritrean War.Template:Fix/category[citation needed]
Template:ETH
Ethiopian Air Force – The air force obtained up to seventeen Su-27 variants (Su-27S, Su-27P, Su-27UB) secondhand from Russia in two separate acquisitions: nine beginning in 1998 and eight starting in 2002.[76] Several have been lost due to crashes over time.[77]
Template:IDN
Indonesian Air Force – Operates five Su-27SKM fighters. Two Su-27SKs and three Su-27SKMs were delivered in the years 2003 and 2010, respectively.[78] In 2017, Indonesia upgraded its two Su-27SK units to the SKM configuration.[79][80]Template:Fix/category[better source needed]
File:A Kazakh Sukhoi Su-27P(modified).jpg
A Kazakh Air Force Su-27 taking off
Template:KAZ
Kazakh Air Defense Forces – Maintains a fleet of twenty Su-27/Su-27BM2 and three Su-27UB/UBM2 aircraftTemplate:Fix/category[citation needed].
Template:RUS
Russian Aerospace Forces – As of 2021, Russia fields approximately 101 Su-27 fighters.[81]Template:Page needed In January 2014, the inventory included a total of 359 Su-27 variants: specifically, 225 Su-27s, seventy Su-27SMs, twelve Su-27SM3s, and fifty-two Su-27UBs.[82] According to World Air Forces data from 2025, fewer than four hundred twenty-two Su-27s remain operational.[83] A refurbishment initiative started in 2004.[84][85][86] By the year 2012, over half the Russian Su-27 fleet had undergone modernization.[87] The modernization to SM3 standard was ongoing as of late 2018.[88][89][90][91]
During the ongoing Russia–Ukraine conflict as of March 4, 2025, Russia has lost two Su-27 fighters with one additional unit damaged on the ground.[65]
Russian Naval Aviation – Operates fifty-three Su-27 aircraft as reported in January of 2014.[82]
Template:UKR
Ukrainian Air Force – Maintains a stockpile of seventy Su-27 fighters.[92] Of these, thirty-four were actively deployed as of March 2019.[93] Following the Russian invasion by March 4, 2025, Ukraine lost sixteen Su-27 aircraft.[65]
Template:USA
United States Air Force – Two Su-27P jets were received from Belarus in the year 1995.[94][95] Additionally, two Su-27UB models were purchased from Ukraine in 2009 by Pride Aircraft, a private company intending civilian sales.[96][97] The USAF acquired one such aircraft in 2011 which was retired by 2023.[98] These jets have been observed operating within the Area 51 airspace for testing and training purposes.[99]
Template:UZB
Uzbekistan Air and Air Defence Forces – Reported to operate thirty-four Su-27 fighters as of January 2013.[71]
Template:VIE
Vietnam People's Air Force – Utilizes nine Su-27SK and three Su-27UBK aircraft as recorded in January 2013.[71]

Former Operators

Template:Flagcountry
Belarusian Air Force − Acquired between 23 and 28 Su-27 aircraft from the former 61st Fighter Aviation Regiment of the Soviet Union.[94] As of December 2010, 22 Su-27s remained operational.[100] In 1998, nine Su-27s were transferred to Angola. Prior to their retirement in December 2012, Belarus operated a total of 17 Su-27P and 4 Su-27UBM1 jets.[72][101][102]
Template:USSR
Soviet Air Force[103] − Following the dissolution of the Soviet Union in 1991, these aircraft were distributed among various successor states.
Soviet Air Defence Forces − US intelligence estimated the inventory at over 100 Su-27 fighters in 1988.[104]

Civilian Ownership

According to data from the U.S. FAA, as of 2015 there are two Su-27 aircraft held privately within the United States.[105] These two Su-27UBs, originally from the Ukrainian Air Force, were demilitarized and acquired by Pride Aircraft based in Rockford, Illinois. Pride Aircraft customized these jets by converting cockpit instrumentation labels into English and replacing much of the original Russian avionics with systems from Garmin, Bendix/King, and Collins. Each aircraft was subsequently sold to private buyers for roughly $5 million.[106] The United States Air Force purchased these jets in 2011, and by 2023 one was placed on display at the National Museum of the United States Air Force.[98]

On August 30, 2010, the Financial Times reported that ECA Program, a Western private firm specializing in training support, had signed a $1.5 billion contract with Belarusian state arms exporter BelTechExport for the delivery of 15 unarmed Su-27s, with an option for an additional 18. These aircraft were intended for use in establishing a dissimilar air combat training center at the former NATO airbase located in Keflavik, Iceland, with scheduled deliveries by late 2012.[107][108] However, a September 2010 article by RIA Novosti, Russia's state-owned news agency, cast doubt on whether this agreement was finalized.[109] No additional updates about this initiative surfaced by 2014; instead, reports emerged that Belarus planned to upgrade and reactivate its retired Su-27 fleet as of February that year.[110]

Noteworthy Incidents

File:Russian Knights Tkachenko tribute flight Mishin.jpg
Russian Knights honoring their leader Igor Tkachenko, who tragically passed away during a training session a week prior
  • On 9 September 1990, a Soviet Su-27 crashed during the Salgareda airshow after executing a loop at an insufficient altitude. The Lithuanian aviator, Rimantas Stankevičius, along with a spectator, lost their lives in the accident.[111]Cite error: The opening <ref> tag is malformed or has a bad name
  • On 12 December 1995, two Su-27s and one Su-27UB from the Russian Knights aerobatic team collided with terrain near Cam Ranh, Vietnam, resulting in the deaths of four pilots. The group was returning from the Langkawi International Maritime and Aerospace Exhibition with six Su-27s and an Ilyushin Il-76 support plane. During their approach for refueling at Cam Ranh, the Il-76 flew dangerously close to the ground, causing the three Su-27s flying on its right flank to crash. The remaining aircraft landed without incident. The mishap was attributed to controlled flight into terrain, influenced by pilot error, challenging mountainous geography, and adverse weather conditions.Cite error: The opening <ref> tag is malformed or has a bad name
  • On 27 July 2002, a Ukrainian Su-27 crashed during an aerobatic display at the Sknyliv air show disaster, resulting in 77 spectator fatalities, marking it as the deadliest airshow catastrophe recorded. Both pilots ejected safely with only minor injuries.Cite error: The opening <ref> tag is malformed or has a bad name
  • On 15 September 2005, a Russian Su-27 fighter went down close to Kaunas in Lithuania. The pilot ejected safely without injury. Subsequent investigation concluded pilot error as the cause.Cite error: The opening <ref> tag is malformed or has a bad name
  • On 16 August 2009, two Su-27s from the Russian Knights collided mid-flight during rehearsals for the 2009 MAKS Airshow near Zhukovsky Airfield, southeast of Moscow. This collision claimed the life of the team's commander, Igor Tkachenko. One jet crashed into a residential building, sparking a fire. An official investigation suggested that a "flying skill error" might have led to the accident.[112][112]
  • On 30 August 2009, a Belarusian Su-27UBM (tail number black 63) crashed while performing at the Radom Air Show.Cite error: The opening <ref> tag is malformed or has a bad name
  • On 14 March 2023, a Russian Su-27 engaged aggressively with a USAF MQ-9 unmanned aerial vehicle operating in international airspace over the Black Sea. The Russian jet released fuel on the drone—apparently attempting to ignite it—and ultimately collided with its propeller. This forced the USAF operator to intentionally ditch the UAV into the sea.[113]

Aircraft on display

File:Su-27 Red 27 at Central Armed Forces Museum 09.09.2012.jpg
Su-27PD exhibited at the Central Armed Forces Museum in Moscow

Specifications (Su-27SK)

File:Sukhoi Su-27 3-view line drawing.svg
Three-view illustration of the Sukhoi Su-27

Template:Aircraft specs

Prominent Media Features

Main article: Aircraft in fiction § Sukhoi Su-27 and derivatives

See also

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

References

References
  1. ↑ 1.0 1.1 Cite error: Invalid <ref> tag; no text was provided for refs named Great Book
  2. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  3. ↑ Gordon 2007, pp. 34–35.
  4. ↑ Gordon 2007, p. 40.
  5. ↑ Gordon 2007, p. 43.
  6. ↑ Gordon 2007, pp. 43, 45.
  7. ↑ Gordon 2007, p. 45.
  8. ↑ Gordon 2007, p. 47.
  9. ↑ Gordon 2007, pp. 44–46.
  10. ↑ Gordon 2007, p. 46.
  11. ↑ Gordon 2007, pp. 46–47, 49.
  12. ↑ Gordon 2007, pp. 50–51.
  13. ↑ Gordon 2007, pp. 50–57.
  14. ↑ Gordon 2007, p. 57.
  15. ↑ Gordon 2007, pp. 57–58.
  16. ↑ 16.0 16.1 Gordon 2007, p. 58.
  17. ↑ Gordon 2007, p. 61.
  18. ↑ 18.0 18.1 Gordon 2007, p. 62.
  19. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  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. ↑ 23.0 23.1 23.2 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. ↑ 25.0 25.1 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. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named Fly MiG
  30. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named RussianJetFightsForBothSides
  31. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named ka_trendafflovski_2019-03
  32. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named lenta888
  33. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named airplanes
  34. ↑ 34.0 34.1 Cite error: Invalid <ref> tag; no text was provided for refs named Russian fighter jets 'breach Japan airspace'
  35. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named Japan accuses Russian jets of violating airspace
  36. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named Japan scrambles fighter jets as Russian warplanes intrude into airspace
  37. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named Japan says 2 Russian fighters entered its airspace
  38. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named bseata
  39. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named dw03.26
  40. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named Milavia
  41. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named Cast
  42. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named defense-update.com
  43. ↑ Thomas Newdick, "Our First Detailed Look At Russian Su-27 Flanker Jets In The Ukraine War", The Drive, 7 December 2022
  44. ↑ Firefighters extinguished the fire at the airport near Zhytomyr, Galychyna, 24 February 2022
  45. ↑ ["Legendary Ukrainian display pilot known as Grey Wolf dies in combat", The Week, 1 March 2022]
  46. ↑ Video shows explosion after fighter jet shot down, official says, CNN, 25 February 2022
  47. ↑ Colonel Oleksandr "Grey Wolf" Oksanchenko killed in air battle, The Aviation Geek Club, 1 March 2022
  48. ↑ Ukrainian mayor meets Russians about occupation plan after key southern city falls, The Drive, 2 March 2022
  49. ↑ Stetson Payne, "Ukraine Strikes Back: Su-27s Bomb Occupied Snake Island In Daring Raid", The Drive, 7 May 2022
  50. ↑ Possible air-to-air shootdown captured on camera in Ukraine, Aerotime.aero, 6 June 2022
  51. ↑ ASN Wikibase Occurrence #279043, Aviation Safety Network
  52. ↑ Тяжка втрата: під час виконання завдання розбився житомирський льотчик, Zhzh.com.ua, 24 August 2022
  53. ↑ ASN Wikibase Occurrence #282655
  54. ↑ Thomas Newdick, "Ukraine's Su-27s Appear To Be Wielding Anti-Radiation Missiles Now Too", The War Zone, September 2022
  55. ↑ ASN Wikibase Occurrence #296372
  56. ↑ У Чернігові провели в останню путь штурмана авіації полковника Олега Шупіка, Suspilne, 14 October 2022
  57. ↑ ASN Wikibase Occurrence #309095
  58. ↑ Video captures moment Russian fighter rammed USAF MQ-9 drone, AeroTime, 16 March 2023
  59. ↑ Thomas Newdick, "Ukraine's Su-27s Are Launching JDAM-ER Winged Bombs Too", The Drive, 24 August 2023
  60. ↑ ASN Wikibase Occurrence #388070
  61. ↑ President of Ukraine statement honoring Air Force warriors
  62. ↑ Kyiv Independent report on pilot death
  63. ↑ Forbes coverage of ongoing conflict
  64. ↑ Militarnyi report on overhaul contracts for Su-27UB jets
  65. ↑ 65.0 65.1 65.2 Oryx: List Of Aircraft Losses During The Russian Invasion Of Ukraine
  66. ↑ RBC News Ukraine report on Su-27 loss and pilot ejection
  67. ↑ 67.0 67.1 67.2 67.3 67.4 67.5 67.6 67.7 Cite error: Invalid <ref> tag; no text was provided for refs named ref0
  68. ↑ 68.0 68.1 68.2 68.3 68.4 Cite error: Invalid <ref> tag; no text was provided for refs named ref1
  69. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named ref3
  70. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named ref
  71. ↑ 71.0 71.1 71.2 "World Military Aircraft Inventory". 2013 Aerospace: Aviation Week and Space Technology, January 2013.
  72. ↑ 72.0 72.1 Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  73. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  74. ↑ International Institute for Strategic Studies: The Military Balance 2022, p.261
  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. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  78. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  79. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  80. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  81. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  82. ↑ 82.0 82.1 "World Military Aircraft Inventory". 2014 Aerospace: Aviation Week and Space Technology, January 2014
  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. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  86. ↑ Air Forces Monthly, December 2010.
  87. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  88. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  89. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  90. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  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. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  94. ↑ 94.0 94.1 Template:Cite web ...
  95. ↑ Template:Sfnp ...
  96. ↑ Template:Cite web ...
  97. ↑ Template:Cite web ...
  98. ↑ 98.0 98.1 Template:Cite web ...
  99. ↑ Template:Cite web ...
  100. ↑ "Directory: World Air Forces". Flight International, 14–20 December 2010.
  101. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  102. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  103. ↑ Defense Intelligence Agency 1988, p. 80.
  104. ↑ Defense Intelligence Agency 1988, p. 81.
  105. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  106. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  107. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  108. ↑ Air International October 2010, p. 9.
  109. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  110. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  111. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named Salgareda airshow crash 1990
  112. ↑ 112.0 112.1 Cite error: Invalid <ref> tag; no text was provided for refs named BBC Pilot
  113. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named 2023-03-14_M
  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. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  117. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  118. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  119. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  120. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  121. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  122. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  123. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  124. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  125. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  126. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
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).
  • 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).
  • 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).

External links

  • Commons category related to the subject
  • Official webpage for the Sukhoi Su-27SK at Sukhoi and KnAAPO
  • Sukhoi's official site for the Su-27UBK model
  • Official Sukhoi Su-27SKM page hosted by KnAAPO
  • Photographic collection of Sukhoi Su-27 "Flanker" and Su-27SKM by Michel Zacharz
  • Article titled "Sukhoi Flankers: The Shifting Balance of Regional Air Power" by Carlo Kopp, published on Air Power Australia, dated 7 January 2007
  • "Asia's Advanced Flankers," an analysis by Carlo Kopp available through Air Power Australia (archived)
  • Information on Su-27UB aircraft operated within the United States, provided by Pride Aircraft (archived)

Template:Su-27 family Template:Sukhoi aircraft Template:USAF/DoD reporting names

Retrieved from "https://www.alfawiki.org/index.php?title=Sukhoi_Su-27&oldid=75136"