Jump to content

Sukhoi Su-33

From Alfawiki
Sukhoi Su-33
Company typeMilitary aircraft
IndustryAerospace
PredecessorSukhoi Su-27
FoundedApril 18, 1984; 42 years ago (1984-04-18)
Headquarters
Komsomolsk-on-Amur
,
Russia
ProductsAll-weather, carrier-capable, twin-engine air superiority fighter aircraft


Template:Good article

Template:Infobox aircraft

The Sukhoi Su-33 (Russian: Сухой Су-33; NATO reporting name: Flanker-D) is a Soviet and Russian all-weather, carrier-capable, twin-engine air superiority fighter developed by Sukhoi and manufactured by the Komsomolsk-on-Amur Aircraft Production Association. It is a derivative of the Sukhoi Su-27 and was initially designated as the Su-27K. In comparison to the Su-27, the Su-33 features reinforced structural components and landing gear, folding wings, and adjustable stabilators tailored for carrier deployment. The design includes canards and larger wing surfaces than the Su-27 to reduce stall speed. Enhancements include upgraded engines, a dual nose wheel configuration, and in-flight refuelling capability.

The aircraft first saw operational use in 1995 aboard the aircraft carrier Admiral Kuznetsov, which is officially classified as a "heavy aircraft-carrying cruiser" due to its extensive surface-to-surface and surface-to-air weaponry and to comply with international treaties restricting passage of traditional aircraft carriers through the Bosporus and Dardanelles straits. The Su-33 formally entered service in August 1998 under its current designation. Following the dissolution of the Soviet Union and subsequent reductions in the Russian Navy, production was limited to only 24 units. Attempts to export the fighter to countries such as China and India were unsuccessful. With plans to phase out the Su-33 upon reaching the end of their operational lifespan, the Russian Navy procured the Mikoyan MiG-29K in 2009 as its successor.

Background and origins

In the 1970s, the Yakovlev Yak-38, which was the sole carrier-based fixed-wing combat aircraft operated by the Soviet Navy at the time, proved inadequate due to its limited operational range and payload capacity. This limitation significantly restricted the effectiveness of the Soviet Navy's Project 1143 vessels. Consequently, plans were made to create a larger and more capable aircraft carrier designed to support STOL aircraft operations. During this evaluation phase, several carrier designs were examined; the Project 1160 carrier, intended to deploy MiG-23s and Su-24s, was ultimately shelved because of financial limitations. Focus then shifted to the Project 1153 carrier concept, which aimed to accommodate Su-25s as well as proposed MiG-23K and Su-27K variants. However, insufficient budget allocations prevented progress, prompting consideration of a fifth and larger iteration of the Project 1143 series, redesigned to support operations of Yak-141, MiG-29K, and Su-27K aircraft.

To facilitate deployment of the Su-27K and competing MiG-29K aboard the new carrier, development advanced on key technologies such as steam catapult systems, arresting gear, and both optical and radio-based landing aids. Pilot training was conducted at a newly established facility in Crimea, called NITKA (Aviation Research and Training Complex). In 1981, as part of a broader reduction in scope for the Project 1143.5 carriers, the Soviet government cancelled the catapult system along with plans for a fifth Project 1143 carrier and the acquisition of the Varyag. Instead, a takeoff ramp was installed at NITKA to simulate carrier launches for Su-27Ks and MiG-29Ks. Both Sukhoi and Mikoyan adapted their prototypes for testing on this ramp; three Sukhoi T10 variants (−3, −24, and −25), plus an Su-27UB, conducted takeoffs from the simulated ramp. The initial test flight was piloted by Nikolai Sadovnikov on 28 August 1982. Flight evaluations revealed that modifications were necessary, leading to redesigning the ramp with a ski-jump profile.

The conceptual phase for the Su-27K began in 1978. On 18 April 1984, directives from the Soviet government assigned Sukhoi to develop an air defense fighter while Mikoyan was tasked with creating a lighter multirole fighter. The full-scale design process for the Su-27K commenced shortly thereafter under the designation "T-10K," led by Konstantin Marbyshev. Nikolai Sadovnikov was named Chief Test Pilot for this project at the design bureau. By November 1984, the conceptual design had successfully passed its critical design review stage, with detailed design work completed by 1986. Two prototypes were built in collaboration with KnAAPO during 1986–1987.

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
A Su-33 preparing for takeoff from the Admiral Kuznetsov in the Barents Sea, during a visit by Russian president Dmitry Medvedev
File:Sukhoi Su-33 on Admiral Kuznetsov-1.jpg
A Su-33 touching down on the Admiral Kuznetsov aircraft carrier

The initial Su-27K prototype, flown by Viktor Pugachyov, conducted its first flight on 17 August 1987 at the NITKA testing site; a second prototype followed on 22 December.[1] Subsequent flight trials took place at NITKA, where both Su-27Ks and MiG-29Ks validated the practicality of ski-jump takeoffs. Pilots also rehearsed no-flare landing techniques prior to executing actual carrier deck landings. It was an additional two years before the vessel Tbilisi, later renamed Admiral Kuznetsov, departed the shipyard.[2][1]

On 1 November 1989, Viktor Pugachyov, flying the second Su-27K, became the first Russian pilot to perform a conventional landing on an aircraft carrier.[2][3] It was discovered that when raised to a 60° angle, the carrier’s jet blast deflectors were positioned too close to the engine nozzles. As a workaround, the deflectors were fixed at a 45° angle. However, if the aircraft remained in front of the deflector for longer than six seconds—the maximum safe duration—the water pipes within the shield would rupture. During one such instance, Pugachyov reduced engine power, inadvertently causing the detents (devices designed to prevent aircraft from moving forward) to disengage and allowing the fighter to advance unexpectedly. The plane was promptly halted; subsequently, Pugachyov executed takeoffs without relying on blast deflectors or detents. Since that time, a Kamov Ka-27PS search-and-rescue helicopter has been deployed near the carrier as a precaution against accidents.[4]

Over the next three weeks, pilots completed 227 sorties and achieved 35 deck landings.[2] Flight evaluations continued thereafter, and on 26 September 1991 naval aviators commenced testing of the Su-27K; by 1994 it had successfully passed State Acceptance Trials.[5] Between 1990 and 1991, seven production models were manufactured.[2]

Further developments

The twin-seat Su-33UB variant, one of two recognized versions of the Su-33, took its inaugural flight in April 1999. Piloted by Viktor Pugachyov and Sergey Melnikov, it remained airborne for approximately 40 minutes near Ramenskoye Airport. Originally designated as Su-27KUB ("Korabelny Uchebno-Boevoy, or "carrier combat trainer"), this model was intended primarily as a trainer but retained versatility for other operational roles.[6] Enhancements compared to the original Su-33 included a redesigned forward fuselage with modified leading edge slats as well as enlarged wings and stabilators.[7]

Modernization

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

In 2010, Sukhoi introduced an enhanced variant of the Su-33, with flight testing commencing in October of the same year. This upgraded model was intended to rival the Chinese-developed Shenyang J-15, which is based on the original Su-33 design, and to stimulate procurement interest from the Russian Navy. Key improvements included the integration of more robust AL-31-F-M1 engines delivering 132 kN (29,800 lbf) of thrust and an expanded weapons load capacity. However, due to budget limitations, enhancements to the radar and armament systems were not feasible at that time. Military analyst Richard Fisher has suggested that subsequent production versions might feature advanced technologies such as phased-array radar, thrust vectoring nozzles, and extended-range anti-ship missile capabilities.

In September 2016, it was revealed that the Su-33 would be equipped with the new SVP-24 sighting and computing system developed by Gefest & T. This upgrade enables the aircraft to deploy unguided bombs with accuracy comparable to precision-guided munitions, effectively enhancing its role as a strike fighter. The SVP-24 system calculates the optimal release trajectory by integrating data including the aircraft’s current position, flight parameters, target information, and environmental conditions. The introduction of this targeting technology is expected to elevate the Su-33’s operational effectiveness to a level approaching that of the Su-30SM.

According to Naval Aviation Chief Major-General Igor Kozhin, the second phase of modernization will involve fitting the Su-33 with more powerful engines and upgraded detection systems.

Design

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 with its arrestor hook visible under the shortened tail "stinger"

To modify the original Su-27 for carrier-based missions, Sukhoi reinforced the airframe and landing gear to endure the intense stresses encountered during landings, especially rapid descents and non-flare touchdowns (where the aircraft does not reduce its descent rate before contact). The leading edge slats, flaperons, and other control surfaces were enlarged to enhance lift and handling at low speeds, while maintaining the same wingspan. The wing design incorporates double-slotted flaps along with outboard drooping ailerons, collectively increasing the wing area by approximately 10–12%. Both wings and stabilators were redesigned to fold, maximizing carrier deck capacity and facilitating aircraft movement onboard. The Su-33 is equipped with more powerful turbofan engines to boost thrust-to-weight ratio, as well as an aerial refueling probe for extended range. Canards were added to reduce takeoff run and improve agility, necessitating reshaping of the leading edge root extensions (LERX). The rear radome was shortened and reshaped to avoid contact with the carrier deck during high angle-of-attack landings.

When compared to its competitor, the MiG-29K, the Su-33 boasts a maximum takeoff weight 50% greater and carries over twice the fuel capacity, enabling it to fly roughly 80% farther at altitude or 33% farther at sea level. Although the MiG-29K can match Su-33’s time on station using external fuel tanks, this compromises its weapons load. The Su-33 can operate at speeds as low as 240 km/h, whereas the MiG-29K requires a minimum of 250 km/h for effective control. However, the MiG-29K carries a larger payload of air-to-ground ordnance. Due to its larger size and higher cost relative to the MiG-29K, fewer Su-33s can be deployed aboard a carrier. Aviation experts Bill Gunston and Yefim Gordon described the decision to favor the Su-33 over the MiG-29K as "astonishing," noting that the Su-33 was more expensive and lacked surface strike missile capability. Some analysts suggest that the MiG-29K was considered only as a fallback option should the Su-33 prove too heavy for carrier operations, reflecting Soviet Navy priorities focused on fleet air defense rather than strike missions.

The Su-33 is armed with guided missiles including four R-73s and six R-27Es mounted on twelve hardpoints, supported by a 150-round 30 mm GSh-30-1 cannon. It can also carry various unguided rockets, bombs, and cluster munitions for secondary air-to-ground roles. Designed for both day and night maritime operations, its "Slot Back" radar is believed to have limited multi-target tracking capabilities, making it reliant on external radar sources such as airborne early warning platforms like the Kamov Ka-31 helicopter. The R-27EM missiles provide anti-missile interception capability. Additionally, its infrared search and track (IRST) system is positioned to enhance downward visibility.

Soviet Union and Russia

A blue and aqua jet on an aircraft carrier deck with a group of men nearby, the ship's island visible in the background
A Su-33 aboard Admiral Kuznetsov in 1996. Sailors from the U.S. Navy's USS San Jacinto are seen visiting the carrier.

Following the dissolution of the Soviet Union, the Russian Navy experienced significant reductions, leading to the cancellation of numerous shipbuilding initiatives. Had projects such as the Varyag, Oryol, and Ulyanovsk come into service, production would have reached 72 airframes; similarly, early warning aircraft and the MiG-29K programs would have continued rather than being discontinued.[5] At the time when Varyag was sold to China, only 24 units had been manufactured.[2]

The Su-27K made its debut in the mid-1990s. Between December 1995 and March 1996, Admiral Kuznetsov operated in the Mediterranean Sea, deploying a complement of two Su-25UTGs, nine Ka-27 helicopters, and thirteen Su-27Ks.[8][1][9] Officially entering service on 31 August 1998 under the designation "Su-33," this variant was first operated by the 279th independent Shipborne Assault Aviation Regiment stationed at Severomorsk-3.[8][10]

In 2009, plans were announced for the Russian Navy to acquire 24 MiG-29Ks aimed at replacing approximately 19 Su-33s then in service, with deliveries scheduled to conclude by 2015.[11] Nevertheless, in 2015, General Major Igor Kozhin, Chief of Naval Aviation, revealed intentions to establish a second fighter regiment to supplement existing forces; this new unit would operate MiG-29Ks while refurbishing the current fleet of 19 Su-33s for extended use.[12][13] By September 2016, at least six Su-33s had been upgraded with SVP-24 targeting systems in preparation for deployment on combat missions in Syria.[14]

In 2017, the United Engine Corporation announced resumption of production for enhanced AL-31F series 3 engines intended for all remaining Su-33 fighters, numbering eighteen. The initial batch was delivered within that same year.[15]

2015 Russian military involvement in Syria

Main article: Russian military intervention in the Syrian Civil War
File:Возвращение палубной авиации с ТАВКР «Адмирал Кузнецов» на аэродром базирования.webm
Russian Naval Aviation pilots returning to Severomorsk-3 air base following operations in Syria

On 15 November 2016, during Russia’s extensive military campaign targeting terrorist factions in Syria, Su-33 aircraft launched from the Admiral Kuznetsov aircraft carrier were deployed in their inaugural combat mission. These jets conducted precision strikes using 500 kg munitions against ISIL and Al-Nusra Front positions located within Syria’s Idlib and Homs regions.Template:Fix/category[citation needed] The operation primarily focused on destroying ammunition depots, assembly and training facilities, as well as weapons manufacturing sites. The Russian Defence Ministry reported that these airstrikes resulted in the elimination of at least 30 militants, including three field commanders.Template:Fix/category[citation needed]

On 5 December 2016, a Su-33 crashed into the Mediterranean Sea after its arrestor cable malfunctioned during a second landing attempt aboard the carrier. The pilot successfully ejected and survived without injury.[16][17]

Unsuccessful export attempts

China was considered a prospective international buyer for the Su-33. Rosoboronexport, Russia’s official arms exporter, had engaged in discussions regarding a potential order of 50 fighters valued at approximately US$2.5 billion.[18] Initially, China planned to procure two units for evaluation at a cost of $100 million, with options to acquire an additional 12 to 48 aircraft thereafter. These fighters were intended to support China’s emerging aircraft carrier program centered around the former Soviet carrier Varyag. [19][20]

During the sixth Zhuhai Airshow held in late 2006, Lieutenant General Aleksander Denisov publicly confirmed that China had approached Russia about acquiring Su-33s and that negotiations were expected to commence in early 2007. On 1 November 2006, China’s Xinhua News Agency announced plans to integrate the Su-33 into its military aviation fleet.[21] Previously, China had secured a license to manufacture the Su-27 domestically.Template:Fix/category[citation needed]

Sukhoi has been developing an enhanced variant named the Su-33K, which incorporates advanced features from the Su-35 fighter into the original Su-33 design.[21] Concerns arose regarding China’s intentions when reports indicated that it had obtained a T-10K prototype of the Su-33 from Ukraine, possibly for reverse engineering purposes aimed at producing a domestic model.[22] Several aircraft are believed to have derived elements from the Su-33 platform, notably the Shenyang J-15.[23][24] Photographs depicting Shenyang designers alongside a T-10K carrier-based fighter prototype strongly imply a direct connection between the J-15 and the T-10K model.[25]Template:Unreliable source? Negotiations stalled as Shenyang sought to minimize Russian components within their aircraft while Sukhoi aimed to maintain revenue streams from future upgrades and modifications related to the J-11.[22]

India was also considered a potential operator of the Su-33. The Indian Navy intended to equip its aircraft carrier INS Vikramaditya, formerly the Soviet Admiral Gorshkov sold in 2004, with this fighter.[26] Ultimately, India selected the MiG-29K instead due to obsolescence concerns regarding the Su-33’s avionics.[7][27][28] The larger dimensions of the Su-33 reportedly raised concerns about operational challenges on India’s carriers—a limitation not shared by the more compact MiG-29K.[29][30]

Variants

Su-27K
A carrier-adapted model of the Su-27 developed specifically for use on Project 1143.5 and Project 1160 carriers, classified by the Soviets as heavy aircraft cruisers.
Su-27KI
A proposed carrier-based Su-27 variant intended for deployment on Project 1143.5 and Project 1153 carriers, also designated as heavy aircraft cruisers in Soviet terms.
Su-27KPP
A conceptual two-seat electronic warfare aircraft designed for carrier operations.
Su-27KRS
A planned two-seat reconnaissance and target designation platform for carrier use.
Su-27KT/Su-27KTZ
A proposed tanker aircraft variant adapted for carrier operations.
Su-27KU
A two-seat trainer version designed to operate from aircraft carriers.
Su-27KSH
A carrier-capable attack aircraft project.
Su-28K
A two-seat attack aircraft concept intended for carrier service.
Su-28KRS
A carrier-based reconnaissance and target designation variant derived from the Su-28K.
Su-29K
A conceptual carrier interceptor capable of deploying long-range R-33 air-to-air missiles.
Su-33
The designation assigned to the Su-27K following its formal induction into Russian Naval Aviation service on 31 August 1998.
Su-27KUB/Su-33UB/Su-33D
A dual-control training and combat version based on the Su-27K and Su-27KU, featuring side-by-side seating for a crew of two. Only one prototype was constructed.

Operators

Template:RUS

Notable accidents

  • 17 July 2001: During an airshow in Russia's Pskov Region, a Russian Navy Su-33 crashed resulting in the death of pilot Major-General Timur Apakidze.
  • 5 September 2005: An incident occurred when a Russian Navy Su-33’s arresting cable failed after landing aboard Admiral Kuznetsov in the Northern Atlantic at high velocity. The pilot successfully ejected and was rescued. Initially, plans were made to destroy the aircraft with depth charges to prevent recovery of classified systems, but this was abandoned as no sensitive equipment was onboard. The event was recorded on video.
  • 3 December 2016: A Su-33 operating from Admiral Kuznetsov crashed during a second landing attempt following a combat mission over Syria. The pilot survived unharmed and was promptly recovered by rescue teams. According to the Russian Ministry of Defence, the crash resulted from a failure of the arresting cable. Subsequently, the Russian Navy relocated the remaining carrier-based aircraft to a Syrian airbase to maintain operations while addressing issues with the carrier.

Aircraft exhibited

Specifications

Template:Aircraft specs

Prominent appearances in popular media

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

Gallery

See also

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

Notes

Citations

  1. ↑ 1.0 1.1 1.2 Cite error: Invalid <ref> tag; no text was provided for refs named Su-33 history
  2. ↑ 2.0 2.1 2.2 2.3 2.4 Williams 2002, p. 129.
  3. ↑ Gordon 1999, p. 80.
  4. ↑ Gordon 1999, p. 66.
  5. ↑ 5.0 5.1 Cite error: Invalid <ref> tag; no text was provided for refs named Eden, p. 462
  6. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  7. ↑ 7.0 7.1 Williams 2002, p. 131.
  8. ↑ 8.0 8.1 Williams 2002, p. 130.
  9. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  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. ↑ 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. ↑ 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. ↑ 21.0 21.1 Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  22. ↑ 22.0 22.1 Fisher 2008, p. 190.
  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. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  27. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  28. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  29. ↑ Conley 2001, p. 69.
  30. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).

Bibliography

  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  • Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).

External links

  • Collection of media related to Sukhoi Su-33 at Wikimedia Commons
  • Official Sukhoi Su-33 page hosted by Sukhoi and the KnAAPO historical aviation museum website
  • Detailed Sukhoi Su-33 information available on milavia.net
  • Comprehensive overview of the Sukhoi Su-33 and Su-33UB Flanker D found on ausairpower.net
  • Informative Sukhoi Su-33 content accessible at aerospaceweb.org
  • Gallery of Sukhoi Su-33 photographs featured on flankers-site.co.uk

Template:Su-27 family Template:Sukhoi aircraft

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