Sukhoi Su-33

Su-33
Russian Navy Sukhoi Su-33
Role Carrier-based air superiority fighter, Multirole fighter
National origin Russia
Design group Sukhoi
Built by Komsomolsk-on-Amur Aircraft Production Association
First flight 17 August 1987[1]
Introduction 31 August 1998 (official)[2]
Status In service
Primary user Russian Navy
Produced 1987–1999
Number built approx. 35
Developed from Sukhoi Su-27

The Sukhoi Su-33 (Russian: Сухой Су-33; NATO reporting name: Flanker-D) is an all-weather carrier-based twin-engine air superiority fighter designed by Sukhoi and manufactured by Komsomolsk-on-Amur Aircraft Production Association. It is a derivative of the Su-27 "Flanker" and was initially known as the Su-27K. First used in operations in 1995 aboard the carrier Admiral Kuznetsov,[N 1] the fighter officially entered service in August 1998, by which time the designation "Su-33" was used. Following the break-up of the Soviet Union and the subsequent downsizing of the Russian Navy, only 24 aircraft were produced. Attempted sales to China and India fell through.

Compared with the Su-27, the Su-33 has a strengthened undercarriage and structure, folding wings and stabilators, all for carrier operations. The wings are larger than on land-based aircraft for increased lift. The Su-33 has upgraded engines and a twin nose wheel, and is air refuelable. In 2009, the Russian Navy ordered the MiG-29K as a replacement for the Su-33.

Development

Background and origins

During the 1970s, the Yakovlev Yak-38, then the Soviet Navy's only operational carrier-based fixed-wing combat aircraft, was found to be unable to undertake its role due to limited range and payload, which severely hampered the capability of the Soviet Navy's Project 1143 carriers. It was decided to develop a bigger and more potent carrier capable of operating STOL aircraft. During the assessment period, a number of carriers were studied; the Project 1160 carrier would have been able to operate the MiG-23s and Su-24s, but was abandoned due to budget constraints. Design efforts were then concentrated on the Project 1153 carrier, which would have accommodated the Su-25s and the proposed MiG-23Ks and Su-27Ks. Sufficient funding was not secured, and the Navy looked at the possibility of a fifth, and larger, Project 1143 carrier, modified to allow for Yak-141, MiG-29K and Su-27K operations.[4][5]

To prepare for the operations of the Su-27K and the rival MiG-29K on-board the new carrier, work proceeded on the development of the steam catapult, arresting gear, optical and radio landing systems. The pilots were trained at a new establishment in Crimea, named NITKA, for Aviation Research and Training Complex.[4][5][6] In 1981, the Soviet government ordered the abandonment of the catapult system as part of an overall downsize of Project 1143.5 carriers, which also included cancelling the fifth Project 1143 carrier and the Varyag. A takeoff ramp was installed at the complex, where takeoffs would be executed to ensure that the Su-27Ks and MiG-29Ks would be able to operate from carriers.[7] Both Sukhoi and Mikoyan modified their prototypes to validate the takeoff ramp. Three Sukhoi T10s (−3, −24 and −25), along with an Su-27UB, were used for takeoffs from the simulated ramp. The first of these tests were undertaken by Nikolai Sadovnikov on 28 August 1982. Flight tests indicated the need for a change in ramp design, and it was modified to a ski-jump profile.[7]

Conceptual designs of the Su-27K commenced in 1978.[4] On 18 April 1984, the Soviet government instructed Sukhoi to develop an air defence fighter; Mikoyan was ordered to build a lighter multirole fighter.[8] Full-scale design of the Su-27K soon started as the "T-10K" under the guidance of Konstantin Marbyshev. Nikolai Sadovnikov was appointed the design bureau's Chief Test Pilot for the programme. By November 1984, conceptual design had passed its critical design review, with the detailed design finalised in 1986. The two prototypes were constructed in conjunction with KnAAPO in 1986–1987.[5]

Testing

Rear port view of aqua-and-white jet aircraft lining up on aircraft carrier's deck, preparing for takeoff. The jet blast deflector is erected behind the aircraft. Three men in bright orange fluorescent tops stand underneath the jet's right wing
Su-33 preparing for take-off on Admiral Kuznetsov, on the Barents Sea, during a visit by Russian President Dmitry Medvedev

The first Su-27K prototype, piloted by Viktor Pugachyov, made its maiden flight on 17 August 1987 at the NITKA facility; the second followed on 22 December.[5] Flight tests continued at NITKA, where Su-27Ks and MiG-29Ks demonstrated and validated the feasibility of ski-jump operations. The pilots also practised no-flare landings before making an actual landing on a carrier deck. It was another two years before the Tbilisi, subsequently renamed Admiral Kuznetsov, left the shipyard.[1][5]

Viktor Pugachyov, piloting the second Su-27K, became the first Russian to conventionally land aboard an aircraft carrier on 1 November 1989.[1][9] It was found that the carrier's jet blast deflectors were too close to the engine nozzles when raised at an angle of 60°; thus an improvised solution held the deflectors at 45°. However, when the aircraft was in front of it for longer than the maximum six seconds, the shield's water pipes exploded. The pilot, Pugachyov, reduced engine throttle, accidentally causing the detents (blocks used to restrain aircraft from accelerating) to retract and the fighter to move forwards. The aircraft was quickly stopped; Pugachyov later took off without the use of blast deflectors or detents. Since then, a Kamov Ka-27PS search-and-rescue helicopter was flown close to the carrier in the event of an accident.[10]

During the following three-week period, 227 sorties were amassed, along with 35 deck landings.[1] Flight testing continued afterwards, and on 26 September 1991, naval pilots began testing the Su-27K; by 1994, it had successfully passed the State Acceptance Trials.[7] During 1990–1991, seven production aircraft were rolled out.[1]

Further developments

The first of two known versions of the Su-33, the twin-seat Su-33UB, made its first flight in April 1999. The aircraft, piloted by Viktor Pugachyov and Sergey Melnikov, flew for 40 minutes near Ramenskoye Airport. The Su-33UB (Initially named as Su-27KUB, "Korabelny Uchebno-Boevo", or "carrier combat trainer") was planned to be a trainer, but with the potential to fill other roles.[11] Notable improvements over the Su-33 included a revised forward fuselage and leading edge slats, bigger wings and stabilators[12]

In 2010, Sukhoi developed an updated version of the Su-33; flight trials began in October 2010.[13][14][15] This modernised Su-33 was to compete with a potential Chinese indigenous version of the original Su-33, and to encourage orders from the Russian Navy.[16] Major upgrades to the aircraft included more powerful (132 kN, 29,800 lbf) AL-31-F-M1 engines and a larger weapons carriage; upgrades to the radar and weapons were not possible at the time due to funding constraints.[17] According to military author Richard Fisher, it has been speculated that further modifications to a new production batch would include a phased-array radar, thrust-vectoring nozzles, and long-range anti-ship missiles.[17]

Design

To adapt the original Su-27 for naval operations, Sukhoi first incorporated a reinforced structure and undercarriage withstand the great stress experienced upon landing, particularly quick descents and non-flare landings (landings where the aircraft does not assume a nose-up attitude prior to touchdown).[18] The leading edge slats, flaperons and other control surfaces are enlarged to provide increased lift and manoeuvrability at low speeds, although the wingspan remains unchanged.[19] The wings feature double-slotted flaps and outboard drooping ailerons; in total, the refinements enlarge the wing area by 10–12%.[18] The wings and stabilators are modified for folding to maximise the number of aircraft the carrier can accommodate and to allow ease of movement on deck.[18] The aircraft is outfitted with more powerful turbofan engines to increase thrust-to-weight ratio, as well as an in-flight refuelling probe.[18] The Su-33 sports canards that shorten the take-off distance and improve manoeuvrability, but have required reshaping of the leading edge root extensions (LERX).[19] The rear radome is shortened and reshaped to prevent its striking the deck during high-Alpha (angle of attack) landings.[20]

Aqua and blue jet aircraft on aircraft carrier deck, with a group of men standing close-by. Behind the jet is the ship's island
A Su-33 onboard Admiral Kuznetsov in 1996. U.S. Navy sailors from the USS San Jacinto are visiting the carrier.[21]

Compared with the rival MiG-29K, the Su-33's maximum takeoff weight (MTOW) is 50% higher; fuel capacity is more than double, allowing it to fly 80% further at altitude (or 33% at sea level). The MiG-29K can spend as much time as the Su-33 on station by using external fuel tanks, but this limits its ordnance capacity.[22] The Su-33 can fly at speeds as low as 240 km/h (149 mph), in comparison the MiG-29K needs to maintain a minimum of 250 km/h (155 mph) for effective control.[18] However, the MiG-29K carries more air-to-ground munitions than the Su-33.[18] The Su-33 is more expensive and physically larger than the MiG-29K, limiting the numbers able to be deployed on an aircraft carrier.[4][N 2]

The Su-33 carries guided missiles such as the R-73 (four) and R-27E (six) on twelve hardpoints, supplemented by the 150-round 30 mm GSh-30-1.[18][25] It can carry an assortment of unguided rockets, bombs and cluster bombs for secondary air-to-ground missions.[18][25] The aircraft can be used in both night and day operations at sea. The radar used, "Slot Back", has been speculated to have poor multi-target tracking, making the Su-33 reliant on other radar platforms and airborne warning and control system (AWACS) aircraft like the Kamov Ka-31 early-warning helicopter.[20] The R-27EM missiles have the capability to intercept anti-ship missiles. The infra-red search and track (IRST) system is placed to provide better downward visibility.[19]

Operational history

Soviet Union and Russia

The Su-27K entered service in the mid-1990s. From December 1995 to March 1996, the Admiral Kuznetsov set sail in the Mediterranean Sea, carrying two Su-25UTGs, nine Ka-27s, and 13 Su-27Ks.[2][5][26] However, the aircraft officially entered service 31 August 1998 with the 279th Naval Fighter Regiment of the Northern Fleet based at Severomorsk-3, by which time it was officially designated the "Su-33".[2] The Russian Navy currently operates 19 Su-33s, however in the long term these need to be replaced.[27]

With the break-up of the Soviet Union, the Russian Navy was dramatically downsized, with many shipbuilding programmes stopped. Had the Varyag, Oryol and Ulyanovsk been commissioned, a total of 72 production airframes would have been built; the early-airborne warning and MiG-29K would also have proceed, instead of being abandoned.[7] Only 24 examples were built at the time Varyag was sold to China.[1] In 2009, the Russian Navy announced an order for 24 MiG-29Ks to replace the Su-33, to be delivered from 2011 to 2015.[27][28] However, in 2015, Major-General Igor Kozhin, the Commander of the Navy's Air and Air Defense Forces, announced that a second fighter regiment would be formed to augment the current force, with the intention that the MiG-29s be used by this new unit, with the existing Su-33s refurbished for further use.[29][30]

Failed bids

Internationally, the People’s Republic of China was identified as a possible export customer. Russia's state weapons exporter, Rosoboronexport, was previously negotiating an order of 50 aircraft totalling US$2.5 billion.[31] China would have initially acquired two aircraft worth $100 million for testing and then have further options to acquire an additional 12–48 aircraft. The fighters were intended to be used with the fledgling Chinese aircraft carrier programme, with the former Soviet carrier Varyag as the centrepiece.[32][33]

Angled rear view of fighter aircraft, with the engines showing prominently. Above the engines are the two uncanted vertical stabilizers; the wings and horizontal stabilizers are folded
Rear/starboard view of Su-33 at MAKS Airshow 2007. Under the shortened tail "stinger" is the arrestor hook

At the sixth Zhuhai Airshow in late 2006, Lieutenant General Aleksander Denisov publicly confirmed at a news conference that China had approached Russia for the possible purchase of Su-33s, and negotiations were to start in 2007. On 1 November 2006, the Xinhua News Agency published the information on its military website that China planned to introduce the Su-33.[34] China had previously obtained a manufacturing license for Su-27 production.[35]

Sukhoi is working on a more advanced version, the Su-33K, a development to integrate the advanced technologies of the Su-35 fighters into the older Su-33 airframe.[34] However, worries over other Chinese intentions emerged when it was reported that China had acquired one of the T-10Ks, an Su-33 prototype, from Ukraine, potentially to study and reverse engineer a domestic version.[36] Various aircraft are alleged to have originated partially from the Su-33, such as the Shenyang J-11B and the Shenyang J-15.[36][37][38][39] Photos of Shenyang aircraft designers posing in front of a T-10K carrier based fighter prototype strongly suggest that the J-15 is directly related to T-10K.[40] Negotiations stagnated as the Shenyang Aircraft company sought to reduce Russian content in the aircraft, while Sukhoi wanted to ensure a level of income from future upgrades and modifications made to the J-11.[36]

India was also viewed as another potential operator of the Su-33. The Indian Navy planned to acquire the Su-33 for its aircraft carrier, the INS Vikramaditya, the refurbished Soviet Admiral Gorshkov, which was sold to India in 2004.[41] In the end, the rival MiG-29K was opted for, because of the Su-33's outdated avionics.[12][42][43] The size of the Su-33 reportedly led to concerns over potential difficulties in operating it off the Indian carriers, a constraint not shared by the smaller MiG-29K.[44][45]

Operators

 Russia
 Algeria

Notable accidents

Specifications

Data from KnAAPO,[49] Sukhoi,[25][50] Airforce-technology.com,[51] Gordon and Davison,[52] Williams[53]

General characteristics

Performance

Armament

See also

Related development
Aircraft of comparable role, configuration and era

Notes

  1. Officially, Admiral Kuznetsov is referred to as a "heavy aircraft-carrying cruiser" due to her heavy surface-to-surface and surface-to-air armament, as well as a way around an international treaty prohibiting aircraft carriers from sailing through the straits of the Bosporus and the Dardanelles.[3]
  2. Aviation authors Bill Gunston and Yefim Gordon characterised the rejection of the MiG-29K for the Su-33 as "astonishing", noting that the Su-33 was more expensive and incapable of launching missiles against surface targets.[23] However, some analysts stated the view that the MiG-29K was only a fall-back option if the Su-33 had proven to be too heavy for carrier operations; and that the Soviet Navy was only interested in fleet air defence, not strike or attack capabilities.[24]

References

  1. 1 2 3 4 5 6 Williams 2002, p. 129.
  2. 1 2 3 Williams 2002, p. 130.
  3. Gordon 1999, pp. 70–71.
  4. 1 2 3 4 Williams 2002, p. 126.
  5. 1 2 3 4 5 6 "Sukhoi Su-33: Historical background". Sukhoi. Retrieved 2 July 2011.
  6. Flight International 1994, p. 16.
  7. 1 2 3 4 Eden 2004, p. 462.
  8. Williams 2002, p. 127.
  9. Gordon 1999, p. 80.
  10. Gordon 1999, p. 66.
  11. Velovich 1999, p. 17.
  12. 1 2 Williams 2002, p. 131.
  13. van Leeuwen, Marcel (7 October 2010). "Sukhoi begins flight trials of modernized Su-33 fighters". Aviationnews.eu. Archived from the original on 23 August 2013. Retrieved 2 July 2011.
  14. "Sukhoi tests upgraded Su-33". Rusnavy.com. 10 May 2010. Retrieved 2 July 2011.
  15. "Russia's Sukhoi begins Su-33 Flanker-D trials". RIA Novosti. 5 October 2010. Retrieved 9 April 2013.
  16. Fisher 2008, pp. 190–191.
  17. 1 2 Fisher 2008, p. 191.
  18. 1 2 3 4 5 6 7 8 Williams 2002, p. 128.
  19. 1 2 3 Kopp, Carlo (November 2004). "Sukhoi Fullback" (PDF). Australian Aviation. Fyshwick, Australian Capital Territory: Phantom Media. pp. 2–7. ISSN 0813-0876. Archived from the original (PDF) on 5 May 2012. Retrieved 3 July 2011.
  20. 1 2 Eden 2004, p. 463.
  21. "U.S. poised to rescue Russian sailors". Washington Times. 11 January 1996. Retrieved 3 July 2011.
  22. Williams 2002, pp. 126, 128.
  23. Gunston & Gordon 1998, p. 254.
  24. Bangash 2008, p. 281.
  25. 1 2 3 "Sukhoi Su-33: Armaments". Sukhoi. Retrieved 4 July 2011.
  26. Flight International 1995, p. 24.
  27. 1 2 Petterson, Trude (25 September 2009). "New fighter jets for Admiral Kuznetsov". Barents Observer. Archived from the original on 25 February 2013. Retrieved 2 July 2011.
  28. "Russian Navy to buy 24 MiG-29K carrier-based fighters". RIA Novosti. 9 October 2009. Retrieved 2 July 2011.
  29. "Russian Navy to Form Second Aircraft Carrier Aviation Regiment with MiG-29K/KUB". navyrecognition.com. 26 August 2015. Retrieved 17 November 2015.
  30. "In 2015 naval aviation to receive more than 20 MiG-29K aircraft". Ministry of Defence of the Russian Federation. Retrieved 17 November 2015.
  31. "Russia to Deliver Su-33 Fighters to China". Kommersant. 23 October 2006. Retrieved 2 July 2011.
  32. "China to Buy Su-33 Carrier-Based Fighters from Russia?". Defense Industry Daily. 25 November 2012. Retrieved 9 April 2013.
  33. Marcus, Jonathan (14 June 2011). "China extending military reach". BBC News. Archived from the original on 23 August 2013. Retrieved 4 July 2011.
  34. 1 2 Chang, Andrei (25 March 2009). "China can't buy Sukhoi fighter jets". United Press International. Retrieved 2 July 2011.
  35. "Russian-Chinese Su-33 fighter deal collapses". RIA Novosti. 10 March 2009. Retrieved 2 July 2011.
  36. 1 2 3 Fisher 2008, p. 190.
  37. "Russia downplays Chinese J-15 fighter capabilities". RIA Novosti. 4 June 2010. Retrieved 9 April 2013.
  38. Govindasamy, Siva (22 July 2010). "FARNBOROUGH: Russia shrugs off Chinese Su-33 copy". Flight Daily News. Archived from the original on 23 August 2013. Retrieved 9 April 2013.
  39. Fulghum, David A. (27 April 2011). "New Chinese Ship-Based Fighter Progresses". Aviation Week. Retrieved 4 July 2011.
  40. "J-15 fighter based on T-10K prototype". 27 September 2011. Retrieved 4 July 2011.
  41. "India owns Admiral Gorshkov: Navy chief". The Times of India. 3 December 2007. Archived from the original on 23 August 2013. Retrieved 3 July 2011.
  42. Velovich 1999, p. 5.
  43. "Indian Navy to induct 4 'lethal' MiG-29K into its fleet". Economic Times. 19 February 2010. Archived from the original on 23 August 2013. Retrieved 3 July 2011.
  44. Conley 2001, p. 69.
  45. Dubey, Ajit K. (19 February 2010). "MiG-29K Fighter Planes Inducted into Navy". Outlook. Archived from the original on 23 August 2013. Retrieved 9 April 2013.
  46. "News in Brief". The Moscow Times. 18 July 2001. Retrieved 26 July 2011.
  47. "World's best naval flanker Su-33 crashed in Northern Atlantic". Pravda. 6 September 2005. Archived from the original on 23 August 2013. Retrieved 26 July 2011.
  48. "Затонувший Су-33 бомбить не будут - он разрушится сам". Lenta.ru. 7 September 2005. Retrieved 11 April 2013.
  49. "Sukhoi Su-33". KnAAPO. Archived from the original on 16 July 2011. Retrieved 2 July 2011.
  50. "Su-33 Aircraft performance". Sukhoi. Retrieved 2 July 2011.
  51. "Su-33 Fighter Aircraft, Russia: Key Facts". Airforce-technology.com. Archived from the original on 28 July 2011. Retrieved 10 July 2011.
  52. 1 2 Gordon & Davison 2006, pp. 92, 95–96.
  53. Williams 2002, p. 138.

Bibliography

  • "Flanker poised for navy go-ahead". Flight International (London: Reed Business Information) 146 (4429): 16. 13–19 July 1994. ISSN 0015-3710. Archived from the original on 23 August 2013. Retrieved 5 July 2011. 
  • "Russian carrier deploys to Adriatic". Flight International (London: Reed Business Information) 148 (4499): 24. 22–28 November 1995. ISSN 0015-3710. Archived from the original on 23 August 2013. Retrieved 3 July 2011. 
  • Bangash, M.Y.H (2009). Shock, Impact and Explosion: Structural Analysis and Design. New York: Springer. ISBN 3-540-77067-4. OCLC 314175998. 
  • Conley, Jerome M (2001). Indo-Russian Military and Nuclear Cooperation: Lessons and Options for U.S. policy in South Asia. Idaho Falls, Indianna: Lexington Books. ISBN 0-7391-0217-6. OCLC 44818532. 
  • Eden, Paul, ed. (2004). The Encyclopedia of Modern Military Aircraft. London: Amber Books. ISBN 1-904687-84-9. OCLC 57452613. 
  • Fisher, Richard D (2008). China's Military Modernization: Building for Regional and Global Reach. Westport, Connecticut: Greenwood Publishing Group. ISBN 0-275-99486-4. OCLC 221153853. 
  • Gordon, Yefim (1999). Sukhoi Su-27 Flanker: Air Superiority Fighter. London: Airlife Publishing. ISBN 1-84037-029-7. OCLC 40588052. 
  • Gordon, Yefim; Davison, Peter (2006). Sukhoi Su-27 Flanker. Warbird Tech 42. North Branch, Minnesota: Specialty Press. ISBN 1-58007-091-4. OCLC 70690625. 
  • Gunston, Bill; Gordon, Yefim (1998). MiG Aircraft since 1937. Annapolis, Maryland: Naval Institute Press. ISBN 1-55750-541-1. OCLC 39646216. 
  • Velovich, Alexander (2–8 June 1999). "Twin-seat naval Flanker flies". Flight International (London: Reed Business Information) 155 (4679): 17. ISSN 0015-3710. Archived from the original on 2 October 2013. Retrieved 2 October 2013. 
  • Velovich, Alexander (13–19 October 1999). "India near to Russian AEW lease". Flight International (London: Reed Business Information) 156 (4698): 5. ISSN 0015-3710. Archived from the original on 2 October 2013. Retrieved 2 October 2013. 
  • Williams, Mel, ed. (2002). "Sukhoi 'Super Flankers'". Superfighters: The Next Generation of Combat Aircraft. Norwalk, Connecticut: AIRtime Publishing. ISBN 1-880588-53-6. OCLC 51213421. 

External links

Wikimedia Commons has media related to Sukhoi Su-33.
This article is issued from Wikipedia - version of the Saturday, February 13, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.