TacSat-3

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
TacSat-3
File:TacSat-3 (transparent).png
Artist's rendering of TacSat-3
Mission type Technology
Reconnaissance
Operator AFRL
COSPAR ID 2009-028A
SATCAT № 35001
Mission duration 2.5 years
Spacecraft properties
Bus ATK
Manufacturer Raytheon
Launch mass 400 kilograms (880 lb)
Start of mission
Launch date 19 May 2009, 23:55 (2009-05-19UTC23:55Z) UTC
Rocket Minotaur I
Launch site MARS LP-0B
Contractor Orbital
End of mission
Decay date 30 April 2012
Orbital parameters
Reference system Geocentric
Regime Low Earth
Perigee 432 kilometers (268 mi)[1]
Apogee 467 kilometers (290 mi)[1]
Inclination 40.4 degrees[1]
Period 93.57 minutes[1]
Epoch 22 May 2009[1]
File:TacSat-3 final logo (090416-F-5147E-001).png

TacSat-3 was the third in a series of U.S. military reconnaissance satellites. It was assembled in an Air Force Research Laboratory Space Vehicles Directorate facility at Kirtland Air Force Base, New Mexico.[2] The TacSat satellites are all designed to demonstrate the ability to provide real-time data collected from space to combatant commanders in the field. TacSat-3 includes three distinct payloads: the Advanced Responsive Tactically Effective Military Imaging Spectrometer (ARTEMIS) hyperspectral imager, the Ocean Data Telemetry Microsatellite Link and the Space Avionics Experiment.[3]

Design

File:Tacsat-3 080717-F-2907C-105.jpg
TacSat-3 bus during integration

TacSat-3 uses a standard satellite bus developed and provided by ATK. The payload consists of a two mirror Ritchey–Chrétien telescope plus correction optics, with a focus device incorporated in the secondary mirror unit, and with a slit Offner spectrometer. The spectrometer uses the ARTEMIS hyperspectral imaging sensor (HSI), which is a single HgCdTe Focal Plane Array covering the entire V/NIR/SWIR spectrum from 400 nm to 2500 nm at a uniform resolution of 5 nm. ARTEMIS measures first the spectral information at each point on the ground in 400 spectral channels. HSI data cubes obtained by ARTEMIS are then handled by a reprogrammable digital signal processor with 16 GB data storage capability to generate on-board products and for in-theater downlink.[4][5] TacSat-3's main focus is land-based HSI.[6] According to Peter Wegner from the Operationally Responsive Space Office, TacSat-3 cost US$90 million [7]

Launch

In January 2009 the Air Force announced that a malfunctioning component has postponed the launch date on its Minotaur rocket.[8] However, in March 2009 it was announced that the component issues had been resolved and a launch date was set for May 5, 2009.[9] The May 5 launch attempt was scrubbed and a new launch date was set for May 19, with a backup date of May 20. The launch occurred successfully at 23:55 UTC on 19 May, 20 minutes into a launch window running from 23:35 to 03:30 (7:35 PM to 11:30 PM local time) each night.[10]

The first attempt to launch TacSat-3 was made on 6 May, during a window running from 00:00-03:00 UTC (20:00-23:00 local time on 5 May). However, due to thunderstorms and very low ceilings which prevented the surveillance plane from taking off, this launch attempt was scrubbed and the next attempt was scheduled for May 8 during the same window. The May 8th attempt was also scrubbed due to thunderstorms and heavy rain, which once again, prevented the surveillance plane from being able to take off. Another attempt was scheduled for the next day on May 9, again with the same window. Although the weather cooperated better for the May 9th attempt, a launch support equipment problem caused a delay of approximately three hours past the scheduled launch time. This problem was resolved and the countdown resumed. However, with 2 minutes and 16 seconds left on the countdown clock, an unexpected hold was called.[11] Several minutes later, this launch attempt was also scrubbed due to low electrical voltage on the AGC of the Flight Termination System. A new launch date was set for May 19 with May 20 as a backup date.

The spacecraft was successfully launched at 23:55 UTC on May 19, 2009 after a small delay to remove off shore boaters from the exclusion area.

Mission

TacSat-3 achieved a HSI ground resolution of 4 meters, which enabled it to detect and identify tactical targets.[12] After a successful completion of a one-year experimental phase, and the acquisition of more than 2100 images, TacSat-3 was handed over to the Air Force in June 2010 as a full-time operational asset. It is the first hyperspectral satellite with the ability to provide reconnaissance within 10 minutes after passing overhead. Field commanders using tactical radio equipment, such as the AN/PRC-117F Multiband Manpack Radio, can directly communicate with the satellite in the ultra high frequency band.[13][14][15] TacSat-3/ARTEMIS observations of the National Mall and the Kilauea Volcano to support technical validation of the sensor have been released in June 2010. The released images comprise three of the more than 400 spectral bands.[16]

TacSat-3 completed operations on 15 February 2012. On 30 April 2012, following the decay of its orbit, TacSat-3 reentered the Earth's atmosphere and burned up.[17][18]

Gallery

References

  1. 1.0 1.1 1.2 1.3 1.4 Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.

External links