Good record overall
The B-52 has a very good overall record and more information is needed before we know what happen.
Quote
Since then, the B-52 had only suffered two Class A incidents, one in 1995 and another in 2005, but no loss of aircraft or crew. In fact, in the past 10 years the aircraft have had a Class A rate of only 0.41 per 100,000 flight hours.
Jul 21, 2008
By Robert Wall and David A. Fulghum
The bodies of two crewmembers of a U.S. Air Force B-52H Stratofortress that crashed early July 21 off the coast of Guam have been recovered, while the fate of the other four remains uncertain, according to the U.S. Air Force.
The bomber was engaged in a training mission and was scheduled to perform a flyover celebrating Guam's Liberation Day when it went down around 9:45 a.m. local time.
The B-52 was deployed from Barksdale Air Force Base, La., to Andersen AFB, as part of the DoD's continuous bomber presence mission in the Pacific. However, USAF officials said there were no weapons or munitions aboard.
A board of officers is investigating the accident. Still, the crash off the northwest coast of Guam has ended an incredibly long run of no losses in the Cold War-era bomber fleet. It is the first B-52 loss since 1994, when four crew members died at Fairchild AFB, Wash., while practicing for an air show. That crash was blamed on pilot error.
Since then, the B-52 had only suffered two Class A incidents, one in 1995 and another in 2005, but no loss of aircraft or crew. In fact, in the past 10 years the aircraft have had a Class A rate of only 0.41 per 100,000 flight hours.
Not counting the latest incident, during the life of the program 79 B-52s have been destroyed, with the loss of life of 315 personnel. The Class A accident number is slightly higher, 98, with an accident rate of 1.27.
Including the latest B-52 crash, so far this fiscal year the Air Force has suffered 22 Class As, with 14 aircraft destroyed. If all six B-52 crew members did not survive the incident, it will double the number of fatalities for the fiscal year that the service has suffered. Guam was also the site of the accident in February that destroyed one of the service's 21 B-2 bombers while taking off (Aerospace DAILY, June 13).
Guam is considered a tough environment for both new and old aircraft with its corrosive, seaside saltwater environment, heat and high humidity. The B-2 crash was traced, in part, to accumulated water in sensors that then reported incorrect speed and angle of attack to the aircraft's flight controls. The result was a low-speed takeoff, a sharp pitchup and a stall that led to the first B-2 crash.
Air Force officials are already closely watching an F-22 deployment at Andersen to ensure they are on top of any issues that might result from an extended employment on Guam, and which might affect the operation of a Hawaii Air National Guard F-22 unit that is to stand up there in 2009-10. An earlier deployment of F-22s to Okinawa wasn't long enough to offer much evidence, USAF officials told Aviation Week.
B-52s bring the added problem of being old aircraft even though airframe time has been carefully managed. Both B-52s and B-1s have suffered from electrical problems and on-board fires over the years when operating from the similar environment of Diego Garcia in the Indian Ocean.
The B-2 and B-52 accidents come in the midst of great expansion of facilities and missions at Guam that includes a unit of three or four unmanned Global Hawk intelligence, surveillance and reconnaissance (ISR) aircraft.
And there's more to come. U.S. Navy planners have an interest in Andersen and other U.S.-manned air bases in the region. They want the Air Force's tankers to be based in places like Guam to service the Navy's long-range, unmanned combat and intelligence gathering air vehicles.
USAF file photo of B-52 at Edwards AFB: Chad Bellay
Link
http://www.aviationweek.com/aw/gene...line=Two B-52 Crew Recovered After Guam Crash