Copy Safeguard Complex Components from CWDB to DB3K as a Hypothetical

tbrandon517 commented 2 years ago

DB Selector

Both

Affected DBID(s)

DBID 1708 LIM-99A Sprint, 1709 LIM-49 Spartan, 1812 Safeguard SAM

Summary of Changes

Regarding the Safeguard SAM system the LIM-49 Spartan and LIM-99A Sprint missiles have a maximum target speed of 1150 kts. Too low for their ABM mission.

Also the LIM-99A Sprint has a top speed of 2300 kts. The missile's literature indicate speeds of Mach 10+.

Quote Crazy Ivan from Forum "The Safeguard ABM facility is currently unusable in its current form. The Spartan needs to have its maximum target speed set to 11000 knots and maximum target altitude set to 560 KM. It also needs it's datalink range increased to 460 miles and be equipped with a 5 Megaton warhead. The Sprint needs its maximum speed to be increased to 6615 knots and its acceleration to be increased to 981 m/s it also will reach its maximum speed in the 0-65000 ft range. The Sprint's maximum target velocity needs to be increased to 10500 knots and maximum target altitude to 40 km. The Air POH for the sprint should also be increased as the missile demonstrated extreme accuracy to the point of effectively being a hit to kill interceptor."

Quote RedEye43 from forum "Sprint missiles, ID 1708, cannot be directed at all. Since they're track via missile and the Safeguard unit has no fire control radar, they're unusable. They should also be command-guided like the Spartan. Sprint missiles should also have much higher max target speed, substantially higher climb rate in the realm of 100 g, and higher top speed in the realm of Mach 10.

Safeguard sites, ID 1812, are equipped with the Bomarc missile reception datalink, not the command datalink. Safeguard sites are also missing the Missile Site Radar, a 360-degree 3D phased array fire control radar.

Spartan missiles, ID 1709, should probably be retargetable/controllable after launch, since they're controlled entirely from the ground via SAGE. They should also have much higher maximum target speed, being designed for ballistic missile interceptions outside the atmosphere."

Also could this be ported over to DB3000 as a hypothetical facility?

Sources

http://www.astronautix.com/s/sprintabm.html

http://www.astronautix.com/s/spartanabm.html

https://en.wikipedia.org/wiki/LIM-49_Spartan

https://en.wikipedia.org/wiki/Sprint_(missile)

http://www.nuclearabms.info/Spartan.html http://www.nuclearabms.info/Sprint.html http://srmsc.org/mis2020.html http://srmsc.org/mis2010.html http://www.nuclearabms.info/Spartan.html http://www.nuclearabms.info/Sprint.html http://fas.org/spp/starwars/program/safeguard.htm

PygmalionOfCyprus commented 2 years ago

Fixed the stat/datalink issues. Will add the MSR in a few once I have enough internet to do proper research.

tbrandon517 commented 2 years ago

Found this about the MSR

https://srmsc.org/msr2050.html https://www.mda.mil/global/documents/pdf/1969%20Sentinel-Safeguard.pdf https://apps.dtic.mil › sti › pdfsPDF AD-A2 -IT c9co519 - DTIC https://www.army.mil/article/194445/smdc_history_safeguard_achieves_full_operational_capability https://www.globalsecurity.org/space/systems/msr.htm

tbrandon517 commented 2 years ago

May also want to add facilities for the Remote Sprint Launchers situated away from the MSR which had 30 Spartan and 16 Sprint. The total safeguard complex had 100 missiles total. The remaining 54 Sprints were in 4 RSL10-20 miles from the MSR with 12, 12, 14, and 16 Sprints respectively.

https://en.wikipedia.org/wiki/Safeguard_Program https://srmsc.org/rsl1000.html

PygmalionOfCyprus commented 2 years ago

Okay, after procrastinating on this for nearly four months I have finally overhauled the Safeguard system in CWDB.

A "full" Safeguard build now consists of 7 separate facilities in Command represented by 6 DBIDs; these mostly correspond to the real-world facilities, though I broke up the MSR into its radar and siloes. You'll need:

The AN/FPQ-16 PARCS radar building (well, you don't need it, but it was there)
The Missile Site Radar building itself
The Missile Site Radar siloes, w/ 30x Spartan and 16x Sprint mounts
4 Remote Sprint Launch Sites, represented by 3 different DBIDs to cover RSLs 1 & 2 (12x), 3 (16x), and 4 (14x)

Breaking them up into separate facilities (and individually modeling the missile siloes rather than lumping them into groups of 3 and 4) has allowed me to adjust sizes and dispersion based on site maps (MSR, RSL) ~~at the expense of my sanity~~ and also to better simulate the multi-face radar on the MSR especially. (Speaking of radar faces, I also fixed the PAR, which was erroneously set up as a 360deg radar in the DB.)

PygmalionOfCyprus commented 2 years ago

I will port this over to DB3K as a hypothetical once DBTwools is ready for use on a live DB, since I would rather strap myself to a Sprint missile than manually copy all this between the databases.

FIM43-Redeye commented 2 years ago

Minor note to be added: the Safeguard datalink being LOS-limited essentially nullifies its range and may not be entirely realistic (the Bomarc likely knows where it is and is only receiving updates on the target's location from SAGE), on top of significantly reducing its usefulness. The primary reason for this is that the Spartan doesn't detonate when it reaches its last known target position; instead it just flies repeatedly in circles around it. Just a note, and I leave it to you to decide whether the LOS limitation is reasonable. This also goes for the Bomarc.

Also of note is that the MSR should probably be air search capable, but that's also spitballing. Just noting what makes sense to me seeing Spartan's dual-use nature.

PygmalionOfCyprus / cmo-db-requests