Boeing X-37

From Infogalactic: the planetary knowledge core
(Redirected from Boeing X-37B)
Jump to: navigation, search
X-37
Boeing X-37B inside payload fairing before launch.jpg
The OTV-1 X-37B in April 2010, inside its payload fairing prior to launch
Role Spaceplane
National origin United States
Manufacturer Boeing Defense, Space & Security
First flight 7 April 2006 (first drop test)
Introduction 22 April 2010 (first spaceflight)
Status 3 spaceflights completed[1][2][3]
1 spaceflight in progress[4]
Primary user X-37A: NASA/DARPA
X-37B: United States Air Force
Number built X-37A: 1
X-37B: 2
Developed from Boeing X-40

The Boeing X-37, also known as the Orbital Test Vehicle (OTV), is a reusable unmanned spacecraft. It is boosted into space by a launch vehicle, then re-enters Earth's atmosphere and lands as a spaceplane. The X-37 is operated by the United States Air Force for orbital spaceflight missions intended to demonstrate reusable space technologies.[5] It is a 120%-scaled derivative of the earlier Boeing X-40.

The X-37 began as a NASA project in 1999, before being transferred to the U.S. Department of Defense in 2004. It conducted its first flight as a drop test on 7 April 2006, at Edwards Air Force Base, California. The spaceplane's first orbital mission, USA-212, was launched on 22 April 2010 using an Atlas V rocket. Its successful return to Earth on 3 December 2010 was the first test of the vehicle's heat shield and hypersonic aerodynamic handling. A second X-37 was launched on 5 March 2011, with the mission designation USA-226; it returned to Earth on 16 June 2012. A third X-37 mission, USA-240, launched on 11 December 2012 and landed at Vandenberg AFB on 17 October 2014. The fourth X-37 mission, USA-261, launched on 20 May 2015 and is in progress.

<templatestyles src="Template:TOC limit/styles.css" />

Development

Origins

In 1999, NASA selected Boeing Integrated Defense Systems to design and develop an orbital vehicle, built by the California branch of Boeing's Phantom Works. Over a four-year period, a total of $192 million was contributed to the project, with NASA contributing $109 million, the U.S. Air Force $16 million, and Boeing $67 million. In late 2002, a new $301-million contract was awarded to Boeing as part of NASA's Space Launch Initiative framework.[6]

1999 artist's rendering of the X-37 spacecraft

The X-37's aerodynamic design was derived from the larger Space Shuttle orbiter, hence the X-37 has a similar lift-to-drag ratio, and a lower cross range at higher altitudes and Mach numbers compared to DARPA's Hypersonic Technology Vehicle.[7] An early requirement for the spacecraft called for a delta-v of 7,000 mph (3.1 km/s) to change its orbit.[8] An early goal for the program was for the X-37 to rendezvous with satellites and perform repairs.[9] The X-37 was originally designed to be carried into orbit in the Space Shuttle's cargo bay, but underwent redesign for launch on a Delta IV or comparable rocket after it was determined that a shuttle flight would be uneconomical.[10]

The X-37 was transferred from NASA to the Defense Advanced Research Projects Agency (DARPA) on 13 September 2004.[11] Thereafter, the program became a classified project. DARPA promoted the X-37 as part of the independent space policy that the United States Department of Defense has pursued since the 1986 Challenger disaster.

Glide testing

The vehicle that was used as an atmospheric drop test glider had no propulsion system. Instead of an operational vehicle's payload bay doors, it had an enclosed and reinforced upper fuselage structure to allow it to be mated with a mothership. In September 2004, DARPA announced that for its initial atmospheric drop tests the X-37 would be launched from the Scaled Composites White Knight, a high-altitude research aircraft.[12]

The Scaled Composites White Knight was used to launch the X-37A on glide tests.

On 21 June 2005, the X-37A completed a captive-carry flight underneath the White Knight from Mojave Spaceport in Mojave, California.[13][14] Through the second half of 2005, the X-37A underwent structural upgrades, including the reinforcement of its nose wheel supports. Further captive-carry flight tests and the first drop test were initially expected to occur in mid-February 2006. The X-37's public debut was scheduled for its first free flight on 10 March 2006, but was canceled due to an Arctic storm.[15] The next flight attempt, on 15 March 2006, was canceled due to high winds.[15]

On 24 March 2006, the X-37 flew again, but a datalink failure prevented a free flight, and the vehicle returned to the ground still attached to its White Knight carrier aircraft. On 7 April 2006, the X-37 made its first free glide flight. During landing, the vehicle overran the runway and sustained minor damage.[16] Following the vehicle's extended downtime for repairs, the program moved from Mojave to Air Force Plant 42 (KPMD) in Palmdale, California for the remainder of the flight test program. White Knight continued to be based at Mojave, though it was ferried to Plant 42 when test flights were scheduled. Five additional flights were performed,[N 1] two of which resulted in X-37 releases with successful landings. These two free flights occurred on 18 August 2006 and 26 September 2006.[17]

X-37B Orbital Test Vehicle

On 17 November 2006, the U.S. Air Force announced that it would develop its own variant from NASA's X-37A. The Air Force version was designated the X-37B Orbital Test Vehicle (OTV). The OTV program was built on earlier industry and government efforts by DARPA, NASA and the Air Force, and was led by the U.S. Air Force Rapid Capabilities Office, in partnership with NASA and the Air Force Research Laboratory. Boeing was the prime contractor for the OTV program.[8][18][19] The X-37B was designed to remain in orbit for up to 270 days at a time.[20] The Secretary of the Air Force stated that the OTV program would focus on "risk reduction, experimentation, and operational concept development for reusable space vehicle technologies, in support of long-term developmental space objectives."[18]

The X-37B was originally scheduled for launch in the payload bay of the Space Shuttle, but following the 2003 Columbia disaster, it was transferred to a Delta II 7920. The X-37B was subsequently transferred to a shrouded configuration on the Atlas V rocket, following concerns over the unshrouded spacecraft's aerodynamic properties during launch.[21] Following their missions, X-37B spacecraft land on a runway at Vandenberg Air Force Base, California, with Edwards Air Force Base as an alternate site.[22] In 2010, manufacturing work began on the second X-37B, OTV-2,[23] which conducted its maiden launch in March 2011.[24]

On 8 October 2014, NASA confirmed that X-37B vehicles would be housed at Kennedy Space Center in Orbiter Processing Facilities (OPF) 1 and 2, hangars previously occupied by the Space Shuttle. Boeing had said the space planes would use OPF-1 in January 2014, and the Air Force had previously said it was considering consolidating X-37B operations, housed at Vandenberg Air Force Base in California, nearer to their launch site at Cape Canaveral. NASA also stated that the program had completed tests to determine whether the X-37B, one-fourth the size of the Space Shuttle, could land on the former Shuttle runways.[25] NASA furthermore stated that renovations of the two hangars would be completed by the end of 2014; the main doors of OPF-1 were marked with the message "Home of the X-37B" by this point.[25]

Most of the activities of the X-37B project are secret. The official U.S. Air Force statement is that the project is "an experimental test program to demonstrate technologies for a reliable, reusable, unmanned space test platform for the U.S. Air Force."[5] The primary objectives of the X-37B are twofold: reusable spacecraft technology, and operating experiments which can be returned to Earth.[5] The Air Force states that this includes testing avionics, flight systems, guidance and navigation, thermal protection, insulation, propulsion, and re-entry systems.[26]

Speculation regarding purpose

In 2010, Tom Burghardt wrote for Space Daily that the X-37B could be used as a spy satellite or to deliver weapons from space.[27] The Pentagon subsequently denied claims that the X-37B's test missions supported the development of space-based weapons.[27] In January 2012, allegations were made that the X-37B was being used to spy on China's Tiangong-1 space station module.[28]

Former U.S. Air Force orbital analyst Brian Weeden later refuted this claim, emphasizing that the different orbits of the two spacecraft precluded any practical surveillance fly-bys.[29] In October 2014, The Guardian reported the claims of security experts that the X-37B was being used "to test reconnaissance and spy sensors, particularly how they hold up against radiation and other hazards of orbit."[30]

Design

At the time of its maiden launch, the X-37 (far right) was the smallest and lightest orbital spaceplane yet flown. Both the North American X-15 and SpaceShipOne were suborbital. Of the spaceplanes shown, only the X-37 and Buran conducted unmanned spaceflights.

The X-37 Orbital Test Vehicle is a reusable robotic spaceplane. It is a 120%-scale derivative of the Boeing X-40,[6][22] measuring over 29 feet (8.8 m) in length, and features two angled tail fins.[5][31] The X-37 launches atop an Atlas V version 501 rocket with a Centaur second stage.[5][19] The X-37 is designed to operate in a speed range of up to Mach 25 on its reentry.[32][33]

The technologies demonstrated in the X-37 include an improved thermal protection system, enhanced avionics, an autonomous guidance system and an advanced airframe.[10] The spaceplane's thermal protection system is built upon previous generations of atmospheric reentry spacecraft,[34] incorporating silica ceramic tiles.[35] The X-37's avionics suite was used by Boeing to develop its CST-100 manned spacecraft.[36] According to NASA, the development of the X-37 will "aid in the design and development of NASA's Orbital Space Plane, designed to provide a crew rescue and crew transport capability to and from the International Space Station".[37]

The X-37 is independently powered by one Aerojet AR2-3 engine using storable propellants, providing thrust of Lua error in Module:Convert at line 1851: attempt to index local 'en_value' (a nil value)..[38] The human-rated AR2-3 engine had been used on the dual-power NF-104A astronaut training vehicle, and was given a new flight certification for use on the X-37 with hydrogen peroxide/JP-8 propellants.[39]

The X-37 lands automatically upon returning from orbit, and is the second reusable spacecraft to have such a capability, after the Soviet Buran shuttle.[40] The X-37 is the smallest and lightest orbital spaceplane flown to date; with a launch mass of around 11,000 pounds (5,000 kg), it is approximately a quarter the size of the Space Shuttle orbiter.[41] In 2013, Guinness World Records recognised the X-37 as the world's smallest orbital spaceplane.[42]

The Space Foundation awarded the X-37 team on 13 April 2015 with the 2015 Space Achievement Award "for significantly advancing the state of the art for reusable spacecraft and on-orbit operations, with the design, development, test and orbital operation of the X-37B space flight vehicle over three missions totaling 1,367 days in space."[43]

Operational history

As of 17 October 2014, the two operational X-37Bs have conducted three orbital missions, spending a combined total 1,367 days in space.[44]

OTV-1

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

OTV-1 sits on the runway after landing at Vandenberg AFB at the close of its USA-212 mission on 3 December 2010.

OTV-1, the first X-37B, launched on its first mission – USA-212 – on an Atlas V rocket from Cape Canaveral Air Force Station, Florida, on 22 April 2010 at 23:58 UTC. The spacecraft was placed into low Earth orbit for testing.[19] While the U.S. Air Force revealed few orbital details of the mission, amateur astronomers claimed to have identified the spacecraft in orbit and shared their findings. A worldwide network of amateur astronomers reported that, on 22 May 2010, the spacecraft was in an inclination of 39.99 degrees, circling the Earth once every 90 minutes on an orbit 249 by 262 miles (401 by 422 km).[45][46] OTV-1 reputedly passed over the same given spot on Earth every four days, and operated at an altitude of 255 miles (410 km), which is typical for military surveillance satellites.[47] Such an orbit is also common among civilian LEO satellites, and the spaceplane's altitude was the same as that of the ISS and most other manned spacecraft.

The U.S. Air Force announced on 30 November 2010 that OTV-1 would return for a landing during the 3–6 December timeframe.[48][49] As scheduled, OTV-1 de-orbited, reentered Earth's atmosphere, and landed successfully at Vandenberg AFB on 3 December 2010, at 09:16 UTC,[50][51][52] conducting America's first autonomous orbital landing onto a runway; the first spacecraft to perform such a feat was the Soviet Buran shuttle in 1988. In all, OTV-1 spent 224 days in space.[53] OTV-1 suffered a tire blowout during landing and sustained minor damage to its underside.[23]

OTV-2

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

OTV-2, the second X-37B, launched on its inaugural mission, designated USA-226,[54] aboard an Atlas V rocket from Cape Canaveral on 5 March 2011.[55] The mission was classified and described by the U.S. military as an effort to test new space technologies.[56] On 29 November 2011, the U.S. Air Force announced that it would extend the mission of USA-226 beyond the 270-day baseline design duration.[53] In April 2012, General William L. Shelton of the Air Force Space Command declared the ongoing mission a "spectacular success".[57]

On 30 May 2012, the Air Force stated that OTV-2 would complete its mission and land at Vandenberg AFB in June 2012.[58][59] The spacecraft landed autonomously on 16 June 2012, having spent 469 days in space.[1][60]

OTV-3

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

OTV-3, the second mission for the first X-37B and the third X-37B mission overall, was originally scheduled to launch on 25 October 2012,[61] but was postponed because of an engine issue with the Atlas V launch vehicle.[62] The X-37B was successfully launched from Cape Canaveral on 11 December 2012.[41][63][64] The launch was designated USA-240.[65][66] The OTV-3 mission ended with a landing at Vandenberg AFB on 17 October 2014 at 16:24 UTC, after a total time in orbit of just under 675 days.[3][67]

OTV-4

The Air Force launched a fourth X-37B mission, designated OTV-4 and codenamed AFSPC-5, aboard an Atlas V rocket from Cape Canaveral Air Force Station on 20 May 2015.[44][68] The launch was designated USA-261 and is the second flight of the second X-37B vehicle.[21] The mission will test a Hall effect thruster in support of the Advanced Extremely High Frequency communications satellite program,[68] and conduct a NASA investigation for testing various materials in space.[4][21][43] The mission is expected to last at least 200 days,[21] and as of 8 December 2015 the vehicle remains in orbit.[69]

Variants

X-37A

The X-37A was the initial NASA version of the spacecraft; the X-37A Approach and Landing Test Vehicle (ALTV) was used in drop glide tests in 2005 and 2006.[14][70]

X-37B

The X-37B is a modified version of the NASA X-37A, intended for the U.S. Air Force.[5] It conducted multiple orbital test missions.[63]

X-37C

In 2011, Boeing announced plans for a scaled-up variant of the X-37B, referring to it as the X-37C. The X-37C spacecraft would be between 165% and 180% of the size of the X-37B, allowing it to transport up to six astronauts inside a pressurized compartment housed in the cargo bay. Its proposed launch vehicle is the Atlas V Evolved Expendable Launch Vehicle.[71] In this role, the X-37C could potentially compete with Boeing's CST-100 commercial space capsule.[72]

Specifications

Three-views of the X-37B

X-37B

Data from USAF,[5][34] Boeing,[73] Air & Space Magazine,[70] and PhysOrg.[74]

General characteristics

  • Crew: none
  • Length: 29 ft 3 in (8.92 m)
  • Wingspan: 14 ft 11 in (4.55 m)
  • Height: 9 ft 6 in (2.90 m)
  • Max takeoff weight: 11,000 lb (4,990 kg)
  • Electrical power: Gallium arsenide solar cells with lithium-ion batteries[5]
  • Payload bay: 7 × 4 ft (2.1 × 1.2 m)[73]
  • Powerplant: 1 × Aerojet AR2-3 rocket engine, 6,596 lbf (29.341 kN) thrust using hydrogen peroxide and JP-8 fuel[38]

Performance

See also

Related development
  • Boeing X-40, a subsonic test glider, direct predecessor to the X-37B
Aircraft of comparable role, configuration and era

Notes

  1. Source of flights: mission markings posted on side of White Knight aircraft.
  2. This figure is based on pre-launch design estimates; it does not reflect the spacecraft's actual performance capacity. During its 2012–2014 test mission, the OTV-3 X-37B spent over 670 days in space.

References

  1. 1.0 1.1 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. 3.0 3.1 Lua error in package.lua at line 80: module 'strict' not found.
  4. 4.0 4.1 Lua error in package.lua at line 80: module 'strict' not found.
  5. 5.0 5.1 5.2 5.3 5.4 5.5 5.6 5.7 Lua error in package.lua at line 80: module 'strict' not found.
  6. 6.0 6.1 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. 8.0 8.1 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. 10.0 10.1 Yenne 2005, p. 277.
  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. 14.0 14.1 Lua error in package.lua at line 80: module 'strict' not found.
  15. 15.0 15.1 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. 18.0 18.1 Lua error in package.lua at line 80: module 'strict' not found.
  19. 19.0 19.1 19.2 Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. 21.0 21.1 21.2 21.3 Lua error in package.lua at line 80: module 'strict' not found.
  22. 22.0 22.1 Lua error in package.lua at line 80: module 'strict' not found.
  23. 23.0 23.1 Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. 25.0 25.1 Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. 27.0 27.1 Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Miller 2001, p. 377.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. 34.0 34.1 Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. 38.0 38.1 Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. 41.0 41.1 Lua error in package.lua at line 80: module 'strict' not found.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. 43.0 43.1 Lua error in package.lua at line 80: module 'strict' not found.
  44. 44.0 44.1 Lua error in package.lua at line 80: module 'strict' not found.
  45. Lua error in package.lua at line 80: module 'strict' not found.
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. Lua error in package.lua at line 80: module 'strict' not found.
  50. Lua error in package.lua at line 80: module 'strict' not found.
  51. Lua error in package.lua at line 80: module 'strict' not found.
  52. Lua error in package.lua at line 80: module 'strict' not found.
  53. 53.0 53.1 Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. Lua error in package.lua at line 80: module 'strict' not found.
  57. Lua error in package.lua at line 80: module 'strict' not found.
  58. Lua error in package.lua at line 80: module 'strict' not found.
  59. Lua error in package.lua at line 80: module 'strict' not found.
  60. Lua error in package.lua at line 80: module 'strict' not found.
  61. Lua error in package.lua at line 80: module 'strict' not found.
  62. Lua error in package.lua at line 80: module 'strict' not found.
  63. 63.0 63.1 Lua error in package.lua at line 80: module 'strict' not found.
  64. Lua error in package.lua at line 80: module 'strict' not found.
  65. Lua error in package.lua at line 80: module 'strict' not found.
  66. Lua error in package.lua at line 80: module 'strict' not found.
  67. Lua error in package.lua at line 80: module 'strict' not found.
  68. 68.0 68.1 Lua error in package.lua at line 80: module 'strict' not found.
  69. Lua error in package.lua at line 80: module 'strict' not found.
  70. 70.0 70.1 Lua error in package.lua at line 80: module 'strict' not found.
  71. Lua error in package.lua at line 80: module 'strict' not found.
  72. Lua error in package.lua at line 80: module 'strict' not found.
  73. 73.0 73.1 Lua error in package.lua at line 80: module 'strict' not found.
  74. Lua error in package.lua at line 80: module 'strict' not found.
  75. Lua error in package.lua at line 80: module 'strict' not found.
  76. Lua error in package.lua at line 80: module 'strict' not found.

Bibliography

  • 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.

External links