Cyrillic-101 for DCS MiG-29 Pilots - SPO-15 LM Radar Warning Receiver (3/3)

After the first two posts introducing the Cyrillic alphabet and HUD markings, we can now move to the RWR or SPO-15LM, which will give us an opportunity to discuss Russian combat aviation historical developments.

You’ve probably already seen Wags’ walk-through of the SPO-15. It’s a necessary step for anybody getting serious about the MiG-29. That said, as you noticed it yourself now that you are more familiar with the Cyriliic alphabet, recurring confusions are worth clearing up up-front: the SPO uses single-letter codes that are not always what they appear to Western eyes: they are legacy Soviet category flags, not Latin labels.

So no, those signs are not the Greek letter "Pi", nor the numeral "three", nor a simple Latin “H”. The one exception that can be confusing is the Latin "F": it does not belong to the Cyrillic alphabet, and historically it referred to ground-based early-warning (EW) radars, not specifically to NATO “F-series” fighters (F-14/F-15/etc...), a topic we will discuss in detail here.

This "three type symbol" is actually the Cyrillic letter for "Z".

If knowing the origins of the "Beryoza" labelling system is not a mandatory step, you'll see that it will still help you remembering how it classifies threats, even if the logic has disappeared with the arrival of more modern radar systems on the battlefield.

I. “Beryoza”, “Biryuza” and other Soviet/Russian weapon system names

Before diving into the actual meaning of the markings on the SPO-15LM, I thought it would be nice to make a short intro on the weapon system names, in particular because it can cause some confusion in the case of the MiG-29.

If you've read DCS manual for the "legacy" MiG-29, you’ve probably noticed the near-homophony between Берёза (Beryoza), the RWR, and Бирюза (Biryuza), the GCI/data-link system. The two names sound very close, but they refer to entirely different systems, and the distinction will make totally sense if you understand how Soviet avionics were named and organized.

Both Beryoza and Biryuza follow the same Soviet convention: assigning simple, neutral, and often nature-related words to electronic systems, deliberately avoiding functional descriptors. This approach allowed sensitive equipment to be referenced in documentation or spoken over channels without revealing its purpose.

So while Beryoza (the birch) alerts the pilot to enemy radar emissions, Biryuza (turquoise) handles mission data and coordination with ground control. They have no direct relationship and the similarity in sound is purely coincidental.

Soviet engineers avoided purely functional designations for sensitive systems. Instead, they used neutral, non-technical words, often mostly drawn from nature, minerals, colors, or weather, which helped obscure purpose in open documentation while maintaining an internal consistency.

This naming logic is consistent across Soviet-era aircraft. Defensive and electronic warfare systems often took plant or floral names: Beryoza (Birch), Rosa (Rose), Lipa (Linden), Gardeniya (Gardenia). Radars and fire-control systems leaned toward minerals and gemstones: Rubin (Ruby), Sapfir (Sapphire), Topaz, Malachit (Malachite). Datalinks and navigation aids drew from colors and sky tones: Lazur (Azure), Biryuza (Turquoise), Raduga (Rainbow). Weather phenomena and natural forces were also used for optical or sensor systems: Shkval (Squall), Groza (Thunderstorm). Even SAM systems occasionally followed evocative names, like Osa (Wasp).

The continuity of these naming conventions stretches across generations. Early MiG-17 and MiG-21 radars were called Rubin and later Sapfir, while the MiG-23 used Sapfir-23. The Su-15 relied on Taifun radar (Typhoon), and the MiG-25 added Smerch (Tornado). These names provided internal consistency for pilots and ground crews while (somewhat) obscuring the system’s function from foreign observers.

We can note that this tradition continued into modern Russian aircraft. The Su-35 features the L-150-35 “Pastel” RWR and "Khibiny" ECM suite; the Su-57 uses the L402 “Himalayas” electronic warfare architecture.

Khibiny are mountains located in Kola peninsula. And no need to explain Himalayas I suppose...

This approach contrasts with Western conventions, which favor acronyms and functional descriptors (ARL-67, APG-65, RBE-2...). Soviet and Russian engineers prioritized internal clarity for pilots and maintainers, while maintaining secrecy against foreign intelligence. The result is a surprisingly coherent naming vocabulary spanning decades of fighter design, where even modern aircraft like the MiG-35 and Su-57 inherit the same cultural approach.

Understanding this background does not really makes it easier to navigate the SPO-15LM symbology and interpret its letters. But as you'll see just after, if the system’s markings may appear arbitrary to Western pilots, they are rooted in a carefully constructed historical and linguistic framework that spans from the early MiG and Su aircraft to the modern generation.

II. SPO-15LM Letters: Historical Meaning

As you've seen it in Wags' video, the SPO-15LM radar warning receiver uses single-letter codes to classify radar threats. These letters are not random: they carry a historical and doctrinal meaning, inherited from earlier Soviet RWR systems such as the SPO-10. Each letter represents a category of emitter, defined by type, range, and origin, rather than individual emitters. The system was designed for pilots to rapidly assess threat type and priority without needing technical detail.

The vintage SPO-10 RWR was in use on the An-26 transport aircarft.

Historically, the letters corresponded to the following categories, from the most dangerous one (on the left), to the less dangerous one (on the right):

1. П (P): Airborne radar threats, primarily fighter radars. The letter likely derives from Перехватчик (“interceptor”) or Пилотируемый (“piloted aircraft”). These were the first radar types Soviet pilots encountered in air-to-air combat. Examples include F-4 and F-104 radars.

2. З (Z): Long-range SAM radars. From Зенитный (“anti-air”), it covered strategic or medium-to-long-range ground-based threats like the S-75 (SA-2), S-125 (SA-3), or S-200 (SA-5).

3. Х (Kh): Medium-range SAM systems, originally referencing the HAWK system (Хок in Russian). It includes SA-6, SA-11 “Buk,” and other comparable SAMs operating at medium distances.

4. Н (N): Short-range SAMs and AAA radar systems, sometimes historically associated with Nike-Hercules. It indicates radars operating at closer ranges or lower altitudes.

5. F: Ground-based early-warning radars, part of the FPS (Fixed Position System) family. Interestingly, this is the only Latin letter in the SPO-15LM symbology. Contrary to what has been said in Wag's video, it does not originally denote F-series fighter aircraft (F-14, F-15, F-16...). Its purpose was to classify legacy Western EW radar emitters used in Soviet threat libraries.

6. С (S): Airborne early-warning and surveillance radars, such as AWACS platforms (A-50 Mainstay, E-3 Sentry). In Russian, Система DRLO (“DRLO System”) describes these platforms, giving the letter its mnemonic value.

Historically, the letter "F" designated the FPS radars (Fixed Position System), like the FPS-24 here.

The letter logic has persisted remarkably well from the SPO-3 and SPO-10 series through the SPO-15, even as radar libraries grew more complex. Soviet engineers deliberately chose letters that were:

• Visually distinct in Cyrillic: (П, З, Х, Н, F, С) for rapid identification.

• Mnemonic: Z for Zenitnyy (SAM), P for Perekhvatchik (fighter), S for Sistema (AWACS).

• Cross-platform standardized, used on MiG, Sukhoi, and Tu-series aircraft.

Over time, some letters, especially F, have shifted in meaning, as it's now the case within DCS. As said above, while historically F represented ground-based early-warning radars, in DCS it is now applied to 4th-generation fighter radars (F-14, F-15, F-16, F/A-18).

Here is also the time to discuss the origins of the letter "Н" (N) for the Short Range threats and AAA category. If MiG-29 and Su-29 manuals link this letter to the "Nike-Hercule" weapon system, this choice seems rather odd, given the fact that the "Nike-Hercule" was one of the most capable long-range system of its time (140 km). The "N" letter might originally have designed its predecessor, the "Nike-Ajax" (48 km), but such range still classifies it within the medium range systems. The only plausible explanation that I can find is that, historically, the Н letter was referring to systems similar as the SA-3 "Нева" (Neva), with only 15 km range. This system is also sometimes described as "Низковысотный мобильный зенитный ракетный комплекс" or "low-altitude mobile anti-aircraft missile system", which is also consistent with the letter "N"...

Historical signification of the symbols used on SPO-15 radar warning receivers.

III. SPO-15LM Letters in DCS World: a Glimpse Into the Electromagnetic Spectrum Complexity

While the historical foundations of the SPO-15LM's letter-based classification system provide a glimpse into Soviet aviation doctrine, DCS World's modeling of the device adapts these elements to fit the modern EME (ElectroMagnetic Environment) and its simulation's replication. ED has taken a physics-based approach to recreate the SPO-15LM in the MiG-29A module, emphasizing analog hardware limitations, signal processing, and modular threat libraries. This results in a system that honors much of the real-world heritage while introducing adjustments for gameplay, available threats, and available data. Below, we'll explore what's consistent or different with the historical meanings described above.

III.1 - Consistent Elements

Several aspects of the SPO-15LM in DCS align closely with its historical roots, ensuring pilots experience the system's doctrinal intent, i.e. rapid, mnemonic-driven threat assessment without overwhelming detail.

• Letter Symbology and Priority Order: the core Cyrillic (and single Latin) letters—П, З, Х, Н, F, С remain unchanged, displayed left-to-right in descending priority. In DCS, the display behavior is faithful: letters illuminate based on signal detection, with flashing for lock-on or launch, and priority determined by factors like track mode, azimuth-altitude criteria, and PRF (pulse repetition frequency).

• Mnemonic and Categories: certain assignments retain their original meaning. For instance, Х consistently represents continuous-wave (CW) radars, rooted in the "Хок" (Hawk) system, and includes medium-range SAMs like the HAWK CWAR/HiPIR. П often signals high-threat airborne or guidance radars (e.g., F-4 with Sparrow illumination), aligning with its origins in air-to-air combat encounters. The system's analog nature—dividing threats into broad categories based on PW (pulse width) and PRF rather than precise identification is accurately simulated.

• Threat Prioritization and Display Logic: DCS replicates the real SPO-15LM's hardware-driven priorities (as outlined in Table 2 of the manual), such as elevating track-mode emitters or those within azimuth-altitude "rows." Elevation (В/Н lights) and signal power (in 2 dB increments) are estimated similarly, with conservative weapon engagement zone (WEZ) indications for SAM threats. Limitations like sector-independent processing (8 azimuth sectors scanned clockwise) and potential "blinding" from high-power signals echo historical accounts, where the device could be overwhelmed by side lobes or multiple emitters.

III.2 - Differences

Despite these consistencies, DCS introduces notable shifts in letter meanings to accommodate the simulation's diverse assets and modern scenarios. These changes stem from the game's focus on signal parameters over rigid doctrinal categories, leading to reassignments that can feel anachronistic compared to the historical interpretations.

• Reassigned Categories Based on Signal Types:

  • П (P): Historically airborne fighter threats (e.g., F-4 radars), but in DCS, it expands to include naval systems like Aegis ships or SAMs (Talos, Terrier) using low PRF (LPRF) with CW illuminators in semi-active (SA) guidance mode. This treats П as a "launch warning" category, consistent in priority but broader than pure air-to-air.

  • З (Z): it's a major divergence since it described long-range SAMs, and DCS shifts it to AAA/short/medium-range SAM fire control (e.g., Vulcan, Sea Wolf). This inverts the range focus, prioritizing point-defense threats over strategic ones. However, due to the short reaction time they offer, short range threats can be considered as priority threats, hence their second position.

  • F: the most obvious difference. In DCS, it's repurposed for 4th-generation HPRF fighter radars (F-14, F-15, F-16, F/A-18). However, their priority should certainly be higher, especially given their ability to shoot modern Fox-3 missiles at very long ranges.

  • С (S): Historically airborne early-warning (AWACS from "Система ДРЛО"), but DCS broadens it to LPRF radars with disabled CW illuminators, including older fighters (F-4, F-5, Mirage-F1) and naval threats. This makes С a "catch-all" for lower-threat or surveillance radars, diluting its AWACS-specific mnemonic.

Conclusion

After introducing the symbology of the SPO-15LM, it might be worth to discuss quickly the choices made by ED in its replication. I'd say that this modeling is not only relevant, but is also effectively capturing the inherent challenges of radar signal classification in an era of increasingly complex radar systems. Modern radars employ diverse signatures, varying pulse repetition frequencies (PRF), pulse widths, and modulation techniques, making precise identification difficult, especially with analog systems like the SPO-15LM. With only six symbols (П, З, Х, Н, F, С) available, DCS groups threats into broad categories based on signal characteristics rather than strictly adhering to historical meanings. This results in some deviations, such as З shifting from long-range SAMs to short-range AAA or F repurposed for 4th-generation fighters instead of early-warning radars. These choices reflect the real-world limitation of the SPO-15LM’s analog hardware, which struggles to differentiate nuanced signatures, forcing pilots to interpret ambiguous warnings.

Radar characteristics are usually tied to intended use, but overlap frequently, making precise identification sometimes impossible.

The most compelling aspect of DCS’s implementation is its introduction of the electronic warfare (EW) threat library concept through the "stock" (Warsaw Pact-era) and "automatic" (mission-specific) threat programs. The stock mode mirrors historical limitations, where outdated libraries led to misidentifications (e.g., friendly radars mistaken for threats), requiring pilots to rely on tactical judgment and ground-controlled intercept (GCI). The automatic mode, conversely, dynamically assigns threats to match the mission’s radar environment, simulating how modern EW specialists have to adapt ob a daily basis to evolving battlefields. This dichotomy highlights the critical role of threat libraries in today’s combat, where rapid updates to radar databases are vital for distinguishing friend from foe amidst sophisticated, multi-mode emitters. By modeling these constraints, DCS not only preserves the SPO-15LM’s historical essence but also underscores the enduring importance of EW adaptability in modern warfare.

Hopefully, this EW library system may serve as a precursor to greater emphasis on the EW aspect of aerial warfare, with more aircraft benefiting from dynamic threat libraries in the future, and as hinted the introduction of GPS jammers to further enrich the electronic battlefield in DCS.

Are GPS jammers about to come in DCS?