Sunday, August 23, 2009

Update

The Image of the Week will now be done on Monday instead of Friday. Ergo, the one you expected to see last week will be posted...tomorrow! This change is due to a rearranging of my schedule.

Comments...some of the comments I've been getting have been asking questions, or asking for a bit of analysis. These will always be posted to the site, but I won't approve them for publishing until I have the answer or an appropriate reply to post as well. So, if you've posted a comment with some inquiries, and haven't seen it appear yet, that's why. Most other comments are approved for posting right away, unless I reject them as spam.

I'm also working on a piece detailing Chinese laser ASAT facilities, expect that to be the next significant article posted. There will also be a SAM Site Overview posted this week, perhaps today or tomorrow. Much of the credit for this update goes to Tim Brewer for sending along a whole mess of new sites over the past few weeks.

Life seems to be settling down a bit for me here of late, so expect to finally begin to see a return to regularity and a greater deal of articles posted beyond the standard SAM Site Overview and Image of the Week. That's all for now, and as always, feel free to send me any comments or ideas!

Thursday, August 6, 2009

Burmese Nukes?

A few days ago, some news outlets began reporting on Burma's potential nuclear weapons program. I was contacted by Dr. Lewis over at ArmsControlWonk and asked to do some image interpretation of one of the potential sites. Check out what I came up with here.

Thursday, July 9, 2009

Non-Google Earth Imagery Finds

INTRODUCTION

Sometimes, Google Earth, useful as it is, is just not enough. In many cases it is necessary to refer to another imagery source to locate current imagery of a given location, or perhaps imagery of a location not covered in Google Earth. There are many other online browsers which can be consulted, such as Microsoft's Bing Maps (formerly known as Windows Live Local), but many of these sources only focus on the most popular (usually meaning populated) areas. This can leave an analyst quite irritated, especially given the fact that procuring imagery from an external supplier can be a tedious and restrictive process. Not to mention expensive. Fortunately, there is an answer.

TERRA SERVER

Terra Server is an imagery provider, a relatively inexpensive and uncomplicated source of imagery from suppliers such as Digital Globe. And for those of you who have been browsing online imagery for quite some time now, no, Terra Server is not related to the former Microsoft endeavor bearing the same name. By far the best feature of Terra Server is the ability to browse imagery online. This allows any potential purchaser to preview exactly what is being offered, even to the point where images of a given target captured on different dates can be browsed.

Terra Server is not meant to be a free imagery viewing service, and as such the imagery is watermarked and the preview window is not that large (although for a monthly fee you can get a larger, non-watermarked viewer). Even with the aforementioned restrictions to viewing, the "service" provided is bascally free of charge for unlimited use. This makes it very valuable to analysts, especially those on a budget! The value is further emphasized when the volume of imagery available for viewing is examined. Many areas not covered by high-resolution imagery in Google Earth are clearly visible, and many other areas feature very recent imagery captured at various points in 2009. In short, any analyst who has not yet browsed through Terra Server's holdings is missing out on a fantastic resource.

WHAT'S BEEN FOUND

The following placemark file for use in Google Earth depicts the locations of a number of interesting facilities identified through Terra Server's imagery browser: Right click, save as.

There are three folders in the file, as well as three other placemark files. The folders include updates for the Chinese 2nd Artillery file, the SAM Site Overview, and interesting sights at Kapustin Yar.

The other three placemarks depict a Tu-144D on display in Germany, the 53T6 testing grounds at Sary Shagan, and the Voronezh-DM BMEW radar at Armavir.

By clicking on each placemark, a window will open containing a link to the Terra Server imagery depicting these locations. Hopefully this will demonstrate the usefulness of Terra Server's service, as well as providing analysts with insight into some of the facilities identifiable using the Terra Server viewer.

SOURCES

-Placemark locations compiled by browsing Terra Server imagery, or Google Earth historical imagery

Sunday, May 31, 2009

Just a quick note...

I went back tonight and recounted (yes, seriously) all of the sites in the SAM Site Overview file. Some of the numbers in the folders for the various inventories were a little off, but they are all now 100% accurate insofar as the number of placemarks are concerned. I reuploaded the new file (nothing new added yet as far as content is concerned), so if you download it you should notice the changes in some places. I also edited the SAM Site Overview post, the total figure is now well over 4,000 as I also account for low-resolution sites in that number. I figured why not, I already included the historical sites in the total, and this would push it over 4,000!

Basically, I wanted to clean up the SAM Site Overview file before I went through adding all of the SHORAD data, that'll be done and uploaded within the next week. I'll also be editing a few more inventory figures for accuracy; the Baltic states, for example, show active S-200 (SA-5 GAMMON) batteries, when we know they are not used anymore. They show as active because they aren't yet visible in high-resolution coverage, and that's the way I was handling S-200 batteries when I started this a while back, but there's no sense to leaving them wrong. So, that'll be repaired by the time the next update is posted. I'm also contemplating shifting a lot more data into the Historical Sites folder, but that may or may not happen to any significant degree. Basically I'm trying to decide what nation's out-of-service types should potentially have their sites relocated inside the file. The problem is that a lot of FSU states re-use SAM sites for newer systems, so they might actually become active in the future. I'll figure it out.

If anybody has any comments, or wants to throw an idea out there to make the SAM Site Overview file easier or more interesting, drop on by the forum and let me know here.

Saturday, May 30, 2009

Nuclear Korea

INTRODUCTION

On the 25th of May, 2009, the Democratic People's Republic of Korea (DPRK) conducted its second nuclear weapons test. Once again, the DPRK has become an area of focus for intelligence analysts and politicians as the next course of action for the West is determined. While it remains to be seen whether or not tensions between the DPRK, its southern neighbor, and the rest of the world will be mitigated, one fact remains: the DPRK is developing a nuclear arsenal.

NUCLEAR TESTING

The DPRK has detonated two nuclear devices in the past three years. The first test took place in October of 2006, with the second taking place in May of 2009. Seismic monitoring has provided analysts with a general location of both test events, along with a rough determination of the yield of both tests. The first test seems to have been a sub-kiloton event, with the second test falling in the 1-3 kiloton range. The test location is roughly 65 kilometers northwest of the Musudan-Ri missile test complex, in the isolated northeastern sector of the DPRK.

THE TEST SITE

The DPRK's nuclear test site consists of multiple areas. The isolated location is ideal for this type of testing; there is no civillian presence to speak of, and the terrain allows for UGFs to be employed at will to protect and mask sensitive activity. The bulk of the test area consists of three likely test locations, five unidentified locations, and a rail transfer point located south of Sumunnae, representing the only significant source of transportation into the area.

The locations of the identified facilities and areas in the DPRK's nuclear test area can be seen in the image below. Unidentified facilities are marked as red buildings.
Two of the possible test locations are similar, with the third site being of a wholly different configuration. Of the two similar sites, the northern site is commonly associated with the DPRK's nuclear testing. Whether this is due to intelligence sources leaking information or due to imagery interpretation, it is interesting to note that the southern site has escaped mention, as has the central site. Moreover, Globalsecurity offers before and after imagery of the northern site captured at the time of the 2006 nuclear test. While the imagery is not the highest quality, it should be pointed out that there does not appear to be any significant difference or change in activity at the northern site in either image. This begs the question: was this the actual site of the October 2006 test?

After the 2009 test event, the CTBTO provided coordinate data for the presumed test events of 2006 and 2009, along with probability ellipses indicating the area around the theorized detonation sites where the event was likely located. All three of the identified facilities in the test area fall within the boundaries of both the 2006 and 2009 probability ellipses.

While there is no firm evidence to suggest which site was the "host" to which event, some conclusions may be drawn. It is likely that at least one event took place at the northern site, given that all of the coordinates released by various agencies such as the USGS and the CTBTO for the epicenters of the 2006 and 2009 events are arrayed roughly in an east-west line just north of the northern site. This suggests that at least one, and perhaps both, of the test events took place at the northern site. The central site is not as expansive as the other facilities, and features an antenna farm of some sort, suggesting that it may represent a monitoring station for the two other facilities. The devices seen mounted atop the masts to the north of the facility may be atmospheric sampling devices meant to track the unintended release of radiation from the underground tests.

Details of the northern, central, and southern sites can be seen in the images below. The first image depicts the north site. A possible security checkpoint for entry into the test area can be seen, as well as the likely location of the test shaft itself.
Next, the central site can be seen. This site contains fewer structures than the north or south sites. In fact, the facilities on the western edge of the main area appear to possibly be in disrepair, suggesting that this may have been an existing facility partially converted to use for monitoring the nuclear testing grounds. To the north, the possible sensor masts can clearly be seen.
Finally, the southern site is depicted. Notice the similar layout to the northern site, with the buildings in the main area of the facility organized in a general "U" shape. There is also a possible security checkpoint, and a facility which may be housing the opening to the vertical test shaft. More likely, however, would be positioning the entrance to a vertical or horizontal shaft inside the main facility itself, given that it is situated in a valley between two ridges.
The remaining four unidentified facilities in the area likely perform administrative and support functions for the test range. One such facility, seen in the image below, contains a helipad and apparent housing structures.
The three remaining facilities may be abandoned or unoccupied military garrisons (the site was imaged in February of 2005), or further housing and support areas for nuclear technicians manning the site during a test cycle. The lack of activity at these locations in the available imagery suggests that the site may only be manned during a test period, and also raises a significant question: where did the bomb come from?

There are numerous UGFs in the area, a helipad, and a rail transfer point to the south. This suggests that range security and transport may be supported by helicopter, and that significant amounts of material and personnel arrive by rail, perhaps after arriving in the region by air. The UGFs and various unidentified facilities are the dark horses of the facility. It is possible that the components were delivered individually and then assembled on-site for a test. It is also possible that there is a nuclear weapons plant buried within one of the UGFs producing the weapons after nuclear material is delivered. A final option, one which has no real supporting evidence but which should nevertheless be considered, is that there is a facility in the region, likely inside of an UGF, that produces both the fissile material and the weapons. Enrichment facilities at Yongbyon would seem to refute this idea, but it does make for an interesting theory: while the world is distracted by the goings-on at Yongbyon, the DPRK quietly produces and tests nuclear weapons at a much more remote and lesser-known facility.

NUCLEAR GOALS

Many analysts have assumed that the DPRK is working towards a nuclear capability and has not as of yet fielded a weaponized bomb. There are two holes in this logic which should be pointed out immediately. Bear in mind that this is speculation, and should not necessarily be taken as pure fact, but rather a logical line of thought given the information at hand.

Firstly, a small detonation is a small detonation, not necessarily a fizzle or test failure. Current estimates indicate that the 2009 event was the result of a device no larger than three kilotons detonating underground. Rather than assuming that this is a step towards a multi-kiloton, or even megaton class nuclear or thermonuclear device, the possibility that the test was a complete success and the weapon performed as designed should not be overlooked. For that matter, the previous test in 2006 may have been a complete success as well, either testing a small-scale nuclear device or validating the performance of the components to be used for a later test.

With regard to the possibility of a small-scale nuclear weapon having been developed successfully, it is known that an armed conflict on the peninsula would result in the DPRK employing a large number of special operations forces. Small devices would be ideal weapons to smuggle into the Repiblic of Korea and detonate in advantageous locations. A small device detonating on the Han river in Seoul, for example, would not only destroy many of the bridges crossing the river, but would likely incite a mass panic, without obliterating a sizeable portion of the city itself. The resulting exodus of civillians, seeking shelter from future attacks or medical care for exposure to radiation, has the potential to interfere with the movement and resupply of military forces in the region. Small warheads would also be ideal for delivery by submarine or missile to targets such as air bases close to the coastline, and could be detonated inside the major port facilities to further complicate the ROK's resupply and civillian evacuation operations. From an asymmetric aspect, they could also be used after an outbreak of hostilities to environmentally cripple fishing grounds in the area which are important for both the ROK and Japan.

The second of the aforementioned holes in logic is that current analysis seems to be focusing on a nuclear-armed ballistic missile representing the end result of the DPRK's nuclear weapons program. As demonstrated previously, this may not necessarily be the case. The standard explanation given is that the DPRK has designs on fielding a nuclear-armed ICBM capable of striking the United States. Testing a weapon and miniaturizing the warhead to fit atop an ICBM takes time. However, this assumes that the second test was another trial, and does not allow for the possibility that the device which detonated was a weapons-ready device. If that were to be the case, then it would be likely that the intended delivery vehicle is not in fact an ICBM.

If DPRK nuclear warheads do not progress much further in yield, they will not have much value atop the nations's largely inaccurate ballistic missiles over intercontinental ranges. This would make aerial delivery or delivery by other means far more likely as they can impart a greater degree of accuracy. Where the weapons would be valuable in terms of missile delivery would be as "terror weapons" meant to be fired at the ROK or Japan. In this capacity the accuracy of the delivery systems would be less important given the large metropolitan and industrial areas in each nation which would be far easier to target. Also, firing a small yield weapon into the ROK to cause panic among the populace as described previously would not result in a release of radiation on the scale found in detonating a much larger weapon. That would almost make it more logical for the DPRK to pursue smaller yield weapons as they could then be employed in select areas without causing a significant degree of ill effects for the DPRK's own military forces to contend with. Alternatively these small weapons could be deployed in artillery shells or battlefield rockets to pulverize US and ROK positions along the DMZ before an advance into the ROK.

However, a limited number of nuclear warheads, large or small yield, are still not logically destined to be fitted to ballistic missiles targeting facilities in or outside the Korean theater. The DPRK's leaders may be paranoid and misguided, but they are not stupid. The United States is fielding numerous ballistic-missile defense systems and has multiple PAC-3 batteries in theater. Japan is also fielding the PAC-3, and the ROK is beginning to field the Patriot system as well, albeit in the PAC-2 form. AEGIS ABM-tasked vessels could also be placed in-theater if needed. This would make relying on ballistic missiles as the delivery system for nuclear warheads a questionable proposition as there is no guarantee that the nuclear-armed missiles would reach their targets. That is not an acceptable proposition for such an important national asset, of which there would only be a limited quantity. In that respect, the asymmetric, naval, or airborne delivery methods begin to seem far more plausible, and more logical from the standpoint of the DPRK. Airborne delivery would not necessarily require any miniaturization of a weapon, making it seem like a decent enough solution, but many of the same air defenses which would be used to intercept ballistic missiles would also be able to target hostile aircraft in conjunction with allied fighters, making airborne delivery a dubious proposition as well. At the end of the day, unless a large number of warheads are fielded to mount atop ballistic missiles and the loss of a percentage is accepted, the most likely uses would seem to be naval or asymmetric.

There is still value to testing a nuclear-capable ballistic missile, even if a large scale deployment is not planned. This would force the US, the ROK, and Japan to divert more attention and resources to missile defense, potentially at the expense of other forces in-theater. Ergo, small-yield weapons testing and ballistic missile trials may not indicate that the DPRK is intending to operationally mate missiles and warheads to a significant degree.

FUTURE EFFORTS

The next question that must be answered is the future direction of the DPRK's nuclear weapons program. It will be important to study the results of any future nuclear test events to answer some of these questions.

Further tests resulting in a yield in the same range seen in the 2009 test will indicate that this is likely the design yield of the weapon. Contrarily, testing of weapons with increasing yield will indicate that the DPRK has its sights set on large yield weapons, and perhaps on thermonuclear weapons. Future nuclear test events will also aid analysts in determining the potential uses for such a weapon. Large yield weapons would have the ability to strike hardened facilities using less-accurate delivery systems, but small yield weapons would have to be accurately delivered and may only have limited use until a time when the DPRK has fielded a ballistic missile with hard-target kill levels of accuracy. Also, an expanded test program with shorter intervals between events will likely indicate that the DPRK has neared deployment of an operational weapon. However, a lack of test events does not necessarily indicate that weapons are not being deployed; if, as theorized previously, the current test met the DPRK's goals, then future testing may not be required until such a time when a larger yield weapon is desired.

Missile testing and training operations will also provide insight into whether nuclear warheads are being developed or deployed. Chemical or biological weapons are more likely to be used given their comparative cheapness and the belief that the DPRK maintains a large stockpile of one or both of those weapons. As long as CBW handling operations are detected in missile units without a significant change in procedure, it can be assessed with a degree of accuracy that nuclear weapons are not present.

A final option to consider for the future is another weapon system that has been rendered partially ineffective by recent defensive systems testing by the West: a FOBS. The DPRK's continued efforts to develop the Taepo-dong 2 SLV/ICBM is potentially indicative of a desire to have a space launch capability. After the most recent test the DPRK declared that a satellite had been orbited, a point which Western analysts dispute. Nevertheless, as a nuclear-tipped TD-2 is a paper threat until the DPRK produces a warhead of significant size to overcome the inherent inaccuracy of the delivery vehicle and develops penetration aids to defeat any American ABM systems, if a satellite launch capability can be developed and demonstrated, a FOBS would be an interesting avenue to pursue.

CONCLUSION

It can be stated with certainty that the DPRK is developing a nuclear weapons capability. How far along the program is, how many weapons may be available, and the intended and actual yields of the developed systems are up for debate. But at the end of the day, it would seem that the world is going to have to make room for another member of the Nuclear Club. How the West approaches and deals with the DPRK will have a significant impact on other nations wishing to acquire the same capability, providing them with an idea of how far the West will go to get its way. In this light, the DPRK's nuclear program, should it reach operational status, may be an impetus for Iran to fully develop a similar capability. And as a final note, the effect of a nuclear DPRK in the Korean theater may have much more ominous implications; could this be the final straw which forces Japan to shake off its self-imposed shackles and become a nuclear and offensive power in its own right?

ADDITIONAL DISCUSSION

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

SOURCES

-Satellite imagery provided courtesy of Google Earth

HYDESim
CTBTO on the DPRK's Nuclear Tests
The ROK's Patriots
DPRK Nuke Test
ISIS Online

Friday, May 29, 2009

Brief Update

Right now I'm finishing up a piece on North Korea's nuclear testing ground. That one will be up today or tomorrow. In other site news, I've added a few more links to the Recommended Websites and Recommended Blogs sections on the right. Eric Palmer's ELP Defens(c)e Blog has replaced his old two blogs, and I've added Andreas Perbo's Verification, Implementation and Compliance blog. I'm not sure how I managed to forget about adding that one, sorry Andreas! I also added a link to the new Intelligence Magazine website. I'll be starting to author some content for that site in the near future, articles will be mentioned here with a link to their page at Intelligence Magazine. That's about it for now, time to finish up the Nork Nuke piece (Norke?).

And yeah, before anyone asks, updates to old articles are still being worked on, and SHORAD systems are still being categorized for the SAM Site Overview file. A lot of that stuff might have gotten finished this week, but then the Norks went all nuclear on us on Monday.

Friday, May 15, 2009

Decoding Codenames

INTRODUCTION

Western intelligence organizations began applying codenames to Soviet military equipment shortly after the Second World War. Codenames were a convenient way to describe military equipment when the native designators were often unknown. Eventually, two naming systems became the standard for Western military use. The US DoD assigned a series of alphanumeric designators to missile systems, and the five-nation Air Standards Coordinating Committee (ASCC, ASIC as of 2005) assigned a codename to various military systems and weapons.

THE DOD SYSTEM

The DoD system assigns identifiers to missiles using an alphanumeric format. The two-letter prefix denotes the missile type, and the numeral following denotes the specific system in that prefix series. For example, AA-8 is the 8th air-to-air missile assigned a designator. Missiles are categorized using the following prefixes:

AA-air to air missile
AS-air to surface missile
AT-anti tank missile
SA-surface to air missile system
SL-space launch vehicle
SS-surface to surface missile
SSC-surface to surface missile for coastal defense (an anti-ship weapon)

Other identifiers have been employed, but those listed above are the most common.

Using the information above, a lot of information can be inferred by examining an identifier. It can be inferred, for example, that the SA-20 is likely a newer system than the SA-10.

Two additional letters can be used before the numerical identifier to describe a system. These are N, denoting a naval system, and X, denoting an experimental system. In the case of the former, these are assigned separate categories. SA-N- and SS-N- prefixes denote naval SAMs and SSMs, respectively. These series are separate from the SA- and SS- series. In other words, the SA-N-4 does not represent a naval variant of the SA-4. In fact, until recently naval SAMs were assigned different numerical designators than land-based counterparts. The naval SA-10 was the SA-N-6. This is because designators are believed ot be assigned chronologically. The first naval SAM system, therefore, was the SA-N-1, even though it was a navalized SA-3. The X designator can be used with naval systems, and in this case it is employed as follows: SA-NX-20. This denotes an experimental naval SAM system, being the 20th naval SAM system identified.

Missiles which are for test purposes are not assigned designators. Only weapon systems believed to be undergoing trials for service are given designators, and they typically possess the X prefix denoting their experimental status. When the weapon enters service, the X is no longer used with that system.

Suffixes applied after the numeric designator are used to denote different variants of that system. For example, there are six in-service variants of the AA-10, and these are referred to as AA-10A through AA-10F.

THE ASCC/ASIC SYSTEM

The ASCC system assignes codenames to various pieces of military hardware. They are usually categorized by the first letter of their codename. Various suffixes are employed to denote different modifications or versions of the system. Systems are categorized into groupings using the following first letters:

A-air to air missile
B-bomber
C-cargo aircraft or airliner
F-fighter aircraft
G-surface to air missile/ABM
H-helicopter
K-air to surface missile
M-miscellaneous aircraft (trainers, AEW&C, tankers, etc)
S-surface to surface missile

It is important to note that in the case of missiles, the codename refers to the missile itself, not the entire system. This becomes important when combining DoD and ASCC/ASIC designators to describe a system.

When dealing with aircraft, single syllable words denote propeller driven aircraft, while jet powered aircraft have two syllable codenames. For example, the Tu-95 has the codename BEAR, while the Tu-160 has the codename BLACKJACK.

Suffixes do not appear to follow a specific rule, but rather a set of loose rules. Firstly, the letters I and O are not used, to avoid confusion with the numbers 1 and 0. Modified variants can be denoted using the suffix Mod., followed by a numeral indicating which modification is being identified. This is commonly used for SAMs and SSMs. For example, GRUMBLE mod 1 refers to the 5V55R missile, while GRUMBLE mod 0 is the earlier 5V55K. Aircraft typically employ an alphabetical suffix to denote which variant of the airfract is being referred to. The Su-27 series is an excellent example. FLANKER-A refers to the original T-10 prototype series, while FLANKER-B refers to the T-10S series production model. Further examples include FLANKER-G for the Su-30MKK series, or FLANKER-H for the Su-30MKI series. Different variations of a subvariant are denoted by adding Variant to the codename, followed by a sequential numerical designator to note the variation. The FLANKER provides another example here, in the form of the Su-27M and Su-37. The former was designated FLANKER-E Variant 1, while the latter was designated FLANKER-E Variant 2.

The ASCC/ASIC system is different from the DoD system insofar as it often assigns codenames to anything identified regardless of whether or not it is predicted to be used operationally. For example, both the MiG-AT and Yak-130 received codenames, even though it was widely assumed that only one would be purchased for the Russian Air Force.

The ASCC/ASIC system also assignes two-word codenames to radar systems (airborne, ground-based, and naval), such as TOMB STONE, although these do not appear to follow any sort of naming convention. In some cases, such as SPOON REST or CLAM SHELL, the codenames are an amusing play on the visual appearance of the radar array.

COMBINING DESIGNATORS

As mentioned previously, US DoD and ASCC/ASIC designators can be combined to describe a given system. Consider the example of the S-300P series. Being a SAM system, it has a DoD designator prefixed with SA and an ASCC/ASIC codename starting with G: SA-10 GRUMBLE. Employing the proper suffixes can provide a detailed description of the system. A SAM battery described as employing SA-10B GRUMBLE Mod 0 systems can therefore be known to possess mobile components (SA-10B refers to the S-300PS or S-300PMU) equipped with the 5V55K missile. Ergo, the system is not operating to the limit of its capability, as the 5V55K is shorter-ranged and uses a simpler guidance method than the 5V55R or 5V55RD.

COMMON ERRORS

There are numerous errors in the way that these designators are referred and employed by analysts, journalists, and authors. First and foremost, ASCC and DoD codemanes are often used by NATO forces, and have erroneously been referred to as "NATO names". This is not the case; NATO did not devise these designators, the US DoD and/or the ASCC/ASIC did. Secondly, codenames are often not properly formatted. Codenames should be written in all capitals. Returning to the Su-27, the commonly seen printed name is Flanker rather than the correct FLANKER. Thirdly, correct codenames are often misused. Many sources refer to the 64N6 as TOMB STONE, when this is in fact BIG BIRD, for example. Other sources confuse the same issue altogether, referring to the guidance radar as "64N6 Tomb Stone". Correct codename, wrong radar system, and improperly formatted.

CONCLUSION

This is not intended as an all-inclusive lesson on Western codenames, but rather an introduction to how they are devised and employed. Understanding the systems in place aids an analyst who is not fully versed on Soviet/Russian system names (many Chinese or Warsaw Pact systems such as the JH-7 and L-29 have also been named using these systems as well), and also will aid in properly employing them.

FURTHER READING

For a comprehensive listing of known codenames and further explanation of other DoD and ASCC/ASIC sequences, Andreas Parsch has done a very good job here.