Jump to content

Shenyang J-11

From Alfawiki
Shenyang Aircraft Corporation
IndustryAerospace, Defense
Headquarters
Shenyang
,
China
ProductsMilitary aircraft (including J-11 fighter)


Template:Infobox aircraft

The Shenyang J-11 (Chinese: 歼-11; NATO reporting name: Flanker-B+/Flanker-L), also referred to as Yinglong (Template:Lang-zh), represents a fourth-generation twin-engine jet fighter originating from the People's Republic of China. It is a derivative of the Soviet-designed Sukhoi Su-27SK and is produced by the Shenyang Aircraft Corporation (SAC). This aircraft is actively operated by both the People's Liberation Army Air Force (PLAAF) and the People's Liberation Army Naval Air Force (PLANAF).

Initial J-11 Concept

Drawing from lessons learned during the Vietnam War, the PLAAF issued a 1969 requirement for a short takeoff and landing (STOL) light fighter intended to succeed the Shenyang J-6 and Nanchang Q-5. The design submitted by the Shenyang Aircraft Design Institute together with Shenyang Aircraft Factory was designated "J-11"; it bore resemblance to the French Dassault Mirage F1 and was powered by a British Rolls-Royce Spey 512 engine. However, this project was discontinued due to the inability to secure an appropriate engine, while the competing Nanchang J-12 demonstrated more advanced capabilities.[1]

Acquisition of Su-27

Main article: Sukhoi Su-27 § China

China became the initial export client for the Su-27.[2] Following the 1989 Tiananmen Square protests and subsequent Western arms embargo, China sought weaponry from the Soviet Union. It opted for the Su-27 over alternatives like the Mikoyan MiG-29. Throughout the 1990s, three orders were placed, resulting in deliveries of 36 Su-27SKs and 42 Su-27UBKs commencing in 1992 and extending into the early 2000s.[3]

Licensed Production of J-11

In 1996, China and Rosoboronexport formalized a US$1.2 billion contract[4] allowing SAC to manufacture 200 Su-27UBKs under license.[3] The production utilized kits supplied by the Komsomolsk-on-Amur Aircraft Plant (KnAPPO), while critical subsystems such as avionics, radars, and engines were imported directly from Russia without licensed manufacturing.[4] The agreement also barred China from exporting these aircraft.[3] Production commenced in 1997,[4] with initial units completed by December 1998; however, these early aircraft suffered from poor assembly quality, necessitating Russian technical support for reconstruction.[3] By 2000, five units had been assembled, increasing to twenty by 2003. At this stage, production quality improved significantly with incorporation of locally manufactured airframe components. Russia permitted substitution of certain airframe parts, enabling KnAPPO to reduce kit contents.[5] Russia initially resisted China's requests for avionics upgrades but later replaced the outdated N001 pulse-Doppler radar with an enhanced N001V version. Indigenous production of the J-11A variant began in 2000, featuring improved domestic avionics. By 2006, over 105 units of J-11 and J-11A had been produced.[3]

Co-production reportedly ceased around 2004 when development commenced on the J-11B "Flaming Dragon,"[6] a variant incorporating entirely domestic subsystems that contravened the original co-production agreement.[5][7] Despite this, China retained licenses through 2009 for producing Russian aircraft and components, including confidential intellectual property provisions. The initial license did not cover carrier-capable models such as the Sukhoi Su-33 or derivatives like the Shenyang J-15.[8]

By 2015, existing J-11 fighters were fitted with Chinese-developed missile approach warning systems (MAWS). Unofficial reports indicated enhancements including upgraded cockpit displays and fire control systems compatible with R-77 or PL-10 missiles.[9]

J-11B

The J-11B represents a multirole adaptation of the J-11, integrating indigenous Chinese systems. It was developed to reduce reliance on Russian components. In mid-2002, SAC revealed a mockup of the J-11B, and by 2006, three prototypes had been delivered to the PLAAF for evaluation. The two-seat variant, known as the J-11BS, was introduced two years subsequent to the J-11B. By 2011, it was reported that approximately 90% of the J-11B's subsystems and components were domestically designed, with the engine likely constituting a significant portion of the remaining foreign elements. Many of these Chinese-made subsystems are enhanced versions of those originally installed on the Su-27SK.

Subsystems developed in China for the J-11B include the Type 1493 radar, a three-axis data system, power supply units, emergency power sources, braking mechanisms, hydraulic and fuel systems, environmental control units, molecular sieve oxygen generation technology, a digital flight control system, and a glass cockpit. The airframe benefits from weight reduction through increased use of composite materials.

Regarding armaments, the J-11B is compatible with PL-12 and PL-8B air-to-air missiles. The upgraded J-11BG model supports advanced weaponry such as PL-15 and PL-10 missiles.

Engine replacement

By 2004, testing was underway to equip the J-11 with the Shenyang WS-10 engine. Initial evaluations may have commenced as early as 2002; photographic evidence from that year's China International Aviation & Aerospace Exhibition suggests a J-11 fitted with a WS-10 on one side. The development of the WS-10 engine faced significant challenges. Although one regiment transitioned to WS-10-powered J-11Bs in 2007, these aircraft experienced extended grounding periods due to reliability issues. After 2009, improvements in the WS-10A variant allowed it to adequately power the J-11B Block 02 models. By 2014, Jane’s Defence Weekly reported that the J-11B was operationally equipped with WS-10 engines.

Operational history

In March 2011, PLAAF J-11Bs took part in Shaheen 1, a joint military exercise conducted with Pakistan. This marked the inaugural occasion when the PLAAF engaged in "operational" aerial drills on Pakistani soil alongside the Pakistan Air Force.

P-8 interception

File:Chinese Shenyang J-11 from below in August 2014.JPG
A J-11BH armed with two PL-8 and two PL-12 missiles as observed from a P-8.

On 19 August 2014, a J-11B intercepted a U.S. Navy P-8 Poseidon anti-submarine warfare aircraft flying over the South China Sea.

During a press briefing on 22 August 2014, Admiral John Kirby, spokesperson for the U.S. Department of Defense, provided details of the encounter. He stated that the event took place approximately 135 miles (217 km) east of Hainan Island in international airspace. The Chinese fighter made multiple close passes beneath the P-8, with separation distances ranging between 50 and 100 feet. Notably, the J-11B flew perpendicular to the P-8’s nose, positioning its underside toward the aircraft, presumably to display its armament. Subsequently, it maneuvered directly beneath and alongside the P-8, bringing their wingtips within roughly 20 feet of each other before performing a roll over the P-8 at an estimated proximity of 45 feet. Admiral Kirby described these maneuvers as "unprofessional" and "unsafe," emphasizing that they did not align with the type of military-to-military rapport the United States aims to cultivate with China. Following this incident, an official protest was lodged through diplomatic channels. The Pentagon further clarified that such military operations may lawfully occur within another nation's Exclusive Economic Zone as part of exercising navigation and overflight freedoms.

In response, Yang Yujun, spokesperson for the Chinese Ministry of National Defense, rejected U.S. allegations as "completely unfounded," asserting that the Chinese pilot maintained a professional and safe distance throughout. He attributed the incident to frequent and extensive close surveillance by U.S. forces and urged cessation of such reconnaissance flights to foster improved military relations between both countries.

Variants

  • J-11: Su-27UBKs manufactured under license using kits supplied by Russia.[3]
  • J-11A: Produced with increased indigenous components and enhanced avionics and cockpit instrumentation. Some earlier J-11 and J-11A models underwent upgrades to reach comparable specifications.[3]
  • J-11A MLU: Mid-life upgrade initiative for the J-11A, aligning its capabilities with the J-11B model, featuring advanced avionics such as missile approach warning system (MAWS), a fully glass cockpit, and updated radar technology.[10]
  • J-11B (Flanker-L[11][12]): A domestically developed version incorporating indigenous subsystems[5], including the Type 1493 radar and an integrated internal electronic countermeasure (ECM) suite.[3] The Block 02 variant is equipped with Shenyang WS-10 turbofan engines.[13][14]
  • J-11BS (Flanker-L[11]): This is the two-seat variant of the J-11B.[9] By 2012, more than 120 units of both J-11B and J-11BS were operational.[15]
  • J-11BH: Naval adaptation of the J-11B.[16][17] This version was first observed in May 2010.[16][18]
  • J-11BSH: Naval version of the twin-seat J-11BS.[16][17]
  • J-11BG: A variant of the J-11B distinguished by a grey radome, reportedly featuring active electronically scanned array (AESA) radar along with integration of PL-10 and PL-15 missiles. First identified in 2019.[19]
  • J-11BGH: Naval counterpart to the J-11BH incorporating the same enhancements as those found on the J-11BG.[19]
  • J-11D: A variant that did not enter production,[19] characterized by increased use of composite materials, two additional weapon stations, AESA radar, an updated fly-by-wire control system, and WS-10B engines. Three prototypes were constructed during 2015 and 2016. Its avionics suite was later transferred to the Shenyang J-15B.[19]

Accidents and incidents

  • On December 7, 2017, a J-11B aircraft belonging to the Western Theater Command Air Force's 111th Aviation Brigade crashed amid a training operation. The pilot, Captain Huang Peng, lost his life in the accident after reportedly trying to preserve the plane.[20] [21] Following his death, Huang was honored with martyr status.[21]Cite error: The opening <ref> tag is malformed or has a bad name</ref>

Operators

Template:PRC

Specifications (J-11A/J-11)

Template:Aircraft specs

See also

Comparable aircraft

Related lists

References

Citations
  1. ↑ Gordon & Komissarov 2008, p. 92.
  2. ↑ Gordon & Komissarov 2008, p. 104.
  3. ↑ 3.0 3.1 3.2 3.3 3.4 3.5 3.6 3.7 Cite error: Invalid <ref> tag; no text was provided for refs named rupprecht_flanker_story
  4. ↑ 4.0 4.1 4.2 Cite error: Invalid <ref> tag; no text was provided for refs named csp-4_p35
  5. ↑ 5.0 5.1 5.2 Cite error: Invalid <ref> tag; no text was provided for refs named csp-4_p36
  6. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named pd_2009
  7. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named csp-4_p46
  8. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  9. ↑ 9.0 9.1 Cite error: Invalid <ref> tag; no text was provided for refs named Fisher_2015-03-11
  10. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  11. ↑ 11.0 11.1 Cite error: Invalid <ref> tag; no text was provided for refs named IISS_2023
  12. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named oni_navy
  13. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named Rupprecht
  14. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named janes_2014-08-26
  15. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  16. ↑ 16.0 16.1 16.2 Cite error: Invalid <ref> tag; no text was provided for refs named Parsons_2010-05-10
  17. ↑ 17.0 17.1 Cite error: Invalid <ref> tag; no text was provided for refs named Yeo_2015-11-02
  18. ↑ Lua error in Module:Citation/CS1/Configuration at line 2123: attempt to index field '?' (a nil value).
  19. ↑ 19.0 19.1 19.2 19.3 Cite error: Invalid <ref> tag; no text was provided for refs named ras_j11
  20. ↑ 20.0 20.1 Cite error: Invalid <ref> tag; no text was provided for refs named :0
  21. ↑ 21.0 21.1 Cite error: Invalid <ref> tag; no text was provided for refs named xinhau_2017-11-22
  22. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named air force
  23. ↑ Cite error: Invalid <ref> tag; no text was provided for refs named naval air force
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).

External links

Template:Su-27 family Template:AVIC aircraft Template:PRC fighters Template:PLAAF Aircraft Template:Chinese Military Aircraft

Retrieved from "https://www.alfawiki.org/index.php?title=Shenyang_J-11&oldid=75108"