Western Range (USSF)
Page Module:Message box/ambox.css has no content.
 | This article focuses only on one specialiTemplate:Szed aspect of its subject. (July 2013) |
Template:United States space program sidebar Template:DMCA Template:DMCA
The Western Range (WR)Lua error in package.lua at line 80: module 'Module:Footnotes/anchor_id_list' not found. is the space launch range that supports the major launch head at Vandenberg Space Force Base.[1]Template:Rp Managed by the Space Launch Delta 30,[2]Template:Rp the WR extends from the West Coast of the United States to 90° east longitude in the Indian Ocean[2]Template:Rp where it meets the Eastern Range[3]Template:Rp Operations involve military, government, and commercial interests. The WR has been operated by civilian contractors since its establishment, following the precedent of the Eastern Range. On 1 October 2003, InDyne Inc. took over the range contract from ITT Industries which had operated the range for the previous 44 years.[4]
History
Navy's Pacific Missile Range (PMR)
The Navy established the Naval Missile Facility at Point Arguello (NMFPA) after the transfer from the Army of 19,800 acres from the southern portion of Camp Cooke in May 1958. Camp Cooke was a World War II training and POW facility and a maximum security Disciplinary Barracks site.Lua error in package.lua at line 80: module 'Module:Footnotes/anchor_id_list' not found. Cooke Air Force Base, later Vandenberg Space Force Base, was established on 64,000 acres of the northern portion.Lua error in package.lua at line 80: module 'Module:Footnotes/anchor_id_list' not found. The Secretary of Defense directed the Navy to establish the Pacific Missile Range (PMR) with headquarters at Point Mugu and instrumentation sites along the California coast and downrange in the Pacific Ocean.Lua error in package.lua at line 80: module 'Module:Footnotes/anchor_id_list' not found. Agreements between the Navy and the Air Force specified that nearly all launches from Vandenberg Space Force Base were under the command and control of Navy and the PMR.Lua error in package.lua at line 80: module 'Module:Footnotes/anchor_id_list' not found.
A Pacific Missile Impact Location System (MILS) was installed to support both Intermediate Range Ballistic Missile (IRBM) and Intercontinental Ballistic Missile (ICBM) tests. IRBM impacts were northeast of Hawaii and covered by a system terminating at the Marine Corps Air Station Kaneohe Bay operational November 1958. The ICBM impacts required MILS monitoring between Midway Island and Wake Island and between Wake Island and Eniwetok. Two target arrays and a Broad Ocean Area (BOA) array system were installed. The ICBM range was operational in May 1959 with two target arrays. MILS shore facilities were at Kaneohe and each of the islands.[5][6]
Air Force — Western Test Range
Secretary of Defense Robert S. McNamara directed a restructure of the missile ranges on 16 November 1963 with an effective date of 1 July 1964. This restructure shifted responsibility of major sections of the Navy's Pacific Missile Range to the United States Air Force.Lua error in package.lua at line 80: module 'Module:Footnotes/anchor_id_list' not found. In a final transfer, on 1 February 1965, the Air Force, with headquarters at Vandenberg Air Force Base, took control of Pillar Point, California, two sites in Hawaii, Canton Island, Midway Island, and Wake Island in the mid-Pacific as well as Eniwetok and Bikini Atoll in the Marshall Islands.Lua error in package.lua at line 80: module 'Module:Footnotes/anchor_id_list' not found. The Air Force also took control of the six range instrumented ships Huntsville, Longview, Range Tracker, Richfield, Sunnyvale, and Watertown.Lua error in package.lua at line 80: module 'Module:Footnotes/anchor_id_list' not found. The Navy retained a missile test facility at Point Mugu.Lua error in package.lua at line 80: module 'Module:Footnotes/anchor_id_list' not found. In 1979, the name was shortened to simply the Western Test Range.Lua error in package.lua at line 80: module 'Module:Footnotes/anchor_id_list' not found.
Notable launches
- 28 February 1959 - Discoverer 1 - first spacecraft placed in a polar orbit.Lua error in package.lua at line 80: module 'Module:Footnotes/anchor_id_list' not found.[7]
- 29 September 2013 – Falcon 9 Flight 6, the first launch of the Falcon 9 v1.1 launch vehicle from a privately developed leased launchpad at Vandenberg Air Force Base was used in an unusual post-mission launch vehicle test.[8] The first-stage booster of the SpaceX Falcon 9 launch vehicle will conduct a propulsive-return over-water test. After the second stage with the CASSIOPE payload separates from the booster, the booster will do a retro burn to reduce velocity from approximately Template:Cvt to a controllable descent velocity, and then a second burn just before it reaches the water to simulate a vertical landing of the first stage.[9] This will be the first high-altitude, high-velocity test of the SpaceX reusable launch system development program.
See also
References
Page Template:Reflist/styles.css has no content.
- ^ Page Module:Citation/CS1/styles.css has no content."Chapter 1: Eastern and Western Range Safety Policies and Processes 31 December 1999 Change to 1997 EWR" (PDF). Retrieved 31 August 2008.
- ^ a b Page Module:Citation/CS1/styles.css has no content.Center for Aerospace Technology (CAST) (February 2000). "30th SPACE WING / VANDENBERG AIR FORCE BASE LAUNCH SITE SAFETY ASSESSMENT" (PDF). Research Triangle Institute Center for Aerospace Technology (CAST). Federal Aviation Administration Associate Administrator for Commercial Space Transportation. Retrieved 31 August 2008.
- ^ Page Module:Citation/CS1/styles.css has no content.Loyd C. Parker; Jerry D. Watson; James F. Stephenson (July 1989). "BASELINE ASSESSMENT WESTERN SPACE AND MISSILE CENTER" (PDF). RESEARCH TRIANGLE INSTITUTE CENTER FOR SYSTEMS ENGINEERING FLORIDA OFFICE for U.S. DEPARTMENT OF TRANSPORTATION OFFICE OF COMMERCIAL SPACE TRANSPORTATION. Archived from the original (PDF) on 9 August 2016.
- ^ Page Module:Citation/CS1/styles.css has no content.Janene Scully (14 July 2003). "New leader of Western Range signed at VAFB" (PDF). Santa Maria Times. Pulitzer Central Coast Newspapers. Retrieved 2 June 2008.
- ^ Page Module:Citation/CS1/styles.css has no content.Subcommittee on Military Construction (March-April) (29 April 1959). Military Construction Appropriations for 1960: Hearings. pp. 169–170. Retrieved 16 September 2020.
- ^ Page Module:Citation/CS1/styles.css has no content.Subcommittee on Military Construction (May) (20 May 1959). Military Construction Appropriations for 1960: Hearings. pp. 818, 824. Retrieved 16 September 2020.
- ^ Page Module:Citation/CS1/styles.css has no content."NASA - NSSDC - Spacecraft - Details NSSDC ID: 1959-002A". Retrieved 31 August 2008.
- ^ Page Module:Citation/CS1/styles.css has no content.Foust, Jeff (27 March 2013). "After Dragon, SpaceX's focus returns to Falcon". NewSpace Journal. Retrieved 5 April 2013.
- ^ Page Module:Citation/CS1/styles.css has no content.Lindsey, Clark (28 March 2013). "SpaceX moving quickly towards fly-back first stage". NewSpace Watch. Archived from the original on 16 April 2013. Retrieved 29 March 2013.
Bibliography
Page Template:Refbegin/styles.css has no content.
- Page Module:Citation/CS1/styles.css has no content."Western Range (U)". Federation of American Scientists. Retrieved 16 June 2015.
- Page Module:Citation/CS1/styles.css has no content.Gruss, Mike (6 April 2015). "Raytheon Team Wins US$2 Billion Air Force Range Support Contract". SpaceNews. Retrieved 8 April 2015.
- Page Module:Citation/CS1/styles.css has no content.30th Space Wing History Office. "U.S. Air Force Fact Sheet". 30th Space Wing Public Affairs. Archived from the original on 10 January 2015. Retrieved 16 June 2015.
{{cite web}}: CS1 maint: numeric names: authors list (link)
- Western Test Range Handbook, Defense Technical Information Center, July 1981
