Radar Bomb Scoring

From Infogalactic: the planetary knowledge core
(Redirected from Strategic Training Range)
Jump to: navigation, search

Lua error in package.lua at line 80: module 'strict' not found.

Radar Bomb Scoring[1] is a combat aviation ground support operation used to evaluate Cold War aircrews' effectiveness with simulated unguided bomb drops near radar stations of the United States Navy, the USAF Strategic Air Command, and Army Project Nike units. USAF RBS used various ground radar, computers, and other electronic equipment such as jammers to disrupt operations of the bomber's radar navigator,[2] AAA/SAM simulators to require countermeasures from the bomber, and Radar Bomb Scoring Centrals for estimating accuracy of simulated bombings.[3] Scores for accuracy and electronic warfare effectiveness were transmitted from radar sites such as those at Strategic Range Training Complexes[3] (e.g., from Detachment 1 at the "La Junta Bomb Plot").

Most of the SAC sites were in the continental US with units (detachments) manned by technicians and operators of the Automatic Tracking Radar Specialist career field (AutoTrack). Radar Bomb Scoring and the Autotrack specialty were discontinued shortly after the end of the Cold War when increased munitions accuracy (e.g., GPS-guided JDAMs 1st used in 1993) reduced the need for scoring of simulated bomb runs, and GPS avionics allow onboard tracking for "no-drop bomb scoring" of unguided bombs.

History

World War II included Army Air Forces Bombardier Schools' scoring of trainee's proficiency at the "West Texas Bombardier Triangle"[4] and other USAAF ranges (e.g., observers on Range Towers),[5] and ground-directed bombing for combat guided by automatic tracking radars was used in the Mediterranean Theatre's Po Valley. On 6 June 1945 "the 206th Army Air Force Base Unit (RBS) (206th AAFBU), was activated at Colorado Springs, Colorado under the command of Colonel Robert W. Burns [with] operational control of the two SCR-584 radar detachments located at Kansas City and Fort Worth" Army Airfield (Det B),[6]:3199 and dets were later "established at Denver, Chicago, Omaha, Albuquerque and [c. 1952 at] Los Angeles."[7] USAF RBS units were at MacDill AFB in 1947,[8] in Phoenix in 1952,[9] and Guam in 1954.[10]

Strategic Air Command

RBS by Strategic Air Command began with the last of 888 simulated bomb runs against San Diego[11] scored in 1946 as well as 2,499 runs scored in 1947.[7] The 1948 increase to 12,084[7] was the result of a "scathing" Lindbergh review of SAC in the Spring of 1948 (SAC's commanding general was replaced 15 October, and January 1949 simulated raids by Curtis LeMay's "entire command" on Wright-Patt AFB "were appalling").[12] On 21 July 1948, the 263rd AAFBU (RBS) had been renamed the 3903rd Radar Bomb Scoring Squadron (SAC),[13] and early RBS detachments were designated by letters, e.g., Detachment D at Fort George Wright WA in 1950.[14] Three detachments of the 3903rd RBS deployed for ground directed bombing in Korea [15] at "Tactical Air Direction Posts" (colloq. TADPOLE sites).[16] (10 August 1954, the 3933rd Radar Bomb Scoring Squadron was redesignated the 11th Radar Bomb Scoring Squadron.)[citation needed] In 1955, RBS bomb runs for the SAC Bombing and Navigation Competition were on Amarillo, Denver, Salt Lake City, Kansas City, and San Antonio[17] (Phoenix also had runs)[18] and in 1957, SAC installed RBS sites for the competition (named "Operation Longshot")[19] which had 3 targets: Atlanta, Kansas City, and St. Louis.[20] The c. 1963 "Goldwater congressional investigation" investigated working and travel conditions at the Lynchburg, Virginia, detachment, which was a mobile unit that had temporary radar stations at "Blackstone, Staunton and Farmville before [being] shut…down".[6] c. 1960, Det 3 at Heston Aerodrome, England, moved to the Fairey Aviation Plant at Langley.[14]

Army & Navy RBS

By 1960, USAF RBS equipment had been incorporated in US Army Course Directing Centrals for Project Nike (i.e., receivers for telecommunicated tones to indicate the aircraft's bomb release on the Nike radar plotting boards).[21] Nike RBS of SAC/ADCOM bombers used USAF personnel on temporary duty to calculate the simulated bomb run score from the track by a Nike missile crew/radar (e.g., at the Chicago-Gary Defense Area).[22] In 1961, Nike units "scored 1,890 practice bomb runs" and in 1962 the NIKE site at Maitland/Lake Park in Milwaukee was RBSing.[23] Four Navy Radar Bomb Scoring Units during the Cold War included those near Spokane, Washington, and at the Pachino Radar Bomb Scoring Range near Naples, Italy. After the 10th Radar Bomb Scoring Squadron's RBS Express train had been used in 1961 near the Hawthorne Army Ammunition Plant,[24] SAC's Hawthorne Bomb Plot in nearby Babbitt also scored bomb runs of US Navy aircraft (e.g., out of Naval Air Station Fallon).

On 1 August 1961, SAC's 1st Radar Bomb Scoring Group at Carswell AFB merged with the 3908th Strategic Standardization Group to form the 1st Combat Evaluation Group at Barksdale AFB.[14] Manual RBS "bomb scoring projector" computation of "the bomb problem"[25] with scale, protractor,[26] E6B computer, and bombing tables"[14] was replaced with computerized bomb trajectory integration by the 1965 Reeves AN/MSQ-77 Bomb Directing Central developed for Vietnam War Combat Skyspot bombing. The Bayshore Bomb Plot in Michigan (formerly located in Ironwood, Michigan) was destroyed by a television fire on 26 December 1967,[27] and in 1969, the Combat Skyspot Trophy was first "awarded annually to the most outstanding [RBS] detachment in the 1st Combat Evaluation Group".[28]

At least 1 of the SAC RBS sites was operating until mid-1994 when Wilder Radar Bomb Scoring Site closed after the 1993 Base Realignment and Closure Commission.[29] In 2005, USAF RBS records were designated for destruction "10 years after inactivation of site".[30]

Post-Cold War bomb scoring

The Northrop T-38C was upgraded to have no-drop bomb scoring capability in 2007[31] by estimating the impact from the onboard GPS-calculated position of release,[32] and the United States Marine Corps had no-drop bomb scoring at Yuma Proving Ground in 2010.[33] At least 1 Strategic Air Command RBS site continues as an electronic warfare range—the Belle Fourche Electronic Scoring Site in Powder River Military Operations Area with Infrared Enhance Targets and Unmanned Threat Emitters (the site's call sign remains "Belle Fourche Bomb Plot").[34]

USAF Equipment

  • Bomb Scoring Centrals: SCR-584+RC294, AN/MSQ-1 (AN/MPS-9+OA-132), AN/MSQ-1A (ANMPS-19+OA-626), AN/MSQ-2 (−9+OA-215), AN/MSQ-35, AN/MSQ-39, AN/MSQ-77, AN/TPS-43, AN/TSQ-35, AN/TSQ-81, AN/TSQ-96
  • Simulators: AN/MPQ-T3 (AAA), AN/MPS-T1, AN/MST-T1, AN/VPQ-1 (TRTG)
  • Jammers: AN/MLQ-T4, AN/TLQ-11

See also

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
    Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. The Weapons Impact Scoring Set (WISS) is a manned video scoring set which scores the impact of air-to-ground delivered ordnance within a 4,000-ft (1219.2 m) radius of a defined land target under day or night conditions."
  6. 6.0 6.1 Lua error in package.lua at line 80: module 'strict' not found.
    • Lua error in package.lua at line 80: module 'strict' not found.
    • Lua error in package.lua at line 80: module 'strict' not found.
    • Lua error in package.lua at line 80: module 'strict' not found.
    • Lua error in package.lua at line 80: module 'strict' not found.
    • Lua error in package.lua at line 80: module 'strict' not found.
    • Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 7.2 Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. https://news.google.com/newspapers?id=7bFaAAAAIBAJ&sjid=CFADAAAAIBAJ&pg=3334,2743422&dq=bomb-scoring&hl=en
  10. https://news.google.com/newspapers?id=JvpXAAAAIBAJ&sjid=oPYDAAAAIBAJ&pg=4651,2717497&dq=bomb-scoring&hl=en
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Units 726-6483. Mobileradar.org. Retrieved on 2013-09-18.
  14. 14.0 14.1 14.2 14.3 Lua error in package.lua at line 80: module 'strict' not found.
  15. http://www.1stcombatevaluationgroup.com/GDBInKorea.htm
  16. Multiply.com. Sojapanradargroup.multiply.com (2013-05-31). Retrieved on 2013-09-18.
  17. 7th WING OPERATIONS HISTORY, 1955-1958. 7bwb-36assn.org. Retrieved on 2013-09-18.
  18. https://news.google.com/newspapers?nid=1338&dat=19550502&id=XPpXAAAAIBAJ&sjid=rPYDAAAAIBAJ&pg=4206,164978
  19. bomber command | operation longshot | kansas city | 1957 | 1525 | Flight Archive. Flightglobal.com (1957-10-18). Retrieved on 2013-09-18.
  20. https://news.google.com/newspapers?id=zF9QAAAAIBAJ&sjid=_w8EAAAAIBAJ&pg=7362,5208977&dq=bomb-scoring&hl=en
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Contact Information. Det6.com. Retrieved on 2013-09-18.
  23. https://news.google.com/newspapers?id=szoaAAAAIBAJ&sjid=4CYEAAAAIBAJ&pg=6078,3449013&dq=bomb-scoring&hl=en
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found. (description of Milwaukee bomb run tracked by Nike IFC M-20)
  27. Bayshore Bomb Plot. Reocities.com. Retrieved on 2013-09-18.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. http://www.sheppard.af.mil/shared/media/document/AFD-120424-057.pdf
  32. Last two T-38s get avionics upgrade. Archive.is. Retrieved on 2013-09-18.
  33. [1][dead link]
  34. Lua error in package.lua at line 80: module 'strict' not found.