That was okay, because none of them were particularly fast compared to ballistic missiles. Their reference points wouldn't have been much good.
Not sure what you're trying to say here. They didn't have DSMAC because they didn't need it. They had nukes onboard. DSMAC was/is for hitting small targets with a conventional warhead.
 
Last edited:
Not sure what you're trying to say here. They didn't have DSMAC because they didn't need it. They had nukes onboard. DSMAC was/is for hitting small targets with a conventional warhead.
Maybe you are confused about DSMAC importance and why nuclear armed Tomahawk leaned on it. Some mistakenly believe TERCOM and GPS would have been enough. GPS was in the infancy in that time period and TERCOM was less useful than the terrain matching not requiring accurate pictures. Errors in DSMAC didn't cause the missile to lose it's location.
 
Maybe you are confused about DSMAC importance and why nuclear armed Tomahawk leaned on it. Some mistakenly believe TERCOM and GPS would have been enough. GPS was in the infancy in that time period and TERCOM was less useful than the terrain matching not requiring accurate pictures. Errors in DSMAC didn't cause the missile to lose it's location.
Honestly, I'm wondering if you know what DSMAC is.
 
Enlighten me how this comment is relative to DSMAC in an all out exchange during the contemporary era of the technology. This was in a world that relied mostly on analog at the time and relied on high accuracy not wishful dreams. Sometimes you just to comment on what probably feels good without reading how the technology worked.
If your target isn't mobile, it doesn't matter just how slow the missile is to get to it.

My understanding was that GLCM was to hit non-moving targets like power plants, while Pershing was for targets that could move.
 
Honestly, I'm wondering if you know what DSMAC is.
If you did then you already know highly relevant to GLCM accuracy and mostly irrelevant to the topic. You can spell out your point because so far you have not made one for why it should be relevant. GLCM can lose GPS and have TERCOM fail but complete the mission.
If your target isn't mobile, it doesn't matter just how slow the missile is to get to it.

My understanding was that GLCM was to hit non-moving targets like power plants, while Pershing was for targets that could move.
No. That was not an option for the Pershing I or II. The rocket completed its mission much sooner than GLCM but was targeted at coordinates and fixed sites with an option of using radar for terminal corrections. GLCM allegedly flew slower and 50% further.
 
If you did then you already know highly relevant to GLCM accuracy and mostly irrelevant to the topic. You can spell out your point because so far you have not made one for why it should be relevant. GLCM can lose GPS and have TERCOM fail but complete the mission.
"Maybe you are confused about DSMAC importance and why nuclear armed Tomahawk leaned on it.

No nuclear-armed Tomahawk had it. Also, GLCM did not use GPS guidance.

"GLCM (Ground-Launched Cruise Missile): BGM-109G Gryphon

As early as 1971 the U.S. Air Force had tentative plans to replace the retired MGM-13 Mace with amodern GLCM (Ground-Launched Cruise Missile) with TERCOM precision guidance and a small fuel-efficient turbofan engine. The plansbecame more firm in 1976, and in January 1977 the USAF was allowed to develop and field a GLCM derivative of the Navy's BGM-109Tomahawk SLCM. The first launch of the BGM-109G Gryphon (sometimes spelled Griffin) GLCM from itsmobile TEL (Transporter/Erector/Launcher) occurred in May 1980, and operational testing began in May 1982. The GLCM wasoperationally deployed in Europe from 1983 to counter (together with the U.S. Army's MGM-31C Pershing II)the Soviet RSD-10 Pioner (SS-20 Saber) mobile IRBM system.

The BGM-109G was very similar to the Navy's nuclear-armed BGM-109A except that a different W-84 thermonuclear warhead was used.The Gryphon was launched from a mobile TEL, which could hold four missiles. Like the BGM-109A, it used an INS/TERCOM guidance system with an accuracy of about 80 m (260 ft) CEP."

And no, TERCOM and DSMAC are not the same thing.
 
GLCM can lose GPS and have TERCOM fail but complete the mission.

As Sferrin pointed out the BGM-109A didn't use GPS and if TERCOM failed during the flight even if it reached its' target the W80 would be a dud as the Tomahawk had to overfly ALL 24 of its' TERCOM points before the W80 armed.
 
No nuclear-armed Tomahawk had it. Also, GLCM did not use GPS guidance.
Block III would have been introduced into GLCM if not for INF. They proved it was feasible if authorized. Block III instead was focused on conventional strike.
As Sferrin pointed out the BGM-109A didn't use GPS and if TERCOM failed during the flight even if it reached its' target the W80 would be a dud as the Tomahawk had to overfly ALL 24 of its' TERCOM points before the W80 armed.
W84 was on GLCM, not W80. The other part is nonsense.
 
Enlighten me how this comment is relative to DSMAC in an all out exchange during the contemporary era of the technology. This was in a world that relied mostly on analog at the time
Not as I recall it, by the early 80s we were well into the microprocessor revolution. I'd really love to see an analogue DSMAC system!
 
GLCM can lose GPS and have TERCOM fail but complete the mission.
There's this minor thing called wind-drift. DSMAC is completely incapable of altering the impact point if the vehicle is miles from where it should be.
 
There's this minor thing called wind-drift. DSMAC is completely incapable of altering the impact point if the vehicle is miles from where it should be.
The GLCM had to confirm location over target which could use but did not strictly require TERCOM. Neither TERCOM nor DSMAC was absolutely required for that but could be by configuration. Only one system was absolutely required and it had thresholds of accuracy to match. But if you knew its not for a public discussion.
TERCOM is to get it close enough for DSMAC to work.
Maybe you are purposely stating misinformation. You probably shouldn't say that with such conviction.
That was my point. It used an image for targeting.
The time period has to be considered. Imaging meant something different back then. Pershhing IIs radar was not an AESA with high fidelity processing. It was less sophisticated and was only capable of limited matching the preconfigured mask to radar returns after process filtering. But it wasn't like Google Lens where an AI could intelligently identify the values. People confuse what some of this stuff meant for the timeframe. Much of what was possible simply was not thought of yet by then. Technology has greatly evolved since that time but so have the number of geniuses involved.
 
Last edited:
The GLCM had to confirm location over target which could use but did not strictly require TERCOM. Neither TERCOM nor DSMAC was absolutely required for that but could be by configuration. Only one system was absolutely required and it had thresholds of accuracy to match. But if you knew its not for a public discussion.

Maybe you are purposely stating misinformation. You probably shouldn't say that with such conviction.
I can only tell you what it is. I can't understand it for you.
 
That's what TERCOM is for. TERCOM is to get it close enough for DSMAC to work.
Absolutely. However, he was discussing a situation in which both GPS and TERCOM had failed, but alleged DSMAC would still get a GLCM to the target.
 
Absolutely. However, he was discussing a situation in which both GPS and TERCOM had failed, but alleged DSMAC would still get a GLCM to the target.
Why would TERCOM fail? Not even sure you could jam it for long enough to matter. If the system in the missile went out then yeah, it's hosed. There were even some problems in Desert Storm because the terrain didn't have enough features of the required size along some desired paths to follow.

GLCM didn't even have DSMAC so it's not a factor in the conversation.
 
The GLCM had to confirm location over target which could use but did not strictly require TERCOM. Neither TERCOM nor DSMAC was absolutely required for that but could be by configuration. Only one system was absolutely required and it had thresholds of accuracy to match. But if you knew its not for a public discussion.
Okay, TERCOM and DSMAC for beginners. DSMAC is a terminal phase guidance system, it applies only in the last few miles of a cruise-missile's approach to target. TERCOM is a long range navigation system, its job is to get the cruise missile close enough for DSMAC to take over. TERCOM can work without DSMAC at reduced accuracy, DSMAC can't work without TERCOM or another method of delivering the missile into its DSMAC acquisition bucket. (Remember, cruise missiles are taking that picture from low altitude, they can't see very far and its only in a limited Field of View.

You can think of the two together as a bit like lob-tossing a PGM into a laser-guidance bucket. If it misses the bucket entirely, no amount of guidance technology is going to get it on target.

TERCOM relies on taking a strip of radar altitudes, then finding a matching strip in its radar map to tell the missile where it is and which way to steer to the target. DSMAC relies on taking a forward looking picture of terrain and buildings and doing a mathematical comparison to work out how to make that match with the image in its memory that marks the desired approach path and impact point. But for that to work it must be in the right general area, and looking in the right direction, and it gets there by relying on a long range navigation system, whether that be TERCOM, GPS, or INS.

If the long range navigation system fails en route, the missile never gets close enough for DSMAC to work. Either it fails to make a turn, makes it in the wrong place, or fails to allow for wind-drift. Or all of the above. But the end result is the same: the DSMAC system takes its image, and it's facing the wrong way, in the wrong place, and can't correlate the actual terrain with the stored picture.

Maybe you are purposely stating misinformation.
Or maybe I have a better understanding of the technology than you do.

You probably shouldn't say that with such conviction.
Have you considered applying that approach to your own posts?

The time period has to be considered.
It's the time period in which I began my career in defence software development. I've got probably a rather more intimate understanding of the technology of the time than you do.

Pershhing IIs radar was not an AESA with high fidelity processing.
We're discussing the interrelation of TERCOM and DSMAC, Pershing II is irrelevant to the discussion.
 
Pershing II is irrelevant to the discussion.
In a thread titled, "Pershing Missiles". Nice.
Interesting that you felt my responses to other people somehow applied to you.

GLCM with TERCOM and INS doesn't need DSMAC for approach, because the nuke. Accuracy is sufficient for a nuke.
The USAF disagreed. GLCM that deployed and systems kept for development were not necessarily similar. Remember the deployed systems had neither GPS nor TERCOM. The deployed version did require confirmation of location over a target within a threshold. There are details nobody should be discussing. But we can state DSMAC required much more work than TERCOM. Use in a terminal phase was a preference decision not a necessity. It was not limited to that phase and the real handicap was keeping relevant data within limited storage. And it was not a preferred system in the dark although it had a work around. Newer systems have far different technologies that work better. But in that time period there was no peer.
 
Last edited:
In a thread titled, "Pershing Missiles". Nice.
You were the one insisting on discussing cruise missile specific TERCOM and DSMAC in a thread relating to Pershing.

Interesting that you felt my responses to other people somehow applied to you.
If you post something that's wrong, expect to be corrected.

But we can state DSMAC required much more work than TERCOM. Use in a terminal phase was a preference decision not a necessity. It was not limited to that phase and the real handicap was keeping relevant data within limited storage.
DSMAC required its approach path to be calculated by transforming overhead satellite imagery into low-level contrast maps. That would have required supercomputer use at the time. There would not have been the available capacity to extend it beyond the immediate target area. It certainly couldn't replace long range navigation systems, especially for flight over water.
 
The USAF disagreed. GLCM that deployed and systems kept for development were not necessarily similar. Remember the deployed systems had neither GPS nor TERCOM. The deployed version did require confirmation of location over a target within a threshold.
That's not correct. GLCM had Tercom and an INS. GPS didn't exist back then and should not be part of this discussion.
 
Is there any info on the 1st version of the PERSHING ( XM-14 ) with the OGIVE ( perhaps Ogive-Secant ) nose cone, instead of the usual Multi-Tapered nose cone ? Dimensions are most welcome.
 

Attachments

  • pc0469.jpg
    pc0469.jpg
    247.1 KB · Views: 32
  • pershing_105_25feb60_04.jpg
    pershing_105_25feb60_04.jpg
    31.9 KB · Views: 26
  • pershing_105_25feb60_03.jpg
    pershing_105_25feb60_03.jpg
    32.4 KB · Views: 18
  • pershing_105_25feb60_01.jpg
    pershing_105_25feb60_01.jpg
    15 KB · Views: 20
  • pershing_01.jpg
    pershing_01.jpg
    21.5 KB · Views: 19
  • pershing_108_9jun60_01.jpg
    pershing_108_9jun60_01.jpg
    29 KB · Views: 19
  • pershing-lead.jpg
    pershing-lead.jpg
    1.1 MB · Views: 24
  • Early_test_of_P1_and_ground_equipment - LARGE.jpg
    Early_test_of_P1_and_ground_equipment - LARGE.jpg
    407.5 KB · Views: 17
  • pc0469 - 8 X 10.jpg
    pc0469 - 8 X 10.jpg
    907.4 KB · Views: 17
  • pershing_01.jpg
    pershing_01.jpg
    21.5 KB · Views: 16
  • WP_000727.jpg
    WP_000727.jpg
    73.3 KB · Views: 15
  • 001 - BW.jpg
    001 - BW.jpg
    112.4 KB · Views: 11
  • FIRST TEST VEHICLE - 1 - BW - resized.jpg
    FIRST TEST VEHICLE - 1 - BW - resized.jpg
    122 KB · Views: 18
  • SHOOT and SCOOT.JPG
    SHOOT and SCOOT.JPG
    278.4 KB · Views: 36
Last edited:
Yeesh 654 SS-20s? Didn’t remember there were that many almost 2000 warheads!!
 
East German Stasi report on Conventional Airfield Attack Missile (CAAM) Pershing II missile derivatives. The conventional version of the standard two-stage Pershing II would have an 825 km range carrying a payload of 112 KERP (Kinetic Energy Runway Penetrator) submunitions. Each KERP would be 8.5 kg, length 660 mm, diameter 68 mm, with 1.6 kg of explosive. A single stage missile (Pershing IIRR) would carry 68 KERPs to 625 km. Both missiles would have a 30 meter CEP and a flight time of 7 minutes. Ejection sequence would start at the end of the radar correlation process at an altitude of 1330 m (4.2 s before impact), where the spinning RV (Start of RV spin motion at 1,720 m altitude) would eject the KERP submunitions at an altitude of 1040 m (3 s before impact). Impact pattern was to be 150 meters in diameter with an average spacing between individual KERPs of 9 meters which was determined as optimal. To extend the "duration of paralysis" 1/3 of the KERPs would be fitted with instantaneous fuzes (exploding after a short one millisecond delay to penetrate into the runway before detonating) and 2/3 with long delay fuzes (activation after 5 to 10 hours). Missiles were to be based in NATO airbases in West Germany, in vertical launch cells placed in modified NATO aircraft shelters.
 

Attachments

  • Screenshot 2026-07-27 133632.png
    Screenshot 2026-07-27 133632.png
    166.4 KB · Views: 25
  • Screenshot 2026-07-27 133539.png
    Screenshot 2026-07-27 133539.png
    135 KB · Views: 28
  • Screenshot 2026-07-27 133556.png
    Screenshot 2026-07-27 133556.png
    190 KB · Views: 30
  • Screenshot 2026-07-27 133611.png
    Screenshot 2026-07-27 133611.png
    206.8 KB · Views: 35
  • Development of a Conventional Version of Pershing II Against Airbases.pdf
    230.6 KB · Views: 13
Reichweite (Range) - 825km and 625km. Or is that reach into Russia itself? Seems the 825 is for the 2 stage version (Pershing II) and the 625km is for the IB single stage doing a translate. Is this for the submunition version maybe?
Single-stage Pershing IIs were actually a thing but they elected to deploy them all in the 2-stage variant.
 

Attachments

  • DA-SC-88-01658-1-scaled.jpg
    DA-SC-88-01658-1-scaled.jpg
    855 KB · Views: 27
  • Pershing_II_-_4th_test_launch.jpeg
    Pershing_II_-_4th_test_launch.jpeg
    1.5 MB · Views: 35
East German Stasi report on Conventional Airfield Attack Missile (CAAM) Pershing II missile derivatives. The conventional version of the standard two-stage Pershing II would have an 825 km range carrying a payload of 112 KERP (Kinetic Energy Runway Penetrator) submunitions. Each KERP would be 8.5 kg, length 660 mm, diameter 68 mm, with 1.6 kg of explosive. A single stage missile (Pershing IIRR) would carry 68 KERPs to 625 km. Both missiles would have a 30 meter CEP and a flight time of 7 minutes. Ejection sequence would start at the end of the radar correlation process at an altitude of 1330 m (4.2 s before impact), where the spinning RV (Start of RV spin motion at 1,720 m altitude) would eject the KERP submunitions at an altitude of 1040 m (3 s before impact). Impact pattern was to be 150 meters in diameter with an average spacing between individual KERPs of 9 meters which was determined as optimal. To extend the "duration of paralysis" 1/3 of the KERPs would be fitted with instantaneous fuzes (exploding after a short one millisecond delay to penetrate into the runway before detonating) and 2/3 with long delay fuzes (activation after 5 to 10 hours). Missiles were to be based in NATO airbases in West Germany, in vertical launch cells placed in modified NATO aircraft shelters.
https://www.secretprojects.co.uk/threads/pershing-missiles.10786/#post-186118
 

Attachments

  • CAM-Cutaway-S.jpg
    CAM-Cutaway-S.jpg
    16.1 KB · Views: 35
  • CAM-Terminal-1-S.jpg
    CAM-Terminal-1-S.jpg
    30.2 KB · Views: 32
  • CAM-Terminal-2-S.jpg
    CAM-Terminal-2-S.jpg
    25.3 KB · Views: 27
Reichweite (Range) - 825km and 625km. Or is that reach into Russia itself? Seems the 825 is for the 2 stage version (Pershing II) and the 625km is for the IB single stage doing a translate. Is this for the submunition version maybe?

Those are the maximum ballistic ranges of the missile. 825 km is for the conventional (Conventional Airfield Attack Missile) 2 stage version with a payload of 112 KERPs (~950 kg submunition mass) while 625 km is for the conventional single stage version (not IB, Pershing IIRR, basically Pershing II with the RV mated directly to the first stage) with a payload of 68 KERPs (~580 kg submunition mass). Technically all Pershing II missiles (nuclear or conventional, the motor stack and adapter would be identical) were designed so that the RV assembly could be mated to the first stage to create a single stage missile, however it was never fielded in that configuration and all the operational, nuclear armed missiles were all the default two stage version. For the conventional version they would have been based in NATO airfields located close to the border with East Germany targeting WARPAC airfields in East Germany, so for some of the targets (WARPAC bases on the other side of the border) the longer range of the 2 stage version wouldn't have been needed.
 
Last edited:
If one seeks a rapid reaction PII launch that a hardened fixed shelter provides one would think one would not utilize known/geolocated aircraft shelters. A real attempt at secrecy would seem more prudent. Security would have been more expensive & difficult but, your sites might be reused. The launch sites would not be immediately suffer from counterfire or preemptive counter battery.
 
East German Stasi report on Conventional Airfield Attack Missile (CAAM) Pershing II missile derivatives. The conventional version of the standard two-stage Pershing II would have an 825 km range carrying a payload of 112 KERP (Kinetic Energy Runway Penetrator) submunitions. Each KERP would be 8.5 kg, length 660 mm, diameter 68 mm, with 1.6 kg of explosive. A single stage missile (Pershing IIRR) would carry 68 KERPs to 625 km. Both missiles would have a 30 meter CEP and a flight time of 7 minutes. Ejection sequence would start at the end of the radar correlation process at an altitude of 1330 m (4.2 s before impact), where the spinning RV (Start of RV spin motion at 1,720 m altitude) would eject the KERP submunitions at an altitude of 1040 m (3 s before impact). Impact pattern was to be 150 meters in diameter with an average spacing between individual KERPs of 9 meters which was determined as optimal. To extend the "duration of paralysis" 1/3 of the KERPs would be fitted with instantaneous fuzes (exploding after a short one millisecond delay to penetrate into the runway before detonating) and 2/3 with long delay fuzes (activation after 5 to 10 hours). Missiles were to be based in NATO airbases in West Germany, in vertical launch cells placed in modified NATO aircraft shelters.
Thank you so much for this, where did you find the Stasi docs? are they digitalized or you had to look them up?
 
Thank you so much for this, where did you find the Stasi docs? are they digitalized or you had to look them up?
If i am not mistaken, the document was digitised by the ETH Zürich Centre for Security Studies Parallel History Project on Cooperative Security (PHP)
The same collection of Stasi documents also contains some reports on Pershing Ib and German ABM efforts.

Development of a Conventional Version of Pershing II Against Airbases
16 Nov 1981
Description: This document outlines the planned development of a conventional version of the Pershing II missile to be used against airfields. It was prepared by the East German Staatssicherheit (Stasi) intelligence agency. The report describes the history of this project and technical details, such as the maximum striking distance, precision, deployment, and special properties of the planned warhead. Annexed are figures illustrating some characteristics of the planned weapon.

Collection: Stasi Intelligence

Document Type: Document
Origin (Agency): Ministerium für Staatssicherheit, GDR
Language of Original Document: German
Number of Pages: 10
Cold War Period: 1980s
Document Source: Federal Commissioner for the Records of the National Security Service of the Former Democratic Republic (BStU), Berlin
Call Number: ZA, HVA, 9, pp. 8-17
 

Similar threads

Back
Top Bottom