Showing posts with label Su-27. Show all posts
Showing posts with label Su-27. Show all posts

Saturday, October 31, 2009

Polish Strategic Air Defense: A Cold War Case Study

INTRODUCTION

Poland's countryside is dotted with numerous abandoned SAM sites, a lasting legacy of its Cold War role as part of the Warsaw Pact's air defense network. Numerous strategic SAM batteries played key roles in the Cold War, securing the Warsaw Pact's northern border and defending Polish and Soviet military units.

GENERAL LAYOUT

The Polish strategic SAM network operated five different SAM types during the Cold War: the SA-75 Dvina and S-75 Volkhov (SA-2 GUIDELINE), S-125 Neva and S-125M Neva-M (SA-3 GOA), and S-200VE Vega (SA-5 GAMMON). The network was arranged in accordance with both barrier and area air defense concepts, with a contiguous SAM network along the northern coastline and clustered sites inland protecting key areas such as the capital. At first the strategic SAM forces were under the control of the Polish Army, but in 1962 they transitioned to the control of a new service branch, the Air Defense Army. The Polish Army would, however, operate the 2K11 Krug (SA-4 GANEF) and 2K12 Kub (SA-6 GAINFUL) tactical SAM systems.

Engagement ranges of the strategic SAM systems employed by Poland are as follows:

SA-75 Dvina: 34 km
S-75 Volkhov: 43 km
S-125 Neva: 15 km
S-125M Neva-M: 25 km
S-200VE Vega: 240 km

In the imagery contained within this article, SAM systems will be identified as follows: SA-75 sites are marked with yellow triangles and range rings, S-75 series sites are marked with red triangles and range rings, S-125 series sites are marked with blue triangles and light blue range rings, and S-200 series sites are marked with purple triangles and range rings. Soviet SAM sites are identified using the same color scheme but are marked with stars in place of triangles.

BUILDING THROUGH THE YEARS

Poland's strategic SAM network was born in a 1959 government decree determining that air defense units would be equipped with SAM systems. Crew training on the SA-75 Dvina began in 1960, with 26 batteries available by the end of 1963. The decision to obtain the S-75 Volkhov was also made in 1963, with training beginning in 1964. Nine SA-75 units would reequip with the S-75 and twelve new units would form by the end of 1971. In 1968 the S-125 was acquired and crew training initiated, progressing to the S-125M in 1978. Ultimately, 17 S-125 batteries would form, as well as nine S-125M batteries. 8 S-125M batteries would replace older SAM systems, in some cases even the shorter-ranged S-125. Poland's last Cold War strategic SAM acquisition was the S-200VE. Work towards that end began in 1985, with the battery becoming operational in 1987.

The following image depicts the layout of SAM facilities around Poland. It should be noted that not all of these sites were operational at any given time, this image merely illustrates the overall deployment strategies. Note the coastal barrier extending east from the DDR border to Gdansk, and the clustered arrangement of SAM batteries around major cities. Scattered around the nation are red icons denoting Soviet SAM sites, primarily S-125Ms tasked to defend Soviet airfields. Also of note is Bemowo Piskie, in the northeastern sector. This was the facility responsible for training Polish SAM operators and units.
OVERALL COVERAGE

Due to the constant upgrades and expansion present within the Polish strategic SAM network, chronological analysis provides the most convenient method for viewing the network's status and capability at a given point in time. The following images will depict the SAM network as it existed for a given time period, accompanied by a brief analysis where appropriate. Soviet SAM batteries will not be included here as there is no documentation regarding their deployment timelines.

1966: SA-75 deployment had completed, providing the nation's first SAM network. At this point the sites were positioned to defend key locations, being deployed in a quasi-circular pattern around their areas of interest.
1970: S-75 deployment was nearly complete. By this time, the framework for the coastal SAM barrier was in place, and select SA-75 batteries near Gdansk and Warsaw had been upgraded with the newer S-75.
1976: By this time S-75 deployment was completed, and S-125 deployment had begun. The coastal SAM barrier was complete. S-125 batteries were used to supplement the SA-75 and S-125 batteries, providing enhanced low-altitude coverage.
1977: By 1977 a solitary S-75 battery near Skwierzyna had been deactivated. This battery, the sole strategic SAM battery operated by the Polish Army, was reequipped with the 2K11.
1978: By the end of 1978, S-125 deployment was expanded around Katowice, and the first S-125M batteries had entered service. Warsaw S-125 batteries were reequipped with the newer, longer-ranged S-125M.
1984: By this time, S-125 deployments had taken place around Poznan, supplementing the SA-75 batteries already in place.
1986: S-125M deployment had been completed by 1986, with the system replacing select SA-75 and S-75 batteries near Mrzezyno along the northern coastline, Poznan, and Katowice.
1987: The Polish SAM network saw its last Cold War alteration by 1987, with the deployment of the S-200VE near Mrzezyno.
SOVIET FORCES

Soviet SAM units deployed to Poland during the Cold War were established primarily to provide air defense for Soviet troop locations. Most commonly, S-125M batteries were emplaced on or near military airfields occupied by the Soviet military. Identified Soviet air defense deployments included two S-75M batteries and four S-125M batteries.

Soviet air defense deployments and coverage in Poland can be seen in the image below:
Soviet air defense deployments in Poland were apparently far less robust than they were to the west in the German Democratic Republic (GDR). The reason behind this is likely due to the fact that high-performance Su-27 (FLANKER-B) air superiority fighters were based at Soviet-occupied airfields, providing a far more capable air defense asset than any S-75 or S-125 variant. Also, it was likely believed that any attacking force having penetrated through the GDR and Polish SAM and interceptor nets would be more readily dispatched by available air assets.

An apparent S-300PS (SA-10B GRUMBLE) emplacement near Warsaw provides the only indication that the system was considered for deployment to Poland. Given that there is no evidence to suggest that the Polish government has attempted to purchase the system in the past, the likely operator would have been the Soviet military. The site was in use as recently as 2002 by the Polish military, most likely to support EW assets which would be able to take advantage of the raised berms initially constructed to enhance the fields of view of the S-300PS's 5N63S (FLAP LID B) engagement and 36D6 (TIN SHIELD) or 64N6 (BIG BIRD) EW/battle management radar systems.

The Warsaw S-300PS site can be seen in the image below:
CAPABILITIES AND LIMITATIONS

As designed, the Polish strategic SAM network was fairly robust and during later years did provide relatively layered coverage zones where systems were deployed. Consider the following image, depicting SAM deployments and coverage zones circa 1989 of both Polish and Soviet strategic SAM units:
While the network appears at first glance to contain a significant number of open areas, particularly in the southwestern, central, and eastern portions of the nation, the network must be analyzed in the context of the entire Warsaw Pact air defense network. The GDR was likely to serve as the front line of any conflict with NATO, and as such enjoyed a much more contiguous SAM network.

The following image depicts the strategic SAM deployments in the western Warsaw Pact circa 1989:
The majority of the Warsaw Pact's SAM defenses were consolidated in the GDR, and in western Czechoslovakian territories closest to the West German border. Polish airspace was therefore protected by these networks, their presence acting as an external SAM buffer zone. This may in part explain why Poland continued to rely on the older SA-75 Dvina in greater numbers throughout the Cold War; Czechoslovakia and Hungary, for example, had phased the system out by 1989.

The limitations inherent in the Polish strategic SAM network were ultimately the same shared by its allied states: reliance on outdated Soviet weapon systems. The SA-75, S-75, and S-125 were all single-target command-guided systems, able to engage one target per engagement radar and vulnerable to ECM interference with either the engagement radar or missile guidance command link. However, even these limitations should be taken in context; the Warsaw Pact did not see itself fighting a defensive battle for an extended period and as such the limitations of Polish systems deployed well behind the predicted front lines would have been mitigated by Soviet Army advances into the heart of NATO.

Ultimately, Poland's strategic SAM network was well designed to serve its purposes, even if the systems themselves became more susceptible to Western electronic combat systems as the Cold War continued.

THE 90S AND BEYOND

Following the end of the Cold War, the Polish strategic SAM network began to see a number of changes. In 1990, the SA-75 was finally removed from service, with the S-75 following in 2001. Poland has relied almost solely on the S-125 family since 2001, developing a mobile variant dubbed the Neva-SC featuring truck mounted engagement radars and tank mounted launch rails. The only other holdover from the Cold War period is the S-200VE.

CONCLUSION

Poland's strategic SAM network played a critical role for the Warsaw Pact during the Cold War. The coastal SAM barrier guarded against NATO incursion into one of the Warsaw Pact's main resupply and logistical areas, and would have aided in protecting naval units transiting from the Baltic Sea. Although its strength waned following the Cold War, at strength it was a critical component in the Warsaw Pact's overall air defense strategy.

ADDITIONAL DISCUSSION

Feel free to discuss the content of this article at the IMINT & Analysis Forum in the discussion thread found here.

GOOGLE EARTH PLACEMARK DATA

A Google Earth file containing the placemarks and range rings used in the generation of this article can be downloaded here.

SOURCES

-Satellite imagery provided courtesy of Google Earth

SAM range data taken from various editions of Jane's Land-based Air Defence, and from Fakel's Missiles, an unclassified Fakel publication detailing the bureau's missile development.

I have chosen to pretty much ignore unit subordination for this piece, not because the data is unavailable, but because it can be read in much more depth at the following link:

Polish Air Defense, 1959-1985

Friday, February 6, 2009

Historical Imagery in Google Earth

INTRODUCTION

Google Earth 5 was recently released, and incorporates a wealth of new features for the user to exploit. From an analytical standpoint, the most interesting new feature is the ability to view historical imagery of many areas.

EXPLOITING HISTORICAL IMAGERY

Google Earth's new historical imagery feature allows users to examine past imagery that has been overwritten in the main viewer by either more recent or higher resolution imagery. Take Belgrade, for example. When viewed from an Eye Altitude of 50 miles, it can clearly be seen that the city and the surrounding area has been imaged over time, and that a composite mosaic of these images are currently visible to create a more complete image. For those unfamiliar with the term, the Eye Altitude is the height from which the visual vantage point on screen is being viewed. It is located at the bottom right of the image window in the Status Bar. Returning to the example of Belgrade, the historical imagery feature allows users to view the images used to provide the default view of Belgrade as a series of images, with each series building upon the last and adding the next most recent set of imagery to the screen. An excellent overview of how to fully exploit this new feature can be found here. It should be noted that not every piece of imagery visible in Google Earth's default view is available in the historical imagery feature, nor does using this feature limit the on-screen view to only the imagery captured on the date selected.

AN UNEXPECTED BENEFIT

An interesting and useful application of the historical imagery feature is that it will actually bring images into better focus at certain altitudes. To better illustrate this point, a simple exercise has been derived.

1. Open Google Earth, and click the icon to add a placemark. Copy the following coordinates into the Latitude and Longitude boxes: 56°55'57.57"N 40°32'34.96"E This will create a placemark on a mobile ICBM base near Teykovo in Russia.

2. Travel to the new placemark and zoom in so that the Eye Altitude is approximately 2500 feet.

3. Note that the date that the image was captured is August 12, 2007.

4. Under the View menu at the top left of the screen, select Historical Imagery. The Historical Imagery slider will appear along the upper left portion of the image window. The slider is currently set to coincide with the current date, which at the time of writing is 2009. Three blue lines appear in the slider, indicating images which may be selected for viewing of that particular area.

5. Set the slider to coincide with the date at which the image was captured. In this case, this will be the far right blue line. Simply drag the slider to the left until it locks into position at that date.

6. Once the slider is moved to the left from its default position, note that the image appears to have become clearer to a slight degree, helping to further accentuate many of the details. In this example, pay close attention to the three grey rectangular buildings in the center of the compound. Moving the slider to the left results in the detail on the roof of each building to become far more distinct.

As can clearly be seen, employing the historical imagery feature can be seen to provide clearer imagery. The imagery is likely loaded by Google Earth in a slightly less refined format at higher Eye Altitudes in order to facilitate quicker loading times. It should be noted that zooming in closer will result in the fully detailed image being visible, but exploiting this aspect of the historical imagery function does permit clearer images of a broader scale to be examined and saved for further use or analysis. This is exceptionally valuable when examining images containing many small objects such as vehicles or aircraft, or large facilities.

INTERESTING HISTORICAL IMAGES

The following images are examples of historical images captured in Google Earth, dealing with subjects which will be of interest to readers of this site. Examine these images, and then compare them to the default locations in Google Earth to fully comprehend the value of the historical imagery feature.

The first image depicts Bangalore, India, in February of 2007. Note that three LCA prototypes are visible on the tarmac.
The next image illustrates a useful application of the historical imagery feature. An S-300PS battery in Kaliningrad is shown, sited at a location which is mostly obscured by cloud cover in the current default imagery set. As can be seen, the historical imagery feature can be used to depict locations which may not be visible in Google Earth's default data set.
The following image depicts the parking apron at the Kazan aircraft manufacturing plant. Three Tu-160 strategic bombers can be seen. Scanning through the past imagery of this location indicates that various Tu-160s were in and out of Kazan for maintenance.
Next up is another SAM battery, this time an S-300PT battery on the Kola Peninsula. This highlights yet another advantage of having access to historical imagery in Google Earth: the default image of this location is newer, but is of a lesser resolution.
The following image depicts the Russian Navy's Admiral Kuznetsov aircraft carrier moored at sea near Murmansk.
A series of FLANKER fighter jets can be seen on the tarmac of Luliang AB in China in the next image. Currently available imagery shows this location to have been refurbished as a new J-10 operating base; the addition of the historical imagery allows an analyst to track the history of the aircraft types operated here.
The next image depicts a deployed 64N6 battle management radar near Novosibirsk. This image allows analysts to identify the empty position currently visible in the default data set as an unoccupied 64N6 radar position.
The following image depicts the World's Ugliest Aircraft (who else was suprised that the satellite didn't break capturing the image), Boeing's X-32 demonstrator, on the ramp at Palmdale in August of 2003. This highlights one of the past disadvantages of Google Earth: sometimes new imagery removes interesting and unique sights from view. The addition of the historical imagery feature rectifies this problem to a large degree.
A third S-300P series SAM battery is seen in the image below. This is an S-300PMU battery deployed near Beijing. Current imagery shows this site to have been abandoned in the past, but its past operational status allows analysts to investigate Chinese SAM deployment patterns.
The next image is truly fascinating, showing three submarines undergoing various stages of dismantlement at Severodvinsk in Russia. The missile tubes can clearly be seen to have been removed from both the Typhoon SSBN and the Oscar SSGN.
The final example is a truly historical image, from July of 2005. It depicts the Yankee Notch SSGN conversion pierside at Nerpa. This submarine has since been scrapped, and Google Earth's historical imagery feature allows users to view it when it was still in existance, illustrating the characteristic layout of the converted SSBN.
CONCLUSION

The historical imagery feature in Google Earth 5 provides the analyst with a wealth or new data to exploit. It is now possible to conduct a degree of analysis previously available to only those users with access to other sources of imagery. Both trend and temporal analysis can be conducted, allowing the analyst to note changes occuring over time in certain areas. This new feature will certainly bring about a new appreciation for open source imagery and the analytical products which can be derived from its exploitation.

SOURCES

-Satellite imagery provided courtesy of Google Earth

The Google Earth Blog

Thursday, August 9, 2007

FLANKERs In Imagery

INTRODUCTION

The Su-27 (FLANKER) is one of the most famous aircraft to come out of Russia. The result of a Cold-War requirement for an aircraft capable of besting the latest fighter aircraft the West had to offer, Sukhoi's T-10S design represented the pinnacle of Russian aerodynamic achievement in the 20th Century. The Su-27 design eventually spawned numerous variants, including the carrier capable Su-27K (FLANKER-D) and the Su-34 (FULLBACK) strike aircraft.

FLANKERS WORLDWIDE

Su-27s and their offspring are employed by various nations worldwide. This article will provide an overview of all FLANKER users with airframes visible in overhead imagery provided by Google Earth. This is in no way a representation of every Su-27 user, or an accurate representation of true inventories, but rather an analysis of available imagery. As such, known Su-27 operators such as Indonesia and Angola are not covered; this does not suggest that there has been an oversight on the part of the author, but rather that there are no visible Su-27 airframes in these nations.

There are currently 498 FLANKER-family airframes visible in the available imagery. They operate from 29 airbases in 10 nations. Each nation will be detailed in the following format:

NATION (total number of airframes visible)

Airbase
-Location: (coordinates)
-Inventory: (number and type; this field will be repeated for different types visible at a given airfield)

(Imagery highlights; not a visible representation of every FLANKER, but rather interesting or unusual aircraft)

(Image of identified FLANKER bases where more than one location has been identified)

Su-27 family types will be identified using the following designators:

Su-27: denotes Su-27 or Su-27UB, or export versions thereof
Su-30K: denotes Indian Su-30K
Su-30KI: denotes Russian single-seat prototype
Su-30MKI: denotes Indian advanced fighter aircraft
Su-30MKK: denotes Chinese twin-seat strike fighter
Su-33: denotes Russian carrier-based Su-27 derivative
Su-34: denotes Russian strike derivative
Su-35: denotes Russian advanced fighter derivative
J-11: denotes Chinese kit-assembled Su-27SK or UBK
FLANKER: generic designator used to denote an Su-27 or derivative where imagery cannot determine the type; for example, KnAAPO-located Su-27s are denoted as FLANKER as they cannot be identified as Su-27 or Su-27SM aircraft when both types are known to operate at the location

TYPE IDENTIFICATION

Identifying individual types is a detailed process that involves both a knowledge of standard recognition features, and the inventory of the nation being examined. Most FLANKER variants cannot be specifically identified due to the resolution of the imagery available. There are, however, features that are visible that can aid in identifying certain specific types. These features are the configuration of the tail structure which extends aft between the engine nozzles, and the presence or lack of canard foreplanes.

The basic Su-27

A lineup of basic Su-27s can be seen below. Note the lack of canards, and the standard-length tail structure:


The Su-30 and Su-30MKI

Tandem twin-seat FLANKERs such as the Su-27UB and Su-30 are not able to be distinguished using the available imagery. In the case of India, however, all FLANKER-family aircraft are of the tandem twin-seat variety, being either Su-30K or Su-30MKI variants. The two types are distinguishable as the Su-30MKI features visible canard foreplanes.

The following image depicts four Su-30K and one Su-30MKI aircraft visible at Pune AB in India. The arcraft on the north end of the lineup is the Su-30MKI. Note how the starboard canard is visible, as well as its associated shadow on the runway, differentiating this aircraft from the others in the lineup. The white rectangular shapes which appear to cover the port sides of the aircraft are actually markings on the runway.


The Su-33

The Su-33 is identifiable thanks to its shorter tail structure and the presence of canards, as evidenced in the image below. The aircraft on the right is an Su-33, and is also displaying another characteristic of the aircraft which is sometimes visible in overhead imagery: folding wings to permit storage at sea. In contrast, the FLANKER on the left possesses the standard tail structure. Canards make the aircraft either an Su-30MKI or an Su-35, both of which have been trialled at Akhtubinsk where the image was taken.


The Su-34

The Su-34 is easily identifiable. While the altered forward fuselage and side-by-side cockpit layout is not discernable, the tail structure of greatly increased length is readily distinguishable, as can be seen in the following image of three Su-34s parked at Akhtubinsk:


RUSSIA (376)

Akhtubinsk Flight Test Center
-Location: 48°18'24.62"N 46°12'08.80"E
-Inventory: 18 FLANKER, 1 Su-33, 3 Su-34

The following image depicts the primary Sukhoi ramp at Akhtubinsk:


Besovets-Petrozavodsk-15
-Location: 61°53'11.51"N 34°09'21.87"E
-Inventory: 28 Su-27

Chkalovsk
-Location: 54°46'00.03"N 20°23'45.05"E
-Inventory: 24 Su-27

Kilp-Yavr
-Location: 69°05'41.83"N 32°24'04.19"E
-Inventory: 38 Su-27

Komsomolsk-na-Amur
-Location: 50°36'20.98"N 137°04'52.80"E
-Inventory: 64 FLANKER, 1 Su-30KI

The following image depicts the Su-30KI demonstrator at the KnAAPO facility:


Krasnodar
-Location: 45°05'02.94"N 38°56'47.78"E
-Inventory: 18 Su-27

Krymsk
-Location: 44°57'52.14"N 38°00'05.46"E
-Inventory: 47 Su-27

Kubinka
-Location: 55°36'45.74"N 36°39'00.97"E
-Inventory: 15 Su-27, 5 Su-35

The following image depicts 6 Su-27 and 5 Su-35 aircraft in service with the "Russian Knights" aerial demonstration team, based at Kubinka AB:


The following image depicts a "Russian Knights" Su-27 in a probable maintenance area at Kubinka AB:


Kushchevskaya
-Location: 46°32'20.71"N 39°33'04.87"E
-Inventory: 9 Su-27

Lodeynoye Pole
-Location: 60°42'33.90"N 33°34'03.08"E
-Inventory: 28 Su-27

Pushkin
-Location: 59°41'05.32"N 30°20'15.14"E
-Inventory: 24 Su-27

Severomorsk-3
-Location: 68°52'04.55"N 33°43'06.85"E
-Inventory: 10 Su-33

The following image depicts the Su-33 parking apron at Severomorsk-3 AB:


Tsentralnaya Uglovaya
-Location: 43°20'56.01"N 132°03'33.89"E
-Inventory: 30 Su-27

Ussuriysk-Vozdvizhenka
-Location: 43°54'32.00"N 131°55'32.52"E
-Inventory: 10 Su-27

The following image depicts identified FLANKER bases in Western Russia:


The following image depicts identified FLANKER bases in Eastern Russia:


Su-27 airframes are also visible at the following locations inside Russia:

Central Armed Forces Museum
-Location: 55°47'05.76"N 37°37'06.94"E
-Inventory: 1 Su-27

Irkutsk Southeast
-Location: 52°16'16.68"N 104°20'52.98"E
-Inventory: 1 FLANKER

Khodynka Air Museum
-Location: 55°47'16.67"N 37°32'04.73"E
-Inventory: the T10-20 development aircraft

BELARUS (9)

Baranovichi
-Location: 53°05'44.11"N 26°02'51.49"E
-Inventory: 9 Su-27

CHINA (20)

Cangzhou
-Location: 38°24'10.37"N 116°55'51.65"E
-Inventory: 1 Su-30MKK

Dingxin Flight Test Center
-Location: 40°23'58.08"N 99°47'34.81"E
-Inventory: 4 FLANKER

Siuxi
-Location: 21°23'46.28"N 110°11'56.66"E
-Inventory: 1 FLANKER

Wuhu
-Location: 31°23'26.43"N 118°24'35.19"E
-Inventory: 8 Su-30MKK

Zhangjiakao
-Location: 40°44'20.77"N 114°55'52.56"E
-Inventory: 5 J-11

The following image depicts identified FLANKER bases in China:


An Su-27 airframe is also visible at the following location inside China:

Shenyang Aircraft Corporation
-Location: 41°52'11.65"N 123°26'21.81"E
-Inventory: 1 J-11

ERITREA (2)

Asmara International Airport
-Location: 15°17'16.41"N 38°54'28.41"E
-Inventory: 2 Su-27

ETHIOPIA (10)

Debre Zeyt
-Location: 08°42'59.43"N 39°00'21.02"E
-Inventory: 10 Su-27

INDIA (19)

Bareilly
-Location: 28°25'22.37"N 79°26'56.73"E
-Inventory: 10 Su-30K

Pune
-Location: 18°34'55.66"N 73°55'22.05"E
-Inventory: 6 Su-30K, 3 Su-30MKI

KAZAKHSTAN (22)

Taldy-Kurgan
-Location: 45°07'21.15"N 78°26'33.87"E
-Inventory: 22 Su-27

UKRAINE (14)

Zhitomir
-Location: 50°09'30.22"N 28°44'24.34"E
-Inventory: 14 Su-27

UZBEKISTAN (25)

Karshi-Khanabad
-Location: 38°50'01.00"N 65°55'18.57"E
-Inventory: 25 Su-27

VIETNAM (1)

Bien Hoa
-Location: 10°58'31.85"N 106°49'08.29"E
-Inventory: 1 Su-27

SOURCES

-All satellite imagery provided courtesy of Google Earth