Thule Site J

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

For the nearby AFSCN Remote Tracking Station and the Air Traffic Control radar site/former Project Nike command post[1] at Thule Site N-32, see Thule Tracking Station and Pingarssuit Mountain.
Thule Site J
radar structures
Thule BMEWS.jpg
Thule AN/FPS-50 detection reflectors (1959–1987)--concrete foundations included a large refrigeration system to prevent the curing concrete's heat from melting Permafrost.[citation needed]
Landform Greenland
Part of 1982: Air Force Space Command.pngAir Force Space Command (AFSPC)

1979: Shield Strategic Air Command.pngStrategic Air Command (SAC)
1968: USAF - Aerospace Defense Command.pngAerospace Defense Command
1962: Airdefensecommand-logo.jpgAir Defense Command
Location 10 miles from Thule AB (13 road miles)
 - coordinates Lua error in package.lua at line 80: module 'strict' not found.  Early Warning Radar

Lua error in package.lua at line 80: module 'strict' not found. AN/FPS-49A bldg[2]:{{{3}}}
Completed
(radars)		 1958-60 (AN/FPS-50)
1963 (AN/FPS-49A)
1987 (AN/FPS-120)

Thule Site J (J-Site) is a United States Air Force (USAF) radar station in Greenland near Thule Air Base for missile warning and spacecraft tracking. The northernmost station of the Solid State Phased Array Radar System, the military installation was built as the 1st site of the RCA 474L Ballistic Missile Early Warning System and had 5 of 12 BMEWS radars. The station has the following structures:

This list is incomplete; you can help by expanding it.
  • "EWR facility":[3]:{{{3}}} structure with a Solid State Phased Array Radar System (SSPARS) phased array radar[4]
  • BMEWS radar buildings: 3 of the 4 former RCA AN/FPS-50 Radar Set buildings, 1 AN/FPS-49A building[2]
  • Support structures: e.g., buildings with telecommunication equipment at the station's "support site" (cf. "technical site" with radar)[1]—15 major structures were complete in 1961[5] (i.e., Bldg 98 which was for the original BRCS)[6]
BMEWS tracking monitors in the Thule Tactical Operations Room

History

PAVE PAWS (blue) and BMEWS (red) sites and coverage

BMEWS General Operational Requirement 156 was issued on November 7, 1957 (BMEWS had originally been "designed to go with the active portion of the WIZARD system") and on February 4, 1958; the USAF informed Air Defense Command (ADC) that BMEWS was an "all-out program" and was "...being placed on the Department of Defense master urgency list."[7] On January 14, 1958, the US announced its "decision to establish a Ballistic Missile Early Warning System"[8]:{{{3}}} with Thule to be operational in 1959—total Thule and Clear Air Force Station costs in a May 1958 estimate were ~$800 million (an October 13, 1958, plan for both estimated completion in September 1960.)[9]:{{{3}}}

A World War II ship (freighter) operated by the Burns & Roe company[10] originally provided the Site J electrical and heating supplies until a powerplant was constructed years later,[11] and water was from Thule AB via a branch to the site.[12]

Construction

Kiewit was contracted for heavy construction (e.g., the AN/FPS-50 reflector foundations[13] and tunnels between transmitter buildings),[14]:{{{3}}} and construction began in May 1958[15]:{{{3}}} (a trial reflector installation failed due to ordinary carbon steel bolts instead of 1.5% chrome steel.)[14]:{{{3}}} The maintenance building with electric heat was the first building complete; and the four General Electric AN/FPS-50 Radar Set reflectors with 25-ton foundations were complete by August 8, 1959[14] ("two pedestals for trackers" were built for deferred radars.)[16] After the July 13, 1959, treaty No. 5045 with Canada regarding intermediate sites, [2] the Western Electric BMEWS Rearward Communications System (BRCS) was established between the "switchboard[where?] at Thule and the BMEWS Project Office in New York City"—a similar line between Thule and Massachusetts used a summer 1959 "submarine cable... between Thule and Cape Dyer"[17] ("BMEWS Rearward Long-Lines System"[18] stations were at CFS Resolution Island[19] & CFS Saglek.)[20] President Dwight D. Eisenhower was notified on April 23, 1960 of "construction work at Thule on schedule [and that] all technical buildings have been accepted and emplacement of the electronic components is underway [and] erection of the four radar antennas was completed",[21] and radar testing began on May 16, 1960[22]—a simplex vacuum tube IBM 709 used as the prototype Missile Impact Predictor (MIP) occupied 2 floors [3] (duplex IBM-709-TX solid-state computers of the Sylvania AN/FSQ-28 Missile Impact Predictor Set were later installed in Building 2.)[23] To predict when parts "might break down",[24] the contractor also installed a "Checkout Data Processor"[4]--RCA 501 computers [5] with 32k "high speed memory", 5-76KC 556 bpi 3/4" tape drives, & 200 track random access LFE drums.[citation needed] The initial radar transmission from one of the scanner buildings was in August 1960.[6]

RCA operations

On the same date as the BMEWS Central Computer and Display Facility in the US Zone of the Interior, "at midnight on 30 September 1960 ["BMEWS Site I"] achieved initial operational capability", and a "shakedown" period followed which used the simplex MIP and voice transmission of data to the Colorado Springs' CC&DF.[25]:{{{3}}}

False alarms
On October 5, 1960, when Nikita Khrushchev, the Soviet Premier, was in New York,[26] radar returns during Thule moonrise[27] produced a false alarm (on January 20, 1961, CINCNORAD approved 2-second FPS-50 frequency hopping to eliminate reception of echoes beyond artificial satellite orbits.)[28]:{{{3}}} On November 24, 1961, an AT&T operator error at their Black Forest Microwave Station northeast of Colorado Springs[29] caused a BMEWS communications outage to the Ent AFB CC&DF and its output to Strategic Air Command (a nearby B-52's overflight confirmed Site J had not been attacked.)[30]

The BRCS undersea cable from Greenland had been cut "presumably by fishing trawlers" in September, October, and November 1961 (the BMEWS teletype and backup SSB substituted)[31]:{{{3}}}--Hard Head[7] missions for continual monitoring commenced in 1961 [8] (the Bomb Alarm System had been installed at the Thule and Clear BMEWS sites by 10 February 1961.[9]:{{{3}}} After local interference (e.g., "cranes and floor waxers") and equipment problems were mitigated and a 72-hour test verified "the automatic rearward data transmission" (BRCS), the 1961 "authorization to begin fully automatic operation; effective 2400 hours GMT 31 January, was issued"[25]:{{{3}}} "Lt. Col. Harry J. Wills [was the] senior air force officer on the project at Thule" on January 3, 1961[32] ("BMEWS deputy program director" by 1964—he was reassigned from the BMEWS SPO to the "Space Track SPO"[9] on February 14, 1964.)[33]:{{{3}}}

Air Defense Command

Thule operations transferred from civilian contractors (RCA Government Services)[34] to Air Defense Command on January 5, 1962;[35] and 1962 sinkholes formed in the drainage ditch at "Scanner 6".[10] By mid-1962, BMEWS "quick fixes" for ECCM had been installed for Thule "to recognize when it was being jammed."[31]:{{{3}}}

An RCA AN/FPS-49A Radar Set with specialized radome for Thule weather[36] was installed by December 1963,[37] and Thule multipath testing was completed by May 1964.[38] In 1967 when the system cost totalled $1.259 billion, BMEWS modification testing ended on May 15 ("completion of the BMEWS");[33]:{{{3}}} and the Bomb Alarm System caused a false alarm during the 1968 Thule Air Base B-52 crash[11] (the system was deactivated in 1970.)[9]:{{{3}}} In June 1980, [12] Thule's FPS-49A radome by Goodyear[10]:{{{3}}} "burnt to the ground" and was rebuilt, [13] and a late 1960s satellite communications terminal was moved from the Thule P-Mountain site to Site J in 1983.[39] To replace AN/FSQ-28 predictors, a late 1970s plan for processing returns from MIRVs [14] installed new Missile Impact Predictor computers and was complete by September 1984.[33]:{{{3}}}[40] After being contracted for Thule on July 29, 1983; construction of an AN/FPS-120 Early Warning Radar was started on November 7, 1984, the "array plate" was complete on June 26, 1985, and the 1st satellite track was on June 8, 1986.[33]:{{{3}}}

Solid State Phased Array Radar

Thule's BMEWS radars were deactivated[41] in June 1987,[42] after being "replaced"[43] by the SSPARS AN/FPS-120 with "two-faced…phased array radar [completed] in 2QFY87" (January–March).[44] with 240 degree detection arc[45] The AN/FPS-49A was intact and in disrepair in 1996,[15]:{{{3}}} and the antenna and radome were removed by 2014.[15] In 2005 after the Danish parliament approved, [16] Raytheon was contracted to upgrade Thule's "Early Warning Radar" for a 2008 deployment of the Ground-Based Midcourse Defense program[3] (complete June 24, 2009).[17] Thule's AN/FPS-132 Upgraded Early Warning Radar (UEWR)[46] completes about 10% of the United States' observations of Earth orbiting satellites.[18]

External media
Images
image icon site construction
image icon 1961 Thule sketch, FPS-50 wave guides, & "memory and logic unit"
image icon 1961 BMEWS Rearward communications "billboard type" antenna
Video
video icon Eyes of the North

References

  1. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ 2.0 2.1 https://www.google.com/maps?q=76%C2%B034'08.4%22N+68%C2%B019'04.8%22W&ie=UTF8&ll=76.565223,-68.287067&spn=0.014657,0.104628&t=h&cid=0x0&z=14
  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. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ USAF memo to Air Defense Command cited in 1958 NORAD/CONAD Historical Summry, Jan–Jun
  8. ↑ Lua error in package.lua at line 80: module 'strict' not found. (list also at NORAD.mil & in 2008 book
  9. ↑ 9.0 9.1 9.2 Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ 10.0 10.1 Lua error in package.lua at line 80: module 'strict' not found.
  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. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ 14.0 14.1 14.2 Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ 15.0 15.1 Lua error in package.lua at line 80: module 'strict' not found.
  16. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found. (see also "DEWDROP Tropospheric Scatter AM Communications Link between Thule BMEWS and Cape Dyer")
  20. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  23. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  24. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  25. ↑ 25.0 25.1 Lua error in package.lua at line 80: module 'strict' not found.[specify]
  26. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  27. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  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. ↑ 31.0 31.1 Lua error in package.lua at line 80: module 'strict' not found.[specify] "CONAD Control Center (Thule AB, Greenland) ... During Desk Top V, an operational evaluation of the Combat Operations Center was conducted. ... At the start of the Cuban crisis, a Soviet trawler was sighted directly over the [BMEWS undersea] cable. ... BMEWS rearward communications could be substantially affected only by the simultaneous cutting of all cables."
  32. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  33. ↑ 33.0 33.1 33.2 33.3 Lua error in package.lua at line 80: module 'strict' not found.
  34. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  35. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  36. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  37. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  38. ↑ Wall, R. B. Test Plan for BMEWS Multipath Tests at Thule Air Base Greenland for 496 System Project Office, TM-4001, The MITRE Corp., May 1964
  39. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  40. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  41. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  42. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  43. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  44. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  45. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  46. ↑ Lua error in package.lua at line 80: module 'strict' not found.
Retrieved from "https://infogalactic.com/w/index.php?title=Thule_Site_J&oldid=693448252"