Sukhoi Su-34

From Infogalactic: the planetary knowledge core
(Redirected from Su-34)
Jump to: navigation, search
Su-32/34
MAKS2015part1-10 (cropped).jpg
A Russian Air Force Su-34
Role Fighter-bomber, strike fighter[1][2][3][4]
National origin Russia
Manufacturer Sukhoi
First flight 13 April 1990
Introduction 20 March 2014[5][6]
Status In service
Primary user Russian Air Force
Produced 2006–present[7][8]
Number built 102 as of May 2017[9]
Unit cost
US$36 million[10][11]
Developed from Sukhoi Su-27

The Sukhoi Su-34 (Russian: Сухой Су-34; NATO reporting name: Fullback)[12] is a Russian twin-engine, twin-seat, all-weather supersonic medium-range fighter-bomber.[1] It is intended to replace the Sukhoi Su-24 and first entered service in 2014 with the Russian Air Force.[13]

Based on the Sukhoi Su-27, two-seat Su-34 is designed primarily for tactical deployment against ground and naval targets (tactical bombing/attack/interdiction roles, including against small and mobile targets) on solo and group missions in daytime and at night, under favourable and adverse weather conditions and in a hostile environment with counter-fire and EW counter-measures deployed, as well as for aerial reconnaissance.[1][14][15]

Development

The Su-34 had a muddied and protracted beginning.[16] In the mid-1980s, Sukhoi began developing a new tactical multirole combat aircraft to replace the swing-wing Su-24, which would incorporate a host of conflicting requirements. The bureau thus selected the Su-27, which excelled in maneuverability and range, and could carry a large payload, as the basis for the new fighter-bomber.[17] More specifically, the aircraft was developed from T10KM-2, the naval trainer derivative of the Sukhoi Su-27K. The development, known internally as T-10V, was shelved at the end of the 1980s sharing the fate of the aircraft carrier Ulyanovsk; this was the result of the political upheaval in the Soviet Union and its subsequent disintegration.[16][17]

In August 1990, a photograph taken by a TASS officer showed an aircraft making a dummy approach towards the aircraft carrier Tbilisi.[16][17] The aircraft, subsequently and erroneously labelled Su-27KU by Western intelligence, made its maiden flight on 13 April 1990 with Anatoliy Ivanov at the controls.[18] Converted from an Su-27UB with the new distinctive nose, while retaining the main undercarriage of previous Su-27s, it was a prototype for the Su-27IB (Istrebitel Bombardirovshchik, or "fighter bomber").[19] It was developed in parallel with the two-seat naval trainer, the Su-27KUB. However, contrary to earlier reports, the two aircraft are not directly related.[20] Flight tests continued throughout 1990 and into 1991.[17]

Su-34 intercepted by RAF over the Baltic in 2015

In 1992, the Su-27IB was displayed to the public at the MosAeroshow (later renamed "MAKS Airshow"), where it demonstrated aerial refuelling with an Il-78, and performed an aerobatic display. The aircraft was officially unveiled on 13 February 1992 at Machulishi, where Russian President Boris Yeltsin and the CIS leaders were holding a summit. The following year the Su-27IB was again displayed at the MAKS Airshow.[18]

The next prototype, and first pre-production aircraft, T10V-2, first flew on 18 December 1993, with Igor Votintsev and Yevgeniy Revoonov at the controls.[18] Built at Novosibirsk, where Su-24s were constructed, this aircraft was visibly different from the original prototype; it had modified vertical stabilizers, twin tandem main undercarriage and a longer "stinger", which houses a rearward-facing warning radar.[16] The first aircraft built to production standard made its first flight on 28 December 1994.[16] It was fitted with a fire-control system, at the heart of which was the Leninets OKB-designed V004 passive electronically scanned array radar.[16] It was different enough from the earlier versions that it was re-designated the "Su-34".[18] However, at the 1995 Paris Air Show, the Su-34 was allocated the "Su-32FN" designation, signalling the aircraft's potential role as a shore-based naval aircraft for the Russian Naval Aviation. Sukhoi also promoted the Su-34 as the "Su-32MF" (MnogoFunksionalniy, "multi-function").[16]

Budget restrictions caused the programme to stall repeatedly. Nevertheless, flight testing continued, albeit at a slow pace. The third pre-production aircraft first flew in late 1996.[21]

Russia's Ministry of Defence plans to modernize the Su-34; according to the deputy head of the military department, Yuriy Borisov, "We are planning to modernize the aircraft: prolong its service life, increase the number of airborne weapons. Plane is in great demand in our armed forces, and it has a great future."[22][23]

Orders and deliveries

An initial batch of eight aircraft was completed by the Novosibirsk factory in 2004.[24] In March 2006, Russia's Minister of Defence Sergei Ivanov announced the purchase of the first 5 pre-production Su-34s for the Russian Air Force. In late 2008, a second contract was signed for delivery of 32 aircraft by 2015.[10] A total of 70 aircraft were to be purchased by 2015 to replace some 300 Russian Su-24s, which were then undergoing a modernization program.[11] Ivanov claimed that as it is "many times more effective on all critical parameters", fewer of these newer bombers are required than the old Su-24 it replaces. In December 2006, Ivanov revealed that approximately 200 Su-34s were expected to be in service by 2020;[25] and was confirmed by Air Force chief Vladimir Mikhaylov on 6 March 2007.[26] Two Su-34s were delivered in 2006-2007, and three more were delivered by the end of 2009.[10]

Sukhoi Su-34 at the MAKS 2013

On 9 January 2008, Sukhoi reported that the Su-34 had begun full-rate production.[27] The final stage of the state tests were completed on 19 September 2011.[28]

The Russian Air Force received another four Su-34s on 28 December 2010,[29] as combat units in airbases first received six Su-34s in 2011.[30] Delivery came in the form of two contracts, the first in 2008 for 32 aircraft and the second in 2012 for a further 92 aircraft, totaling 124 to be delivered by 2020.[31] In December 2012, Sukhoi reportedly delivered five aircraft under the 2012 State Defense Order.[32] In January 2013, Sukhoi delivered a batch of 5 Su-34s, flying directly from the Novosibirsk aircraft plant to an air base in Voronezh, Russia.[33] On 6 May 2013, the first Su-34s under the 2013 defence procurement plan were delivered.[34]

On 9 July 2013, three more Su-34s were delivered in an official acceptance ceremony held at the Novosibirsk Aircraft Plant. These three aircraft were already in the new Russian Air Force camouflage scheme.[35] By the end of 2013, Sukhoi completed the 2008 contract and started deliveries on 2012 contract.[36]

In August 2013, Sukhoi signed a contract with the Kazan-based Radiopribor holding company for 184 "friend-or-foe" transponders for the Su-34 to be delivered by 2020.[37]

On 10 June 2014, Russia1 TV reported a further delivery of Su-34s was made to the 559th Regiment at Morozovsk.[38] Another three aircraft were delivered on 18 July 2014.[39] 18 aircraft were delivered in 2014,[40][41] and 20 planned to be delivered in 2015.[42]

Sukhoi has delivered the first batch of Su-34s to the Russian Ministry of Defense under the 2015 order on 21 May 2015.[43] On 16 July 2015, the Sukhoi Company handed over another batch of Su-34 frontline bombers to the Ministry of Defense of the Russian Federation. The transfer took place in the framework of the Unified Military Hardware Acceptance Day in the Sukhoi Company’s branch — V.P.Chkalov Novosibirsk aviation plant.[44]

After eight years of negotiations, Rosoboronexport received requests to supply the Su-34 to Algeria, for the Algerian Air Force.[45]

Design

Russian Air Force Su-34

The aircraft shares most of its wing structure, tail, and engine nacelles with the Su-27/Su-30, with canards like the Su-30MKI, Su-33, and Su-27M/35 to increase static instability (higher manoeuvrability) and to reduce trim drag. The aircraft has an entirely new nose and forward fuselage with a cockpit providing side-by-side seating for a crew of two. The Su-34 is powered by a pair of Saturn AL-31FM1 turbofan engines, the same engines used on the Su-27SM; giving the aircraft a maximum speed of Mach 1.8+ when fully loaded.[46] When equipped with a full weapons load, the Su-34 has a maximum range of 4,000 kilometres (2,500 mi) without refuelling, this can be extended further via aerial refueling.[47] When operating at its operational maximum, the airframe can withstand an 'overload' of up to +9G.[48]

The Su-34 is a three-surface design having both a conventional horizontal tailplane at the rear and a canard foreplane in front of the main wings. The foreplane provides both additional lift (force) and greater maneuverability. It has twin tail fins like those of Su-27 from which it is derived. The Su-34 has 12 hardpoints for 8,000–12,000 kg (17,600–26,500 lb) of ordnance,[49][50] intended to include the latest Russian precision-guided weapons. It retains the Su-27/Su-30's 30 mm GSh-30-1 cannon,[51] and the ability to carry R-77 air-to-air missiles (6 pcs) and R-73 (also 6). The maximum weight of any single munition carried is 4000 kg, with a maximum munitions load the maximum attack range is 250 kilometres (160 mi).[52][53] A Khibiny Electronic countermeasures (ECM) system is fitted as standard.[54]

Sukhoi Su-34 cockpit simulator

The Su-34's most distinctive feature is the unusually large flight deck. Much of the design work went into crew comfort. The two crew members sit side by side in a large cabin, with the pilot-commander to the left and navigator/operator of weapons to the right in NPP Zvezda K-36dm ejection seats. An advantage of the side by side cockpit is that duplicate instruments are not required for each pilot. Since long missions require comfort, the pressurization system allows operation up to Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value). without oxygen masks, which are available for emergencies and combat situations.[55] The crew members have room to stand and move about the cabin during long missions.[56][57] The space between the seats allows them to lie down in the corridor, if necessary.[55] A galley and toilet are located behind the crew seats.[55][56] A ladder attached to the nose landing gear and a hatch in the cockpit floor is used to enter the cockpit. The cockpit is a continuous capsule of armour (17 mm[58]).[59] The Helmet Mounted Display System (HMDS) acts as a command center: precision target designation of all onboard weapons is tied to the movement of the pilot's head and eyes.[47]

Maximum detection range for the passive electronically scanned array forward radar is 200–250 km, to cover the rear a second aft-facing radar is mounted.[47] The main radar can simultaneously attack four targets (in the air, on land or on the water).[47] The rear warning radar system can warn of attack from behind and allow it to fire its R-73s against pursuers without needing to turn the aircraft.[47] The rear radar is unofficially called the N-012.[59] The Su-34 reportedly has a frontal radar cross-section that is an order of magnitude smaller than prior generation fighters.[47]

A new 4th generation radar Pika-M of the complex BKR-3, having a range up to 300 km, passed state tests in 2016.[60]

Operational history

Sukhoi Su-34 fighter-bomber

The Su-34's long range was shown in a July 2010 exercise when Su-34s and Su-24Ms were moved from Russian bases in Europe to one on the Pacific coast, 6,000 kilometres away, which requires in-flight refuelling. The exercise included aircraft carrying weapons at full load, simulated delivering them on a target before arriving at the Pacific coast base. Su-24Ms were refuelled three times, while the Su-34 was refuelled twice.[61]

The Russian Air Force completed the final stage of the state tests on 19 September 2011.[28] The aircraft entered service in early 2014.[5] The Su-34 was rumoured to have been used by Russian command during the 2008 South Ossetia war.[62] Russia plans to have 124 in use by 2020.[63] This total is planned to increase to 200 later.[64]

Accidents and incidents

4 June 2015. A Su-34 had an accident in Russia's Voronezh region while conducting a routine training mission. The airplane's parachute failed to open after landing and the Su-34 slid off the runway and flipped over. Nobody was killed.[65] In June 2016, the damaged Su-34 was transported on board Antonov An-124 to the Novosibirsk Aviation Plant to undergo repairs. The aircraft was probably returned in service in the same year.[66]

17 October 2022. A Russian Air Force Sukhoi Su-34, RF-81726/20 red, operated by 303rd Composite Aviation Division, 277th Red Banner Bomber Aviation Regiment, crashed into the yard of a an apartment building in Yeysk, about 4 km east from the end of the runway of Yeysk Airport (EIK/URKE) immediately after takeoff following a suspected multiple bird ingestion into both engines. The two pilots ejected safely, however 15 people on the ground died as a result of injuries sustained from the crash and many more were injured. [67]

2015 Russian military intervention in Syria

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

An Su-34 at Bassel Al-Assad International Airport in Latakia, Syria, in late 2015, early in Russia's intervention in Syria.

In September 2015, six Su-34s arrived at Latakia airport in Syria, for attacks against rebel and ISIL forces.[68] Russian air attacks in Syria started on the 30 September, in the Homs region.[69] On 1 October, the Su-34 was used to bomb Islamic State targets in Syria.[70] The Russian Air Force Su-34 fighter-bombers destroyed an Islamic State command center and training camp south-west of the city of Raqqa.[71] These included precision strikes from an altitude of over 5,000 m (16,400 ft).[72] Russian Su-34 and Su-25 attack aircraft carried out air strikes the next day against Islamic State targets in Syria's Hama province using precision bombs. According to Russian Defense Ministry spokesman Maj. Gen. Igor Konashenkov, Su-34s hit an ISIL fortified bunker in the Hama province with guided bombs.[73] Fortifications, ammunition depots, seven units of the military equipment near Syria's Maarrat al-Numan were also destroyed by the Russian Air Force. An ISIL command center and underground depot were also destroyed with explosives near Raqqa. Defense Ministry spokesman Maj. Gen. Igor Konashenkov said in a statement on 3 October, "Accurate delivery of a concrete-piercing bomb BETAB-500 launched from a Su-34 aircraft near Raqqa destroyed a hardened command centre of one of the illegal armed groups as well as an underground bunker with explosives and ammunition depot."[74] A Russian Air Force representative stated Su-34s acquire targets using the GLONASS satellite system for bombing.[75] During this time six Su-34s were in Syria maintaining a 70 percent availability rate for sorties.[76] Eight more Su-34s arrived in Syria on 20 November 2015.[77] Following the shooting down of an Su-24 by Turkey, Russia announced on 30 November 2015 that Su-34s in Syria had begun flying combat missions while armed with air-to-air missiles.[78] On 16 August 2016, Tu-22M3 long-range bombers and Su-34 bombers, having taken off from their base in Hamadan [Islamic Republic of Iran], carried out group airstrikes against targets belonging to Daesh and Jabhat al-Nusra terrorist groups in the provinces of Aleppo, Deir ez-Zor and Idlib.[79] On August 17, 2016, Russian Su-34 bombers carried out strikes from the Hamadan airfield on the territory of the Islamic Republic of Iran against targets of the Daesh terrorist group in the province of Deir ez-Zor. Aircraft carried high-explosive bombs OFAB-500.[80]

Other usage

These aircraft were used for bombing ice dams on the rivers in Vologda oblast to prevent the floods during the spring of 2016.[81][82][83]

Operators

Su-34 taxiing
 Algeria
 Russia
  • Prototypes and testing gliders – 10 (some can be modified to combat aircraft). Also two aircraft at high readiness, totally constructed 100 aircraft.[96]

Specifications (Su-34)

Su-34 three-view illustration
Front view of the Su-34
File:Su-34 Hardpoint & Armament arrangement.PNG
Su-34 Hardpoint & Armament arrangement

Data from Sukhoi,[97] Gordon and Davison,[98] airforce-technology.com,[99] airwar.ru,[100] ria.ru,[101] deagel.com[102]

General characteristics

Performance

Armament

Avionics

See also

Related development
Aircraft of comparable role, configuration and era

References

  1. 1.0 1.1 1.2 Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. 5.0 5.1 Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. 10.0 10.1 10.2 Lua error in package.lua at line 80: module 'strict' not found.
  11. 11.0 11.1 Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. 16.0 16.1 16.2 16.3 16.4 16.5 16.6 Williams (2002), p. 132.
  17. 17.0 17.1 17.2 17.3 Gordon (1999), p. 92.
  18. 18.0 18.1 18.2 18.3 Gordon (1999), p. 93.
  19. Eden (2004), p. 466.
  20. Andrews, Thomas, "Sukhoi Su-27/Su-30 Family," International Air Power Review, Volume 8, Spring 2003.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. 28.0 28.1 Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. Lua error in package.lua at line 80: module 'strict' not found.
  45. [1][dead link]
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. 47.0 47.1 47.2 47.3 47.4 47.5 47.6 Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. 49.0 49.1 Lua error in package.lua at line 80: module 'strict' not found.
  50. 50.0 50.1 Lua error in package.lua at line 80: module 'strict' not found.
  51. Gordon & Davison (2006), pp. 80–81.
  52. Lua error in package.lua at line 80: module 'strict' not found.
  53. Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. 55.0 55.1 55.2 Lua error in package.lua at line 80: module 'strict' not found.
  56. 56.0 56.1 Spick (2000), pp. 518–519.
  57. Eden (2004).
  58. Lua error in package.lua at line 80: module 'strict' not found.
  59. 59.0 59.1 Lua error in package.lua at line 80: module 'strict' not found.
  60. Lua error in package.lua at line 80: module 'strict' not found.
  61. Lua error in package.lua at line 80: module 'strict' not found.
  62. Lua error in package.lua at line 80: module 'strict' not found.
  63. Lua error in package.lua at line 80: module 'strict' not found.
  64. Lua error in package.lua at line 80: module 'strict' not found.
  65. Lua error in package.lua at line 80: module 'strict' not found.
  66. Lua error in package.lua at line 80: module 'strict' not found.
  67. https://aviation-safety.net/wikibase/299454
  68. Lua error in package.lua at line 80: module 'strict' not found.
  69. Lua error in package.lua at line 80: module 'strict' not found.
  70. Lua error in package.lua at line 80: module 'strict' not found.
  71. Lua error in package.lua at line 80: module 'strict' not found.
  72. Lua error in package.lua at line 80: module 'strict' not found.
  73. Lua error in package.lua at line 80: module 'strict' not found.
  74. Lua error in package.lua at line 80: module 'strict' not found.
  75. Lua error in package.lua at line 80: module 'strict' not found.
  76. Lua error in package.lua at line 80: module 'strict' not found.
  77. Lua error in package.lua at line 80: module 'strict' not found.
  78. Lua error in package.lua at line 80: module 'strict' not found.
  79. Lua error in package.lua at line 80: module 'strict' not found.
  80. Lua error in package.lua at line 80: module 'strict' not found.
  81. Lua error in package.lua at line 80: module 'strict' not found.
  82. Lua error in package.lua at line 80: module 'strict' not found.
  83. Lua error in package.lua at line 80: module 'strict' not found.
  84. Lua error in package.lua at line 80: module 'strict' not found.
  85. Lua error in package.lua at line 80: module 'strict' not found.
  86. Lua error in package.lua at line 80: module 'strict' not found.
  87. Lua error in package.lua at line 80: module 'strict' not found.
  88. Lua error in package.lua at line 80: module 'strict' not found.
  89. Lua error in package.lua at line 80: module 'strict' not found.
  90. Lua error in package.lua at line 80: module 'strict' not found.
  91. Lua error in package.lua at line 80: module 'strict' not found.
  92. Lua error in package.lua at line 80: module 'strict' not found.
  93. Lua error in package.lua at line 80: module 'strict' not found.
  94. Lua error in package.lua at line 80: module 'strict' not found.
  95. Lua error in package.lua at line 80: module 'strict' not found.
  96. Lua error in package.lua at line 80: module 'strict' not found.
  97. Lua error in package.lua at line 80: module 'strict' not found., Lua error in package.lua at line 80: module 'strict' not found.
  98. Gordon & Davison (2006), pp. 92, 95–96.
  99. Lua error in package.lua at line 80: module 'strict' not found.[unreliable source?]
  100. Lua error in package.lua at line 80: module 'strict' not found.
  101. Lua error in package.lua at line 80: module 'strict' not found.
  102. Lua error in package.lua at line 80: module 'strict' not found.
  103. Lua error in package.lua at line 80: module 'strict' not found.
  104. Lua error in package.lua at line 80: module 'strict' not found.
  105. Lua error in package.lua at line 80: module 'strict' not found.
  106. 106.0 106.1 Lua error in package.lua at line 80: module 'strict' not found.

Bibliography

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.

External links