added Category:USA satellites using HotCat
|
|
||
Line 23: | Line 23: | ||
USA-214 was launched by [[United Launch Alliance]], using an [[Atlas V]] 531 carrier rocket flying from [[Cape Canaveral Air Force Station Space Launch Complex 41|Space Launch Complex 41]] at the [[Cape Canaveral Air Force Station]]. The launch occurred at 11:07 UTC on 14 August 2010,<ref>{{cite web|url=http://www.spaceflightnow.com/atlas/av019/|title=Rise and shine: Atlas 5 rocket successfully soars at dawn|last=Ray|first=Justin|date=14 August 2010|publisher=Spaceflight Now|accessdate=16 August 2010}}</ref> and resulted in the spacecraft being deployed successfully into a [[geosynchronous transfer orbit]] with a [[apsis|perigee]] of {{convert|221|km}}, an [[apsis|apogee]] of {{convert|50179|km}}, and 22.2° degrees [[inclination]].<ref>{{cite web|url=http://planet4589.org/space/jsr/latest.html|title=Issue 632|last=McDowell|first=Jonathan|date=12 August 2010|publisher=Jonathan's Space Report|accessdate=16 August 2010}}</ref> |
USA-214 was launched by [[United Launch Alliance]], using an [[Atlas V]] 531 carrier rocket flying from [[Cape Canaveral Air Force Station Space Launch Complex 41|Space Launch Complex 41]] at the [[Cape Canaveral Air Force Station]]. The launch occurred at 11:07 UTC on 14 August 2010,<ref>{{cite web|url=http://www.spaceflightnow.com/atlas/av019/|title=Rise and shine: Atlas 5 rocket successfully soars at dawn|last=Ray|first=Justin|date=14 August 2010|publisher=Spaceflight Now|accessdate=16 August 2010}}</ref> and resulted in the spacecraft being deployed successfully into a [[geosynchronous transfer orbit]] with a [[apsis|perigee]] of {{convert|221|km}}, an [[apsis|apogee]] of {{convert|50179|km}}, and 22.2° degrees [[inclination]].<ref>{{cite web|url=http://planet4589.org/space/jsr/latest.html|title=Issue 632|last=McDowell|first=Jonathan|date=12 August 2010|publisher=Jonathan's Space Report|accessdate=16 August 2010}}</ref> |
||
The spacecraft was intended to manoeuvre from the transfer orbit into which it was launched to its operational [[geosynchronous orbit]] by means of a liquid-fueled [[apogee motor]] and several [[Hall effect thruster]]s, a process which normally takes 105 days.<ref name="SFN-EngineFailure">{{cite web|url=http://www.spaceflightnow.com/atlas/av019/100830orbit.html|title=Military satellite relying on backup plan to save itself|last=Ray|first=Justin|date=30 August 2010|publisher=Spaceflight Now|accessdate=31 August 2010}}</ref><ref>{{cite web |url=http://www.aviationweek.com/aw/generic/story_channel.jsp?channel=space&id=news/asd/2010/11/12/02.xml |title=Japanese Engine Not AEHF Issue: USAF Official |first=Amy |last=Butler |date=15 November 2010 |publisher=Aviation Week |accessdate=29 January 2011}}</ref><ref>{{cite web |url=http://www.aviationweek.com/aw/generic/story_generic.jsp?channel=space&id=news/awst/2010/11/22/AW_11_22_2010_p36-270626.xml |title=USAF: AEHF-1 Engine Failure An Anomaly |first=Amy |last=Butler |date=22 November 2010 |publisher=Aviation Week |accessdate=29 January 2011}}</ref> However, the satellite's Liquid Apogee Engine motor malfunctioned shortly after ignition on both its first burn on 15 August 2010 and a second attempt on 17 August,<ref>Ray, Justin (Sept. 2, 2010), ''Spaceflight Now'', "[http://spaceflightnow.com/atlas/av019/100902inquiry.html Investigators probing what went wrong with AEHF 1]" (accessed Dec. 14, 2011)</ref> and it was declared inoperable.<ref name="SFN-EngineFailure" /><ref>{{cite web|title=Main engine probably not to blame for AEHF 1 trouble|url=http://spaceflightnow.com/atlas/av019/101019aehf2.html|accessdate=2010-10-19}}</ref> |
The spacecraft was intended to manoeuvre from the transfer orbit into which it was launched to its operational [[geosynchronous orbit]] by means of a liquid-fueled [[apogee motor]] (LAE) and several [[Hall effect thruster]]s, a process which normally takes 105 days.<ref name="SFN-EngineFailure">{{cite web|url=http://www.spaceflightnow.com/atlas/av019/100830orbit.html|title=Military satellite relying on backup plan to save itself|last=Ray|first=Justin|date=30 August 2010|publisher=Spaceflight Now|accessdate=31 August 2010}}</ref><ref>{{cite web |url=http://www.aviationweek.com/aw/generic/story_channel.jsp?channel=space&id=news/asd/2010/11/12/02.xml |title=Japanese Engine Not AEHF Issue: USAF Official |first=Amy |last=Butler |date=15 November 2010 |publisher=Aviation Week |accessdate=29 January 2011}}</ref><ref>{{cite web |url=http://www.aviationweek.com/aw/generic/story_generic.jsp?channel=space&id=news/awst/2010/11/22/AW_11_22_2010_p36-270626.xml |title=USAF: AEHF-1 Engine Failure An Anomaly |first=Amy |last=Butler |date=22 November 2010 |publisher=Aviation Week |accessdate=29 January 2011}}</ref> However, the satellite's Liquid Apogee Engine motor malfunctioned shortly after ignition on both its first burn on 15 August 2010 and a second attempt on 17 August,<ref>Ray, Justin (Sept. 2, 2010), ''Spaceflight Now'', "[http://spaceflightnow.com/atlas/av019/100902inquiry.html Investigators probing what went wrong with AEHF 1]" (accessed Dec. 14, 2011)</ref> and it was declared inoperable.<ref name="SFN-EngineFailure" /><ref>{{cite web|title=Main engine probably not to blame for AEHF 1 trouble|url=http://spaceflightnow.com/atlas/av019/101019aehf2.html|accessdate=2010-10-19}}</ref> |
||
To solve the problem, the perigee altitude was raised to 4700 km (2900 miles) using twelve firings of the smaller Reaction Engine Assembly thrusters, originally intended for attitude control during LAE maneuvers.<ref name= "Ray2011">Ray, Justin (October 9, 2011), ''Spaceflight Now'', "[http://spaceflightnow.com/atlas/av019/111009.html Air Force satellite's epic ascent should finish soon]" (accessed Dec. 14 2011)</ref> From this altitude, the solar arrays were deployed and the orbit was raised toward the operational orbit over the course of nine months using the 0.27 Newton [[Hall effect thruster|Hall thrusters]], a form of [[Electrically powered spacecraft propulsion|electric propulsion]] which is highly efficient, but produces very low thrust. |
To solve the problem, the perigee altitude was raised to 4700 km (2900 miles) using twelve firings of the smaller Reaction Engine Assembly thrusters, originally intended for attitude control during LAE maneuvers.<ref name= "Ray2011">Ray, Justin (October 9, 2011), ''Spaceflight Now'', "[http://spaceflightnow.com/atlas/av019/111009.html Air Force satellite's epic ascent should finish soon]" (accessed Dec. 14 2011)</ref> From this altitude, the solar arrays were deployed and the orbit was raised toward the operational orbit over the course of nine months using the 0.27 Newton [[Hall effect thruster|Hall thrusters]], a form of [[Electrically powered spacecraft propulsion|electric propulsion]] which is highly efficient, but produces very low thrust. |
Template:Infobox spacecraft USA-214, known before launch as Advanced Extremely High Frequency 1orAEHF SV-1, is a military communications satellite operated by the United States Air Force. It is the first of four spacecraft to be launched as part of the Advanced Extremely High Frequency program, which will replace the earlier Milstar system.[1]
The USA-214 spacecraft was constructed by Lockheed Martin, and is based around the A2100 satellite bus. The spacecraft has a mass of 6,168 kilograms (13,598 lb) and a design life of 14 years.[2] It will be used to provide super high frequency and extremely high frequency communications for the armed forces of the United States, as well as those of the United Kingdom, the Netherlands, and Canada.[1]
USA-214 was launched by United Launch Alliance, using an Atlas V 531 carrier rocket flying from Space Launch Complex 41 at the Cape Canaveral Air Force Station. The launch occurred at 11:07 UTC on 14 August 2010,[3] and resulted in the spacecraft being deployed successfully into a geosynchronous transfer orbit with a perigee of 221 kilometres (137 mi), an apogee of 50,179 kilometres (31,180 mi), and 22.2° degrees inclination.[4]
The spacecraft was intended to manoeuvre from the transfer orbit into which it was launched to its operational geosynchronous orbit by means of a liquid-fueled apogee motor (LAE) and several Hall effect thrusters, a process which normally takes 105 days.[5][6][7] However, the satellite's Liquid Apogee Engine motor malfunctioned shortly after ignition on both its first burn on 15 August 2010 and a second attempt on 17 August,[8] and it was declared inoperable.[5][9]
To solve the problem, the perigee altitude was raised to 4700 km (2900 miles) using twelve firings of the smaller Reaction Engine Assembly thrusters, originally intended for attitude control during LAE maneuvers.[10] From this altitude, the solar arrays were deployed and the orbit was raised toward the operational orbit over the course of nine months using the 0.27 Newton Hall thrusters, a form of electric propulsion which is highly efficient, but produces very low thrust.
| |
---|---|
January |
|
February |
|
March |
|
April |
|
May |
|
June |
|
July |
|
August |
|
September |
|
October |
|
November |
|
December |
|
Launches are separated by dots ( • ), payloads by commas ( , ), multiple names for the same satellite by slashes ( / ). |
This article about one or more spacecraft of the United States is a stub. You can help Wikipedia by expanding it. |