Air Defense

5P85D TEL

Also known as
  • 5P85D
  • 5П85Д
  • 5P85D launcher
  • 5P85D transporter erector launcher
  • 5P85D S-300PS
  • S-300PS 5P85D
  • SA-10B 5P85D

The 5P85D is a Soviet road-mobile transporter-erector-launcher associated with S-300PS and early S-300PMU air-defense batteries. It is the additional slave launcher in a 5P85SD launcher group, normally controlled by a 5P85S master TEL, carries four S-300 missile canisters on a MAZ-543M-family 8x8 chassis, and has been separately identified in Ukrainian and Armenian/Artsakh visual-loss records.

5P85D TEL, S-300PS slave transporter-erector-launcher, Air Defense
Image source: S-300 launcher, 2009.jpg

Role in Conflicts

Profile / Specs

Profile

Origin
Soviet Union
Type
S-300PS slave transporter-erector-launcher
Service note
Cold War S-300PS component documented in post-Soviet conflicts
Designer
KBSM / Special Machine-Building Design Bureau launcher work; Almaz Central Design Bureau parent S-300P system
Designed
Introduced with the S-300PS generation in the mid-1980s
Produced
Associated with S-300PS / early S-300PMU production and service
Developed from
S-300P / S-300PS launcher family

Specifications

Role
Additional slave transporter-erector-launcher for S-300PS / early S-300PMU fire units
Launcher load
Four missile canisters, one missile per canister
Missile family
5V55R in S-300PS technical references; Army Recognition also names 5V55KD
Launcher group
One 5P85S master launcher plus up to two 5P85D additional launchers in a 5P85SD complex
Control arrangement
Controlled through the F3S container on the 5P85S master launcher rather than fully autonomous
Chassis
MAZ-543M-family 8x8 wheeled chassis
Associated radar
5N63S Flap Lid B engagement radar in S-300PS battery references
Engagement range context
75 km range cited for the 5V55R S-300PS missile fit
Documented conflict losses
Exact 5P85D rows appear in Oryx visual-loss lists for Ukrainian equipment in 2022 and Armenian/Artsakh equipment in 2020
Variants

Open sources describe 5P85D as part of the 5P85 launcher family rather than a standalone missile system. The key distinction is command autonomy: S-series TELs carried the master electronics, while D-series launchers depended on a master vehicle.

VariantConfigurationDesignation notes
5P85S TEL, S-300PS master transporter-erector-launcher, Air Defense5P85S TELMaster TEL

The 5P85S carried control logic and datalink equipment for the 5P85SD launcher group, normally controlling paired 5P85D launchers.

Sources: Air Power Australia S-300P TEL Vehicles, Army Recognition 5P85S

5P85T / 5P85TETowed launcher line

The towed branch provided trailer launchers for S-300PMU family systems, separate from the self-propelled 5P85S/D launcher group.

Sources: Air Power Australia S-300P TEL Vehicles

5P85SELater autonomous TEL

Later self-propelled export launchers moved toward autonomous TEL electronics instead of the master-slave arrangement used by the 5P85S and 5P85D group.

Sources: Air Power Australia S-300P TEL Vehicles

Parent Air-Defense System

The launcher is useful as a catalog component because its role is defined by the S-300PS battery rather than by independent fire-control or conflict-use reporting.

Compatible itemItem typeCompatibility evidence
S-300, Long-range surface-to-air missile system, Air DefenseS-300Long-range surface-to-air missile system

The 5P85D works inside S-300PS / early S-300PMU launcher groups, normally as an additional TEL controlled by a 5P85S master launcher and associated fire-control radar.

Sources: Army Recognition 5P85D, Missilery S-300PS

5P85S TEL, S-300PS master transporter-erector-launcher, Air Defense5P85S TELMaster S-300PS launcher

The 5P85D depends on the 5P85S master launcher in the 5P85SD group; sources describe the master launcher as the vehicle carrying the control equipment for up to two 5P85D launchers.

Sources: Air Power Australia S-300P TEL Vehicles, Army Recognition 5P85S

30N6 engagement radar, S-300-family engagement and missile-guidance radar, Air Defense30N6 engagement radarS-300PS engagement radar

S-300PS battery references place the 5N63S/30N6 Flap Lid B engagement radar in the same fire-unit architecture as the 5P85S and 5P85D launchers.

Sources: Army Recognition S-300PS, Missilery S-300PS

Why the D launcher matters

The D-series launcher increased ready missile count for a fire unit but depended on the master launcher and radar/control vehicles for battery operation.

Sources: Missilery S-300PS, Air Power Australia S-300P TEL Vehicles

Launcher Group Role

The 5P85D should be read as a launcher component within an S-300PS fire unit, not as a self-contained air-defense system. Sources distinguish it from the 5P85S master launcher by the missing equipment cabin behind the driver's compartment and by its dependence on the master TEL for control, while visual-loss records identify exact 5P85D launchers in Ukraine and Nagorno-Karabakh.

Launcher group

The 5P85SD launcher complex is described with one 5P85S master launcher and up to two additional 5P85D launchers.

Ready missiles

Four containerized 5V55-series missiles, one per launch canister.

Command dependency

The 5P85D is controlled through the F3S preparation-and-launch container on the 5P85S master launcher.

Sources: Army Recognition 5P85D; Missilery S-300PS; Air Power Australia S-300P TEL Vehicles; Oryx Ukrainian Equipment Losses; Oryx Nagorno-Karabakh Losses.

Timeline

5P85D TEL Key Events

  1. S-300P development begins

    S-300P development began under Almaz Central Design Bureau, creating the air-defense family for which 5P85-series launchers later served as mobile TELs.

    Sources: CSIS S-300

  2. S-300P enters service

    CSIS places S-300P operational service entry in 1978; later S-300PS mobility improvements produced the 5P85S and 5P85D launcher group.

    Sources: CSIS S-300, Air Power Australia S-300P TEL Vehicles

  3. S-300PS launcher generation appears

    Open references describe the S-300PS generation as the point where road-mobile 5P85S master and 5P85D additional TELs became central to the launcher-complex layout.

    Sources: Missilery S-300PS, Air Power Australia S-300P TEL Vehicles

  4. 5P85D loss recorded in Nagorno-Karabakh

    Oryx's Armenian/Artsakh loss list for the 2020 fighting separately records one 5P85D launcher for S-300PS destroyed by a loitering munition.

    Sources: Oryx Nagorno-Karabakh Losses

  5. Ukrainian 5P85D losses recorded

    Oryx's Ukrainian equipment-loss list for Russia's full-scale invasion separately records two 5P85D launchers for S-300PS, one destroyed and one captured.

    Sources: Oryx Ukrainian Equipment Losses

Related Weapon Systems
5P85SM2-01 TEL, S-400 self-propelled transporter-erector-launcher, Air DefenseAir Defense5P85SM2-01 TELS-400 self-propelled transporter-erector-launcherThe 5P85SM2-01 is a self-propelled transporter-erector-launcher associated with Russia's S-400 Triumf long-range air-defense system. It carries four launch canisters on a MAZ-543M-family heavy wheeled chassis and depends on the S-400 battery's command post, search radars, and 92N6E engagement radar for target data and missile guidance. Visual-loss tracking has separately documented Russian 5P85SM2-01 launchers in Ukraine, making the TEL identifiable beyond generic S-400 system references.
30N6 engagement radar, S-300-family engagement and missile-guidance radar, Air DefenseAir Defense30N6 engagement radarS-300-family engagement and missile-guidance radarThe 30N6 is the S-300P-family engagement radar lineage known by NATO as Flap Lid and, on later export configurations, Tomb Stone. The 5N63S Flap Lid B branch is the self-propelled S-300PS-era configuration, giving S-300P, S-300PS, S-300PMU, and S-300PMU-2 batteries target tracking, illumination, and missile-guidance functions rather than serving as a standalone weapon. Direct conflict records place Flap Lid-family radars in Ukraine and Nagorno-Karabakh losses, and satellite-based analysis identified a 30N6/30N6E radar as the probable S-300 component hit near Isfahan in April 2024.

Sources

Oryx Ukrainian Equipment LossesPublisher: Oryx | Note: Supports 2014 Russia-Ukraine War direct fielded by Ukraine context by listing visually documented Ukrainian 5P85D launchers for S-300PS as destroyed and captured equipment losses. | Accessed: 2026-07-04Shephard Ukraine S-300 LossesPublisher: Shephard Media | Note: Supports 2014 Russia-Ukraine War direct used by Ukraine context by corroborating early Oryx-tracked Ukrainian S-300PS launcher losses, including a 5P85D launcher. | Accessed: 2026-07-04Oryx Nagorno-Karabakh LossesPublisher: Oryx | Note: Supports 2020 Nagorno-Karabakh Conflict direct fielded by Armenia / Artsakh context by listing a visually documented Armenian 5P85D launcher for S-300PS destroyed by a loitering munition. | Accessed: 2026-07-04Missilery S-300PSPublisher: Raketnaya Tekhnika / missilery.info | Note: Supports S-300PS composition, including 5P85SD launcher complexes with one 5P85S and up to two 5P85D additional launchers, 5V55R missiles, MAZ-543M chassis, KBSM launcher-development context, and the F3S control relationship. | Accessed: 2026-07-04Voenmeh S-300 SAM Systems PDFPublisher: Baltic State Technical University Voenmeh | Note: Supports technical background for S-300PS launcher-complex composition, 5P85S and 5P85D launcher roles, MAZ-543M chassis context, and four transport-launch canisters. | Accessed: 2026-07-04Army Recognition 5P85DPublisher: Army Recognition | Note: Supports 5P85D identity as an S-300PS slave launcher, its paired use with a 5P85S master TEL, four missile canisters, visible layout distinction, 5V55 missile fit, and associated S-300PS radar context. | Accessed: 2026-07-04Army Recognition S-300PSPublisher: Army Recognition | Note: Supports the S-300PS battery layout with one 5P85S TEL, two 5P85D TEL/transloaders, and a 5N63S Flap Lid B radar, plus S-300PS mobility context. | Accessed: 2026-07-04Air Power Australia S-300P TEL VehiclesPublisher: Air Power Australia | Note: Supports 5P85S/D master-slave launcher group architecture, later autonomous 5P85SE family distinctions, and MAZ-543 chassis context for S-300P launcher vehicles. | Accessed: 2026-07-04CSIS S-300Publisher: CSIS Missile Threat | Note: Supports S-300P development under Almaz Central Design Bureau, operational service entry, broad S-300P role, and family-level background for the parent system. | Accessed: 2026-07-04S-300 launcher, 2009.jpgPublisher: Wikimedia Commons | Note: Supports image provenance for a file described as an S-300P 5P85D launcher on parade in Russia, credited to Archlinux and listed under CC BY-SA 3.0. | Accessed: 2026-07-04Army Recognition 5P85SPublisher: Army Recognition | Note: Supports the 5P85S master TEL distinction, including its control relationship to two 5P85D launchers and the visible equipment container behind the driver compartment. | Accessed: 2026-07-04