Jump to content

Sukhoi Su-34

From Alfawiki
Sukhoi Su-34
Company typeMilitary aircraft
IndustryAerospace
Founded1990
FounderSukhoi
Headquarters
Novosibirsk
,
Russia
ProductsFighter-bomber aircraft
ParentSukhoi

Overview

The Sukhoi Su-34 (Russian: Сухой Су-34), known by NATO as Fullback, is a Russian twin-engine, twin-seat, all-weather supersonic fighter-bomber and strike aircraft originally developed during the Soviet era.[1] It conducted its maiden flight in 1990, initially intended for the Soviet Air Forces, and was officially introduced into service with the Russian Aerospace Forces in 2014.[2]

Derived from the Sukhoi Su-27 Flanker air superiority fighter, the Su-34 features a significantly broadened and armoured cockpit that accommodates two crew members seated side-by-side.[3] Its design focuses on tactical missions targeting ground and maritime objectives, fulfilling roles such as tactical bombing, attack, and interdiction. The aircraft is capable of executing both solo and group operations during day or night, in diverse weather conditions, and while facing hostile countermeasures including counter-fire and electronic warfare. Additionally, it performs aerial reconnaissance tasks.[4]Cite error: The opening <ref> tag is malformed or has a bad name

The Su-34 is intended to supersede older platforms like the Su-24 tactical bomber and the Tu-22M long-range bomber within the Russian Aerospace Forces.[3]

Development and Production

Manufactured by Sukhoi and produced at the Novosibirsk Aircraft Production Association (NAPO), the Su-34 entered production in 2006 and continues to be built to date.[5][6] By early 2024, over 163 units have been constructed, including seven test models and 156 serial production aircraft.[7]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

Origins (1980s)

The inception of the Su-34 was complex and extended over a lengthy period. During the mid-1980s, Sukhoi embarked on creating a new tactical multirole combat aircraft intended to succeed the variable-geometry wing Su-24. This new design aimed to fulfill a variety of often conflicting operational requirements. To achieve this, the design bureau chose the Su-27 as the foundation due to its superior maneuverability, extended range, and substantial payload capacity. More precisely, the aircraft evolved from the T10KM-2, a naval trainer variant of the Su-27K. Known internally as T-10V, this project was ultimately halted by the close of the 1980s, paralleling the fate of the Ulyanovsk aircraft carrier program. These cancellations were largely influenced by the political turmoil and eventual collapse of the Soviet Union.

Prototype Development (1990–1993)

In August 1990, a TASS photographer captured an image of an aircraft simulating an approach to the aircraft carrier Tbilisi. This plane was mistakenly identified by Western intelligence as the Su-27KU. Its first flight occurred on 13 April 1990, piloted by Anatoliy Ivanov. This prototype, converted from an Su-27UB, featured a distinctively redesigned nose while retaining the primary landing gear from earlier Su-27 models. It served as a precursor to the Su-27IB (where IB denotes istrebitel-bombardirovshchik, meaning "fighter-bomber"). Developed alongside the two-seat naval trainer variant, the Su-27KUB, these two aircraft were not directly related despite previous assumptions. Flight testing persisted through 1990 and into 1991.

In 1992, the Su-27IB made its public debut at the MosAeroshow, later renamed "MAKS Airshow," where it showcased aerial refueling capabilities with an Il-78 tanker and performed aerobatic maneuvers. The official presentation took place on 13 February 1992 at Machulishi, coinciding with a summit attended by Russian President Boris Yeltsin and leaders of the Commonwealth of Independent States (CIS). The following year, the aircraft was again exhibited at MAKS.

The subsequent prototype and initial pre-production model, designated T10V-2, conducted its maiden flight on 18 December 1993 with pilots Igor Votintsev and Yevgeniy Revoonov. Constructed in Novosibirsk—the same facility responsible for Su-24 production—this version displayed noticeable differences from its predecessor. Notable changes included altered vertical stabilizers, a twin tandem main undercarriage, and an extended "stinger" housing an auxiliary power unit (APU) designed to offset cockpit weight.

Standard Su-34 (1994)

File:Su-34 Paris 1995.jpg
Su-32FN at the 1995 Paris Air Show

The initial production-standard Su-34 completed its first flight on 28 December 1994.[8] Central to its fire-control system was the Leninets OKB-developed V004 passive electronically scanned array radar.[8] This model differed significantly from its predecessors, prompting its reclassification as the "Su-34".[9] During the 1995 Paris Air Show, it was designated "Su-32FN," reflecting its prospective role as a land-based naval fighter for the Russian Naval Aviation. Additionally, Sukhoi marketed the aircraft under the name "Su-32MF" (MnogoFunksionalniy, meaning "multi-function").[8]

Despite ongoing budgetary constraints causing frequent delays in the program, flight tests proceeded, albeit slowly. The third pre-production unit took to the skies in late 1996.[10]

Further development (2016–present)

File:ROYAL AIR FORCE TYPHOONS INTERCEPT 10 RUSSIAN AIRCRAFT IN ONE MISSION MOD 45158990.jpg
An Su-34 intercepted over the Baltic region by the Royal Air Force in 2015

The Russian Ministry of Defence announced plans to upgrade the Su-34 fleet. Deputy defense minister Yuriy Borisov stated, "We intend to extend the aircraft's operational lifespan and enhance its onboard weapons capacity. The Su-34 remains highly valued within our armed forces and holds a promising future."[11]

Two new variants have been developed by Russia: one specialized in electronic warfare, equipped with the L700 Tarantul ECM pod capable of providing electronic protection for multiple aircraft,[12][13] and another designed for intelligence, surveillance, and reconnaissance.[14][15]

The upgraded Su-34M includes enhancements such as a new electro-optical infrared targeting pod, a Kopyo-DL rear-facing radar system capable of alerting pilots to incoming missiles, and automatic countermeasure deployment accompanied by jamming capabilities.[15]

Su-34 (2004–2021)

The Novosibirsk manufacturing facility completed an initial set of eight Su-34 aircraft in 2004. In March 2006, Russian Defence Minister Sergei Ivanov confirmed the acquisition of the first five pre-production Su-34 units for the Russian Air Force. By late 2008, a subsequent contract was finalized to supply 32 additional aircraft by 2015. The overall plan aimed for 70 Su-34s to be procured by 2015, intended to gradually replace roughly 300 Su-24s then in service and undergoing modernization. Ivanov highlighted that the Su-34's superior performance across key metrics meant fewer units were necessary compared to the older Su-24 fleet. In December 2006, he projected that about 200 Su-34s would be operational by 2020, a forecast later affirmed by Russian Air Force commander Vladimir Mikhaylov on 6 March 2007. During 2006–2007, two Su-34s were delivered, followed by three more by the close of 2009.

File:Sukhoi Su-34 at the MAKS-2013 (03).jpg
A Sukhoi Su-34 displayed at MAKS-2013

On 9 January 2008, Sukhoi announced the commencement of full-scale production of the Su-34. The aircraft successfully passed the final phase of state testing on 19 September 2011.

An additional four Su-34s were handed over to the Russian Air Force on 28 December 2010. Combat units stationed at airbases first received six aircraft in 2011. These deliveries were part of two contracts: one signed in 2008 for 32 planes and another in 2012 for an extra 92 units, bringing the total planned deliveries to 124 by 2020.

In December 2012, Sukhoi reportedly fulfilled part of the State Defence Order by delivering five aircraft. The first batch under the 2013 procurement plan was delivered on 6 May that year. Subsequently, on 9 July 2013, three more Su-34 bombers were officially handed over during a ceremony at the Novosibirsk Aircraft Plant. By year-end, Sukhoi had completed deliveries under the initial 2008 contract and began fulfilling the subsequent 2012 agreement.

In August 2013, Sukhoi placed an order with Kazan-based Radiopribor for 184 identification friend or foe transponders intended for installation on Russian Su-34s, with delivery scheduled through to 2020.

On 10 June 2014, another batch of Su-34s was delivered to the 559th Bomber Aviation Regiment at Morozovsk Air Base. A further three aircraft were transferred on 18 July of the same year. In total, eighteen units were supplied during 2014, with plans to deliver twenty more in 2015.

The first group of Su-34s under the defense procurement program for 2015 was delivered on 21 May. On 16 July, Sukhoi handed over an additional batch of frontline bombers to Russia’s Ministry of Defence during the Unified Military Hardware Acceptance Day held at the Novosibirsk Aircraft Production Association Plant.

Following prolonged negotiations spanning eight years, Rosoboronexport received an official request to supply Su-34s to the Algerian Air Force.

The final two aircraft from the 2012 contract were delivered in December 2020 to the 968th Fighter Aviation Regiment based at Lipetsk Air Base. This delivery brought the total operational Su-34 fleet within the Russian Aerospace Forces to 131 units, excluding losses due to accidents or write-offs. Additionally, seven pre-production models had been produced under earlier agreements.

On 25 August 2020, Russia’s Ministry of Defence signed a third contract for an extra twenty-four Su-34 aircraft destined for the Aerospace Forces, with deliveries planned over a three-year period. By December 2021, six new aircraft from this third order had been received by Russian forces.

Su-34M (2022–present)

In June 2022, the Russian Aerospace Forces took delivery of an additional four aircraft from the third production batch. These were the inaugural units manufactured according to the updated "Su-34M" configuration and were assigned to the 277th Bomber Aviation Regiment.

By August 2022, the Russian Ministry of Defence finalized a fresh contract for further Su-34 bomber acquisitions.

November 2022 saw Russia receiving another shipment of upgraded Su-34M variant aircraft; while the exact quantity remains undisclosed, it is reasonable to estimate at least four units were included. Subsequently, at the end of December 2022, another set of modernized Su-34Ms was transferred to the Russian Aerospace Forces. At this stage, the cumulative count of Su-34s produced across all contracts—including seven prototypes and pre-production models—had reached no fewer than 153 aircraft.

Throughout 2023 and into 2024, multiple deliveries occurred, specifically in June, October, and November 2023, followed by April, June, September, October, November, and December 2024. Collectively, these shipments accounted for at least ten new aircraft introduced over the course of the year.

The initial consignment for 2025 was delivered on 18 April. Subsequent batches arrived in July, August, September, October, and November of the same year, marking continuous reinforcement of the Russian Aerospace Forces' Su-34 fleet.

Design

File:Russian Air Force Sukhoi Su-34 Beltyukov-1.jpg
A Su-34 operated by the Russian Air Force

The Su-34 incorporates much of the wing configuration, tail assembly, and engine nacelles from the Su-27/Su-30 family. It features canard foreplanes similar to those on the Su-30MKI, Su-33, and Su-27M/35, which enhance static instability—improving agility—and reduce trim-induced drag.

Equipped with two Saturn AL-31FM1 turbofan engines—the same powerplants as the Su-27SM—the Su-34 achieves a top speed exceeding Mach 1.8 when fully armed.[16] While it is not as fast as the baseline Su-27, the Su-34 maintains the capability to endure high G-forces and execute complex aerobatic maneuvers.[3] With a full complement of armaments, its operational range reaches approximately 4,000 km (2,500 mi; 2,200 nmi), extendable through aerial refueling.[17] The airframe is certified for maneuvers up to +9 g.[18] Moreover, its noise output is reduced by half compared to earlier models.[19]

The aircraft employs a three lifting surface configuration, combining a traditional horizontal tailplane at the rear with a canard foreplane situated ahead of the main wings. This foreplane contributes additional lift and enhances maneuverability. It retains twin vertical stabilizers akin to those on its Su-27 predecessor. The Su-34 supports 12 hardpoints capable of carrying between 12,000–14,000 kg (26,000–31,000 lb) of munitions,[20] including state-of-the-art Russian precision-guided weaponry. The aircraft retains the 30 mm GSh-30-1 cannon found on the Su-27 and Su-30 platforms[21], alongside the capacity to carry six air-to-air missiles such as the R-77 or R-73, primarily intended for self-defense against enemy fighters. Individual munitions can weigh up to 4,000 kg (8,800 lb). Its stand-off weaponry can engage targets at distances reaching 250 km (160 mi; 130 nmi).[22][23] Standard equipment includes a Khibiny electronic countermeasures (ECM) suite.[24]

File:Sukhoi Su-34 (Simulator), Russia - Air Force AN2242851.jpg
Cockpit simulator of a Sukhoi Su-34

Distinct from other Flanker variants, the Su-34 features an entirely redesigned "Duckbill" nose and forward fuselage to maximize internal space and improve crew comfort and protection, earning nicknames such as "Duckling," "Hellduck," or "Platypus".[3][25] The two crew members are seated side-by-side in NPP Zvezda K-36DM ejection seats: the pilot-commanding officer occupies the left seat while the navigator/weapons operator sits to the right. This side-by-side layout eliminates the need for duplicate instrumentation for each occupant. Given the length of typical sorties, the pressurization system supports operations up to 10,000 metres (33,000 ft) without requiring oxygen masks, which remain available for emergency or combat use.[26]

The cabin affords enough space for crew members to stand and move during extended flights[27][28] and includes room between seats allowing them to recline if necessary[26]. Amenities include a portable urinal and vacuum flask kitchen.[29] Access to the cockpit is via a ladder attached to the nose landing gear combined with a hatch located on the cockpit floor. The cockpit itself is encased in a continuous armored capsule made from 17 mm thick armor.[30]Template:Fix/category[citation needed]

The primary radar system is the multifunctional Leninets V004, which offers both terrain-following and terrain avoidance capabilities.[31] Its passive electronically scanned array radar can detect large surface targets at ranges between 200–250[convert: needs unit name].[31] This radar can track up to ten airborne targets simultaneously[32] and engage up to four targets across air, land, or maritime domains.[17] Fighter-sized targets can be detected within a radius of up to 120 km with a scanning range of ±60 degrees.[33] The frontal radar cross-section of the Su-34 reportedly is significantly lower—by an order of magnitude—compared to previous generation fighters.[17]

In 2016, a new fourth-generation radar system called Pika-M from the BKR-3 complex, offering detection ranges up to 300 km, successfully completed state testing.[34] By 2021, multiple RuAF units had their aircraft upgraded with advanced systems that enhance detection capabilities against aerial and ground targets while broadening their armament options.Cite error: Closing </ref> missing for <ref> tag

In July 2010, a group of Su-34s alongside Su-24Ms completed a continuous flight covering approximately 6,000 km (3,700 mi; 3,200 nmi) from bases in European Russia to the Russian Far East. This mission involved carrying a full weapons load and conducting mock strikes on designated targets, highlighting the Su-34’s extended operational range. During the exercise, Su-24Ms required three aerial refuelings, whereas the Su-34s were refueled twice.[35]

The concluding phase of the Su-34’s official state trials was finalized on 19 September 2011, with the aircraft entering active service by early 2014.[36][37]

Accidents and Incidents

  • On 4 June 2015, an Su-34 experienced a runway excursion and overturned after its braking parachute failed to deploy upon landing. The event occurred following a routine training sortie in Russia’s Voronezh region, with no injuries reported.[38] The damaged aircraft was transported by an Antonov An-124 to the Novosibirsk Aircraft Production Association facility for repairs in June 2016 and was presumably returned to operational status within that year.[39]
  • On 18 January 2019, two Su-34s collided mid-flight during a scheduled training operation over Russia’s Far East. The crash resulted in two fatalities among the pilots; one pilot was rescued while another remained missing. Following this incident, all Su-34 flights across Russia were temporarily grounded.[40][41][42]
  • On 6 September 2019, a second mid-air collision involving two Su-34s occurred near the city of Lipetsk in western Russia. According to local sources, pilot error was identified as the cause. Both crews successfully landed their aircraft after the collision.[43][44]
  • On 21 October 2020, an Su-34 crashed during a training flight within Khabarovsk Krai.[45]
  • On 17 October 2022, a Russian Su-34 fighter-bomber crashed into a residential courtyard in Yeysk during a training sortie, igniting fires across two apartment blocks. The accident caused fifteen fatalities and nineteen injuries requiring hospitalization; an evacuation of a nearby school was also carried out. Official statements from the Russian defense ministry attributed the crash to an engine fire during takeoff, noting both pilots ejected safely. Eyewitnesses reported locals assisting one pilot’s rescue. Yeysk serves as a principal training location for Russian naval aviation.[46][47][48][49]
  • On 20 April 2023, during a flight over Belgorod city, an Su-34 accidentally released ordnance which shattered nearby windows, damaged vehicles, and created a crater about twenty meters wide. Three individuals sustained injuries as a result.[50]
  • On 20 September 2023, an Su-34 bearing the identifier "Red 05" (RF-95806) crashed within Voronezh Oblast without causing harm to personnel or infrastructure on the ground. Both aviators safely ejected from the aircraft.[51][52]
  • On 10 June 2024, an Su-34 crashed amid a training mission conducted over the mountainous terrain of North Ossetia–Alania, resulting in the deaths of both pilots aboard.[53]

Syrian Civil War

(2015–2020)
File:Su-34. Bottom view.png
Underside view of an Su-34
File:Russian Sukhoi Su-34 at Latakia (1).jpg
An Su-34 stationed at Bassel Al-Assad International Airport in Latakia, Syria, during early stages of Russia's involvement in 2015

In September 2015, a squadron of six Su-34 aircraft was deployed to Latakia airport in Syria to participate in Russian military operations targeting rebel factions and ISIL forces.[54] The commencement of Russian air raids in Syria was recorded on 30 September, focusing initially on the Homs region.Cite error: The opening <ref> tag is malformed or has a bad name On 1 October, Su-34 bombers engaged Islamic State positions within Syria.Template:Fix/category[citation needed] The Russian Aerospace Forces' Su-34s successfully eliminated an ISIL command post and a training facility located southwest of Raqqa.Template:Fix/category[citation needed] These precision strikes were executed from altitudes exceeding 5,000 meters (16,400 feet).Template:Fix/category[citation needed]

The following day, Russian Su-34 and Su-25 attack jets conducted precision bombing missions against Islamic State targets in the Hama province. According to Maj. Gen. Igor Konashenkov, spokesperson for the Russian Defense Ministry, Su-34s utilized guided munitions to destroy an ISIL fortified bunker in Hama.[55] Additional targets included fortifications, ammunition storage sites, and seven units of military hardware near Maarrat al-Numan. Moreover, an ISIL command center and underground depot near Raqqa were eliminated.

On 3 October, Maj. Gen. Konashenkov reported that a concrete-piercing BETAB-500 bomb delivered by an Su-34 near Raqqa obliterated a hardened command facility belonging to illegal armed groups, along with an underground explosives bunker and ammunition storage.[56] A representative of the Russian Aerospace Forces noted that Su-34s employ the GLONASS satellite navigation system for target acquisition during bombing runs.[57] During this period, six Su-34 aircraft were operationally deployed within Syria.Cite error: The opening <ref> tag is malformed or has a bad name

Following the shootdown of an Su-24 by Turkey, Russia declared on 30 November 2015 that Su-34s operating in Syria had begun conducting combat sorties equipped with air-to-air missiles.Cite error: The opening <ref> tag is malformed or has a bad name</ref> On 16 August 2016, Tu-22M3 long-range bombers alongside Su-34 bombers launched coordinated airstrikes against ISIS and Jabhat al-Nusra targets across the Aleppo, Deir ez-Zor, and Idlib provinces after departing from their base in Hamadan, Islamic Republic of Iran.Cite error: The opening <ref> tag is malformed or has a bad name</ref>

On 3 October 2017, Russian Su-34s and Su-35s targeted a location identified by Russian military intelligence as the site of an Al-Nusra leadership gathering. This strike resulted in the elimination of twelve field commanders and approximately fifty militants of the group, including Ahmad al-Ghizai, Al-Nusra’s security chief, as confirmed by the Russian Defense Ministry.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</ref>

On 28 May 2018, reports indicated that Russian Su-34 jets intercepted two Israeli Air Force F-16 fighters over Tripoli, Lebanon, compelling their withdrawal.Cite error: The opening <ref> tag is malformed or has a bad name</ref>

On 27 February 2020, two Russian Su-34s reportedly executed an airstrike on a Turkish military convoy in Balyun, Syria, resulting in up to thirty-six Turkish soldiers killed and at least sixty wounded.Cite error: The opening <ref> tag is malformed or has a bad name</ref>

On 6 October 2020, a pair of Russian Su-34s carried out airstrikes targeting underground facilities on the eastern bank of the Euphrates River in Deir Ez-Zor province—territory within the Rojava region. This operation led to the death of ISIL field commander Abu Qatada, who was implicated in orchestrating an attack that caused the death of Major General Vyacheslav Gladkikh. The strike also destroyed two subterranean shelters and eliminated approximately thirty militants.Cite error: The opening <ref> tag is malformed or has a bad name</ref>

Russian invasion of Ukraine (2022–present)
Main articles: Russian invasion of Ukraine and Battle of Kharkiv (2022)
File:Russian plane with bombs shot down over Chernihiv (1).jpg
A Russian Su-34 carrying bombs downed over Chernihiv on 5 March 2022

On 28 February 2022, video footage surfaced allegedly depicting Su-34 aircraft flying over Ukraine’s Kharkiv region.[58]

Before the introduction of Russian GPS-guided UMPK (Unified Gliding and Correction Module) bomb kits in 2023, the absence of precision-guided munitions forced Su-34s to conduct low-altitude bombing runs for accuracy, exposing them to intense fire from Ukrainian air defense systems.[59]

By 16 February 2025, visual confirmations indicate that Russian forces have lost, damaged, or abandoned a total of 37 Su-34 variants since the onset of the 2022 invasion (including 36 Su-34s and one Su-34M). These losses comprise 29 destroyed in combat, four lost due to non-combat incidents, and four aircraft damaged.[60]

Ukraine has executed multiple unexpected strikes[61] targeting Russian Su-34 fighter-bombers stationed in occupied southern regions such as Kherson and Mariupol. These attacks employed American-supplied long-range MIM-104 Patriot missile systems and resulted in significant attrition among Russian Su-34 fleets. Throughout ongoing hostilities, Russia has suffered nearly 36 Su-34 fighter-bomber losses by June 2024.[62][63][64] According to data from Oryx (website), by July 2025, a total of 41 Su-34 aircraft have been recorded as either destroyed or damaged.[65]

Chronological Record of Su-34 Shootdowns in the Russo-Ukrainian Conflict
2022
  • The initial Su-34 downed in combat was recorded shortly after hostilities commenced, on 28 February 2022, near the Buzova airfield.[66][67][68]
  • On 1 March, another Su-34 identified as "Red 31", RF-81251, was destroyed near Borodyanka in the Kyiv region.[69][70][71]
  • A Su-34 designated "Red 26", RF-81864, was downed on 5 March near Hrabivka in Chernihiv Oblast; both pilots perished.[72][73][74]
  • On 6 March, a Su-34 with tail number RF-95070 was lost over Kharkiv.[75][76]
  • A Su-34 reportedly crashed on 10 March near Kozhan-Gorodok, Belarus, approximately 17 km from Luninets (air base), with both crew members ejecting safely.[77]
  • On or around 14 March, a Su-34 "Red 35", RF-95010 was lost somewhere within Ukraine.[78][79]
  • A Su-34 "Red 43", RF-95858 was destroyed in Zaporizhzhia Oblast on 21 April.[80]Cite error: Closing </ref> missing for <ref> tag[81][82]

Acquisition by Algeria

Negotiations commenced in January 2016 concerning Algeria's potential acquisition of a dozen Su-34 aircraft intended for its Air Force.[83] The agreement was anticipated to be finalized by late 2016,[84] although by 2017 discussions were still active and no formal contract had been concluded.[85][86] On 27 December 2019, reports indicated that Algeria had inked a contract for fourteen units as part of a broader defense procurement package that also featured Su-35 and Su-57 fighter jets.[87] Nevertheless, official confirmation from either the Russian or Algerian authorities regarding this transaction has not been forthcoming.

According to Mil.press, after eight years of unsuccessful negotiations over the export version Su-32 with Algeria, Russia agreed in 2019 to supply the upgraded, fully capable Su-34ME variant; Algeria's interest in this model was sparked by its demonstrated combat effectiveness during operations in Syria. As of March 2021, production of the initial batch was underway and, based on information from CAWAT, completion was expected within that year. Pilot training for Algerian crews was planned to begin in 2022, with full delivery scheduled by 2023.[88] However, a statement from a representative of Russia's Federal Service for Military-Technical Cooperation (FSVTS) on 17 March 2021 refuted claims that aircraft production for Algeria had commenced.[89]

The unveiling of a Su-34 painted in a newly introduced desert camouflage scheme featuring brown and yellow hues in mid-May 2025 has triggered speculation about the initiation of export production. While Algeria is considered the most probable recipient, other clients operating in similar arid environments such as Iran or Sudan are also potential candidates.[90]

Variants

  • Su-34 – the standard version of the aircraft.
  • Su-32 – an export variant proposed to Algeria in 2012, currently not available on the market.
  • Su-34E – the export version presently offered.
  • Su-34M / Su-34 NVO (Навигация и Внешнее Оборудование, Navigation and External Equipment Upgrade) – a modernized iteration, also referred to as Su-34 Sych (named after the Athene). The Russian Ministry of Defense signed a contract for this model in 2020, which replaced the original Su-34 in production. This upgrade impacts nearly all avionics systems significantly, including enhancements to radar, targeting, and communication equipment. The bomber’s capability to deploy a wider array of guided weapons has been notably increased. Electronic warfare systems have also been improved through the addition of new hardpoints. Reports from September 2023 indicate this variant was equipped with long-range cruise missiles. An armed reconnaissance configuration was introduced into service by July 2025.

Operators

Template:RUS

Specifications (Su-34)

File:Sukhoi Su-34.svg
Three-view diagram of the Su-34
File:Su-34 nose.jpg
Front perspective of the Su-34
File:Fixing KAB-500S guided bombs to a Sukhoi Su-34 at Latakia (1).jpg
Mounting KAB-500S GLONASS Satellite-guided bombs on a Sukhoi Su-34 at Bassel Al-Assad International Airport, 2015
File:Su-34 Hardpoint & Armament arrangement.svg
Arrangement of Su-34 hardpoints and weaponry

Template:Aircraft specs

See also

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

References

  1. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named NATOname
  2. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named awst_Russian_Industry_reorg
  3. ↑ 3.0 3.1 3.2 3.3 Cite error: Invalid <ref> tag; no text was provided for refs named rbth.com
  4. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named sukhoi-su32
  5. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named 2006prod
  6. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named 2010prod
  7. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named bmpdDec2022
  8. ↑ 8.0 8.1 8.2 Williams (2002), p. 132.
  9. ↑ Gordon (1999), p. 93.
  10. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  11. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  12. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  13. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  14. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  15. ↑ 15.0 15.1 Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  16. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  17. ↑ 17.0 17.1 17.2 Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  18. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  19. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  20. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  21. ↑ Gordon & Davison (2006), pp. 80–81.
  22. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  23. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  24. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  25. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  26. ↑ 26.0 26.1 Gordon (1999), p. Template:Page needed.
  27. ↑ Spick (2000), pp. 518–519.
  28. ↑ Eden (2004).
  29. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  30. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  31. ↑ 31.0 31.1 Cite error: Invalid <ref> tag; no text was provided for refs named ausairpower1
  32. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  33. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  34. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  35. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  36. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  37. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  38. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  39. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  40. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  41. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  42. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  43. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  44. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  45. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  46. ↑ 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. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  49. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  50. ↑ "Emergency release of air ordnance occurred during Su-34 flight above Belgoroddate" Archived 21 April 2023 at the Wayback Machine. tass.com
  51. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  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. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named aviationist 6 arrive
  55. ↑ Template:Fix/category[citation needed]
  56. ↑ Template:Fix/category[citation needed]
  57. ↑ Template:Fix/category[citation needed]
  58. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  59. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  60. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  61. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  62. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).Template:Fix/category[permanent dead link]
  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).
  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. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  83. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  84. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  85. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  86. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  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. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  95. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  96. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  97. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  98. ↑ 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).

External links

File:Commons-logo.svg
Wikimedia Commons has media related to Lua error in Module:Commons_link at line 62: attempt to index field 'wikibase' (a nil value)..

Template:External media

Template:Su-27 family Template:Sukhoi aircraft

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