Space Test Program
The Space Test Program (STP) is the primary provider of spaceflight for the United States Department of Defense (DOD) space science and technology community. STP is conducted by the Space Development and Test Wing of the United States Air Force.[1] STP provides spaceflight via the Space Shuttle, International Space Station, piggybacks, secondary payloads and dedicated launch services.
Contents
STP-1 Launch
On March 9, 2007, six satellites were launched into LEO on a shared Atlas V launch vehicle. The satellites were:
- Orbital Express: ASTRO and NextSat, (DARPA)
- MidSTAR-1, (United States Naval Academy)
- FalconSat3, (United States Air Force Academy)
- STPSat 1, USAF's Space Test Program
- CFESat, (Los Alamos National Laboratory)
The satellites shared the launcher through use of an Evolved Expendable Launch Vehicle Secondary Payload Adapter (ESPA).[2] United Launch Alliance provided a video feed of the launch.[3]
STP-S26
Activities during 2001
During August 2001 STP conducted two successful activities using the Shuttle and ISS. STS-105 delivered and successfully deployed the Materials International Space Station Experiment (MISSE) externally on the ISS. MISSE, a passive materials exposure experiment, is the first external experiment on ISS. In addition, STS-105 retrieved and returned MACE II (Middeck Active Control Experiment II) from the ISS. MACE II was the first experiment on ISS and was operated for nearly a year.[4]
On September 30, 2001, STP and NASA launched the Kodiak Star mission on an Athena I launch vehicle. This was the first orbital launch out of Kodiak Island, Alaska. In addition to NASA's Starshine III spacecraft, this mission included three small DoD spacecraft which tested a variety of new space technologies.[5]
STP and the Air Force Research Laboratory’s Space Vehicles Directorate developed a secondary payload adapter ring for the Evolved Expendable Launch Vehicle (EELV), which can host up to six 400-pound micro satellites. STP also worked closely with NASA and the United States Navy on the Geosynchronous Imaging Fourier Transform Spectrometer/Indian Ocean Meteorology and Oceanography Imager project.[citation needed]
In December 2001, STS-108 hosted the Ram Burn Observation (RAMBO) Experiment and Shuttle Ionospheric Modification with Pulsed Localized Exhaust (SIMPLEX) experiment. RAMBO used an operational satellite to view Shuttle engine firings to optimize band selection for SBIRS and improve the fidelity of DOD plume models. SIMPLEX observed ionospheric disturbances created by Shuttle engine burns via ground radar sites and supported plume technology, plume signature, and space weather modeling.[citation needed]
Activities during 2002
RAMBO and SIMPLEX flew again on STS-110 in April 2002.[citation needed] In June 2002, RAMBO was again successful on STS-111 with a total of four Shuttle engine burns viewed. STP also worked to obtain a 1-year radio frequency license extension for the Picosat experiment launched on the September 2001 Kodiak Star mission.[citation needed]
Activities during 2003
On January 6, 2003, STP and the Naval Research Laboratory launched the Coriolis satellite, a risk-reduction effort for NPOESS, aboard a Titan II launch vehicle.[6]
Activities during 2008
The C/NOFS (Communications/Navigation Outage Forecasting System) satellite, which was launched on 2008-04-16, will be operated by the Space Test Program.[citation needed]
Activities during 2014
As announced on Tuesday, October 14, 2014, the United States Department of Defense awarded Sierra Nevada Corporation’s Space Systems (previously known as SpaceDev) with a contract to develop and build a next-generation science and technology demonstration satellite, known as STPSat-5, for their Space Test Program.[7]
Upcoming activities
The STP-2 (DoD Space Test Program) payload is scheduled to be launched aboard a Falcon Heavy in March 2017.[8] The payload should include an ISAT (Innovative Spacebased radar Antenna Technology) flight demonstrator satellite massing over 5000 kg, and COSMIC-2, a cluster of six satellites, massing at 277.8 kg each.[9] The ISAT program aims to deploy extremely large (up to 300 yards) electronically scanning radar antennas in orbit.[10] The primary role of the COSMIC-2 satellite constellation is to provide radio occultation data with an average latency of 45 minutes. The six satellites will be placed on an orbit with an inclination of 24 to 28.5 degrees with six separate orbital planes with 60 degree separation between them.[11] The integrated payload stack will be integrated using EELV Secondary Payload Adapter. Two ESPA Grande rings will be used to mount the six COSMIC-2 satellites beneath the ESPA ring hosting the DSX payload and avionics modules.[12] STP-2 will also host up to 8 CubeSat nanosatellites deployed with P-PODs (Poly Picosatellite Orbital Deployers).[9]
Other secondary payloads include LightSail,[13] Prox-1 nanosatellite,[13] Oculus-ASR nanosatellite,[14] GPIM,[15][16][17] and the Deep Space Atomic Clock.[18]
References
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ NASA: Kodiak Star 2001
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 9.0 9.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ 13.0 13.1 Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
