Jump to content

Sukhoi Su-35

From Alfawiki
Sukhoi
IndustryAerospace, Defense
Founded1939
FounderPavel Sukhoi
Headquarters
Moscow
,
Russia
ProductsMilitary aircraft, including Su-27, Su-35, Su-37, Su-30 variants

Overview

The Sukhoi Su-35 (Russian: Сухой Су-35; known by NATO as Flanker-E/M and sometimes referred to as the "Super Flanker") represents two enhanced variants derived from the original Su-27 air defense fighter. These models are single-seat, twin-engine aircraft exhibiting advanced supermaneuverability, classified as 4.5 generation air superiority fighters. They were conceptualized by the Sukhoi Design Bureau and manufactured by Sukhoi.

Initially developed within the Soviet Union as the Su-27M, this variant introduced canard foreplanes and a multifunction radar system, enabling it to fulfill multi-role functions. Its maiden flight occurred in June 1988. After the Soviet Union's collapse, the designation was changed to Su-35 to enhance its appeal for international sales. A total of fourteen units were produced for testing and demonstration purposes; among these, one aircraft was equipped with thrust-vectoring engines and subsequently redesignated as the Su-37. Additionally, a single two-seat trainer model, the Su-35UB, resembling the Su-30MK series, was constructed in the late 1990s.

In 2003, Sukhoi commenced a comprehensive modernization of the Su-27 platform aimed at producing an interim export fighter while awaiting the development of the Sukhoi PAK FA (Su-57). This upgraded iteration, also called the Su-35, integrates technologies from the PAK FA project, featuring a revamped cockpit layout, an advanced weapons control system, and thrust-vectoring engines replacing the earlier canard configuration. The first flight of this version took place in February 2008. Although originally intended for export markets, the Russian Air Force became its initial operator in 2009 with the production model designated as Su-35S. The People's Liberation Army Air Force of China has also procured this aircraft.

Enhanced Su-27

The initial aircraft to bear the Su-35 designation emerged in the early 1980s, coinciding with the introduction of the Su-27 into service within the Soviet Armed Forces. The definitive production model of the Su-27, designated T-10S by the manufacturer, commenced large-scale manufacturing at the Komsomolsk-on-Amur Aircraft Production Association (KnAAPO) in 1983. By the following year, this variant had achieved initial operational capability with the Soviet Air Defence Forces.[1] Development of an upgraded Su-27 model began in 1982,[2] and in December 1983, the Sukhoi Design Bureau received directives from the Soviet Council of Ministers to base a new design, the Su-27M (T-10M), on the existing Su-27 platform.[3] Throughout much of the project, Nikolay Nikitin led the design team under the supervision of General Director Mikhail Simonov, who had previously served as chief designer for the Su-27,[4] alongside Mikhail Pogosyan.Template:Fix/category[citation needed]

File:Sukhoi Su-35 (Su-27M).png
Planform view of the Su-27M

Although retaining the general blended wing-body configuration characteristic of the Su-27, the Su-27M is notably differentiated by its addition of canards, small lifting surfaces positioned forward of the main wings. These were experimentally tested in 1985 on a prototype,[1] and worked in conjunction with a redesigned wing leading-edge extension to modify airflow patterns, thereby eliminating buffeting at elevated angles of attack. This aerodynamic refinement enabled the airframe to endure 10-g stresses—an increase from the original Su-27’s 9 g limit—without requiring extra structural reinforcement.[5] More crucially, when combined with a relaxed-stability configuration and an advanced fly-by-wire flight control system, this setup enhanced manoeuvrability significantly and permitted momentary flight with the nose pitched beyond vertical while maintaining forward velocity. This capability theoretically allowed a pilot during combat to elevate the aircraft’s nose by up to 120 degrees within two seconds and engage targets with missiles.[6] Additional visible modifications relative to the T-10S included taller vertical tails, integration of in-flight refueling capability, and a reinforced two-wheel nose landing gear designed to support a heavier airframe.[7] [8]

Beyond enhanced agility, one of the defining improvements of the Su-27M over its predecessor was its updated weapons control system. Central to this was the multi-function N011 Bars (meaning "Leopard") phased-array radar featuring pulse-Doppler tracking technology that enabled detection of targets beneath the horizon. Introduced on the third prototype, this radar transformed the aircraft from a pure air-defense interceptor into a versatile multi-role fighter capable of ground attack missions.[1][9] Compared to the original Su-27’s N001 Myech ("Sword") radar—which could track up to ten targets but guide missiles toward only two simultaneously—the N011 Bars could monitor fifteen targets and engage six concurrently.[1] The radar’s added weight at the front necessitated fitting canards; engineers later recognized these also provided aerodynamic benefits.[10] [11] Additionally, a rearward-facing Phazotron N012 self-defense radar was installed in an extended tail boom section, making this aircraft globally unique at that time for possessing such a feature.[9] Other enhancements comprised more powerful turbofan engines and increased incorporation of lightweight materials such as advanced composites and aluminium-lithium alloys within its structure.[7] [12]

Testing and demonstration

In 1987, Sukhoi began the modification of the initial prototype, designated T10M-1, by converting a T-10S airframe at its Moscow experimental facility. Although equipped with canards, this first prototype and several that followed did not feature many of the extensive physical changes characteristic of the finalized design. The converted aircraft completed its maiden flight on 28 June 1988, piloted by Oleg Tsoi, with the second prototype taking to the skies in January 1989. After these two Su-27M prototypes were modified, production responsibilities shifted to KnAAPO in the country's Far East. The third aircraft, T10M-3, marked the first Su-27M constructed entirely new by KnAAPO and conducted its first flight in April 1992. By that time, the Soviet Union had collapsed, and Russia’s economic turmoil throughout the 1990s led to the cancellation of plans for large-scale production slated for 1996 to 2005. Instead, these aircraft were employed as test platforms to validate canard aerodynamics, flight-control systems, and thrust-vectoring technologies. By 1995, a total of two prototypes, nine pre-production flying units, and three production models had been built; production aircraft were delivered to the Russian Air Force in 1996 for weapons testing.

File:Su-35 (12509727094).jpg
The ninth Su-27M during flight

Prior to the Soviet Union's dissolution, Sukhoi had already been showcasing the Su-27M to top defense and government representatives. When introduced to Western audiences at the 1992 Farnborough Airshow, the aircraft was redesignated as the Su-35. Subsequently, it participated in international flying demonstrations aimed at securing export contracts, beginning with the Dubai Airshow in November 1993 where Viktor Pugachev performed a simulated dogfight against an Su-30MK before an audience. Following Dubai, the aircraft appeared at Berlin’s ILA Air Show and Paris Air Show and became a regular attraction at Moscow’s MAKS Air Show. The Russian government authorized exports during Sukhoi’s unsuccessful sales efforts in South Korea during the late 1990s and early 2000s; additionally, marketing campaigns targeted Brazil, China, and the United Arab Emirates.

During flight testing of the Su-27M, engineers identified issues with pilot control during specific maneuvers such as Pugachev's Cobra. To address this, the eleventh Su-27M (T10M-11) was outfitted with thrust-vectoring nozzles in 1995. This modified aircraft evolved into the Su-37 technology demonstrator, which made its inaugural flight on 2 April 1996. It also tested an upgraded N011M radar system alongside the twelfth developmental Su-27M model. The Su-37 attracted significant media attention due to its capability to sustain high angles of attack while flying near zero airspeed. Later iterations featured new engines along with enhanced fly-by-wire controls and cockpit systems for further evaluation.

In addition to single-seat variants, a two-seat version was developed through collaboration between Sukhoi and KnAAPO engineers. This led to the creation of the Su-35UB, which integrated thrust-vectoring engines with design elements from the Su-27M. Based on a modified Su-30MKK airframe, it first flew on 7 August 2000 and was subsequently utilized as an avionics test platform. Although financial constraints prevented mass production of the original Su-27M design, Sukhoi advanced canard applications from that model and thrust-vectoring innovations from the Su-37 for incorporation into the two-seat Su-30MKI fighter tailored for India’s air force. Additionally, the tenth Su-27M (T10M-10) served as a testbed for evaluating the Saturn AL-41F1 engine intended for use in the Sukhoi Su-57 (formerly known as "PAK FA") stealth fighter jet.

Modernization

File:Sukhoi Su-35S 07 RED PAS 2013 07.jpg
Thrust vectoring nozzle on a Sukhoi Su-35S

To rejuvenate Russia's aging Su-27 fleet, Sukhoi and KnAAPO initiated upgrades in 2002 by incorporating glass cockpit technology and enhanced weapons-control systems capable of supporting a broader array of armaments. This upgraded version, designated the Su-27SM, completed its maiden flight in December 2002. The favorable outcome of this effort prompted Sukhoi to launch a more comprehensive modernization initiative in December 2003, internally referred to as the T-10BM program. This project focused on an extensive redesign of the airframe to reduce the performance gap between Russian fighters and contemporary fourth-generation aircraft globally. The resulting aircraft, also named Su-35, was intended as a transitional platform pending the arrival of the PAK FA fifth-generation fighter, later known as the Su-57. The Su-35 incorporated several advanced features from this forthcoming model. Primarily targeted at international customers, KnAAPO marketed the Su-35 as a single-seat alternative to the two-seat Su-30MK variants produced by Irkutsk Aviation Plant (IAP).

In design terms, the T-10BM shares more similarities with the original Su-27 than with the Su-27M. During evaluations of thrust-vectoring engines combined with the aerodynamic layout of the Su-27M, Sukhoi determined that eliminating the canards—which had added weight to the airframe—did not significantly compromise maneuverability when thrust-vectoring nozzles were introduced. Advances in avionics and radar technology also contributed to weight reductions and shifted the aircraft’s center of gravity rearwards. Consequently, designers removed both the canards and dorsal air brake present on the Su-27M, while reducing dimensions of the vertical stabilizers, aft-cockpit hump, and tail boom. These changes, along with increased use of aluminium, titanium alloys, and composite materials, lowered the aircraft’s empty weight without affecting its maximum take-off weight compared to the Su-27M.

File:MAKS Airshow 2013 (Ramenskoye Airport, Russia) (523-02).jpg
Su-35S cockpit arrangement featuring a head-up display, two multi-function liquid crystal displays, and HOTAS controls on the stick

Although the Su-27M was equipped with avionics qualifying it as a multi-role fighter, Russian Air Force flight tests revealed challenges in efficiently deploying its weaponry. Pilots reported that weapons trials at Akhtubinsk and Lipetsk were problematic, particularly criticizing cockpit layout for increasing pilot workload during combat operations. In response, engineers collaborated closely with test pilots and software developers to overhaul cockpit design and improve human-machine interfaces. The updated avionics system now features dual digital computers processing flight and weapons control data, which is presented on two 9 in × 12 in (23 cm × 30 cm) multi-function liquid crystal displays—replacing the smaller triple cathode-ray tube screens used in the Su-27M. Critical flight parameters are also projected onto a head-up display, while pilots operate using Hands On Throttle-And-Stick controls.

The Su-35 is equipped with the advanced N035 Irbis-E ("Snow Leopard") passive electronically scanned array (PESA) radar system derived from the N011M radar tested on Su-27M prototypes. This radar can detect airborne targets up to 400 km (250 mi; 220 nmi) away, track thirty targets simultaneously, and engage eight at once. Additionally, it offers high-resolution ground mapping through synthetic aperture radar mode. Positioned forward of the cockpit is an OLS-35 optoelectronic targeting system that provides additional tracking capabilities including infra-red search and track. For electronic defense against enemy detection systems, the Su-35 carries the L175M Khibiny-M electronic countermeasures suite. To further reduce radar signature, radar-absorbent materials are applied to engine intakes and compressor stages, halving frontal radar cross-section and decreasing detection range by hostile radars. The overall radar cross-section is estimated between 1 and 3 square meters. Armed for multiple roles, this fighter can deploy air-to-air missiles with ranges up to 300-kilometre (190 mi), carry heavy anti-shipping cruise missiles such as the Oniks, along with diverse air-to-ground munitions.

"Classical air combat begins at high velocity; however, if an initial shot misses—which is common due to evasive maneuvers—the engagement extends longer. After maneuvering phases at reduced speeds where neither side may have firing solutions, supermaneuverability enables an aircraft to execute a turn within three seconds and quickly regain firing position."
— Sergey Bogdan, Chief Test Pilot at Sukhoi

Powering the Su-35 are two Saturn AL-41F1S turbofan engines—previously known as izdeliye 117S—a significantly enhanced derivative of the AL-31F closely related to the Saturn AL-41F1 used on the Su-57 but differing mainly in engine control systems. These engines feature thrust-vectoring nozzles mounted at an angle that allows rotation primarily in pitch but also enables differential vectoring for roll and yaw control—a configuration first introduced on the Su-30MKI and also employed by the Su-57. The integration of thrust vectoring with flight and propulsion control systems grants the aircraft sustained 9-g turns and exceptional "supermaneuverability," allowing post-stall maneuvers at low speeds—a contrast to Western doctrines that prioritize maintaining kinetic energy during combat. Furthermore, these engines provide limited capability for sustained supersonic cruising above Mach 1.1 without afterburner activation—commonly referred to as "supercruise."

Testing and production

File:Sukhoi Su-35S (28333541172).jpg
A Russian Aerospace Forces Su-35S performing a routine takeoff

After finalizing the design phase, KnAAPO completed the initial prototype by mid-2007. This first model, designated Su-35-1, was subsequently delivered to the Gromov Flight Research Institute at Zhukovsky Airfield to prepare for its inaugural flight.[13] On 19 February 2008, Sergey Bogdan piloted the aircraft during its maiden flight lasting 55 minutes from Zhukovsky.[13]Cite error: The opening <ref> tag is malformed or has a bad name Later, Bogdan also conducted the first flight of the second prototype on 2 October, departing from KnAAPO’s Dzyomgi Airport.[14] Initially, the flight-test program planned to utilize three flying prototypes; however, on 26 April 2009, just one day before its scheduled first flight, the fourth Su-35 (which was not a static test airframe) crashed during taxiing at Dzyomgi Airport. The aircraft collided with a barrier at the runway's end and was destroyed by fire. The pilot ejected but suffered burn injuries.[15]Cite error: The opening <ref> tag is malformed or has a bad name Investigation revealed that the accident resulted from a malfunction in the engine control system, which caused the afterburner to remain engaged.Cite error: The opening <ref> tag is malformed or has a bad nameCite error: The opening <ref> tag is malformed or has a bad nameCite error: The opening <ref> tag is malformed or has a bad nameCite error: The opening <ref> tag is malformed or has a bad name

Although developed primarily for export purposes, the Su-35 secured its initial production order at the 2009 MAKS Air Show when the Russian Defence Ministry contracted 48 Su-35S units as part of a broader agreement valued at US$2.5 billion for 64 fighter jets.[16]Cite error: The opening <ref> tag is malformed or has a bad name[17] Early in testing, Sukhoi projected a potential market demand of approximately 160 aircraft, focusing on regions such as Latin America, Southeast Asia, and the Middle East. Some prospective buyers—like Algeria, Malaysia, and India—were already operators of Su-30MK variants. The aircraft was slated to be available for export beginning in 2010,[18] and during its international presentation at the 2013 Paris Air Show, Mikhail Pogosyan, General Director of Sukhoi’s parent company United Aircraft Corporation, estimated total demand at around 200 units split equally between domestic and foreign customers.Cite error: The opening <ref> tag is malformed or has a bad name It was only by late 2015 that China signed the first export contract; by this time, Russia had placed an additional order for 50 aircraft.[19]

Beyond the initial procurement announced at MAKS 2009, funding for production was supported by an agreement between the Russian government and state-owned development bank Vnesheconombank, providing Sukhoi with necessary capital.Template:Fix/category[citation needed] In November 2009, KnAAPO—renamed KnAAZ in 2013 following integration into Sukhoi—commenced manufacturing of the first production-standard aircraft,Cite error: The opening <ref> tag is malformed or has a bad name with general assembly completed by October 2010;Cite error: The opening <ref> tag is malformed or has a bad name by that stage, pilots and engineers had concluded preliminary system tests successfully.Cite error: The opening <ref> tag is malformed or has a bad name The maiden flight of the first Su-35S occurred in May 2011,Template:Fix/category[citation needed] after which it was delivered to Akhtubinsk to begin state joint trials alongside the Defence Ministry aimed at operational readiness. Since production overlapped with testing phases, some early-production models underwent modifications based on test outcomes.[20] In December 2018, United Aircraft Corporation announced that the Komsomolsk-on-Amur Aircraft Plant had produced its 100th serial Su-35S.Cite error: The opening <ref> tag is malformed or has a bad name

Russia

In 1996, the air force received three production Su-27Ms at the 929th State Flight Test Centre named for V. P. Chkalov (GLITs) located at Vladimirovka air base [ru], Akhtubinsk, to conduct weapons testing.[21] By 2001, the air force planned to allocate several Su-27Ms for upgrading the Russian Knights aerobatics team, prompting pilots to carry out familiarisation flights on these aircraft.[22] In 2003, the team received three production and two pre-production Su-27Ms at their base in Kubinka near Moscow; however, these aircraft were primarily cannibalized for spare parts to support the demonstration fleet.[23]

File:Russian Air Force Sukhoi Su-35 Belyakov.jpg
A Russian Air Force Sukhoi Su-35 performing at MAKS 2009 air show in Moscow

Between 2007 and 2009, a total of one static and three flyable prototypes (bearing bort nos. 901, 902, and 904) were constructed.[14] One of these prototypes (bort no. 904) was subsequently lost after crashing into a barrier during taxiing operations.[15]

The initial contract for producing 48 aircraft was finalized during the 2009 MAKS Air show held in Moscow.Template:Fix/category[citation needed] Sukhoi delivered the first Su-35S to Akhtubinsk in May 2011 to initiate state joint testing with the Defence Ministry aimed at preparing the fighter for active service.[24] The trials began their first phase in August of that year. By March 2012, flight tests involving two prototypes and four production models were underway to evaluate the aircraft’s technical capabilities,[24] with assessments by year-end indicating general compliance with established criteria.Template:Fix/category[citation needed] Subsequently, six production units were delivered in December 2012.[25] In February 2013, five of these aircraft at the Gromov Flight Research Institute in Zhukovsky commenced the second phase of testing focused on weapons systems and combat maneuverability.[26]

In December 2013, twelve production Su-35Ss were supplied,[27] followed by another batch of twelve aircraft in February 2014. Of these latter deliveries, ten were assigned to the Far East’s 23rd Fighter Aviation Regiment, while two remained engaged in completing final state joint tests.[20] This transfer marked the official induction of the Su-35S into operational service.[28] Several units were later relocated to Lipetsk for advanced combat tactics development and personnel training.[29] Additionally, Russia’s Su-35Ss maintain permanent deployment at Besovets air base, near Finland’s border,[30] as well as at Centralnaya Uglovaya air base near Vladivostok.[31]

File:Sukhoi Su-35S bn15 2019-1.jpg
Sukhoi Su-35S taxiing with drogue parachute after landing during Aviadarts contest, 2019

The integration of the Su-35S into service with the Russian Aerospace Forces forms part of Russia’s state armament program for the years 2011–2020. This initiative was developed following the conflict with Georgia in 2008 with objectives aimed at substantially modernizing military hardware within Russia’s armed forces.[32] Alongside the Su-35S, deliveries included variants such as the Su-30M2, Su-30SM, and the larger Su-34 strike aircraft.[33] The first two are domestic versions derived from KnAAPO's Su-30MK2 and Irkut's export-oriented Su-30MKI twin-seat fighters. Reports suggest that procuring these three derivatives concurrently was intended to sustain both manufacturers during a period of reduced export demand.[28] The Su-30M2 additionally serves as a training platform for pilots transitioning to the Su-35.[33]

By late 2018, the Su-35S had achieved full operational capability (FOC).[34][35][36]

In July of 2020, eight new Su-35Ss were supplied to augment the Russian Knights aerobatic team’s existing fleet of Su-30SM aircraft.[37]

On September 9, 2022, three additional Su-35S fighters were delivered to the Russian Aerospace Forces' aggressor squadron, known as the 185th Combat Training and Combat Application Center.[38]

Syrian Civil War

Main article: Russian military intervention in the Syrian Civil War
File:Su-35S multipurpose fighter.webm
A Russian Defence Ministry video showcasing the Su-35S

In January 2016, Russia deployed the Su-35S in combat for the first time by dispatching four units to Syria. This move followed escalating tensions between Russia and Turkey, triggered by alleged Russian aircraft violations of Turkish airspace and the downing of a Russian Su-24 bomber by a Turkish F-16 fighter jet in November 2015.[39][40] The operational experience gained during the Syrian deployment facilitated identification and resolution of various issues, including those related to avionics.[41] Observations of Su-35s in Syria reveal usage of unguided bombs, while Russian sources assert that these aircraft have conducted precision strikes employing guided munitions.[39]

File:Russian SU-35 Over Syria.jpg
A Su-35S intercepting a US MQ-9 Reaper drone over Syrian airspace in 2023.

On 20 August 2019, two Su-35Ss from the Russian Aerospace Forces operating out of Khmeimim Air Base intercepted a pair of Turkish Air Force F-16s over southern Idlib, compelling them to exit Syrian airspace.[42] Later, on 10 September 2019, Russian Su-35Ss once again intercepted multiple Israeli aircraft over southern Syria, preventing planned airstrikes.[43] Another interception took place on 19 September 2019 when two Su-35Ss blocked Israeli jets preparing to strike Damascus suburbs.[44] On 15 October 2019, Russian Su-35Ss intercepted a Turkish F-16 attempting to bomb the headquarters of the Syrian Democratic Forces in Manbij, forcing it to withdraw.[45] During an airstrike on Damascus on 12 November 2019, a Russian Su-35S intercepted an Israeli fighter jet.[46] Subsequently, on 7 December 2019, several Israeli aircraft were forced to retreat after being intercepted by Russian Su-35Ss during an attempted strike on the T-4 Airbase.[47]

Russo-Ukrainian War

Main article: 2022 Russian invasion of Ukraine

During the conflict, Russian Su-30SM and Su-35S fighter jets were deployed primarily for air superiority operations. By September 2022, Russian forces had confirmed at least seven air-to-air kills against Ukrainian fighter aircraft[48] as well as one victory against a Ukrainian Naval Aviation Mil Mi-14 helicopter.Cite error: The opening <ref> tag is malformed or has a bad name

On 6 March 2022, a pilot from the 4th Centre for Combat Employment and Retraining of Personnel flying a Su-35S successfully downed two Ukrainian Mi-8 helicopters and a Su-25 attack jet in a single mission amid the Battle of Mykolaiv.Cite error: The opening <ref> tag is malformed or has a bad nameCite error: The opening <ref> tag is malformed or has a bad nameCite error: The opening <ref> tag is malformed or has a bad nameCite error: The opening <ref> tag is malformed or has a bad name

A Russian Su-35S was shot down by Ukrainian forces on 3 April 2022 near Izyum; the pilot ejected safely but was captured. The pilot reported that his aircraft was lost while engaged with Ukrainian air defense systems.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

The Ukrainian Air Force announced on 19 July 2022 that their air defense units had destroyed a Su-35 close to Kakhovka. However, photographic evidence confirming this claim was not immediately available.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 early February 2023, images surfaced verifying the wreckage as an Su-35S.Cite error: The opening <ref> tag is malformed or has a bad name

In May 2023, two separate incidents involved Ukrainian MIM-104 Patriot missile systems shooting down Su-35 fighters over Russia’s Bryansk region—first on the 14th and again on the 22nd.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 28 September 2023, a friendly fire incident occurred near Tokmak when a Russian S-300 surface-to-air missile mistakenly targeted and destroyed an Su-35. Initial investigations indicated the missile’s fire control radar failed to discriminate between allied and enemy aircraft.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

The Ministry of Defense of Ukraine reported that in February 2024, Ukrainian air defenses succeeded in downing two additional Su-35s. This achievement marked their most significant success in neutralizing Russian jets since October 2022, when they claimed to have shot down ten Su-34s along with one Beriev A-50 early warning aircraft.[49]

According to data from the International Institute for Strategic Studies as of May 2023, Russia had lost over five Su-35 fighters since the onset of hostilities in Ukraine. These losses resulted from various causes including friendly fire incidents, crashes, and destruction by Ukrainian forces employing Western-supplied air defense systems.Cite error: The opening <ref> tag is malformed or has a bad nameCite error: The opening <ref> tag is malformed or has a bad nameCite 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 7 June 2025, footage emerged showing wreckage of a burning Russian Su-35 near Kursk. The Ukrainian Air Force claimed responsibility for shooting down the jet.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

China

In the early 1990s, discussions took place regarding the potential sale of the Su-27M to China. By 1995, Sukhoi representatives had proposed a joint production plan, conditional upon Beijing's commitment to purchasing 120 units. However, the Russian Foreign Ministry reportedly intervened to halt the sale of both the Su-27M and the Tupolev Tu-22M bomber, citing concerns related to Chinese licensed production of Su-27 derivatives like the Shenyang J-11.

China became the inaugural foreign buyer of the Su-35 in November 2015 when the Russian and Chinese governments finalized a $2 billion agreement for 24 aircraft intended for the People's Liberation Army Air Force (PLAAF). This transaction attracted international attention due to its strategic importance. According to David Ochmanek from RAND Corporation, the deal was mutually advantageous: Russia depended on exports to sustain its defense manufacturing capabilities, while China aimed to advance its military strength by acquiring sophisticated platforms such as the Su-35. Nevertheless, Moritz Rudolf of the Mercator Institute for China Studies noted that the relatively modest number of aircraft purchased suggested a largely symbolic nature of the deal, reflecting ongoing competition between Russia and China for regional influence in Central Asia. Ben Moores from IHS Markit posited that this order might represent China's final significant procurement from Russia, highlighting that Sino-Russian military collaboration has been limited in scope and substance, with China being less reliant on Russia than vice versa.

Initial Chinese interest in the Su-35 dates back to 2006. However, it was not until the 2010 Zhuhai Airshow that Alexander Mikheyev of Rosoboronexport, Russia's state agency overseeing defense exports and imports, publicly indicated readiness to commence negotiations with China over the Su-35. By 2012, Russian authorities confirmed ongoing discussions and signed a protocol agreement concerning the purchase. Subsequent reports hinted at contract finalization and imminent deliveries in 2013; yet, formal negotiations only concluded in 2015.

The protracted nature of these talks largely stemmed from intellectual property concerns. China had previously reverse engineered the Su-27SK and Su-33 to develop the J-11B and J-15 respectively, prompting fears that it might replicate the Su-35 airframe and market such copies internationally. At one point, Rosoboronexport insisted on a legally binding commitment from China to prevent duplication. Chinese industry showed particular interest in acquiring the AL-41F1S engine and Irbis-E radar systems. According to The Diplomat, China was focused on the Su-35’s propulsion system and was already testing the J-11D variant, which reportedly offers reduced range, payload capacity, and maneuverability compared to the Su-35 but features an active electronically scanned array radar rather than the latter’s passive electronically scanned array radar. Rosoboronexport initially demanded a minimum purchase of 48 jets to mitigate copying risks; after Kremlin intervention in 2012, this threshold was lowered to 24 units. Another sticking point involved China's demand for integration of indigenous components and avionics into the Su-35; this requirement was ultimately accepted following Russian government mediation despite being a significant concession given the profitability associated with selling such parts. The finalized contract did not include any technology transfer provisions.

The first four Su-35 aircraft were delivered to Chinese forces in December 2016. Following this initial shipment, an official PLAAF statement suggested that with the induction of the Chengdu J-20 stealth fighter, Russia recognized that the Su-35 would soon lose appeal within China’s market; it expressed hope that this would be China's final import of combat aircraft. Subsequently, a second batch comprising ten jets arrived in 2017, followed by an additional ten units delivered in 2018. The Su-35S officially entered service with PLAAF in April 2018 and is stationed primarily in Guangdong province in southeastern China. In June 2019, Russia proposed supplying China with another batch of Su-35s; however, according to Asia Times citing Chinese sources, further purchases were deemed impractical as Russian fighters offered limited advantages over China's domestically produced Shenyang J-16 jets, which possess superior radar systems, avionics suites, and other technologies.

On 20 September 2018, the United States imposed sanctions targeting China's Equipment Development Department of the Central Military Commission along with its director Li Shangfu. The sanctions cited their involvement in significant transactions with Rosoboronexport—specifically referencing China's acquisition of ten Su-35 fighters in 2017 as well as equipment related to the S-400 surface-to-air missile system in 2018.

Iran

After Russia acquired Iranian suicide drones amid the Ukraine conflict, reports from US sources indicate that the Islamic Republic of Iran Air Force (IRIAF) is contemplating the purchase of Sukhoi Su-35 fighters. This potential transaction would involve Iran supplying additional ammunition, drones, and ballistic missiles to Russian military forces. Training sessions for Iranian pilots reportedly commenced in spring 2022, with expectations that the aircraft might be delivered during 2023. The arrangement could encompass 24 Su-35 jets initially manufactured for Egypt, although no official confirmation regarding their delivery has been released. Iranian state media Tasnim News Agency confirmed the agreement on 28 December 2022, and on 15 January 2023, an Iranian parliament member announced that deliveries would start in spring, also mentioning Iran’s orders from Russia for air defense systems, missile technology, and helicopters.

Nevertheless, in July 2023, Iran’s Defense Minister, Mohammad-Reza Gharaei Ashtiani, made ambiguous remarks suggesting a reassessment of the Su-35 acquisition plan due to growing investment in domestic fighter aircraft development. This led some analysts to speculate that the deal might have fallen through. Despite this uncertainty, the IRIAF has taken delivery of Yak-130 advanced jet trainers, which serve to prepare pilots before transitioning to frontline combat aircraft like the Su-35. These trainers have been outfitted with IRIAF markings and serial numbers. On 28 November 2023, Iran’s deputy defense minister announced that a finalized agreement for Su-35 procurement from Russia had been reached, though specifics regarding quantities or timelines were not disclosed. In April 2024, reports surfaced of an order for 24 Su-35 jets; however, these claims were subsequently refuted by Iran’s SNN media outlet. Then in January 2025, Ali Shadmani, a senior official within the Islamic Revolutionary Guards Corps, confirmed that Iran had purchased Su-35 aircraft but did not specify the number acquired or whether deliveries had begun.

On 23 September 2025, an Iranian legislator stated that the Su-35 jets were "en route" to Iran.

United Arab Emirates

During the mid-1990s, the United Arab Emirates conducted evaluations of the Su-27M,[50] but ultimately opted to procure the Mirage 2000 given the nation's strong ties with France.[51] In February 2017, the UAE planned to finalize a preliminary agreement for acquiring the Su-35 and concurrently entered into a partnership with Rostec, Russia’s state corporation responsible for advanced industrial development, to collaborate on a fifth-generation fighter derived from the MiG-29.[52]

India

India has demonstrated hesitation in placing orders for the Sukhoi/HAL FGFA largely due to its substantial cost. Reports indicate that India and Russia are exploring an upgrade to the Su-35 incorporating stealth features akin to the F-15 Silent Eagle, presenting a potentially more cost-effective alternative to the FGFA (Su-57).[53] The Su-35 is among eight contenders competing in a new tender known in Indian media as MMRCA 2.0, aimed at acquiring 114 multi-role combat aircraft.[54]

Algeria

Kommersant reported that Algeria’s armed forces requested a Su-35 for evaluation in February 2016; sources indicated satisfaction with the aircraft’s flight performance, and Moscow is awaiting an official order submission.[55] On 27 December 2019, it was reported that Algeria signed a contract for 14 Su-35 fighters as part of a broader military procurement deal including Su-34 and Su-57 aircraft.[56] Nevertheless, neither the Russian nor Algerian authorities have officially confirmed this agreement.Template:Fix/category[citation needed]

Turkey

In July 2019, following Turkey's exclusion from the F-35 program by the United States due to its acquisition of the S-400 missile system, Russia proposed supplying the Su-35 fighter jet to Turkey. Rostec's CEO, Sergey Chemezov, stated, "Should our Turkish partners express interest, we are prepared to arrange the delivery of Su-35 aircraft." Earlier in May 2019, Chemezov had also indicated Russia's willingness to collaborate with Turkey on both exporting and locally manufacturing the Su-57 fighter jets.

Vietnam

According to reports from The New York Times, Vietnam has been discreetly pursuing the procurement of Su-35 jets, involving measures such as sanction circumvention and indirect payment methods. Analysts who reviewed previously undisclosed air-defense documents confirmed that Vietnam likely finalized a deal for Su-35s along with other aircraft. One Vietnamese official verified a substantial order from Russia, which included approximately 40 new Su-35 and Su-30 fighters, valued at around $8 billion.

Others

After several advanced Russian military systems were deployed in Syria, multiple nations reportedly showed interest in acquiring the Su-35. Among these were Algeria, Egypt, and Vietnam. Additional countries that have demonstrated curiosity about the aircraft include Kazakhstan, North Korea, and Pakistan; however, Russian officials have denied any ongoing negotiations with Pakistan regarding the Su-35. Furthermore, Sudan expressed interest in purchasing Su-35 fighters during President Omar Hassan al-Bashir's visit to Moscow in November 2017.

Brazil

During the mid-1990s, discussions took place between Brazilian and Russian officials regarding the potential purchase of the Su-27M. In 2001, Brazil initiated the F-X competition aimed at acquiring a minimum of 12 new fighters to replace the Brazilian Air Force's outdated fleet, primarily the Mirage III aircraft. As part of efforts to boost the domestic aerospace and defense sectors, Sukhoi formed a partnership with Brazilian defense firm Avibras to participate in the tender. Together, they proposed the Su-27M for the US$700 million contract, offering an offset arrangement that would involve Brazilian industry in manufacturing certain components. However, due to internal political challenges, the tender was put on hold in 2003 and ultimately cancelled in 2005 while awaiting new fighter options. The Su-27M had been favored over its closest competitor, the Mirage 2000BR; had it been procured, it would have marked the introduction of a heavy fighter into Latin America for the first time.

When the competition was revived in 2007 as the F-X2 program, the Brazilian Defence Ministry sought to acquire at least 36 aircraft—with an option for up to 84 more—to replace its existing fleet of A-1Ms, F-5BRs, and Mirage IIIs. Contenders included the F/A-18E/F Super Hornet, F-16BR, JAS Gripen NG, Dassault Rafale, Eurofighter Typhoon, and an upgraded Su-35. Despite initial consideration, Brazil excluded the Su-35 from the competition in 2008. Following this, Rosoboronexport proposed supplying 120 fighters accompanied by full technology transfer and involvement in the PAK FA development program. Ultimately, in December 2013, Brazil selected the Gripen NG light fighter due to its affordability and comprehensive technology transfer benefits for local industry.

Egypt

In March 2019, reports emerged indicating that Egypt intended to acquire more than twenty Su-35 fighter jets from Russia, with the deal reportedly valued at approximately $2 billion and concluded in late 2018. Initial deliveries were anticipated to commence around 2020 or 2021. However, Sergei Kornev, deputy head of Rosoboronexport, refuted claims of any signed agreement for the Su-35 supply to Egypt. Meanwhile, U.S. Secretary of State Mike Pompeo cautioned Egypt against proceeding with the purchase, warning that such a transaction would trigger sanctions under the CAATSA.

By 19 May 2020, Russia had initiated production of Su-35 aircraft designated for Egypt, with the first five units rolling off the assembly line at the KnAAZ facility on 28 July 2020. As of June 2021, a total of seventeen Su-35 jets had been manufactured for Egyptian use.

On 5 January 2022, the Egyptian publication Arabo reported that Egypt, along with Algeria and Indonesia, had decided to cancel their Su-35 orders from Russia. Subsequently, in March 2022, an agreement was announced for the sale of F-15E variants to the Egyptian Air Force, signaling that Egypt had either abandoned or terminated its Su-35 contract. The aircraft originally produced for Egypt are now slated for delivery to Iran. Finalization of this transfer contract is pending negotiation over pricing and delivery schedules.

Indonesia

In 2014, Russia proposed the Su-35 as a contender in Indonesia's competition to replace its Northrop F-5E fleet. By 2015, the Su-35 was chosen, largely due to the Indonesian Air Force's existing operational experience with the Su-27SK and Su-30MK2 models. Other aircraft considered in the selection process included the Eurofighter Typhoon, Dassault Rafale, F-16, and Saab JAS 39 Gripen. In February 2018, a contract was finalized for the procurement of 11 Su-35 fighters, with approximately half of the $1.14 billion deal to be settled through commodity payments. The initial pair of jets was scheduled for delivery by October of that year.

As of May 2024, none of the aircraft have been delivered. In March 2020, Bloomberg reported that the acquisition had been cancelled under pressure from the United States; however, both Indonesia and Russia have denied that the deal was terminated. Later, in December 2021, Air Chief Marshal Fadjar Prasetyo, Chief of Staff of the Indonesian Air Force, announced that budget constraints would lead to cancellation of the purchase. By June 2023, the Indonesian Ministry of Defense indicated that concerns over potential U.S. sanctions enforced via CAATSA and OFAC had impeded progress on the procurement. Nevertheless, in May 2024, Indonesian Ambassador to Russia Jose Tavares affirmed that the contract remains active.

Other Prospects

In 1996, Russia entered the Su-27M and Su-37 into South Korea's F-X programme, which aimed to replace 40 aircraft within the Republic of Korea Air Force's inventory, including F-4D/Es, RF-4Cs, and F-5E/Fs. These Russian contenders faced competition from the Dassault Rafale, Eurofighter Typhoon, and F-15K Slam Eagle. The Sukhoi proposal incorporated a phased-array radar system and thrust vectoring engines, alongside a full technology transfer package and local final assembly in South Korea. The contract, valued at approximately US$5 billion, was to be partially funded through a debt-forgiveness arrangement related to Russia’s outstanding debts to South Korea. Nevertheless, the Su-27M was eliminated early in the selection process, which ultimately favored the F-15K.

Venezuela was identified as a potential initial export client for the upgraded Su-35. Under President Hugo Chávez, the Venezuelan government placed an order in July 2006 for 24 Su-30MK2 fighters intended to replace their fleet of F-16s affected by a US arms embargo. These aircraft were delivered to the Venezuelan Air Force between 2006 and 2008. It was anticipated that Venezuela might place a subsequent order for additional Su-30MK2s or proceed with acquiring the Su-35. Despite reports indicating Venezuelan interest and potential orders for the Su-35, no confirmed contracts have been publicly announced.

Libya was also considered an early export market for 12 to 15 Su-35 units alongside other Russian military equipment; however, these plans were disrupted by the civil conflict and subsequent international intervention, which halted procurement activities.

Russia has extended offers of the modernized Su-35 to India, Malaysia, and Greece. Nonetheless, no binding agreements have been finalized, as India and Malaysia have prioritized alternative fighter programs, making acquisition of the updated Su-35 unlikely in the near term.

Variants

Su-27M/Su-35
This single-seat fighter, internally designated T-10M (Modernizerovany, meaning "Upgraded"), incorporated a redesigned forward fuselage, canards, and an advanced fly-by-wire flight control system on its initial two prototypes. Among KNAAPO's nine pre-production aircraft, three (T10M-5, T10M-6, and T10M-7) were conversions from existing Su-27 airframes. The third prototype (T10M-3) was the first of seven pre-production models to feature taller vertical stabilizers, a two-wheel nose landing gear, and aerial refueling capability. Propulsion was provided by AL-31FM turbofan engines. By 1995, the program had produced two prototypes, nine pre-production units, and three production aircraft; additionally, two static test airframes (T10M-0 and T10M-4) were built. Despite these developments, the Su-27M did not proceed to full-scale production.
File:Sukhoi Su-37 at Farnborough 1996 airshow.jpg
Sukhoi Su-37 showcased at the 1996 Farnborough Airshow
Su-37
Developed as a technology demonstrator from the eleventh Su-27M prototype (T10M-11), this variant featured a digital fly-by-wire system, a modern glass cockpit, the N011M radar, and AL-31FP engines equipped with thrust-vectoring nozzles. Subsequently, it was upgraded with standard AL-31F engines and received revisions to its flight control and cockpit systems.
File:Su-35UB.jpeg
The only two-seat Su-35UB in 2001
Su-35UB
This two-seat trainer was designed and manufactured by KnAAPO. The sole example (T-10UBM-1) incorporated canards and taller vertical stabilizers akin to those on the Su-27M, along with a forward fuselage resembling the Su-30MKK. Its avionics suite was derived from the Su-30MKK but featured a distinct fly-by-wire system tailored for canard integration. Powered by AL-31FP engines with thrust-vectoring nozzles, the Su-35UB was engineered to maintain full combat capability despite its training role.
Su-35BM
Representing a significant redesign of the original Su-27 platform, this single-seat fighter eliminated canards and the dorsal air brake present on the Su-27M. It is equipped with the advanced N035 Irbis-E radar and features an updated cockpit layout. Thrust-vectoring AL-41F1S turbofan engines enable supercruise performance. Known internally as T-10BM (Bolshaya Modernizatsiya, or "Major Modernization"), Sukhoi markets this model simply as the "Su-35".
File:FighterAircraftExercise2020-01.jpg
Combat-ready Su-35S armed with pairs of R-73, R-27, and R-77 missiles during exercises.
Su-35S
The production version of the T-10BM tailored for the Russian Aerospace Forces carries the designation Su-35S. According to Aviation Week & Space Technology, the "S" denotes Stroyevoy ("Combatant"). NATO assigns it the reporting name Flanker-M. This latest iteration of the Su-35 family offers enhanced multirole air superiority capabilities derived from the Su-27 lineage. It boasts exceptional maneuverability (+9g) with high angle-of-attack performance and is outfitted with advanced weapon systems that significantly improve dogfighting effectiveness. In August 2009, Russia placed an order for 48 units with deliveries planned through 2015. Component manufacturing commenced in November 2009. The aircraft integrates an information management system linked to onboard subsystems and a new phased-array radar capable of long-range target detection. The first production Su-35S was delivered to the 929th State Flight Test Centre in August 2011 for evaluation flights. By December 2012, six production aircraft had been handed over to the Russian Ministry of Defence. In 2015, China procured 24 Su-35S fighters for its People’s Liberation Army Air Force.
Su-35SM
An enhanced variant of the Su-35S developed for the Russian Aerospace Forces focuses on improving air superiority and electronic warfare capabilities. This model introduces an AESA radar similar to that installed on the Su-57, replacing the Irbis-E radar to extend detection range and strengthen resistance against electronic countermeasures. It incorporates the “Himalaya” electronic warfare suite designed to provide advanced defense against radar-guided threats. Additional upgrades include secure communications and data-link systems optimized for network-centric operations as well as a laser-based DIRCM system to counter infrared-guided missiles. The airframe may utilize radar-reducing materials and be configured for compatibility with next-generation weapons such as R-37M and R-77M missiles.

Operators

File:Su-35 Operators.png
Su-35 Operators
File:Flag of Algeria.svg Algeria
Template:Country data People's Republic of China
Template:Country data Iran
File:SU-35 in Langkawi 2023.jpg
Su-35S of the "Russian Knights" in Langkawi for LIMA 2023
File:Flag of Russia.svg Russia

Significant Incidents

On 26 April 2009, the fourth Su-35BM prototype was lost during a high-speed taxi test caused by brake malfunction. The aircraft collided with the runway barrier and was completely destroyed. The pilot ejected safely but suffered burn injuries.

A Su-35S fighter jet crashed on 31 July 2021 in Russia's Khabarovsk Territory after experiencing engine failure during a standard training flight, as reported by the Russian Defence Ministry. Preliminary findings published by the Russian outlet Top War indicated malfunctions in the environmental control systems responsible for temperature regulation, including heating and cooling functions.

On 28 March 2024, a Su-35 went down into the sea near Sevastopol. Reports confirm that the pilot successfully ejected from the aircraft.

Specifications (Su-35S)

File:Electronically Scanned Array IRBIS E.jpg
Irbis-E radar featured on the upgraded Su-35 at MAKS Airshow 2009
File:Su-35 GSh-301 cannon LeBourget2013 2171.JPG
GSh-30-1 cannon mounted in the starboard wing root of a Su-35, displayed at Paris Air Show 2013

Template:Aircraft specs

Prominent media appearances

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

Related topics

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

Notes

Sources

  1. ↑ 1.0 1.1 1.2 1.3 Cite error: Invalid <ref> tag; no text was provided for refs named JIR
  2. ↑ Gordon 2007, p. 69.
  3. ↑ Andrews 2003, p. 39.
  4. ↑ Gordon 2007, pp. 58, 122.
  5. ↑ Fink 1993, p. 45.
  6. ↑ Gordon 2007, pp. 122–123.
  7. ↑ 7.0 7.1 Cite error: Invalid <ref> tag; no text was provided for refs named Williams p. 119
  8. ↑ Gordon 2007, pp. 123, 127.
  9. ↑ 9.0 9.1 Cite error: Invalid <ref> tag; no text was provided for refs named G07_p124
  10. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named Butowski 2004 p38
  11. ↑ Gordon 2007, p. 69.
  12. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named G07_p123
  13. ↑ 13.0 13.1 Cite error: Invalid <ref> tag; no text was provided for refs named TO0508
  14. ↑ 14.0 14.1 Cite error: Invalid <ref> tag; no text was provided for refs named 902FirstFlight
  15. ↑ 15.0 15.1 Cite error: Invalid <ref> tag; no text was provided for refs named VZ
  16. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named Super_Flanker
  17. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named UltimateFlanker
  18. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named G07_p111
  19. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named AW_second_order
  20. ↑ 20.0 20.1 Cite error: Invalid <ref> tag; no text was provided for refs named Fomin_2014_p37
  21. ↑ Gordon 2007, p. 366.
  22. ↑ Gordon 2007, pp. 365–366.
  23. ↑ Gordon 2007, pp. 137, 141.
  24. ↑ 24.0 24.1 Fomin 2012, p. 16.
  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. ↑ 28.0 28.1 Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  29. ↑ Fomin 2014, p. 36.
  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. ↑ 33.0 33.1 Pyadushkin 2010, p. 28.
  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. ↑ 39.0 39.1 Butowski Air International October 2019, p. 39.
  40. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  41. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  42. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  43. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  44. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  45. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  46. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  47. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  48. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named 2022RUWAir
  49. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named Su-357444287
  50. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  51. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named Andrews_2003_p58
  52. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  53. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  54. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  55. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named Kommersant
  56. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  57. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  58. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  59. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named Su-35_China
  60. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  61. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  62. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  63. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  64. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  65. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  66. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  67. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  68. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  69. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  70. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  71. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  72. ↑ 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. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  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).

Further reading

  • 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).
  • 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).
  • 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

File:Commons-logo.svg
Wikimedia Commons has media related to Sukhoi Su-35.Template:Preview warning

Template:External media

Template:Su-27 family Template:Sukhoi aircraft Template:PLAAF Aircraft

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