Aircraft Nomenclature (part 1): Russia and China
Table 1 Russian Designer Bureaus Instead of design bureaus, Chinese aircraft designations begin with one or two letters based on the aircraft’s intended purpose, such as ‘J’ for fighter or ‘H’ for bomber. Table 2 depicts the most commonly used Chinese military aircraft letter designations, the Chinese word they represent, and their associated meanings. Combinations of letters are used in some instances, such as the JL-9, a fighter-trainer.
Table 2 Chinese Aircraft Nomenclature The numbering that follows is somewhat inconsequential other than that it generally reflects chronologic prototype development, similar to U.S. practices. Russian and Chinese fighters and fixed-wing ground attack aircraft tend to be odd-numbered (e.g. MiG-19, J-11, Su-25) while bombers, helicopters, and all others are even-numbered (H-6, Mi-24, Il-76). This is not a strict convention, however; numerous exceptions—such as the Su-30, J-10, and Tu-95—buck the even/odd trend. More letters follow the numbers. For Chinese aircraft, the letter suffix reflects subsequent variants of a particular model with ‘A’ being the first modification, or second aircraft variant. So the J-11B, for example, is the third indigenous FLANKER variant China produced—the first was the original J-11 and the second the J-11A. Russian aircraft, on the other hand, feature letters to indicate an aircraft’s specific purpose, or how it has been subsequently modified, with letter assignments being made based on a corresponding Russian word. The letter ‘P’, for example, is taken from the word perekhvatchik, meaning ‘interceptor’, and identifies aircraft such as the obsolete MiG-25P. In fact, the FOXBAT series provides a useful illustration for this discussion as many other variants of the aircraft exist, such as the MiG-25R, MiG-25RBV, and MiG-25RBT reconnaissance models; the MiG-25PU two-seat trainer; the revised MiG-25PD, MiG-25PDS A/A interceptors; and so on. As can be seen, many letter suffix possibilities exist in the FOXBAT series alone, each with a distinct meaning. Table 3 provides a partial list of the many possible letter suffixes for Russian fighter aircraft, the corresponding Russian words, and the English translations. Note that some letters have more than one meaning.
Table 3 Russian Aircraft Naming Suffixes Letter suffixes are also used to designate export variants customized for another country. The Su-30MKI, for example, is a FLANKER modified (‘M’) for export (‘K’) to India (‘I’). Table 4 lists the letters and corresponding export countries for recent Russian aircraft proliferation. The letters are derived from the export country spelling in Russian, not English, and thus may not coincide.
Table 4 Russian Aircraft Naming Country Modifiers Finally, in some instances numbers are used with or in lieu of letter suffixes to identify follow-on modifications, such as the Su-27SM3 / FLANKER J mod. What this all boils down to is indigenous aircraft designators are helpful to understand variants of aircraft but somewhat limited in usefulness due to the complexity. Fortunately, the second part—the NATO codename and variant identifier—is a little more user-friendly, as we will see next.
By convention, NATO reporting names are written in all capital letters in military correspondences. Fortunately for us, early committee members diligently selected a logical threat naming convention that persists to this day. Bombers are assigned a code word beginning with the letter ‘B’, cargo planes ‘C’, fighters ‘F’, and so on. Table 5 lists the most commonly used letters, their meanings, and a real-world example.
Table 5 NATO Codename Conventions Propeller-driven, fixed-wing aircraft are assigned single-syllable codenames (e.g. BEAR, MAY), while jet-powered aircraft are given two-syllable names (CONDOR, FULLBACK, etc.). This tidbit can be particularly useful during recognition training. With this understanding, for example, an observer provided with the accompanying photograph is more likely to correctly identify the aircraft as the Tu-142M / BEAR F then, say, a Tu-22M / BACKFIRE A or Tu-16P / BADGER L based on the propeller engines clearly evident under its wings. The BACKFIRE and BADGER must both be jet-powered because of their two-syllable names.
The syllable convention does not apply to rotary-wing aircraft. The letter following the NATO codename reflects the chronological assignment of subsequent variants within that codename family. ASIC however, assigns a new letter only when a significant airframe modification or increase in capability is observed over the previous variant. Our FOXBAT example from earlier provides a useful illustration: the MiG-25P was the first operational model noted and thus earned the codename FOXBAT A. When the MiG-25R reconnaissance variant was first observed, it was assigned FOXBAT B. Even though the MiG-25RB, MiG-25RBV, MiG-25RBT subsequently debuted with incrementally better reconnaissance and electronic intelligence gear, because of their commonality ASIC assigned them all FOXBAT B designations. The two-seat MiG-25PU trainer, however, was sufficiently different to earn FOXBAT C. Later improved reconnaissance variants were assigned FOXBAT D, and so on.
It is incorrect to mix the NATO letter suffix with the indigenous nomenclature. The MiG-29 / FULCRUM A, for example, should not be referred to as the MiG-29A. Finally, numeric variant identifiers are occasionally used within the intelligence community to distinguish aircraft when multiple variants are assigned the same NATO codename and letter identifier. For example, the Su-30MKK, Su-30MK2, and Su-27UBK and are all assigned the codename FLANKER G. To distinguish between the three aircraft, some documents refer to the Su-27MKK as the FLANKER G v1, the Su-27MK2 as FLANKER G v2, and the Su-27UBK as FLANKER G v3.