VSS Enterprise crash

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
VSS Enterprise crash
VSS Enterprise, the spaceship involved in the accident, attached to its mothership, VMS Eve.
VSS Enterprise, the spacecraft involved in the accident, attached to its mothership, VMS Eve
Accident summary
Date October 31, 2014 (2014-10-31)
Summary Inflight break-up, cause under investigation
Site Mojave Desert, California, United States
Crew 2
Injuries (non-fatal) 1
Fatalities 1
Survivors 1
Aircraft type Scaled Composites Model 339 SpaceShipTwo
Aircraft name VSS Enterprise
Operator Virgin Galactic
Registration N339SS
Flight origin Mojave Air and Space Port, California, United States
Destination Mojave Air and Space Port

On October 31, 2014, VSS Enterprise, a Virgin Galactic Scaled Composites Model 339 SpaceShipTwo experimental spaceflight test vehicle, suffered a catastrophic in-flight breakup and crashed in the Mojave Desert, California, United States while performing a test flight.[1][2] The co-pilot, Michael Alsbury, was killed and the pilot, Peter Siebold, was seriously injured.

Aircraft

The vehicle in the accident, VSS Enterprise, registration N339SS, was the sole Scaled Composites Model 339 SpaceShipTwo test vehicle.[3] It was the first of the five SpaceShipTwo craft planned by Virgin Galactic.[4] Since October 2010, VSS Enterprise had flown 20 captive flights while remaining attached to its WhiteKnightTwo carrier aircraft, 31 unpowered glide-to-landing tests, and three rocket-powered test flights.[citation needed] There were several performance issues during the ship engine's development in 2012 and 2013.[5][6]

A rocket-powered test flight of SpaceShipTwo took place on April 29, 2013, with an engine burn of 16 seconds duration. The brief flight began at an altitude of 47,000 feet (14,000 m), and reached a maximum altitude of 55,000 feet (17,000 m) and a speed of Mach 1.2 (920 miles per hour (1,480 km/h)).[7]

In order to receive a Federal Aviation Administration license to carry passengers, the craft needs to complete test missions at full speed and 62 miles (100 km) altitude.[8][citation needed]

A second SS2 vehicle, VSS Unity, was rolled out in February of 2016.[9]

Accident

VSS Enterprise crash is located in California
VSS Enterprise crash
The aircraft crashed near Cantil, California.

On October 31, 2014, VSS Enterprise crashed in the Mojave Desert near Cantil, California, United States.[3][10][11] The aircraft was performing a test flight, powered flight 4 (PF04),[12] from the Mojave Air and Space Port in which it was dropped from the WhiteKnightTwo carrier aircraft, VMS Eve.[13] The test flight was the aircraft's first powered flight in nine months, and was to include the first flight testing of a new, more powerful and steadier-thrust hybrid rocket engine whose fuel grain was composed of nylon instead of rubber. The flight was the aircraft's 55th, and its 35th free flight. VSS Enterprise was piloted by Peter Siebold and Michael Alsbury.[14][15]

According to the NTSB briefing, SpaceShipTwo dropped from the mother ship and fired its new hybrid rocket engine normally. About eleven seconds later, the space plane violently broke apart,[16] substantially giving the appearance of an explosion, and creating a 35-mile (56 km) long debris field.[17] Witnesses reported seeing a parachute before the aircraft crashed. The co-pilot, Michael Alsbury, was killed in the crash, whereas the pilot, Peter Siebold, survived with serious injuries and was transported to Antelope Valley Hospital in nearby Lancaster.[16] The carrier aircraft, VMS Eve, landed safely.[13][18]

Despite considerable early conjecture by industry experts[19][20] that the new rocket engine was at fault in the loss of VSS Enterprise, this was quickly discounted when the craft’s engine and propellant tanks were recovered intact, indicating there was no explosion due to either the solid (nylon-based) or liquid (nitrous oxide) components of the hybrid engine.[21]

A preliminary investigation and cockpit video subsequently indicated that the feathering system, the ship's air-braking descent device, deployed too early.[22][23] Two seconds later, while still under rocket propulsion, the craft disintegrated.[24] The feathering system requires two levers to operate. The system was unlocked by Michael Alsbury, but the feathering control was not moved, indicating an uncommanded feathering as "that action alone should not have been enough to pivot the tails upright" according to the NTSB.[25][26] The feathering system had been deliberately deployed supersonically during earlier powered flight tests of SS2, although previous activation either occurred in thinner air at higher altitudes, or at much lower speeds than the flight on October 31.[27]

Regarding the possibility of pilot error being the proximate cause of the crash, acting NTSB chairman Christopher Hart said: "We are not ruling anything out. We are looking at all of these issues to determine what was the root cause of this mishap … We are looking at a number of possibilities, including that possibility [of pilot error]."[21]

The incident resulted in the first fatality on a spacecraft in flight since the Space Shuttle Columbia disaster in 2003.[28] The survival of pilot Peter Siebold also marks the first time in history that anyone has survived the destruction of a spacecraft during a flight when others on board have died.[29][30][31] Investigators are trying to determine how Siebold managed to get out of the rocket plane and parachute to the ground from an altitude of roughly 50,000 feet, an altitude virtually devoid of oxygen.[32] On November 7, Siebold told investigators that the aircraft broke up around him. He was still strapped into his seat. He released the straps and his parachute later deployed automatically. Siebold was not wearing a pressure suit during the flight.[33]

Investigation

NTSB Go-Team inspects a tail section of VSS Enterprise

The National Transportation Safety Board (NTSB) investigated the accident. A Go Team was dispatched to the accident site on October 31.[34] The team, consisting of around fifteen personnel, arrived at the Mojave Air and Space Port on November 1. They began their investigation that day.[35]

At a news conference on November 2 NTSB acting chairman Christopher Hart said the lock–unlock lever for the vehicle's feathering mechanism was moved to the unlocked position at slightly above Mach 1. SpaceShipTwo's feathering mechanism then began moving even though that motion had not been commanded.[36] The on-site investigation was scheduled to take four to seven days.[37] It was reported on November 12 that the on-site investigation had been completed and that parts of the wreckage had been placed in secure storage should they be needed for further investigation.[33] It was expected to take about a year for the final report to be released.[37]

During a hearing in Washington D.C. on July 28, 2015,[38][39] and a press release on the same day[40] the NTSB cited inadequate design safeguards, poor pilot training, lack of rigorous federal oversight and a potentially anxious co-pilot without recent flight experience as important factors in the 2014 crash. They determined that the co-pilot, who died in the accident, prematurely unlocked a movable tail section some ten seconds after SpaceShipTwo fired its rocket engine and was breaking the sound barrier, resulting in the craft breaking apart. However, the Board also found that the Scaled Composites unit of Northrop Grumman, which designed and flew the prototype space tourism vehicle, did not properly prepare for potential human slip-ups by providing a fail-safe system that could have guarded against such premature deployment. "A single-point human failure has to be anticipated," board member Robert Sumwalt said. Instead, Scaled Composites "put all their eggs in the basket of the pilots doing it correctly."

The report’s details of the final moments of the flight reveal that the feather system was unlocked as SS2 accelerated under rocket power through Mach 0.92 at 10.07:28, some 9 seconds after release from the WhiteKnightTwo (WK2) carrier aircraft and an estimated 14 seconds before the vehicle would have reached Mach 1.4, the minimum speed at which the tail was designed to be unlocked. Telemetry, in-cockpit video and audio data confirmed that co-pilot Michael Alsbury announced "unlocking" as Mach 0.92 was passed and vehicle breakup occurred within the next 4 seconds. The feathering device, conceived by Scaled Composites designer Burt Rutan as a carefree and stable reentry method for recovery of SpaceShipOne, is designed to be activated outside of the thicker layers of the atmosphere before the vehicle begins its descent. The system operates by rotating the vehicle’s twin tail booms upward about the trailing edge of the wing by around 65 degrees; following reentry, the actuators rotate the booms down into the flush position for approach and landing.[41]

Investigators said the developer of the spacecraft failed to protect against human error[42] and that co-pilot Michael Alsbury may have been influenced by time pressure, along with strong vibration and acceleration forces he had not experienced since his last powered test flight in April 2013. The combination “could have increased the co-pilot’s stress." The board found that during years of development and flight tests, engineers at Scaled Composites assumed that any pilot mistakes would occur only in reaction to systems failures, not as the cause of such failures. The NTSB members also criticized the FAA, which approved the experimental test flights, for failing to pay enough attention to human factors or to provide necessary guidance to the nascent commercial space flight industry on the topic. They also cited pressure from some FAA managers to quickly approve experimental flight permits, sometimes without fully understanding technical issues or the details of the spacecraft.

In its submission to the NTSB, Virgin Galactic says the second SS2, nearing completion, had been modified with an automatic mechanical inhibit device to prevent locking or unlocking of the feather during safety-critical phases. An explicit warning about the dangers of premature unlocking has also been added to the checklist and operating handbook, and a formalized crew resource management (CRM) approach, already used by Virgin for its WK2 operations, is being adopted for SS2. This will include call-outs and a challenge/response protocol. While the report cites CRM issues as a likely contributing cause, Virgin says there is no plan to modify the cockpit display system.[43]

NTSB chairman Christopher Hart said that, as the Board had learned "with a high degree of certainty the events that resulted in the breakup", he hoped the investigation would prevent such an accident from happening again. "Many of the safety issues that we will hear about today arose not from the novelty of a space launch test flight, but from human factors that were already known elsewhere in transportation." Hart added "for commercial spaceflight to successfully mature, we must meticulously seek out and mitigate known hazards, as a prerequisite to identifying and mitigating new hazards."[44] Virgin Galactic is proceeding with its plans for space flight and is building another craft; company officials said that their commitment to commercial spacecraft had not wavered despite the crash and they expected the company to resume test flights later in 2015, though that date subsequently slipped.[45]

Responses

Virgin Galactic CEO George T. Whitesides, in a news conference following the incident, said that “Space is hard and today was a tough day.”[46][47] Virgin founder Richard Branson said after the crash: "We do understand the risks involved and we are not going to push on blindly—to do so would be an insult to all those affected by this tragedy. We are going to learn from what went wrong, discover how we can improve safety and performance and then move forwards together," and "Space is hard, but worth it."[48]

Michael Moses, Head of Operations for Virgin Galactic, admitted to tensions between Richard Branson’s upbeat projections and the persistent hurdles that challenged the company’s technical experts. “There’s a difference between the marketing and the engineering sides of the company", Mr. Moses said on November 10, 2014.[49]

The International Association for the Advancement of Space Safety (IAASS) heavily criticized Virgin Galactic within hours of the accident. Tommaso Sgobba, Executive Director of the IAASS, claimed that Virgin Galactic had refused to let IAASS scientists review its procedures and snubbed industry gatherings. He stated: "They operated in secrecy, which is difficult to understand. They don’t use modern techniques in putting safety into the design. They use outdated methods like testing and then seeing what happens. There has been no independent oversight. There is no peer review. I have been saying for some years now this was an accident waiting to happen."[19][50][51] Sgobba, the former head of flight safety for the European Space Agency, said on November 6, 2014 that industry best practice called for operators to build in "two-failure tolerance", or sufficient safeguards to survive two separate, unrelated failures—two human errors, two mechanical errors or one of each. "What we see in the incident is what we call 'zero-failure tolerance'," Mr Sgobba said. "So you make the mistake—you have a catastrophe. The design would not be acceptable in other safety-critical industries, such as aircraft manufacture."[52] Other members of IAASS also commented on the accident in the immediate aftermath. Rocket propulsion expert and rocket powered dragster driver[53] Carolynne Campbell-Knight was quoted as saying that Virgin Galactic "...should stop, give up. Go away and do something they might be good at like selling mobile phones. They should stay out of the space business."[54][55] Campbell-Knight also stated that an explosion of the nitrous oxide hybrid propulsion system was the cause of the accident,[51] although the initial NTSB report did not indicate that the propulsion system contributed to the breakup of the vehicle.[21]

Rocket Scientist Geoff Daly confirmed that he had written to the U.S. Chemical Safety Board in July 2013 urging them to do something about his safety concerns over SpaceShipTwo. "Even the company's own engineers privately doubted that their venture was safe."[19] Daly's concerns centered around the use of nitrous oxide in the hybrid propulsion system,[56][57] although the final NTSB report does not indicate the propulsion system contributed to the accident.[21]

A number of key employees had resigned from Virgin Galactic within the year leading up to the crash, including the Vice-President of Safety, Jon Turnipseed, and Vice-President of Propulsion, Thomas Markusic.[58]

In an editorial in Time magazine on October 31, 2014, Jeffrey Kluger concluded that "A fatal accident in the Mojave Desert is a lesson in the perils of space hubris. It’s hard not to be angry, even disgusted, with Branson himself. He is, as today’s tragedy shows, a man driven by too much hubris, too much hucksterism and too little knowledge of the head-crackingly complex business of engineering. For the 21st century billionaire, space travel is what buying a professional sports team was for the rich boys of an earlier era: the biggest, coolest, most impressive toy imaginable."[59]

On November 14, 2014, the Wall Street Journal published an article discussing the history of safety and technical problems of the aircraft, citing unnamed engineers and a former government official involved with the project. According to the article, the official said that nagging vibrations were "very distressing to pilots because they simply couldn’t read their instruments", although Virgin Galactic denies this claim. Furthermore, the engine did not have enough power to lift six passengers into space, so Virgin Galactic switched to a new plastics-based fuel, the Journal reported. At a test of the new fuel earlier in 2013, "an explosion all but obliterated the test stand", according to the Journal's sources.[60]

Virgin Galactic's attempts at distancing itself

In November 2014, Private Eye magazine criticised Branson and Virgin Galactic for their attempts to distance the company from the accident by referring to the test pilots as Scaled Composites employees.[61] Virgin Galactic’s official statement on October 31, 2014 said: “Virgin Galactic’s partner Scaled Composites conducted a powered test flight of SpaceShipTwo earlier today. [...] Local authorities have confirmed that one of the two Scaled Composites pilots died during the accident”.[62] This was in strong contrast to Virgin Galactic’s reports of an earlier successful test flight (also operated by Scaled Composites and its test pilots) which simply stated: “The Virgin Galactic flight was piloted by Mark Stucky and co-pilot Clint Nichols”.[63] Similarly, in his blog of September 15, 2014, Richard Branson made no distinction between Virgin Galactic and Scaled Composites employees when he wrote: "As Virgin Galactic continues its flight test program and puts its spaceships, pilots and crew through its paces, another group has been preparing for their first flights to space: SpaceShipTwo’s Future Astronauts."[64] Photos posted on the Virgin Galactic website before the 2014 accident which showed Branson with project engineers, including many who were Scaled Composites employees, were simply captioned "the Galactic team".[61]

See also

References

  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. ↑ 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. ↑ Mojave Air and Space Port press conference on October 31, 2014, at 2:00 p.m. PDT — involving: the Spaceport, Sheriff's Department, County Fire Department, Scaled Composites, Virgin Galactic
  13. ↑ 13.0 13.1 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. ↑ 16.0 16.1 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.
  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. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  23. ↑ 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. ↑ 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. ↑ 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. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  32. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  33. ↑ 33.0 33.1 Lua error in package.lua at line 80: module 'strict' not found.
  34. ↑ 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. ↑ 37.0 37.1 Lua error in package.lua at line 80: module 'strict' not found.
  38. ↑ 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. ↑ 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. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  44. ↑ 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. ↑ 51.0 51.1 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. ↑ http://www.knightsarrow.com/about-us/
  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. ↑ http://www.csb.gov/assets/1/7/Daly.pdf
  57. ↑ http://www.cbc.ca/m/touch/news/story/1.2821452
  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. ↑ 61.0 61.1 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. ↑ 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.

External links

Retrieved from "https://infogalactic.com/w/index.php?title=VSS_Enterprise_crash&oldid=714363363"