Recent from talks
Nothing was collected or created yet.
Vandenberg Space Force Base
View on Wikipedia
Key Information
| Part of a series on the |
| United States space program |
|---|
Vandenberg Space Force Base (IATA: VBG, ICAO: KVBG, FAA LID: VBG), previously Vandenberg Air Force Base, is a United States Space Force Base in Santa Barbara County, California. Established[3] in 1941, Vandenberg Space Force Base is a space launch base, launching spacecraft from the Western Range, and also performs missile testing. The United States Space Force's Space Launch Delta 30 serves as the host delta for the base, equivalent to an Air Force air base wing. In addition to its military space launch mission, Vandenberg Space Force Base also hosts space launches for civil and commercial space entities, such as NASA and SpaceX.
History
[edit]United States Army
[edit]Camp Cooke (1941–1953)
[edit]In 1941, just before the United States entered World War II, the United States Army embarked on an initiative to acquire lands in the United States to be used to train infantry and armored forces. These areas needed to be of a varied nature to ensure relevant training. In March 1941, the Army identified approximately 86,000 acres (35,000 ha) of open ranch lands along the Central Coast of California between Lompoc and Santa Maria. With its flat plateau, surrounding hills, numerous canyons, and relative remoteness from populated areas, the Army was convinced this portion of the Gaviota Coast was an ideal training location. The government purchased most of the land, however, some smaller parcels were obtained either by lease, license, or as easements.[4] The land was previously part of six ranchos: Casmalia, Guadalupe, Mission de la Purisima, Rancho Lompoc and Rancho Todos Santos y San Antonio, and Jesús María.[5]
Construction of the Army camp began in September 1941. Although unfinished, the camp was activated on the 5th of October and was named Camp Cooke in honor of Phillip St. George Cooke, a cavalry officer with a distinguished career spanning the Mexican War, Indian Wars, the Civil War.[4]
Troop training didn't wait for construction to finish. The 5th Armored Division was the first to arrive in February and March 1942. Throughout the war, Camp Cooke served as a training ground for numerous armored and infantry divisions before their deployment overseas. Additionally, anti-aircraft artillery, combat engineer, ordnance, and hospital units trained at Cooke. In total, over 400 groups passed through the camp.[4]
As the war progressed, Camp Cooke was used to house German and Italian prisoners of war. Following the Geneva Convention, the groups were kept separate and assigned various jobs within the camp, including construction, clerical work, food service, and laundry. To address wartime labor shortages, German prisoners also participated in agricultural work in nearby communities.[4][6]
After the war's conclusion in 1946, Camp Cooke became home to a maximum-security military prison, while most of the land was largely leased for agriculture and grazing. From 1950 to 1953, Camp Cooke served again as a training ground for units heading to the Korean War. In 1953, the camp was inactivated, and the military prison became a federal prison for civilians, now known as the United States Penitentiary, Lompoc.[4]
The final remaining buildings from Camp Cooke were demolished in 2010.[4]
Known United States Army Units at Camp Cooke
[edit]World War II
Korean War
United States Air Force
[edit]Cooke Air Force Base
[edit]As the 1950s ushered in the age of missiles, and the United States urgently needed a training ground that could also serve as an initial combat ready missile base. In 1956, after examining over 200 potential locations, a committee selected Camp Cooke. Similar to its appeal in 1941 for the Army, Camp Cooke's vast size, remoteness, moderate climate, and coastal location made it ideal. Missiles could be launched westward over the Pacific Ocean without flying over populated areas, and satellites could be placed into polar orbit towards the South Pole without traversing any landmass until reaching Antarctica.[4]
Following the committee's recommendation, on 16 November 1956, the Secretary of Defense directed the Army to transfer 64,000 acres (26,000 ha) to the United States Air Force. This land was initially called North Camp Cooke, but when the official transfer happened on 21 June 1957 it was named Cooke Air Force Base.
The first airmen of the 6591st Support Squadron arrived on 15 February, before the official transfer, and found the base in rough shape. World War II-era buildings were dilapidated, and roads needed extensive repair. Over the next two years, launch and control facilities emerged, old structures were renovated, and new housing was built. The initial mission of the base was to train personnel on the PGM-17 Thor, SM-65 Atlas, and HGM-25A Titan I missiles, while also serving as an emergency operational facility for the Atlas.[4][8]
The 1957 launch of Sputnik by the Soviet Union intensified the urgency of the U.S. missile program. In November, the Department of Defense authorized ballistic missile launches from Cooke AFB. Management responsibility shifted from the Air Research and Development Command (ARDC) to the Strategic Air Command (SAC) in January 1958. SAC assumed responsibility for training missile launch crews and achieving initial operational capability. ARDC retained oversight of site activation, research, and development testing. This began a close working relationship between the two commands that would last 35 years.[4]
In February 1958, the PGM-19 Jupiter program was transferred from the Army to the Air Force. SAC established squadrons for both the Jupiter and Atlas missiles at Cooke. Construction also began on the Operational System Test Facility for the Titan I. The first Thor missile arrived later that year.[4][8]
The southern 19,800 acres (8,000 ha) of Cooke AFB was transferred to the Navy in May 1958 for their Pacific Missile Range. However, in 1963, a restructuring returned major sections of this range, including Point Arguello, to the Air Force. This move gave the Air Force full responsibility for missile range safety at Vandenberg and much of the Pacific Ocean. The Air Force renamed the area the Western Range.[4]
Vandenberg Air Force Base
[edit]
The facility was renamed Vandenberg Air Force Base on 4 October 1958 in honor of General Hoyt Vandenberg, the Air Force's second Chief of Staff.[4]
The final acquisition of 15,000 acres (6,100 ha) of land for the base occurred in 1966 to accommodate the construction of Space Launch Complex 6 for the Manned Orbiting Laboratory program. With the annexation, the base reached its final size, 99,099 acres (40,104 ha).
Ballistic missile testing
[edit]PGM-17 Thor
[edit]
The transition from U.S. Army camp to missile base solidified on 15 December 1958 when Vandenberg AFB successfully launched its first missile, a PGM-17 Thor IRBM (Intermediate Range Ballistic Missile). The launch from Vandenberg inaugurated the intermediate-range ballistic missile portion of the Pacific Missile Range and was fired by a crew from the 1st Missile Division. The first successful launch of a Thor IRBM by a Royal Air Force crew took place at Vandenberg AFB on 16 April 1959. The launch was part of integrated weapon system training. In October 1959, the first combat training launch of a Thor IRBM by a Royal Air Force crew was successful.
On 22 April 1960, the fourth and final British-based Thor IRBM squadron was turned over to the Royal Air Force by the Strategic Air Command, thus completing the deployment of this weapon system in the United Kingdom. The next month, the first missile to be removed from an operational unit and sent to Vandenberg AFB for confidence firing arrived from a Thor IRBM squadron (No. 98 Squadron RAF) in the United Kingdom. Confidence firing was the predecessor of SAC's operational test program.[4][8]
SM-65 Atlas
[edit]
On 16 October 1958, the first Atlas ICBM launcher (576A-1) constructed at Vandenberg AFB, California, was accepted from the contractor by the 1st Missile Division. The first intercontinental ballistic missile, the SM-65D Atlas ICBM, was delivered and was accepted by SAC's 576th Strategic Missile Squadron on 18 February 1959. The first Atlas-D flew on 9 September 1959, and following the successful launch, General Thomas S. Power, CINCSAC, declared the Atlas ICBM to be operational. The following month, equipped with a nuclear warhead, the Atlas at Vandenberg became the first ICBM to be placed on alert in the United States. It was an SM-69D Atlas ICBM (AFSN 58-2190) on launcher 576A-1. In April 1960, the first attempted launch of a Series D Atlas ICBM from a coffin-type launcher (576B-2) was successful. This launcher was the prototype of the ones to be used at the first operational Atlas squadron, the 564th Strategic Missile Squadron, Francis E. Warren Air Force Base, Wyoming. Following this successful launch, Major General David Wade, Commander of the 1st Missile Division, declared the coffin-type launcher to be operational.[8]
In July 1959, construction began on the first Series E Atlas ICBM coffin-type launcher (Atlas operational system test facility #1). On 28 February 1962, the first successful launch of the SM-65E Atlas took place. Construction began on the first SM-65F Atlas ICBM "silo-lift" launcher (Atlas operational system test facility #2) in November 1962. The first Atlas F arrived in June 1961 and the first operationally configured Series F Atlas was successfully launched on 1 August 1962.[8]
During its testing phase, Vandenberg would operate two Atlas-D launch complexes; two Atlas-E, and three Atlas-F silos.[9] The Atlas-Ds were taken off alert at the 576th Strategic Missile Squadron (Complex 576B) in May 1964 as part of the phaseout of the Atlas from active ICBM service. The last Atlas F test launch was on 18 January 1965, and the 576th Strategic Missile Squadron was inactivated on 2 April 1966. The 576th SMS carried out 53 Atlas-D, 7 Atlas-E and 7 Atlas-F test launches between 1959 and 1965.[8]
The Atlas would remain in use as a launch vehicle for satellites from Vandenberg as a space booster configured with an RM-81 Agena upper-stage rocket and the Atlas-Agena would launch many different types of satellites into orbit until its phaseout in the late 1980s.[4]
HGM-25A Titan I
[edit]
The HGM-25A Titan I was the United States' first multistage ICBM. When designed and manufactured, the Titan I provided an additional nuclear deterrent to complement the U.S. Air Force's SM-65 Atlas missile. It was the first in a series of Titan rockets, and was an important step in building the Air Force's strategic nuclear forces.
In July 1958, construction began on the Titan I ICBM Operational System Test Facility (OSTF). This was the prototype of the hardened Titan I launch control facility at its operational sites. It consisted of one silo-lift launcher, blockhouse, and associated equipment. Designated "OSTF-8", the facility was destroyed on 3 December 1960 when the launcher elevator failed while lowering a fully fueled missile back into the silo. There were no injuries. This was the first silo accident at Vandenberg.[8]
The first "silo-lift" launch of the Titan I was successful in September 1961, and the first SAC launch of the ICBM was successful in January 1962. As a result, the Titan I ICBM launch complex (395-A1/A2/A3) at Vandenberg was turned over to the Strategic Air Command 395th Strategic Missile Squadron to perform test launches of the missile.[8]
However, the operational lifetime of the Titan I was short, as Secretary of Defense McNamara announced in November 1964 that all remaining first-generation ICBMs (Series E and F Atlas and Titan I) would be phased out (Project Added Effort) by the end of June 1965.[8]
On 5 March 1965, the last test launch of a Titan I ICBM conducted by the Strategic Air Command at Vandenberg was successful. The 395th SMS performed 19 test launches between 1963 and 1965 before moving on to exclusively Titan II testing. During the 1980s, some Titan I second stages were used as targets for early Strategic Defense Initiative (SDI) testing.[8]
LGM-25C Titan II
[edit]
The LGM-25C Titan II ICBM was a second-generation ICBM with storable propellants, all inertial guidance, and in-silo launch capability. Construction of the first Titan II site began in 1962, and eventually Vandenberg operated four Titan II launch complexes.[10][8]
Most of the testing of the missile was done at Cape Kennedy Air Force Station, Florida by the 6555th Aerospace Test Group, and the first successful underground silo launch of a Titan II ICBM took place at Vandenberg by the 395th SMS in April 1963. The first fully operational test took place in March 1965.[8]
On 25 March 1966, the 200th SAC missile launched from Vandenberg AFB, California was a Titan II. The operational testing of the Titan II continued until 1985.[8] Like its predecessor the Atlas ICBM, the Titan II GLV a derivative of that missile was used to launch Project Gemini spacecraft and the Titan 23G was used as a space booster to launch satellites. The final launch of a Titan II was made in 2003 when the last Titan IIG was expended.[4]
LGM-30 Minuteman
[edit]
The advent of solid-propellant gave the three-stage LGM-30 Minuteman ICBM a major advantage over earlier liquid propellant ICBMs. In February 1961, the construction began on Minuteman ICBM test launch facilities at Vandenberg. Silos 394A-1 through A-7 were the first constructed for use by the SAC 394th Strategic Missile Squadron.[11][4][8]
LGM-30A Minuteman IA flight tests began in September 1962. The first Minuteman IB test took place in May 1963. On 24 February 1966, the first attempted salvo (simultaneous) launch of two model "A" Minuteman I ICBMs from Vandenberg silos LF-04 (394A-3) and LF-06 (394-A5) was successful. This launch demonstrated the multiple countdown and launch techniques that would be used at operational bases under actual combat conditions. Minuteman I testing continued until 1968.[11][8]
LGM-30F Minuteman II testing began in August 1965 with the first launch conducted by Air Force Systems Command, was successful. The missile flew 5,000 mi (8,000 km) down the Pacific Missile Range and its reentry vehicle impacted in the target area.[8]
On 22 October 1970, the first attempted OT GT70F (Salvo) operational test launch (simultaneous) launch of two Minuteman II ICBMs was successful from LF-25 and LF-26. The last Minuteman II phase I operational test was performed in April 1972.[8][12]
The first LGM-30G Minuteman III phase II operational test was launched on 5 December 1972 from the LF-02 silo. The ICBM flew 800 mi (1,300 km) downrange before impacting in the Pacific Ocean. This was the beginning of Minuteman III launches which continue to this day from Vandenberg.[8]
In July 1974, the initial training of Minuteman missile combat crews, formerly performed by Air Training Command (ATC) instructors at Vandenberg AFB, California, was incorporated into the 4315th Combat Crew Training Squadron's Operational Readiness Training (ORT) program at Vandenberg. As a result of this action, the entire Minuteman missile combat training, from beginning (initial training) to end (upgrade training) became the responsibility of Strategic Air Command.[8]
SAC launched two Minuteman III ICBMs from Vandenberg AFB during exercise Global Shield, a comprehensive exercise of SAC's nuclear forces on 10 July 1979 from LF 08 and LF 09. One of these Global Shield missions, Glory Trip 40 GM, was the last Minuteman III phase I operational test flight. The missiles were launched 12 seconds apart by a SAC task force from the 90th Strategic Missile Wing, Francis E. Warren Air Force Base, Wyoming.[8]
Glory Trip 77GM, a Minuteman III Operational Test in September 1980, became the longest Minuteman flight test when its payload impacted a broad ocean area target over 5,600 nmi (10,400 km) downrange.[8]
LGM-118 Peacekeeper
[edit]
The last ICBM tested from Vandenberg was the LGM-118 Peacekeeper (MX) ICBM beginning in June 1983. In addition to having a longer range than earlier ICBMs, the Peacekeeper could deliver up to 10 reentry vehicles to separate targets.[4] It was intended as a replacement for the LGM-30 Minuteman, but it suffered from a long development time, and was retired in 2005 before the Minuteman because of arms reduction treaties.
The first Peacekeeper ICBM was launched by Air Force Systems Command from an above ground canister-type launch facility from Launch Complex TP-01 on 17 June 1983. This was the first "cold launch" of a missile at Vandenberg AFB, the missile reaching 600 mi (970 km) downrange. Two more test launches were conducted in 1983 from Launch Complex TP-01.[8][13]
The first Peacekeeper with a Mark-21 test reentry vehicle was flight-tested from TP-01 on 15 June 1984. The Mark-21 resembled the reentry vehicle intended for the Peacekeeper weapon system. Two more test launches were conducted in 1984, the missile from TP-01. Air Force Systems Command conducted the final Peacekeeper launch from the above-ground TP-01 launch pad on 30 June 1985.[8][13]
The first silo launch from LF-05 took place on 24 August 1985 from LF-08. LF-02 began to be used in 1986 for additional launches. On 23 August 1986 the first launch of a completely operational hardware configured missile and launch facility, and also the first Peacekeeper launch by a SAC combat crew under the control of Air Force Systems Command took place from silo LF-02.[8][13]
A new Peacekeeper Missile Procedures Trainer was dedicated in March 1987. The US$17 million facility featured a state-of-the-art computer based simulator which would be used to train and evaluate missile crew members. The first LGM-118 Peacekeepers were deployed to Francis E. Warren Air Force Base in Wyoming that year.[8][13] LGM-118 Peacekeeper test launches continued from Vandenberg with a third silo, LF-05 becoming operational in March 1990. The final launch of a LGM-118 Peacekeeper 33PA took place on 21 July 2004 before the missile was retired from service.[8][13]
Ground-Based Midcourse Defense Interceptor
[edit]
The latest missile deployed at Vandenberg in 2005 is the Ground-based Interceptor (GBI) missile suborbital booster for the U.S. Missile Defense Agency's Ground-based Midcourse Defense system's EKV ballistic missile kill vehicle. It is part of a National missile defense system advocated by President George W. Bush. The OBV is under development by Orbital Sciences; for every interceptor missile there is a missile silo and a Silo Interface Vault (SIV), which is an underground electronics room adjacent to the silo.[4] The basic OBV consists of the upper three stages and guidance system from the Taurus orbital launch vehicle (essentially a wingless Pegasus-XL). The developmental OBV is launched from an open pad; the operational version is to be silo-launched.[14]
The first test firing of the OBV took place from former Atlas-F pad 576-E on 6 February 2003. Launch silo LF-23 is used for ongoing silo testing, with target missiles consisting of surplus inert Minuteman ICBM second and third stages being launched from the Kwajalein Meck launch site in the Pacific Range.[14][15]
Early space exploration
[edit]The world's first polar orbit satellite, Discoverer 1, launched from Vandenberg on 28 February 1959. The launch vehicle for this mission consisted of a Thor-Agena combination.[4] The Discoverer series of satellites provided other significant firsts for Vandenberg. For instance, in August 1960, the data capsule was ejected from Discoverer XIII in orbit and recovered from the Pacific Ocean to become the first man-made object ever retrieved from space. A week later, on 19 August 1960, the descending capsule from Discoverer XIV was snared by an aircraft in flight for the first air recovery in history.[4] Shrouded in a cover story of scientific research, Discoverer was actually the cover name for CORONA, America's first photo reconnaissance satellite program. The publicized Discoverer series came to an end on 13 January 1962 after 38 launches (or launch attempts).[4]
Over the years, satellites of every description and purpose, including international satellites, were placed in orbit from Vandenberg by a widening variety of boosters. Among the parade of newer space boosters are the Titan IV (March 1991), Taurus (March 1994), Pegasus (April 1995), Delta II (February 1996), Atlas IIAS (December 1999), Minotaur (2000), and beginning in late 2005, the Falcon 1, the Delta IV, and Atlas V vehicles.[4]
The most ambitious Air Force endeavors at Vandenberg were the Manned Orbiting Laboratory (MOL) and the Space Shuttle programs. The MOL vehicle consisted of a Titan III booster carrying a modified Gemini space capsule (Gemini B) attached to a space laboratory. Construction work for MOL began at Space Launch Complex-6 (SLC-6) on South Vandenberg in March 1966. President Richard Nixon canceled the estimated US$3 billion program in June 1969, as a result of cost overruns, completion delays, emerging new technologies, and the expense of fighting the Vietnam War. SLC-6 remained closed for the next decade.[4]
Space Shuttle
[edit]
In 1972, Vandenberg was selected as the West Coast Space Shuttle launch and landing site, but it was never used as such.
Space Launch Complex-6 (SLC-6, pronounced as "Slick Six"), originally built for the abandoned Manned Orbital Laboratory project, was extensively modified for shuttle operations. Over US$4 billion was spent on the modifications to the complex and construction of associated infrastructure. The original Mobile Service Tower (MST) was lowered in height and two new flame ducts were added for the shuttle's solid rocket boosters. Additional modifications or improvements, included liquid hydrogen and liquid oxygen storage tanks, a payload preparation room, payload changeout room, a new launch tower with escape system for the shuttle crewmembers, sound suppression system and water reclamation area and a Shuttle Assembly Building were added to the original complex.
The existing 8,500-foot (2,590 m) runway and overruns on the North Base flightline were lengthened to 15,000 feet (4,580 m) to accommodate end-of-mission landings, along with construction of the Precision Approach Path Indicator (PAPI) lights/large triangle arrows at both ends of the runway. Turn-around servicing and refurbishing of the Space Shuttle orbiter would be accomplished in the adjacent Orbiter Maintenance and Checkout Facility (OMCF). The Mate-Demate Facility, to load and unload the Orbiter from the Boeing 747 Shuttle Carrier Aircraft (SCA), was changed from the large structure found at Dryden Flight Research Center and Kennedy Space Center, to a transportable "erector set-like" Orbiter Lifting Frame (OLF). This facility design change was due to the possibility of needing to support a landing at a location where there was no facility to load the Orbiter onto the SCA. The OLF could be disassembled, loaded onto two C-5 aircraft, shipped to the overseas Orbiter landing site, and reassembled to load the Orbiter onto the Boeing 747. To transport the Orbiter from the OMCF (on North Vandenberg AFB) to SLC-6, the 22 mi (35 km) route was upgraded to accommodate a 76-wheeled vehicle, built by Commetto in Italy specifically to carry the Orbiter on its large flat deck utilizing the three external tank interface points, versus towing the Orbiter on its landing gear that long distance.
Modification of SLC-6 to support polar missions had been problematic and expensive.[citation needed] SLC-6 was still being prepared for its first Shuttle launch, mission STS-62-A targeted for 15 October 1986, when the Challenger disaster grounded the Shuttle fleet and set in motion a chain of events that finally led to the decision to cancel all west coast shuttle launches. The orbiter transporter was sent to Kennedy Space Center in Florida after the Vandenberg AFB launch site was abandoned and was used to transport the Orbiter from the Orbiter Processing Facility to the Vehicle Assembly Building.
Persistent site technical problems and a joint decision by the Air Force and NASA to consolidate Shuttle operations at the Kennedy Space Center, following the Challenger disaster in 1986, resulted in the official termination of the Shuttle program at Vandenberg on 26 December 1989.
Had the space shuttle program been successful at SLC-6, the West Coast operation would have contrasted with that at the Kennedy Space Center by creating the orbiter stack directly on the launch pad, rather than assembling it and then moving it. Three movable buildings on rails, the Launch Tower, Mobile Service Building and Payload Changeout Room were used to assemble the Shuttle orbiter, external tank and SRBs. These buildings were designed to protect the shuttle "stack" from high winds in the area and were used during a series of "fit tests" utilizing the space shuttle Enterprise in 1985.
Delta IV
[edit]After the end of the shuttle program at Vandenberg in 1989, SLC-6 was reconfigured in 1999 to support polar-orbit satellite launches by the new Delta IV family of launch vehicles, utilizing a Common Core Booster for all its class sizes including the Delta IV (Heavy) launcher. After the reconfiguration, the 132 acres (53 ha) launch site included structures similar to those at the Delta IV launch site at Cape Canaveral Space Launch Complex 37 (SLC-37B) in Florida, with a Fixed Umbilical Tower, Mobile Service Tower, Fixed Pad Erector, Launch Control Center and Operations Building, and a Horizontal Integration Facility. SLC-6 also featured a Mobile Assembly Shelter that protects the rocket from adverse weather.
The first of the Delta IV launch vehicles to fly from SLC-6 successfully lifted off at 20:33 PDT on 27 June 2006 when a Delta IV Medium+ (4,2) rocket lofted NROL-22, a classified satellite for the National Reconnaissance Office, into orbit. The payload was successfully deployed approximately 54 minutes later.[16] ten Delta IVs were launched from SLC-6, with the last launching in 2022 before the site was relinquished to SpaceX.
Atlas V
[edit]The Atlas V was developed by Lockheed Martin as part of the United States Air Force (USAF) Evolved Expendable Launch Vehicle (EELV) program. The Atlas V launches from Space Launch Complex-3E (SLC-3E). Lockheed Martin Commercial Launch Services markets the Atlas V to government and commercial customers worldwide.[17]
The first Atlas V launch vehicle to fly from SLC-3E was launched on 19 March 2008 for the National Reconnaissance Office (NRO).[18]
All Atlas V launches from Vandenberg have been successful.
SpaceX Falcon
[edit]
SpaceX briefly used SLC-3W during the early development of the Falcon 1 launch vehicle,[19][20] and later moved operations to Space Launch Complex 4-East (SLC-4E). SpaceX refurbished SLC-4E for Falcon 9 launches in a 24-month process that began in early 2011.[21] The draft environmental impact assessment with a finding of "no significant impact" was published in February 2011.[21] Demolition began on the pad's fixed and mobile service towers in summer 2011.[22]
By late 2012, SpaceX continued to anticipate that the initial launch from the Vandenberg pad would be in 2013, but would be a Falcon 9 launch—actually a heavily modified and much larger Falcon 9 v1.1.[23] As the pad was nearing completion in February 2013, the first Falcon 9 launch was scheduled for summer 2013[24] and was finally launched on 29 September 2013. This was the maiden flight of the Falcon 9 v1.1 evolution, carrying Canada's CASSIOPE satellite.[25] In October 2018, SpaceX landed a Falcon 9 booster on a Vandenberg ground pad for the first time.[26]
In April 2023, SpaceX leased SLC-6 to begin converting it and adding two first stage landing pads for Falcon 9 and Falcon Heavy launches after the last Delta IV launch there.[27] SpaceX expects to begin Falcon 9 launches from SLC-6 in 2025 and Falcon Heavy launches in 2026.[28]
Boeing X-37B
[edit]The Boeing X-37B, a reusable uncrewed spacecraft operated by the Space Force, also known as the Orbital Test Vehicle (OTV), has landed at Vandenberg in the past.[29] On 3 December 2010, the X-37B spaceplane successfully landed at the base after 224 days in space thus performing the first autonomous orbital landing onto a runway conducted by a U.S. spacecraft. Since then, the X-37B has successfully landed on the 15,000-foot runway at Vandenberg two more times, on 16 June 2012 after 468 days in orbit and again on 14 October 2014 after 674 days in orbit. All of the X-37B missions thus far have been launched from Florida, the first four using expendable Atlas V rockets from Cape Canaveral Space Force Station and the fifth on a reusable SpaceX Falcon 9 from Kennedy Space Center.
Major commands to which assigned
[edit]- Air Research and Development Command, 21 June 1957
- Strategic Air Command, 1 January 1958
- Air Force Space Command, 15 January 1991 – 20 December 2019[30]
- Space Operations Command, 20 December 2019 – present
Major units assigned
[edit]- 1st Strategic Aerospace Division, 16 July 1957 – 1 September 1991
- 392d Strategic Missile Wing, 18 October – 20 December 1961
- Space and Missile Test Center, 1 April 1970 – 1 July 1980
- Air Force Space Test Center, Provisional, 2 January – 15 May 1964
- Air Force Western Test Range, 5 May 1964 – 1 April 1970
- Redesignated Western Space and Missile Center, 1 October 1979
- Redesignated 30th Space Wing, 1 November 1991 – present
- 704th Strategic Missile Wing (ICBM), 1 July 1957 – 1 July 1959
- 6565th Test Wing, 20 October 1960
- Redesignated 6595th Aerospace Test Wing, 1 April 1961 – 1 October 1979
- 10th Aerospace Defense Group, 1 January 1967 – 31 December 1971 (Aerospace Defense Command)
- 30th Launch Group, 1 December 2003 – present
- 30th Operations Group, 19 November 1991 – present
- 6595th Missile Test Group, 1 May 1970 – 1 October 1990
- 6595th Space (later Satellite, later Aerospace) Test Group, 1 May 1970 – 1 October 1990
- 6595th Space Transportation (later Shuttle) Test Group, 21 May 1979 – 30 September 1987
- 2d Space Launch Squadron, 19 November 1991 – 31 October 2005; 1 June 2019 – present
- 4th Space Launch Squadron, 15 April 1994 – 29 June 1998; 1 December 2003 – 31 May 2019
- 10th Aerospace Defense Squadron, 15 November 1963 – 1 January 1967; 31 December 1970 – 1 November 1979
- 394th Missile Testing Squadron (ICBM-Atlas), 1 April – 15 December 1958
- 394th Strategic Missile Squadron (ICBM-Titan), 1 July 1960 – 30 June 1976
- Redesignated 394th Test Maintenance Squadron, 1 July 1976
- Redesignated 394th Operational Missile Maintenance Squadron, 1 September 1991
- Redesignated 394th Field Missile Maintenance Squadron, 1 September 1994 – present
- 395th Strategic Missile Squadron (ICBM-Titan), 1 February 1959 – 31 December 1969
- 576th Strategic Missile Squadron (ICBM-Atlas), 1 April 1958 – 2 April 1966
- Redesignated 576th Flight Test Squadron, 1 September 1991 – present
- Assigned to Air Force Global Strike Command, 1 December 2009 – present
- 644th Strategic Missile Squadron, 15 January – 1 November 1959
- 670th Aircraft Control and Warning Squadron, 5 May 1950 – 2 August 1951
- 4315th Combat Crew Training Squadron, 1 May 1958 – 15 January 1991
United States Space Force
[edit]
On 14 May 2021, the base was renamed Vandenberg Space Force Base, in keeping with the expansion and standing up of the Space Force.[33]
As of March 2025, the Space Force has activated the Site Activation Task Force (SATAF) Detachment to modernize the nation's nuclear defence capabilities, preparing to replace the Minuteman III ICBM fleet with the newly developed LGM-35A Sentinel.[34]
Role and operations
[edit]The host unit at Vandenberg SFB is the Space Launch Delta 30 (SLD 30). The unit oversees the Western Range, a vast testing area stretching from Vandenberg's coast westward to the Western Pacific, including sites in Hawaii. This range facilitates Department of Defense space and missile testing, including launches that place satellites into near-polar orbits. Their operations involve collaboration with a multitude of federal agencies and commercial partners.
SLD 30 is organized into operations, mission support and medical groups, along with several directly assigned staff agencies:
- The 30th Operations Group provides the core capability for West Coast spacelift and range operations. The group is responsible for operating and maintaining the Western Range for spacelift, missile test launch, aeronautical and space surveillance missions.
- The 30th Mission Support Group is responsible for quality-of-life needs on the base, including, housing, personnel, services, civil engineering, contracting and security.
- 30th Medical Group
- The 30th Medical Group provides medical, dental, bio-environmental and public health services for the base.
Space and Missile Heritage Center
[edit]The Space and Missile Heritage Center is located at Space Launch Complex 10, site of the first IRBM tests of the Thor[35] which went on to launch the Discoverer (aka CORONA) spy satellite series of launches.[36] It is Vandenberg's only National Historic Landmark that is open for regularly scheduled tours through the 30th Space Wing's Public Affairs office. The Center preserves and displays artifacts and memorabilia to interpret the evolution of missile and spacelift activity at Vandenberg from the beginning of the Cold War through current non-classified developments in military, commercial, and scientific space endeavors.[37]
The current display area is made up of two exhibits, the "Chronology of the Cold War" and the "Evolution of Technology". The exhibits incorporate a combination of launch complex models, launch consoles, rocket engines, re-entry vehicles, audiovisual and computer displays as well as hands-on interaction where appropriate. There are plans to evolve the center in stages from the current exhibit areas as restorations of additional facilities are completed.
Based units
[edit]Notable units based at Vandenberg Space Force Base.[38] Units marked GSU are Geographically Separate Units, which although based at Vandenberg, are subordinate to a parent unit based at another location.
United States Space Force[edit]Space Systems Command (SSC)
Space Training and Readiness Command (STARCOM)
Space Operations Command (SpOC)
|
United States Air Force[edit]Air Education and Training Command (AETC)
Air Force Global Strike Command (AFGSC) Air National Guard[edit]
Department of Defense[edit]
|
Geography
[edit]
Much of the base is rugged, mountainous, and undeveloped; predominant groundcover includes chaparral with coastal sage scrub and oak woodland. Because of its protected nature—none of the backcountry areas are open to the public or to any kind of development—the base contains some of the highest quality coastal habitat remaining in southern or central California. It is home to numerous threatened or endangered species, including Gambel's watercress (Nasturtium gambellii).[39] The western terminus of the Santa Ynez Mountains is on the base, and is dominated by Tranquillion Peak, which rises 2,297 ft (700 m) above sea level. An optical tracking station is located at the top of the peak, which overlooks the various space launch complexes. The Amtrak Coast Starlight and Pacific Surfliner trains travel along the coast, providing a splendid view and one of the few ways for the public to see these remote areas. Conversely, State Route 1, California's Pacific Coast Highway, avoids these coastal protected areas and instead turns inland to serve the base's eastern side. The Breeze Bus provides service between the base, Santa Maria, and Lompoc.
Beaches
[edit]Surf Beach is open to the public, while Wall and Minuteman beaches are restricted to those with regular access to the base. Sections of these three beaches are closed between 1 March and 30 September every year during the nesting season of the Western Snowy Plover.[40] The closures are in place to protect the bird under the Endangered Species Act. If a set number of trespass violations have been reached during any nesting season (50 for Surf, 10 for Wall, 10 for Minuteman), the beach is closed entirely.[41]
Surf Beach is adjacent to the Surf Amtrak station, just south of Ocean Beach Park, run by the Santa Barbara County Parks Division.[42] On 22 October 2010, 19-year-old Lucas Ransom, a University of California, Santa Barbara (UCSB) student, was killed by a great white shark near Surf Beach.[43] On 23 October 2012, 38-year-old Francisco Javier Solorio Jr. was killed by a shark near Ocean Beach.[44]
Wildlife
[edit]Snowy plovers nest on the beach.[45]
Demographics
[edit]Vandenberg Space Force Base | |
|---|---|
| Country | United States |
| State | California |
| County | Santa Barbara |
| Elevation | 505 ft (154 m) |
| Population (2020) | |
• Total | 3,559 |
| Time zone | UTC-8 (Pacific) |
| • Summer (DST) | UTC-7 (PDT) |
| GNIS feature ID | 2409501 |
| U.S. Geological Survey Geographic Names Information System: Vandenberg Space Force Base | |
The United States Census Bureau has designated Vandenberg Space Force Base as a separate census-designated place (CDP) for statistical purposes, covering the base's residential population. Per the 2020 census, the population was 3,559.[47] The CDP was formerly known as Vandenberg Air Force Base, reflecting the base's former name.
| Census | Pop. | Note | %± |
|---|---|---|---|
| 1970 | 13,193 | — | |
| 1980 | 8,136 | −38.3% | |
| 1990 | 9,846 | 21.0% | |
| 2000 | 6,151 | −37.5% | |
| 2010 | 3,338 | −45.7% | |
| 2020 | 3,559 | 6.6% | |
| U.S. Decennial Census[48] 1850–1870[49][50] 1880-1890[51] 1900[52] 1910[53] 1920[54] 1930[55] 1940[56] 1950[57] 1960[58] 1970[59] 1980[60] 1990[61] 2000[62] 2010[63] 2020[64] | |||
| Race / Ethnicity | Pop 2000[65] | Pop 2010[66] | Pop 2020[64] | % 2000 | % 2010 | % 2020 |
|---|---|---|---|---|---|---|
| White alone | 4,198 | 2,005 | 1,851 | 68.25% | 60.07% | 52.01% |
| Black or African American alone | 686 | 285 | 314 | 11.15% | 8.54% | 8.82% |
| Native American or Alaska Native alone | 25 | 8 | 14 | 0.41% | 0.24% | 0.39% |
| Asian alone | 233 | 197 | 215 | 3.79% | 5.90% | 6.04% |
| Pacific Islander alone | 40 | 20 | 36 | 0.65% | 0.60% | 1.01% |
| Other Race alone | 23 | 9 | 20 | 0.37% | 0.27% | 0.56% |
| Mixed Race or Multi-Racial | 263 | 198 | 309 | 4.28% | 5.93% | 8.68% |
| Hispanic or Latino (any race) | 683 | 616 | 800 | 11.10% | 18.45% | 22.48% |
| Total | 6,151 | 3,338 | 3,559 | 100% | 100% | 100% |
See also
[edit]- Point Arguello Light
- Canyon Fire – a 2016 wildfire that burned over 12,500 acres (51 km2) on the base.[67]
References
[edit]- ^ "About Us".
- ^
One or more of the preceding sentences incorporates text from this source, which is in the public domain: "Airport Diagram – Vandenberg AFB (KVBG)" (PDF). FAA. 10 October 2019. Retrieved 2 November 2019.
- ^ "Vandenberg SFB Base Guide". Military.com. Retrieved 14 August 2025.
- ^ a b c d e f g h i j k l m n o p q r s t u v w
One or more of the preceding sentences incorporates text from this source, which is in the public domain: "Vandenberg AFB history office fact sheet". Vandenberg.af.mil. Archived from the original on 27 September 2011. Retrieved 31 March 2013.
- ^ "Judith Dale: Vandenberg Air Force Base – into the future, a look at the past". 22 August 2020.
- ^ "Camp Cooke". 20 May 2006. Archived from the original on 20 May 2006. Retrieved 1 November 2019.
- ^
One or more of the preceding sentences incorporates text from this source, which is in the public domain: "Historic Posts, Camps, Stations and Airfields: Camp Cooke by Jeffrey Geiger Chief, Office of History, 30th Space Wing". Militarymuseum.org. 1 February 1953. Archived from the original on 27 March 2013. Retrieved 31 March 2013.
- ^ a b c d e f g h i j k l m n o p q r s t u v w x y z "SAC Missile Chronology 1 May 1990 Office of the Historian, Strategic Air Command". Alternatewars.com. Archived from the original on 3 March 2016. Retrieved 31 March 2013.
- ^ "Atlas Missile Silo Coordinates". Techbastard.com. Retrieved 31 March 2013.
- ^ "Titan II Missile Silo Coordinates". Techbastard.com. Retrieved 31 March 2013.
- ^ a b "Vandenberg Air Force Base Launch sites". asuwlink.uwyo.edu. Archived from the original on 25 July 2012. Retrieved 31 March 2013.
- ^ "Minuteman II". Astronautix. Archived from the original on 22 May 2013. Retrieved 31 March 2013.
- ^ a b c d e "Martin Marietta LGM-118 Peacekeeper". Astronautix. Archived from the original on 6 October 2007. Retrieved 31 March 2013.
- ^ a b "OBV". Astronautix. 15 December 2010. Archived from the original on 22 May 2013. Retrieved 31 March 2013.
- ^ "Kwajalein Meck launch site". Astronautix.com. Archived from the original on 22 May 2013. Retrieved 31 March 2013.
- ^ Bergin, Chris (27 June 2006). "Delta IV - NROL-22 launch success". Retrieved 14 September 2023.
- ^ "Lockheed Martin Ready For Launch of Intelsat 14 Spacecraft". Lockheed Martin. 11 November 2009. Archived from the original on 17 December 2011.
- ^ "Atlas V launch successful". Vandenberg Air Force Base. 19 March 2008. Archived from the original on 25 January 2012.
- ^ NASASpaceflight.com Forum > General Space Flight (Atlas, Delta, ESA, Russian, Chinese) > Commercial Launchers (Space X, Sea Launch, etc.) > Topic: Elon Musk Q&A – Updates SpaceX status on Falcon and Dragon > Reply #2554
- ^ Federal Register /Vol. 73, No. 245 / Friday, 19 December 2008 / Proposed Rules, page 77579.
- ^ a b Scully, Janene (5 February 2011). "Report: Falcon plan OK for environment". Santa Maria, California: Santa Maria Times. Retrieved 7 February 2011.
- ^ "SpaceX News". SpaceX. 15 August 2011. Archived from the original on 10 August 2011. Retrieved 15 August 2011.
- ^ "SpaceX Gears Up for Launches at Vandenberg Air Force Base". SpaceNews. 12 November 2012. Retrieved 9 February 2013.
- ^ "First look/SpaceX Launch Complex/Vandenberg AFB". dailybreeze.com. 11 February 2013. Retrieved 1 April 2013.
- ^ Space.com, SpaceX Falcon 9 From Vandenberg AFB Near Perfect (accessed 5 August 2014)
- ^ popularmechanics.com, SpaceX Completes First Ever Falcon 9 Launch and Landing on the West Coast
- ^ "SPACE LAUNCH DELTA 30 TO LEASE SPACE LAUNCH COMPLEX 6 TO SPACE X". Vandenberg Space Force Base. 24 April 2023. Retrieved 29 October 2023.
- ^ Scully, Janene (4 December 2023). "SpaceX Yearly Launch Rate at Vandenberg SFB Could Soar to 100 by 2025". Noozhawk. Retrieved 5 December 2023.
- ^
One or more of the preceding sentences incorporates text from this source, which is in the public domain: "Fact Sheet Display". af.mil. Retrieved 10 August 2017.
- ^ a b Mueller, Robert, Air Force Bases Volume I, Active Air Force Bases Within the United States of America on 17 September 1982, Office of Air Force History, 1989
- ^ Maurer, Maurer Air Force Combat Units of World War II. Washington, D.C.: U.S. Government Printing Office 1961 (republished 1983, Office of Air Force History, ISBN 0-912799-02-1)
- ^ Ravenstein, Charles A. Air Force Combat Wings Lineage and Honors Histories 1947–1977 Maxwell Air Force Base, Alabama: Office of Air Force History 1984 ISBN 0-912799-12-9
- ^ Flores, Oscar (12 May 2021). "Vandenberg AFB Renames Base and 30th Space Wing". NBC Los Angeles. Retrieved 28 June 2021.
- ^ Green-Lanchoney, Jennifer (7 March 2025). "Air Force Activates Key Unit for Nuclear Modernization at VSFB". Vandenberg Space Force Base.
- ^ "Space Launch Complex 10". National Park Service. Retrieved 22 September 2025.
- ^ Foley, Theresa (1 September 1995). "Corona Comes in From the Cold". Air and Space Forces Magazine. Retrieved 22 September 2025.
- ^ "Space and Missile Heritage Center". Vandenberg Space Force Base. Retrieved 23 January 2024.
- ^ "Units". Vandenberg AFB. US Air Force. Archived from the original on 26 October 2006. Retrieved 2 November 2019.
- ^ "Nasturtium gambelii". Center for Plant Conservation. Archived from the original on 6 June 2013. Retrieved 31 March 2013.
- ^ "Vandenberg Air Force Base utilizes unique horse patrol to help protect plovers, maintain conservation efforts". Santa Ynez Valley News. 19 March 2019. Retrieved 25 March 2019.
- ^
One or more of the preceding sentences incorporates text from this source, which is in the public domain: "Vandenberg Beaches to close for Annual Snowy Plover Nesting Season". Vandenberg Air Force Base. 1 March 2012. Archived from the original on 4 November 2013. Retrieved 23 October 2012.
- ^ "Ocean Beach Park". Country of Santa Barbara. Retrieved 23 October 2012.
- ^ "UPDATE: UCSB student dead after large shark severs leg off Surf Beach". Lompoc Record. 22 October 2010. Retrieved 23 October 2012.
- ^ "UPDATE: Man reportedly dead in shark attack near Surf Beach". Lompoc Record. 23 October 2012. Retrieved 23 October 2012.
- ^ Sahagun, Louis (9 May 2017). "Rare birds find Southern California beach housing". Los Angeles Times. Retrieved 26 August 2017.
- ^ "Vandenberg Air Force Base". Geographic Names Information System. United States Geological Survey, United States Department of the Interior.
- ^ "Vandenberg SFB CDP, California". United States Census Bureau. Retrieved 14 May 2022.
- ^ "Decennial Census by Decade". United States Census Bureau.
- ^ "1870 Census of Population - Population of Civil Divisions less than Counties - California - Almeda County to Sutter County" (PDF). United States Census Bureau.
- ^ "1870 Census of Population - Population of Civil Divisions less than Counties - California - Tehama County to Yuba County" (PDF). United States Census Bureau.
- ^ "1890 Census of Population - Population of California by Minor Civil Divisions" (PDF). United States Census Bureau.
- ^ "1900 Census of Population - Population of California by Counties and Minor Civil Divisions" (PDF). United States Census Bureau.
- ^ "1910 Census of Population - Supplement for California" (PDF). United States Census Bureau. Archived from the original (PDF) on 23 August 2024. Retrieved 12 August 2024.
- ^ "1920 Census of Population - Number of Inhabitants - California" (PDF). United States Census Bureau.
- ^ "1930 Census of Population - Number and Distribution of Inhabitants - California" (PDF). United States Census Bureau.
- ^ "1940 Census of Population - Number of Inhabitants - California" (PDF). United States Census Bureau.
- ^ "1950 Census of Population - Number of Inhabitants - California" (PDF). United States Census Bureau.
- ^ "1960 Census of Population - General population Characteristics - California" (PDF). United States Census Bureau.
- ^ "1970 Census of Population - Number of Inhabitants - California" (PDF). United States Census Bureau.
- ^ "1980 Census of Population - Number of Inhabitants - California" (PDF). United States Census Bureau.
- ^ "1990 Census of Population - Population and Housing Unit Counts - California" (PDF). United States Census Bureau.
- ^ "2000 Census of Population - Population and Housing Unit Counts - California" (PDF). United States Census Bureau.
- ^ "2010 Census of Population - Population and Housing Unit Counts - California" (PDF). United States Census Bureau.
- ^ a b "P2 Hispanic or Latino, and Not Hispanic or Latino by Race – 2020: DEC Redistricting Data (PL 94-171) – Vandenberg SFB CDP, California". United States Census Bureau.
- ^ "P004: Hispanic or Latino, and Not Hispanic or Latino by Race – 2000: DEC Summary File 1 – Vandenberg AFB CDP, California". United States Census Bureau.
- ^ "P2 Hispanic or Latino, and Not Hispanic or Latino by Race – 2010: DEC Redistricting Data (PL 94-171) – Vandenberg AFB CDP, California". United States Census Bureau.
- ^ Phipps, Staff Sgt. Shane (27 September 2016). "Coalition unites to extinguish base wildland fires". Vandenberg Air Force Base. 30th Space Wing Public Affairs. Archived from the original on 2 October 2016. Retrieved 28 September 2016.
This article incorporates public domain material from the Air Force Historical Research Agency
This article incorporates public domain material from Vandenberg Space Force Base. United States Air Force.
Further reading
[edit]- Geiger, Jeffrey (2014). Camp Cooke and Vandenberg Air Force Base, 1941–1966: From Armor and Infantry Training to Space and Missile Launches. McFarland. OCLC 857803877.
- Page, Joseph T. (2014). Images of America: Vandenberg Air Force Base. Arcadia Publishing. OCLC 905345173.
- Valencia, Joseph (2004). Beyond Tranquillon Ridge. AuthorHouse. OCLC 57341426.
External links
[edit]Official sites
- Vandenberg Space Force Base official site
- History/Chronology of Vandenberg AFB
- Space and Missile Heritage Center
Other
- Vandenberg Air Force Base Spacecraft and Rocket Listing
- California Spaceport Website
- Vandenberg AFB Launch Schedule
- Vandenberg AFB Launch History
- Vandenberg SFB Launch Schedule
- FAA Airport Diagram for Vandenberg AFB (PDF), effective October 2, 2025
- Resources for this U.S. military airport:
- FAA airport information for VBG
- AirNav airport information for KVBG
- ASN accident history for VBG
- NOAA/NWS latest weather observations
- SkyVector aeronautical chart for KVBG
Vandenberg Space Force Base
View on GrokipediaHistory
Establishment and World War II Era (1941–1945)
In March 1941, the United States Army initiated development of a new training installation in Santa Barbara County, California, selected for its coastal dunes, rolling hills, and scrubland terrain resembling European battlefields, ideal for armored maneuvers.[7] The site encompassed approximately 86,000 acres adjacent to Lompoc, with land acquisition occurring between March and September 1941.[8] Construction commenced in September 1941 under the direction of the Army Corps of Engineers, prioritizing barracks, firing ranges, and maneuver areas despite the U.S. entry into World War II later that December.[9] The camp, named Camp Cooke in honor of Major General Philip St. George Cooke—a cavalry officer and veteran of the Mexican-American War, Indian Wars, and Civil War—was activated on October 5, 1941, though facilities remained incomplete.[9][10] A public dedication ceremony occurred on September 11, 1941, followed by the arrival of initial troops in early October.[11] Primarily designated as an armored training center, it hosted tank destroyer battalions, infantry divisions, artillery units, and support elements, conducting rapid training cycles to prepare forces for combat in Europe and the Pacific theaters.[12] Throughout the war, Camp Cooke expanded to accommodate upward of 175,000 personnel at various points, serving as a key West Coast hub for desert and coastal warfare simulations.[11] In 1944, a German prisoner-of-war branch camp was established on-site to provide labor for agricultural and base support tasks, housing captives from North African and European campaigns.[13] By late 1945, as Allied victories mounted and demobilization accelerated, training activities scaled down, with the installation transitioning toward postwar uses while retaining its role in infantry and artillery readiness until full inactivation in 1946.[8]Post-War Transition to Missile Testing (1946–1956)
Following World War II, Camp Cooke was largely deactivated in June 1946, with the majority of its facilities placed in caretaker status under minimal Army oversight. Portions of the installation were leased to local ranchers for grazing cattle and sheep, while a maximum-security disciplinary barracks was constructed and operated using prisoner labor to maintain essential infrastructure. This period of reduced activity reflected the broader demobilization of U.S. military forces, though the site's remote coastal location and existing roadways preserved its potential for future reuse.[10][14] In August 1950, following the outbreak of the Korean War, the U.S. Army reactivated Camp Cooke as a training ground for armored, infantry, and artillery units, hosting divisions such as the 13th, 20th, 40th, 44th, and 86th Infantry, as well as Army National Guard elements. The base supported intensive maneuvers emphasizing tank destroyer and amphibious operations, leveraging its expansive terrain and proximity to the Pacific for realistic exercises. By February 1953, with the armistice in Korea approaching, training activities wound down, leading to another deactivation and return to mothball status by 1954, as the Army consolidated postwar training at fewer sites.[15][10] The mid-1950s marked a pivotal shift driven by the U.S. Air Force's urgent need for a West Coast missile testing range to complement the Atlantic Missile Range at Cape Canaveral, enabling safer over-ocean launches, polar orbital trajectories, and dispersal of national assets amid escalating Cold War tensions. After a comprehensive nationwide evaluation of approximately 200 candidate sites, the Air Force's Atlas Site Selection Board recommended the northern sector of Camp Cooke in 1956, citing its isolation, favorable geography for southward firings into the Pacific, minimal population risk, and adaptable infrastructure from prior military use. On November 16, 1956, Secretary of Defense Charles E. Wilson formally approved the transfer of about 64,000 acres from the Army to the Air Force, designating it for initial operational capability of intercontinental ballistic missiles (ICBMs) and establishing the foundation for the Western Test Range. This decision prioritized empirical safety and operational efficiency over costlier greenfield developments, setting the stage for subsequent ICBM deployments like the Atlas and Thor.[16][17][18]Naming and Early Space Force Integration (1957–1963)
Cooke Air Force Base was redesignated Vandenberg Air Force Base on October 4, 1958, in honor of General Hoyt S. Vandenberg, the United States Air Force's second Chief of Staff, who had served with distinction during World War II and advocated for air power and missile development.[12] The renaming reflected the base's evolving role from Army training grounds to a critical hub for intercontinental ballistic missile (ICBM) testing and emerging space operations amid the Cold War space race triggered by the Soviet Union's Sputnik launch in 1957.[10] The first launch from the newly named Vandenberg occurred on December 16, 1958, when a Thor intermediate-range ballistic missile was fired from Space Launch Complex 2 East, marking the base's initial operational milestone in missile testing over the Pacific Ocean for safety and tracking purposes.[1] This event preceded the base's pivot toward space missions, with the inaugural polar-orbiting satellite launch on February 28, 1959, via a Thor-Agena A rocket carrying Discoverer 1 from Vandenberg—the world's first such satellite, ostensibly for scientific research but serving as a cover for the U.S. Corona reconnaissance program to gather intelligence on Soviet capabilities.[12][19] Throughout 1959–1963, Vandenberg integrated space launch activities alongside ICBM tests, supporting programs like Thor-Agena for satellite deployments and Atlas missile firings, with the first Atlas launch on September 9, 1959, from Launch Facility 576A-2.[20] The base's coastal location enabled southward trajectories ideal for polar orbits, minimizing overflight risks and facilitating recovery operations, thus establishing it as the primary West Coast site for national security space missions under Air Force oversight. By 1963, launches included NASA's Scout rocket deploying Explorer 19 on August 8 to study atmospheric density, demonstrating Vandenberg's dual military-civilian utility in the nascent U.S. space program.[21]Cold War Expansion and Launch Operations (1964–1991)
Vandenberg Air Force Base underwent significant expansion during the Cold War to support operational testing of intercontinental ballistic missiles (ICBMs) and polar-orbit space launches, driven by the need to validate U.S. nuclear deterrence capabilities and deploy reconnaissance satellites over the Soviet Union. The base hosted the first Minuteman II operational test launches as part of Glory Trip missions, with Phase II testing commencing in the mid-1960s to assess post-boost vehicle performance and reentry accuracy.[22] By the 1970s, facilities like Launch Facility complexes were adapted for Minuteman III silo-based tests, which included multiple unarmed launches to demonstrate readiness, such as those verifying multiple independently targetable reentry vehicle (MIRV) systems.[1] In parallel, space launch operations intensified with the use of modified Thor, Atlas, and Titan vehicles for national security payloads. Space Launch Complex 4 East (SLC-4E), constructed in 1964, supported 27 Atlas-Agena D launches between August 14, 1964, and June 4, 1967, primarily for KH-7 Gambit reconnaissance satellites before modification for Titan III configurations.[23] Thor-Delta rockets from SLC-2 facilitated satellite deployments into sun-synchronous orbits, enabling persistent imaging of denied areas, while Titan IIIC vehicles from SLC-4 West handled heavier classified missions through the 1980s.[1] These efforts underscored Vandenberg's role in the Western Range, providing overflight safety for southward trajectories unavailable from Cape Canaveral. The 1980s saw introduction of the LGM-118A Peacekeeper ICBM, with Vandenberg serving as the primary test site for its cold-launch system, where gas pressure ejected the missile from the silo before ignition, reducing topside damage.[24] Operational tests, including Glory Trip 133P on June 11, 1991, validated the four-stage design's accuracy and MIRV payload delivery.[25] Concurrently, ambitious plans for manned polar launches materialized in SLC-6 development; initially built from 1966 for the canceled Manned Orbiting Laboratory (MOL) program in 1969, it was repurposed in 1972 for Space Shuttle operations, involving $4 billion in modifications from 1979 to 1986.[26] The shuttle facility was ultimately abandoned post-Challenger disaster on January 28, 1986, due to safety risks, seismic concerns, and fiscal priorities, marking a pivotal shift away from crewed West Coast missions.[27]Post-Cold War Modernization (1992–2020)
Following the dissolution of the Soviet Union, Vandenberg Air Force Base shifted emphasis from large-scale intercontinental ballistic missile (ICBM) deployments to sustained testing, space launch operations, and emerging missile defense roles, reflecting reduced strategic nuclear threats and growing demand for polar-orbit satellite insertions. The Western Space and Missile Center was redesignated the 30th Space Wing on November 19, 1991, streamlining command under Air Force Space Command to manage range operations, launch support, and test missions across 99,604 acres.[1] ICBM activities persisted, with Peacekeeper missiles undergoing operational tests, including a successful launch carrying eight unarmed reentry vehicles on March 12, 2003, from Launch Facility-02, validating accuracy and multiple independently targetable reentry vehicle performance before the program's phaseout.[28] Facility repurposing accelerated modernization, particularly at Space Launch Complex-6 (SLC-6), originally constructed for Space Shuttle operations but abandoned post-1986 Challenger disaster. Minimal modifications enabled four Athena I and II launches between August 15, 1995, and April 27, 1999, primarily for commercial and scientific payloads like GemStar-1 and Ikonos-1, demonstrating viability for smaller expendable vehicles.[29] By 2006, SLC-6 was upgraded for larger boosters, hosting the first Delta IV Medium+ (4,2) launch on June 27, 2006, with a Defense Meteorological Satellite Program payload, followed by ten Delta IV missions through 2022 that supported national reconnaissance and weather satellites. These adaptations included reinforced pads, enhanced propellant storage, and integration with the Western Range's telemetry systems to accommodate cryogenic fuels and heavier lift capacities.[30] Missile defense testing expanded in the 1990s and 2000s, positioning Vandenberg as a key site for Ground-Based Midcourse Defense validation amid rising concerns over rogue state threats. A landmark Flight Test G2 event on September 1, 2006, saw an interceptor launched from Vandenberg successfully destroy an ICBM-class target over the Pacific, achieving multiple firsts including operational sensor integration and exo-atmospheric kill vehicle performance, as confirmed by Missile Defense Agency instrumentation.[31] Silos at the base housed early Ground-Based Interceptors, with infrastructure upgrades like expanded radar tracking and command centers enabling end-to-end simulations.[32] Commercial integration grew, with SLC-8 designated the world's first operational commercial spaceport on September 19, 1996, facilitating private-sector access to polar trajectories for Earth observation and communications satellites.[1] This era saw increased partnerships, culminating in SpaceX's inaugural Falcon 9 launch from SLC-4E on September 29, 2013, deploying the CASSIOPE mission, which introduced reusable booster concepts and diversified launch cadences beyond government-exclusive operations.[33] Minuteman III ICBM tests continued routinely, ensuring stockpile reliability, while upgrades to 16 launch complexes and a 15,000-foot runway supported hybrid military-commercial manifests, averaging dozens of annual missions by 2020.[1] ![Delta IV launch from SLC-6][float-right]Establishment of Space Force and Recent Developments (2021–Present)
Vandenberg Air Force Base was redesignated as Vandenberg Space Force Base on May 14, 2021, during a ceremony on the base parade grounds, marking its formal integration into the United States Space Force structure.[34][1] This change aligned the installation with the Space Force's establishment in December 2019 via the National Defense Authorization Act, transitioning oversight from Air Force Space Command elements to Space Launch Delta 30, which assumed host responsibilities equivalent to an Air Force base wing.[1] The redesignation emphasized the base's role in space launch and missile testing, with approximately 2,000 launches conducted to date as of 2021.[12] Post-redesignation, Vandenberg Space Force Base enhanced its operational tempo, supporting increased commercial and national security launches. In response to growing reliance on commercial operators, the Commercial Integration Cell was established at the base in 2021 to facilitate collaboration between the Space Force, industry, and U.S. Space Command.[35] Space Launch Delta 30 managed range operations exceeding 7,000 annually, including polar orbit missions critical for reconnaissance and communication satellites.[12] Recent developments include a surge in launch activities, with SpaceX targeting up to 50 Falcon 9 rockets from the base in 2024 and potentially 100 in 2025, alongside proposals to double missions to 100 annually by 2026.[36][37] Key missions encompassed the September 10, 2025, Falcon 9 launch of the Space Development Agency's first satellites for a new military constellation from Space Launch Complex 4 East.[38] In September 2025, the "Space Vandenberg" initiative secured $9.5 million in state investment to bolster launch infrastructure and regional partnerships.[39] Integration efforts extended to allied and commercial sectors, with U.S. Space Command leaders highlighting collaborative strategies in 2025 to counter space threats through enhanced data sharing and joint operations.[40] The base also advanced resilience training and operational imperatives, including the stand-up of an Integrated Capabilities Office in 2024 to streamline development for space domain awareness.[41] These enhancements positioned Vandenberg as a pivotal hub for polar launches and missile defense testing amid escalating space competition.[42]Mission and Operations
Space Launch Capabilities
Vandenberg Space Force Base serves as the primary West Coast launch site for the United States Space Force, enabling access to polar and sun-synchronous orbits that are optimal for reconnaissance, Earth observation, and scientific satellites due to minimal overflight of populated areas.[5] Space Launch Delta 30, the base's host unit, oversees launch operations, range safety, telemetry, and tracking via the Western Range, supporting missions for the Department of Defense, National Reconnaissance Office, NASA, and commercial entities.[43] This infrastructure facilitates responsive and reliable deployment of national security payloads, with capabilities extending to intercontinental ballistic missile evaluation and missile defense testing.[43] The base supports a range of expendable launch vehicles, including the Atlas V, Falcon 9, Minotaur family, and Pegasus, though recent operations have emphasized high-cadence commercial launches such as SpaceX's Starlink constellation.[43] In 2024, Vandenberg achieved a record 51 launches, revolutionizing West Coast space access and demonstrating enhanced throughput for both classified and unclassified missions.[6] These efforts include national security satellite deployments, as seen in the September 2025 launch of the Space Development Agency's Tranche 1 satellites.[44] Active launch pads include Space Launch Complex 4 East (SLC-4E), primarily utilized by SpaceX for Falcon 9 vertical takeoffs and booster landings, hosting frequent Starlink missions into low-Earth orbit.[45] SLC-2 West supports smaller vehicles like Firefly Aerospace's Alpha rocket, while SLC-3 is undergoing modifications for United Launch Alliance's Vulcan Centaur to enable heavier-lift capabilities.[46] SLC-6, previously adapted for Delta IV, has been leased to SpaceX for potential Falcon Heavy operations and further expansions, enhancing the base's versatility for medium- and heavy-class payloads.[47] Future enhancements focus on increasing launch tempo and integrating advanced vehicle operations, including a new Vehicle Operations Room for real-time mission rehearsal and control, ensuring sustained support for evolving space superiority requirements.[48] The U.S. Air Force has authorized SpaceX to augment annual launch capacity at Vandenberg, signaling ongoing adaptations to meet demand for proliferated satellite architectures and rapid deployment needs.[49]Intercontinental Ballistic Missile Testing
Vandenberg Space Force Base has conducted intercontinental ballistic missile (ICBM) testing since the late 1950s, serving as the primary West Coast site for operational and developmental launches due to its coastal location enabling safe trajectories over the Pacific Ocean.[50] The base's silo-based launch facilities, including Launch Facility 10 (LF-10), supported early ICBM programs such as the Atlas, which achieved the first ICBM operational test launch from Vandenberg on December 16, 1958.[50] [51] These tests validated missile reliability, guidance systems, and reentry vehicle performance under simulated combat conditions.[52] In the 1960s, Vandenberg hosted tests for the Titan I and Titan II ICBMs, with facilities like the Operational Silo Test Facility enabling silo-launch demonstrations.[53] Minuteman I made its first Vandenberg launch on September 28, 1962, marking the transition to solid-fuel missiles for quicker response times.[54] Subsequent Minuteman II and III variants underwent extensive operational testing from the base, with the 576th Flight Test Squadron overseeing launches to confirm system integrity.[51] During the 1980s and 1990s, the LGM-118 Peacekeeper (MX) ICBM was tested from modified Minuteman silos, such as LF-08, demonstrating multiple independently targetable reentry vehicle (MIRV) capabilities before its retirement in 2005.[25] These Cold War-era tests emphasized survivability against counterforce strikes through hardened silos and cold-launch techniques.[24] Today, unarmed Minuteman III ICBMs are launched approximately four times annually from Vandenberg to validate the U.S. nuclear deterrent's safety, security, and effectiveness, targeting areas like the Kwajalein Atoll.[55] [52] The 377th Test and Evaluation Group, established in 2022 and based at Vandenberg, manages these operations as the nation's sole dedicated ICBM test unit.[56] Recent examples include launches on February 19, 2025, and May 21, 2025, using single telemetered reentry vehicles to gather flight data.[57] [58] The Western Range supports these missions, ensuring compliance with environmental and safety protocols while preparing for future systems like the LGM-35A Sentinel.[59][60]Western Range Management
The Western Range serves as the principal West Coast infrastructure for space launches, missile testing, and related operations, extending over 2,500 miles with instrumentation assets valued in excess of $1.5 billion. Managed by Space Launch Delta 30 (SLD 30) at Vandenberg Space Force Base, it delivers critical uprange support including radar tracking, telemetry data acquisition, optical sensing, communications, meteorological analysis, and range safety functions to enable polar orbit insertions, intercontinental ballistic missile evaluations, and missile defense trials originating from Vandenberg or Edwards Air Force Base.[61][62] The 2d Range Operations Squadron (2 ROPS), subordinate to SLD 30, executes primary control and operational oversight of the Western Range, integrating mission support for launch providers while supervising over 1,000 Space Force and contractor personnel across five sites. Its responsibilities encompass optimizing performance of tracking radars (such as the FPS-16 for precision vehicle monitoring), telemetry antennas (including 24-foot and 40-foot automatic tracking systems for data reception), command destruct systems for flight termination, and weather instrumentation to mitigate hazards and ensure mission viability.[62][63][64] Range Management, a specialized SLD 30 unit, focuses on acquiring, modernizing, and sustaining the Launch and Test Range System (LTRS), which comprises 11 core subsystems for radar, telemetry, secure communications, and environmental monitoring. Recent efforts include transitioning to IP-enabled networks for remote operations, enabling concurrent missions (up to three simultaneous major events), and implementing digital tools for subsystem reconfiguration in under one hour alongside post-mission data delivery within 24 hours, thereby enhancing efficiency for Department of Defense, civil, and commercial users.[63] SLD 30 facilitates customer access through dedicated protocols, including new customer questionnaires and forms for Major Range and Test Facility Base activities, FAA-licensed commercial launches, and exercises, with operations restricted to U.S. entities to align with national security requirements. Coordination with the Federal Aviation Administration ensures airspace management and hazard area delineation, minimizing risks to aviation and maritime traffic during active phases.[65][61]Support for National Security and Commercial Missions
Vandenberg Space Force Base supports national security missions by providing launch infrastructure for intelligence, surveillance, reconnaissance satellites, and proliferated space architectures essential to U.S. defense. Space Launch Delta 30, headquartered at the base, manages the Eastern and Western Test Ranges, coordinating over 20 mission partners including Space Force and Air Force units to ensure secure and reliable access to space for Department of Defense payloads.[66][67] In January 2025, the base's new Advanced Vehicle Operations Room facilitated its inaugural National Security Space Launch (NSSL), enhancing processing for classified missions under Phase 3 Lane 2 contracts awarded in April 2025 to providers like United Launch Alliance and SpaceX.[68][69] The Combined Space Operations Center at Vandenberg integrates data from the National Reconnaissance Office and missile warning systems, enabling real-time threat analysis and space domain awareness.[70] For proliferated architectures, Vandenberg launched the Space Development Agency's first Tranche 1 Transport Layer satellites on September 11, 2025, deploying vehicles to support tactical data transport and missile tracking for warfighters.[71] These operations underscore the base's role in deterring adversaries through assured access to space, with facilities like the 30th Operations Support Squadron providing multi-source intelligence on launch threats.[67] In parallel, Vandenberg accommodates commercial missions, leveraging its coastal location for polar and sun-synchronous orbits ideal for Earth-imaging and communications satellites. SpaceX operates from Space Launch Complex 4E, conducting Falcon 9 launches for Starlink broadband constellations; on October 24, 2025, it deployed 28 satellites, marking the company's 135th Falcon 9 mission that year.[72] The U.S. Space Force approved expanding SpaceX operations in October 2025, permitting up to 100 annual launches including Falcon Heavy from SLC-6 starting in 2026, despite environmental concerns raised by state regulators.[73][74] Commercial integrations, such as the May 2024 launch of Maxar Technologies' WorldView Legion satellites via the DoD's Commercial Integration Cell, demonstrate hybrid models where private payloads share rides with national security assets, boosting launch cadence and cost efficiency.[75] Expanded processing facilities announced in April 2025 further enable commercial vehicle handling to meet NSSL demands.[76] This dual-use approach fosters resilience by diversifying launch providers while prioritizing government missions.[77]
Facilities and Infrastructure
Launch Complexes and Pads
![Launch of Falcon 9 from SLC-4E][float-right] Vandenberg Space Force Base hosts multiple Space Launch Complexes (SLCs) optimized for southward trajectories over the Pacific Ocean, enabling polar and sun-synchronous orbits without overflying populated areas. These facilities support both national security and commercial missions, with infrastructure including launch pads, mobile service towers, and propellant storage systems. Key complexes have evolved from Cold War-era missile testing to modern reusable rocket operations.[33] SLC-2, situated in the northern section of the base, initiated operations with the first Thor intermediate-range ballistic missile launch on December 16, 1958, from its east pad. It accommodated Thor-Agena and early Delta rockets through the 1960s and 1970s, but the east pad was demolished post-1972, rendering the complex largely inactive for orbital launches today.[1]| Complex | Pads | Primary Rockets Launched | Current Status |
|---|---|---|---|
| SLC-2 | 2E (demolished), 2W | Thor, Thor-Agena, Delta | Inactive for major launches[1] |
| SLC-3 | 3E | Atlas V, planned Vulcan Centaur | Active; infrastructure upgrades for Vulcan include expanded hydrogen storage to 100,000 gallons[78][46] |
| SLC-4 | 4E | Falcon 9 (since 2013) | Active; supports up to 70 Falcon 9 launches per year following 2025 approvals, primarily for Starlink satellites[33][79] |
| SLC-6 | 6 | Delta IV (until 2022), planned Falcon 9/Heavy | Under modification by SpaceX; October 2025 environmental impact statement authorizes construction of erector, storage tanks, and transport systems for Falcon operations[80] |
| SLC-10 | 10 | Thor IRBM (historic) | Inactive; preserved as National Register of Historic Places site for missile testing heritage[81] |
Testing and Operations Centers
The Western Range Operations Control Center (WROCC), located at Vandenberg Space Force Base, serves as the primary command and control facility for launch and range operations, ensuring safety and coordination for space vehicle and missile tests across the Western Range.[83] Activated in phases beginning December 15, 2005, with the Area Control Center as its first major component, the WROCC integrates radar, telemetry, and communications systems to monitor trajectories, enforce safety protocols, and abort missions if necessary during real-time events.[83] It supports both national security and commercial launches, contributing to the base's record of 51 launches in 2024 by providing continuous oversight from pre-launch preparations through post-flight analysis.[84] The Combined Space Operations Center (CSpOC), operated by Space Delta 5, functions as the hub for 24/7 tactical command and control of space forces, directing planning, integration, and execution of operations to deliver effects for U.S. Space Command and allied partners including Australia, Canada, France, Germany, New Zealand, and the United Kingdom.[70] Co-located with the 18th Space Defense Squadron, it comprises divisions for combat operations, space defense, intelligence, surveillance, reconnaissance, and system integration, alongside squadrons handling cyber operations and combat training.[70] This center synchronizes joint and coalition space activities, including satellite support and threat response, distinct from range-specific launch control by focusing on broader theater and global space domain awareness.[70] For intercontinental ballistic missile (ICBM) testing, the 576th Flight Test Squadron maintains dedicated operations facilities to execute developmental and operational tests of systems like the Minuteman III, utilizing the Western Range as the primary ground for validating nuclear deterrent readiness.[51] These efforts, supported by the 377th Test and Evaluation Group and Air Force Operational Test and Evaluation Center's operating location at the base, involve silo launches and flight evaluations to assess reliability, with recent tests in 2025 demonstrating safe and effective performance of the U.S. nuclear triad.[85][86] The Vandenberg Tracking Station, part of the Ellison Onizuka Satellite Operations Facility under the 21st Space Operations Squadron, provides real-time command, control, tracking, and telemetry for Department of Defense, allied, and civil satellites during launch and on-orbit phases.[87] Complementing these, the 30th Operations Support Squadron oversees airfield operations, weather monitoring with 228 sensors across 118,000 acres, and maintenance of 67 air traffic and atmospheric systems, enabling integrated testing for aviation and space vehicle programs such as the X-37B.[67] The Emergency Operations Center (EOC) acts as a backup command node during launch operations, coordinating emergency response and continuity for high-stakes tests and missions.[88] These centers collectively underpin Vandenberg's role in Major Range and Test Facility Base activities, prioritizing empirical validation of systems through data-driven telemetry and control processes.[65]Recent Upgrades and Expansions
In April 2023, Space Launch Delta 30 leased Space Launch Complex 6 (SLC-6) to SpaceX for redevelopment to support Falcon 9 and Falcon Heavy launches, marking the reactivation of a facility dormant since the 1990s shuttle program cancellation.[89] Modifications include a new horizontal integration hangar south of the existing facility and two adjacent landing pads for reusable boosters, enabling up to five Falcon Heavy missions annually alongside standard Falcon 9 operations.[90] In October 2025, the Department of the Air Force finalized an environmental assessment approving an expansion of SpaceX's overall operations at Vandenberg from 50 to 100 launches per year, incorporating enhanced landing capabilities in the Pacific Ocean.[91] [92] The Space Vandenberg initiative, launched in September 2025 with a $9.5 million state grant to regional partners including REACH Central Coast, targets supporting infrastructure to accommodate the base's increasing launch cadence and commercial activity.[93] Key projects encompass harbor expansions for larger vessels, upgraded roads and power grids, additional launch pad enhancements, and improved gate access to handle projected growth in personnel and logistics.[94] This effort aligns with over $800 million in federal investments to integrate new technologies and create more than 2,000 jobs, positioning Vandenberg as a hub for national security and commercial space endeavors.[95] In September 2025, Space Systems Command established a new Operational Test, Training, and Infrastructure System Delta at Vandenberg to streamline acquisition and testing of space domain capabilities, collaborating with STARCOM units for resilient operational architectures.[96] Complementing these, a base-wide network upgrade completed in February 2025 improved data throughput and mission reliability, with a summer 2025 project adding redundant boundary systems for enhanced cybersecurity and resilience.[97] These developments occur amid broader Western Range modernizations, including a $4 billion contract awarded in July 2025 to Jacobs Technology for range-wide upgrades supporting missile testing and launches.[98]Based Units
United States Space Force Units
Space Launch Delta 30 (SLD 30) serves as the host unit for Vandenberg Space Force Base, overseeing space launch operations, intercontinental ballistic missile (ICBM) testing, and range management for the Western Range. Established as the successor to the 30th Space Wing following the 2019 creation of the United States Space Force, SLD 30 ensures assured access to space through polar orbit launches using vehicles such as Falcon 9, Atlas V, and Minotaur rockets, supporting Department of Defense, national security, and allied missions. In fiscal year 2023, SLD 30 facilitated 28 launches from the base, contributing to over 50% of U.S. national security space launches.[99] Subordinate to SLD 30 are several specialized squadrons within its operations, maintenance, and support groups. The 30th Operations Group includes the 1st Space Launch Squadron, responsible for Delta IV and Atlas V launches; the 2nd Space Launch Squadron, which handles Falcon 9 missions and emerging proliferated low-Earth orbit constellations; and the 4th Space Launch Squadron, focused on Minotaur and Pegasus small satellite deployments. The 30th Maintenance Group encompasses the 576th Flight Test Squadron for ICBM test launches, including Minuteman III evaluations, and the 533d Training Squadron for guardian proficiency in launch and range operations. Additionally, the 30th Contracting Squadron and 30th Space Communications Squadron provide logistical and cyber support, ensuring secure communications for launch activities.[100] Tenant United States Space Force units at Vandenberg include elements from Space Operations Command (SpOC) and other deltas, enhancing the base's role in space domain awareness and testing. The 9th Space Operations Squadron operates satellite control for defense communications, while the 17th Test Squadron conducts advanced space testing and evaluation. The 18th Space Defense Squadron focuses on missile warning and defense integration, and the 21st Space Operations Squadron supports tactical satellite operations. Space Delta 5, part of the Combined Space Operations Center, coordinates joint space warfighting from the base, integrating data from global sensors for real-time mission planning. These units collectively numbered over 4,000 Space Force personnel as of 2024, underscoring Vandenberg's centrality to U.S. space operations.[99][101]| Unit | Primary Role |
|---|---|
| Space Launch Delta 30 | Host delta; launch and range operations |
| 1st Space Launch Squadron | Delta IV/Atlas V missions |
| 2nd Space Launch Squadron | Falcon 9 and proliferated satellite launches |
| 576th Flight Test Squadron | ICBM testing (e.g., Minuteman III) |
| 9th Space Operations Squadron | Satellite control and communications |
| 17th Test Squadron | Space systems testing and evaluation |
| 18th Space Defense Squadron | Missile warning and defense |
United States Air Force and Other Units
The United States Air Force operates several tenant units at Vandenberg Space Force Base, primarily focused on testing, intelligence, and satellite operations in support of broader Department of Defense missions. These units leverage the base's infrastructure for activities distinct from core Space Force launch and range management functions.[99] The 17th Test Squadron, Detachment 4, subordinate to the Air Force Test Center at Edwards Air Force Base, conducts developmental and operational testing of space systems, including instrumentation for missile and launch vehicle evaluations. Established as part of Air Force Materiel Command's testing enterprise, this detachment utilizes Vandenberg's range assets to validate technologies under realistic conditions, such as polar orbit trajectories and ICBM flight paths.[99][103] The 18th Intelligence Squadron, Detachment 1, under Air Force Intelligence, Surveillance, and Reconnaissance, provides multi-discipline intelligence analysis and fusion for space domain awareness, including threat assessment for orbital assets and ground-based support to national security space launches. This unit integrates data from Vandenberg's sensors to inform tactical and strategic decisions, operating as a key enabler for joint space operations.[99] The 148th Space Operations Squadron, assigned to the California Air National Guard's 195th Wing, maintains and operates portions of the Air Force Satellite Control Network, emphasizing protected tactical satellite communications for secure data relay in contested environments. Activated in 2001 and relocated to Vandenberg, the squadron supports global users by managing uplink/downlink terminals and ensuring resilient comms links, drawing on the base's strategic location for polar and high-inclination orbit access.[104][103] The 576th Flight Test Squadron, part of Air Force Global Strike Command, oversees force development evaluation testing for the Minuteman III intercontinental ballistic missile program, conducting alert readiness and system integrity assessments from Vandenberg's silos and launch facilities. This squadron's activities, ongoing since the 1960s missile era, ensure nuclear deterrence reliability through periodic launches and telemetry data collection.[99] Beyond Air Force elements, the United States Army's 100th Missile Defense Brigade, under U.S. Army Space and Missile Defense Command, maintains a presence for ground-based midcourse defense sensor operations and integration testing, supporting ballistic missile defense experiments that utilize the base's Western Range for threat simulation and intercept validation.[99]Tenant and Support Organizations
Tenant organizations at Vandenberg Space Force Base encompass U.S. Space Force squadrons focused on space operations, missile testing, and domain awareness, as well as detachments from other services and federal agencies. The 576th Flight Test Squadron, under Space Launch Delta 30's oversight but operating as a tenant for intercontinental ballistic missile evaluations, conducts developmental and operational tests of the Minuteman III ICBM system, including flight tests from silos at the base.[12] Similarly, the 17th Test Squadron, Detachment 4, supports technical evaluations for space systems and range instrumentation.[103] Space domain awareness and operations tenants include the 18th Space Defense Squadron, which performs orbital analysis and conjunction assessments to safeguard U.S. space assets, and the 21st Space Operations Squadron, a tenant unit that manages satellite command and control for assured access to space-based capabilities.[99] [103] The 148th Space Operations Squadron, part of the California Air National Guard, operates military satellite communications systems, providing 24/7 global connectivity from Vandenberg facilities.[104] Additional tenants such as the 9th Space Operations Squadron and 216th Electronic Warfare Squadron (Hawaii ANG) contribute to satellite operations and electromagnetic spectrum management, respectively.[99] Federal agency tenants support national security and civil space missions. The National Reconnaissance Office (NRO) utilizes Vandenberg for launching classified reconnaissance satellites into polar orbits, leveraging the base's western range infrastructure.[12] The National Aeronautics and Space Administration (NASA) maintains a presence for earth science and technology demonstration launches, including missions like the Terra satellite series. The National Oceanic and Atmospheric Administration (NOAA) coordinates polar-orbiting environmental satellites, such as JPSS series, to enhance weather forecasting and climate monitoring.[103] Support organizations include the Aerospace Corporation, which provides independent technical assessments, systems engineering, and launch integration services for Department of Defense and civil missions at the base.[103] Space Operations Command (SpOC) elements, including detachments for combined space operations, offer overarching coordination for warfighting functions, while Space Delta 5 focuses on battle management and combat training integration as a tenant activity.[99] These entities rely on host-provided infrastructure but maintain distinct missions, contributing to Vandenberg's role in over 1,000 launches and tests since 1957.[12]Strategic Importance and Achievements
Contributions to National Defense and Deterrence
Vandenberg Space Force Base plays a central role in validating the operational readiness of the United States' intercontinental ballistic missile (ICBM) arsenal, a key component of nuclear deterrence. The base hosts the 377th Test and Evaluation Group, the nation's sole dedicated ICBM test organization, which conducts periodic launches of the LGM-30G Minuteman III to confirm system reliability, safety, and effectiveness. These tests, such as the one executed on May 21, 2025, from Vandenberg, demonstrate the sustained capability of the land-based leg of the nuclear triad without deploying warheads, signaling to adversaries the credibility of U.S. retaliatory forces.[56][55] Historically, Vandenberg has supported testing for multiple generations of ICBMs, including the Titan, Minuteman, and Peacekeeper programs, contributing over 1,980 missile and space launches since 1957 to refine strategic capabilities. These efforts ensured the evolution of solid-fuel propulsion and multiple independently targetable reentry vehicles (MIRVs), enhancing penetration and response times critical for deterrence during the Cold War and beyond. The base's isolated coastal location facilitates safe southward trajectories over the Pacific, minimizing risks while allowing full-range evaluations.[20] In addition to missile testing, Vandenberg enables the deployment of space-based assets vital for defense, including reconnaissance satellites launched for the National Reconnaissance Office (NRO) into polar orbits for comprehensive global coverage. These missions provide intelligence, surveillance, and reconnaissance (ISR) data, missile warning, and secure communications, underpinning deterrence by enabling early detection of threats and informed decision-making. Since its inception, the NRO has relied on Vandenberg for launches that sustain U.S. superiority in space domain awareness.[105][106]Key Milestones in Launch History
The launch history of Vandenberg Space Force Base commenced on December 16, 1958, with the inaugural Thor intermediate-range ballistic missile test from Space Launch Complex 2 East, initiating westward over-ocean trajectories essential for polar and safety considerations in missile development.[20] This event established the base as a primary West Coast testing ground, supporting subsequent intercontinental ballistic missile programs including Atlas, Titan, Minuteman, and Peacekeeper, with over 1,000 missile flights validating nuclear deterrence reliability through silo-based and rail-mobile configurations.[1] Orbital launch capabilities emerged in 1959, highlighted by the February 28 liftoff of Discoverer 1 on a Thor-Agena from Space Launch Complex 1, the first attempt to place a payload into polar Earth orbit and a precursor to reconnaissance missions under the Corona program.[1] The base hosted diverse space vehicles thereafter, including Scout for small scientific satellites from the 1960s to 1990s, Thor-Agena derivatives for intelligence payloads, and evolved Delta and Atlas families for national security satellites, enabling over 500 orbital insertions by the early 2000s.[1] Modern milestones reflect increased commercial and military tempo, with the September 28, 2021, Atlas V launch of Landsat 9 marking the facility's 2,000th departure alongside the 300th Atlas vehicle utilization.[107] Launch rates peaked in 2024 with a record 51 missions, including the April 11 Falcon 9 deployment of the U.S. Space Force's Weather System Follow-on – Microwave satellite, demonstrating enhanced infrastructure for rapid national asset placement.[6] Ongoing Minuteman III tests, such as the February 2025 operational flight, continue to affirm ICBM readiness.[108]Role in Commercial Space and International Partnerships
Vandenberg Space Force Base plays a pivotal role in commercial space operations by providing launch infrastructure for polar and sun-synchronous orbits, which are essential for Earth observation and communication satellites. SpaceX leases Space Launch Complex 4 East (SLC-4E) for Falcon 9 rockets, with the first launch occurring on October 8, 2013, carrying the CASSIOPE mission, and subsequent missions including frequent Starlink deployments for global broadband internet.[33] By 2025, SpaceX had executed dozens of Falcon 9 launches from Vandenberg, supporting commercial payloads such as transpondersat and other private sector satellites, leveraging the site's westward trajectory to minimize ground track over populated areas.[109] United Launch Alliance (ULA) has utilized Space Launch Complex 6 (SLC-6) for Delta IV vehicles, which retired after supporting commercial missions like the October 5, 2022, launch of SES-20 and SES-21 satellites for C-band spectrum services aiding 5G transitions.[110] ULA plans Vulcan Centaur debuts at Vandenberg for future commercial and national security payloads, enhancing capacity for high-inclination orbits.[111] The U.S. Space Force's Commercial Integration Cell facilitates seamless integration of commercial launches into range operations, as demonstrated by the May 8, 2024, support for Maxar Technologies' WorldView Legion satellites, which bolster Earth intelligence capabilities.[75] In international partnerships, Vandenberg serves as a hub for multinational space cooperation exercises and strategy development. The U.S. Space Force unveiled its International Partnership Strategy on July 8, 2025, prioritizing alliances to counter contested space domains through shared domain awareness and interoperability.[112] Global Sentinel 2025, hosted at Vandenberg in May, involved nearly 30 partner nations and NATO in capstone events focused on operational collaboration and threat response.[113] Schriever Wargame 2025, concluded August 26, 2025, further strengthened ties with nine nations by simulating future space scenarios, while events like the Space Chiefs Forum reinforce collective assessments of global space security.[114][115] These initiatives, often conducted at Vandenberg, enable allied forces to train on base facilities, though direct foreign launches remain limited to U.S.-approved payloads on American rockets.Environmental Considerations and Controversies
Natural Resources Management
The Integrated Natural Resources Management Plan (INRMP), revised in September 2021, directs ecosystem-based conservation of fish, wildlife, plants, and water resources at Vandenberg Space Force Base while sustaining military readiness and ensuring no net loss in land capabilities for mission support.[116] This plan complies with the Sikes Act Improvement Act of 1997, integrates operational needs such as up to 70 annual space launches through 2025, and emphasizes adaptive strategies to minimize development impacts, control invasives, and monitor climate effects.[116][117] The base spans 99,579 acres of varied habitats, including up to 5,110 acres of wetlands (with 4,967 acres mapped in a 2018 survey), 19,324 acres of grasslands, 4,354 acres of oak woodlands, about 22,673 acres of forested land, and 42 miles of coastline supporting dunes and estuaries.[116] Biodiversity encompasses over 850 plant species, including six federally or state-listed threatened/endangered taxa such as the Vandenberg monkeyflower (Diplacus traskiae) and beach layia (Layia carnosa), alongside 53 mammals, 315 birds (115 breeding), 17 reptiles, and 10 amphibians.[118][116] Among 11 federally listed animal species, management targets include the western snowy plover (Charadrius nivosus nivosus), with base breeding sites historically comprising over 20% of California's population in 2004, and the southern sea otter (Enhydra lutris nereis), whose local numbers rose from 2–5 to 35–60 individuals by 2020 through haul-out protections.[116] Fish resources in streams like the Santa Ynez River and San Antonio Creek feature endangered species such as steelhead (Oncorhynchus mykiss), tidewater goby (Eucyclogobius newberryi), and unarmored threespine stickleback (Gasterosteus aculeatus williamsoni), with non-natives managed to safeguard natives.[116] Programs address invasive species via integrated pest management, targeting plants like iceplant (Carpobrotus spp.), veldt grass (Eragrostis lehmanniana), and European beachgrass (Ammophila arenaria), as well as feral pigs, beavers, and ground squirrels to prevent habitat degradation.[116] Endangered species efforts involve annual surveys, population monitoring, and mitigation, including seasonal closures (March–September) of beaches like Surf, Wall, and Minuteman to protect plover nesting, enforced under the Endangered Species Act with fines up to $50,000 and potential imprisonment for violations such as dog access or kite flying.[118][116] Habitat restoration covers oak woodlands, riparian zones, chamise chaparral, coastal dunes, and wetlands like Barka Slough (480 acres), with restrictions on grazing, off-road vehicles, and development in sensitive areas; vernal pools (80% surveyed) support fairy shrimp conservation.[116] Ongoing initiatives include over a decade of southwestern pond turtle (Actinemys pallida) studies across lakes, ponds, creeks, and the Santa Ynez River; seabird, shorebird, amphibian, and marine mammal monitoring to reduce launch disturbances; and the Bird-Wildlife Aircraft Strike Hazard program via the Airfield Operations Board.[117] Post-wildfire restoration, invasive removal, and wetlands enhancement occur under cooperative agreements with the U.S. Fish and Wildlife Service (since 1963) and The Nature Conservancy (since 1988), maintaining permits from NOAA and the California Coastal Commission to balance ecological preservation with national defense priorities.[116][117] The base ranks second among Department of Defense installations for terrestrial threatened and endangered species management, with annual INRMP reviews to adapt to emerging threats like climate change.[117][116]Environmental Impact Assessments
The Final Environmental Impact Statement (EIS) for authorizing changes to the Falcon Launch Program at Vandenberg Space Force Base, released in October 2025, evaluated the potential effects of increasing Falcon 9 and Falcon Heavy launches to up to 100 per year from prior levels of around 12 annually. This NEPA-compliant analysis, prepared by the Department of the Air Force, assessed cumulative impacts across multiple resources, including air quality (emissions from propellants and vehicle operations), noise (from sonic booms and engine ignition), terrestrial and marine biological resources, water resources, cultural sites, and coastal zones. The EIS incorporated modeling for up to 50 routine launches and 50 with reusable first-stage landings, projecting short-term localized exceedances of noise thresholds over beaches and ocean areas but no long-term degradation to air quality standards under federal and California regulations.[92][119] Biological resources received particular scrutiny due to the base's proximity to habitats for federally listed species, with the EIS requiring documentation of effects on the threatened western snowy plover (Charadrius nivosus nivosus), endangered California least tern (Sternula antillarum browni), threatened southern sea otter (Enhydra lutris nereis), and threatened California red-legged frog (Rana draytonii). Launch noise and vibrations have been observed to disturb nesting plovers, leading to site abandonment in some cases, and to displace sea otters from nearshore foraging areas, though recovery occurs post-event. Marine mammal strandings or behavioral changes linked to launches remain under monitoring, with no causal links established in the EIS beyond temporary acoustic exposure. Terrestrial impacts include potential habitat fragmentation for plovers on base dunes, mitigated through seasonal launch restrictions and geospatial noise modeling to avoid active nests. The assessment concluded these effects are not likely to adversely affect species viability when combined with ongoing conservation measures, such as predator control and habitat enhancement.[120][121][122] A Record of Decision signed on October 10, 2025, approved the proposed action under the preferred alternative, determining that all identified impacts could be reduced to below significance levels through mitigation commitments, including real-time wildlife monitoring, adaptive launch scheduling, and erosion controls for coastal sites. Public comments during the draft phase, solicited through July 2025, raised concerns over unmodeled cumulative effects on biodiversity and air pollutants like aluminum oxide particulates, but the final EIS incorporated additional analysis without altering the no-significant-impact finding after mitigation. Earlier assessments, such as the 2016 Environmental Assessment for Falcon boost-back landings, similarly found negligible effects on sea otters due to their nearshore distribution avoiding splashdown zones. For missile programs, a 2019 Environmental Assessment for Ground Based Strategic Deterrent testing analyzed similar noise and exhaust impacts, concluding minimal biological disruptions with standard flight safety buffers.[123][124][125] Separate 2024 environmental sampling under the Missile Community Cancer Study detected polychlorinated biphenyls and volatile organic compounds at levels below regulatory action thresholds in soil and groundwater near historical launch sites, indicating no ongoing contamination risks from past operations. These findings, from Air Force Global Strike Command-led efforts, underscore routine compliance monitoring but do not address launch-specific acute impacts covered in programmatic EIS documents.[126]Debates Over Launch Increases and Wildlife Effects
Proposals to increase rocket launch cadence at Vandenberg Space Force Base (SFB) have intensified debates over potential wildlife disruptions, particularly amid SpaceX's Falcon program expansions. The U.S. Department of the Air Force (DAF) authorized an increase in annual Falcon launches from prior limits of around 36 to up to 100 per year through operations at Space Launch Complexes 4 and 6, as detailed in the Final Environmental Impact Statement (EIS) and Record of Decision (ROD) issued on October 10, 2025.[127][120] This escalation supports national security and commercial space objectives but has drawn scrutiny from conservationists citing risks to coastal species in the base's ecologically sensitive surroundings.[121] Central to the controversy are acoustic and vibrational effects from launches on avian species, including the federally threatened western snowy plover (Charadrius nivosus nivosus), which nests on Vandenberg's beaches from March to September. Environmental assessments have documented instances where launch noise prompted plovers to flush from nests, potentially increasing predation risks or abandonment; for example, post-launch surveys following Falcon Heavy events review camera footage for behavioral changes.[128] The Santa Barbara Audubon Society argued in October 2024 comments on a draft assessment that such disturbances could have significant adverse effects on plover reproductive success, urging deferral of approvals without additional data.[129] Similarly, California least terns have shown nesting responses to projected launch noise zones, with public input during EIS scoping highlighting over 160 comments on bird impacts, including 35 specifically requesting snowy plover studies.[130][128] Marine mammals, such as southern sea otters and pinnipeds including harbor seals, California sea lions, and northern elephant seals (Mirounga angustirostris), face potential haul-out disturbances from sonic booms or vessel traffic associated with downrange landings in the Pacific. Northern elephant seals generally exhibit lower levels of disturbance compared to other pinnipeds but experience behavioral changes such as flushing from haul-out sites due to launch noise and sonic booms.[131] Recent findings indicate launches have disturbed otters and correlated with plover site abandonments, prompting calls for expanded monitoring.[121] NOAA Fisheries' 2023 monitoring report under the base's incidental harassment authorization tracks such effects on protected species, requiring behavioral observations and injury assessments post-launch.[132] Groups like the Gaviota Coast Conservancy and Surfrider Foundation have opposed the surge—from 6 to potentially 100 annual SpaceX launches—fearing cumulative stress on biodiversity hotspots without sufficient baseline data on chronic noise exposure.[133] The California Coastal Commission unanimously rejected SpaceX's consistency certification for up to 95 launches in August 2025, citing unresolved coastal resource harms.[134] The DAF's EIS evaluated these risks under NEPA, concluding that while temporary behavioral disruptions occur, no long-term population-level effects are anticipated with mitigations like pre-launch surveys, nest monitoring, and adaptive scheduling to avoid peak nesting.[127][123] Ongoing research, including collaborations with universities to compare pre- and post-launch bird vocalizations and wildlife responses, aims to quantify subtler impacts like altered foraging or stress hormones.[135] Critics, however, contend that accelerated cadence outpaces evidentiary baselines, potentially violating Endangered Species Act consultations, as evidenced by Representative Carbajal's 2024 bill seeking community aid for launch noise externalities amid wildlife concerns.[130] These tensions reflect broader trade-offs between space launch proliferation and habitat preservation in a region hosting diverse, recovering populations of coastal endemics.Geography and Ecology
Location and Physical Features
Vandenberg Space Force Base is located in northwestern Santa Barbara County, California, approximately seven miles northwest of Lompoc and 60 miles northwest of Santa Barbara.[136] The base's central coordinates are 34°44′14″N 120°35′04″W.[137] Positioned along the central California coast, it lies adjacent to the Pacific Ocean, with its western boundary forming part of the shoreline.[3] The base covers approximately 99,600 acres, encompassing diverse terrain that includes coastal dunes, cliffs, and beaches extending about 35 miles along the Pacific.[1][138] Inland areas feature a flat plateau ideal for aerospace infrastructure, surrounded by rolling hills, numerous canyons, and elevations rising toward the Santa Ynez Mountains to the east.[12][139] This geography includes transitional ecosystems such as chaparral, oak woodlands, and wetlands, with much of the undeveloped land serving as open space preserves.[140] The base's remoteness from major population centers, combined with its ocean-facing orientation, supports its role in space launches while preserving rugged natural features characteristic of the region's coastal-mountain interface.[12]Coastal Areas and Beaches
Vandenberg Space Force Base borders approximately 15 miles of Pacific Ocean shoreline in Santa Barbara County, California, characterized by sandy beaches, rocky intertidal zones, dunes, and bluffs that form part of the Central Coast's relatively undisturbed coastal ecosystem.[141] These areas include six base-managed beaches—Surf, Wall, Minuteman, Ocean Park, and two others—preserved as exemplars of pre-development California coastline with minimal human impact, supporting native habitats amid ongoing space launch activities.[141] The adjacent Vandenberg State Marine Reserve spans nearly 33 square miles offshore, encompassing sandy beaches, rocky reefs, kelp forests, and subtidal zones to depths exceeding 120 feet, where extraction of living marine resources is prohibited to maintain biodiversity.[142] Surf Beach provides the sole public access point to the base's coastal areas, reachable from the Amtrak station parking lot in Lompoc and hosting facilities like the Lompoc-Surf Station for lifeguard operations.[141] Wall Beach, nearest the base's cantonment area, features a rocky shoreline ideal for exploration by authorized personnel, while Minuteman Beach and Ocean Park (near the Santa Ynez River estuary) offer recreational use restricted to base pass holders, dependents, and sponsored guests.[141][142] Access to these beaches is governed by seasonal restrictions from March 1 to September 30 annually, closing sections of Surf, Wall, Minuteman, and Ocean Park beaches to protect nesting endangered species such as the western snowy plover, with full reopening typically occurring on September 19.[143][144] Base environmental management includes a comprehensive beach plan directing the 30th Civil Engineer Squadron to conduct regular cleanups, resulting in notably low trash levels compared to surrounding public coasts.[145] Rules prohibit entry into posted closed dunes and nesting areas, with enforcement ensuring compatibility between military operations and habitat preservation.[3] These measures balance recreational opportunities for the base community—such as surfing and hiking—with regulatory compliance under federal and state environmental laws.[118]Wildlife and Biodiversity
Vandenberg Space Force Base (VSFB) encompasses 99,579 acres of varied coastal habitats, including dunes, wetlands, chaparral, oak woodlands, and grasslands, which collectively support over 850 plant species and more than 300 wildlife species, reflecting a transitional zone between central and southern California ecosystems.[116][118] Wetlands cover approximately 4,967 to 5,110 acres, while coastal dunes span 760 to 1,660 acres, providing critical nesting and foraging areas amid 42 miles of coastline.[116] These ecosystems host 53 mammal species, 315 bird species (with 115 breeding on base), 17 reptile species, and 10 amphibian species, alongside fish and invertebrates such as the federally threatened vernal pool fairy shrimp.[118][116] The base's coastline sustains five marine mammal species, including Pacific harbor seals (with historical counts exceeding 1,300 individuals), California sea lions, northern elephant seals, Steller sea lions, and southern sea otters (population of 35 to 60 observed in 2020).[116] Bird diversity is particularly notable, encompassing shorebirds, seabirds, and raptors; coastal lagoons alone support 44 species, while riparian areas and scrub habitats attract migrants like whimbrels, marbled godwits, and black turnstones.[116] Among terrestrial mammals, species such as bats and ground squirrels persist, though feral pigs are managed as invasives to prevent habitat degradation.[116] Federally listed threatened or endangered species number at least 17 across plants and animals, including the endangered Vandenberg monkeyflower (Diplacus vandenbergensis), beach layia (Layia carnosa), and California least tern (Sternula antillarum athalassos), as well as threatened western snowy plover (Charadrius nivosus nivosus), tidewater goby (Eucyclogobius newberryi), and California red-legged frog (Rana draytonii).[146][116] These species benefit from habitat protections, such as seasonal restrictions on disturbances from February 15 to August 15 for nesting areas.[116] Biodiversity management occurs through the Integrated Natural Resources Management Plan, which coordinates with agencies like the U.S. Fish and Wildlife Service and California Department of Fish and Wildlife to control invasives (e.g., iceplant, European beachgrass), monitor populations, and restore native vegetation, ensuring compatibility with base operations.[116] Efforts include partnerships for releasing species like pigeon guillemots and surveys of sea lion haul-outs, with periodic assessments addressing climate vulnerabilities in grasslands and coastal scrub.[116][147]Base Community and Demographics
Population Composition
Vandenberg Space Force Base sustains a total population exceeding 18,000, comprising active-duty military personnel, Department of Defense civilians, contractors, and dependents.[148] Approximately 3,100 military members, primarily guardians assigned to Space Launch Delta 30, form the core uniformed workforce, supported by around 1,300 civilian employees including non-appropriated fund personnel.[3] Contractors number about 2,800, contributing specialized expertise in launch operations, maintenance, and technical support.[3] Dependents, estimated at 4,200 family members, reside primarily on base or in nearby communities, reflecting the transient nature of military assignments with typical tours of 2-4 years.[3] The on-base residential population, captured in census data for the Vandenberg AFB census-designated place, totals around 3,700 individuals as of 2023, with 53.8% male and 46.2% female.[149] Racial and ethnic composition includes 58.5% White, 14.6% Hispanic or Latino, and 11.3% two or more races, alongside smaller proportions of Black (9.2%), Asian (3.7%), and other groups.[150] Workforce demographics align closely with U.S. Space Force averages, where active-duty members are 81.1% male, 62.3% non-Hispanic White, and 57.9% hold a bachelor's degree or higher as of November 2023.[151] Civilian and contractor roles enhance continuity in technical fields, mitigating turnover from military rotations, though exact base-level breakdowns for education or ethnicity remain aggregated at the service level.[152] Retirees and their families, numbering approximately 20,000 in the surrounding area, further integrate into the local economy but are not directly base-assigned.[3]| Category | Approximate Number |
|---|---|
| Active-Duty Military | 3,100[3] |
| DoD Civilians/NAF | 1,300[3] |
| Contractors | 2,800[3] |
| Family Members | 4,200[3] |
| Total Supported Population | >18,000[148] |

