2008 Andersen Air Force Base B-2 accident

From Wikipedia, the free encyclopedia

2008 Andersen Air Force Base B-2 accident
Crashed B-2.jpg
The crashed Spirit of Kansas
Accident
Date23 February 2008 (2008-02-23)
SummaryCrashed on take-off following stall
SiteAndersen Air Force Base, Guam
13°35′13″N 144°56′19″E / 13.58694°N 144.93861°E / 13.58694; 144.93861Coordinates: 13°35′13″N 144°56′19″E / 13.58694°N 144.93861°E / 13.58694; 144.93861
Aircraft
Aircraft typeNorthrop Grumman B-2 Spirit
Aircraft nameSpirit of Kansas
OperatorUnited States Air Force
Registration89-0127
Flight originAndersen Air Force Base, Guam
Occupants2
Crew2
Fatalities0
Injuries2
Survivors2

On 23 February 2008, Spirit of Kansas, a B-2 Spirit stealth bomber of the United States Air Force, crashed on the runway moments after takeoff from Andersen Air Force Base in Guam. The aircraft was destroyed, but both crew members successfully ejected.[1] The accident marked the first operational loss of a B‑2 bomber, and as of 2021 it remains the only one. With an estimated loss of US$1.4 billion, it was also the most expensive aircraft crash in history.[2][3]

Crash[]

On 23 February 2008, a B‑2 crashed on the runway shortly after takeoff from Andersen Air Force Base in Guam.[1] The crash of the Spirit of Kansas, 89-0127, which had been operated by the 393rd Bomb Squadron, 509th Bomb Wing, Whiteman Air Force Base, Missouri, and which had logged 5,100 flight hours,[4] was the first ever crash of a B‑2.[5]

The two-officer crew attempted to control the bomber but were unable to do so, and as one of its wingtips made contact with the ground, they ejected and survived the crash. The aircraft was destroyed, a total loss estimated at US$1.4 billion.[6]

According to the Air Force Times, which is a private-industry magazine, no munitions were on board.[7] The Air Combat Command accident board report states that "classified material" had been loaded onto the bomber the morning the aircraft was returning to Whiteman Air Force Base "after a four-month deployment in support of Pacific Air Forces' continuous bomber presence."[8]

At Guam Naval Hospital, one pilot was evaluated and released, and the second was hospitalized. A B‑2 already in the air was called back to Andersen following the crash, where it and the other B‑2s were grounded until an initial investigation into the crash was complete. Six Boeing B‑52s of the 96th Bomb Squadron, 2nd Bomb Wing at Barksdale Air Force Base, Louisiana, were deployed to replace the B‑2s.[1][9]

The commander of the 509th Bomb Wing, Brig. Gen. Garrett Harencak, followed up on the incident by temporarily suspending flying operations for all 20 remaining B‑2s to review procedures. Harencak termed the suspension a "safety pause" and stated that the B‑2s would resume flying if called upon for immediate operations.[10] The B‑2 fleet returned to flight status on 15 April 2008.[11]

Investigation[]

The findings of the investigation stated that the B‑2 crashed after "heavy, lashing rains" caused moisture to enter skin-flush air-data sensors. The data from the sensors are used to calculate numerous factors including airspeed and altitude. Because three pressure transducers failed to function[12]—attributable to condensation inside devices, not a maintenance error—the flight-control computers calculated inaccurate aircraft angle of attack and airspeed. Incorrect airspeed data on cockpit displays led to the aircraft rotating at 12 knots (22 km/h) slower than indicated. After the wheels lifted from the runway, which caused the flight control system to switch to different control laws, the erroneously sensed negative angle of attack caused the computers to inject a sudden, 1.6 g (16 m/s2), uncommanded 30-degree pitch-up maneuver. The combination of slow lift-off speed and the extreme angle of attack, with attendant drag, resulted in an unrecoverable stall, yaw, and descent. Both crew members successfully ejected from the aircraft soon after the left wing tip started to gouge the ground alongside the runway. The aircraft hit the ground, tumbled, and burned after its fuel ignited.[2][8][13][14]

References[]

  1. ^ Jump up to: a b c Lavitt, Michael O. "B‑2 Crashes on Takeoff From Guam." Aviation Week, 23 February 2008. Archived 17 January 2012 at the Wayback Machine
  2. ^ Jump up to: a b "Moisture confused sensors in B‑2 crash", AirForceTimes, 6 June 2008.[dead link]
  3. ^ Whitaker, Raymond (25 February 2008). "The Most Expensive Air Crash in History". Common Dreams. Retrieved 2 January 2020.
  4. ^ https://www.businessinsider.com/videos-b-2-stealth-bomber-crash-2018-2%3famp
  5. ^ https://www.cnn.com/style/amp/b-2-spirit-stealth-bomber/index.html
  6. ^ "Air Force: Moisture caused $1.4 billion bomber crash". CNN.com. 6 June 2008. Archived from the original on 10 June 2008. Retrieved 7 June 2008.
  7. ^ "No munitions on board B‑2 that crashed", Air Force Times, 23 February 2008.
  8. ^ Jump up to: a b Air Combat Command, Accident Investigation Board, "Summary of Facts", "B-2A, S/N 89-0127, 20080223 KSZL501A"; link: AFD-080605-054 Archived 4 March 2016 at the Wayback Machine, hosted by GlenPew.com
  9. ^ "B-2 stealth bomber crashes on Guam". 23 February 2008. Retrieved 22 January 2017.
  10. ^ "B-2 pause", Air Force Times, February 2008.
  11. ^ Linch, Stephen. "B-2s return to flight after safety pause", USAF, 21 April 2008. Archived 17 October 2008 at the Wayback Machine
  12. ^ [1]
  13. ^ "Air Force: Sensor Moisture Caused 1st B-2 Crash". NBC News. 5 June 2008.
  14. ^ Shachtman, Noah (6 June 2008). "Video: Stealth Bomber Crashes". Wired. Archived from the original on 14 October 2008.

External links[]

Retrieved from ""