B-52 crash Guam
 

Sounds like the crew got out. I'm glad to hear that.
Fly safe!

Air Force B-52 crashes in Guam, crew bails to safety

Crazy day for aviation. What's next?

"The plane had taken off from Andersen Air Force Base to perform a flyby in the Guam Liberation Day celebration."

Stand by for more policies.

Glad the crew is safe.

That was the purpose of the crash in 2008.

Correct.

This was (likely) planned to be a show of force near the "Made in China" islands. As such, a big fuel load.

Rumor is aborted takeoff, and hot brakes and/or runway excursion.

http://www.facebook.com/photo.php?fb...type=3&theater

Meh... it should Buff right out. Parts+5.

On a serious note, I'm surprised the Wing CC has gone out with a public statement of what a great decision it was the crew made. I hope the accident and safety investigation determine that is the case.

No black box that I'm aware of onboard. I suppose the investigation will rely mainly on what the crew says.

Semi serious question: Will the buff abort for a single engine failure before V1, or do you have to have multiple?

Watching them take off for Viet Nam, fully loaded with bombs and fuel, one wondered if eight engines would be enough. :rolleyes:

Valid point, Tom, but those were Ds and Fs. The H (only model still flying) has about 40% more thrust than those earlier birds. It's the only turbofan of the bunch.

Nope, no FDR, but I believe the intercom system was upgraded when CONECT was added. I don't know if that included a cockpit voice recorder or not. (Retired in 2010).

Yes, absolutely. And it's S1 or decision speed in BUFF terms. If S1 is not reached in X time, then abort. Or if critical event happens before S1, abort. The timing starts at 70 knots. The navigator calls off the time: "Coming up on 16.3 seconds: ready, ready, NOW".

It's been a while, but IIRC, normal dry runway S1 speeds and times for average gross weights (~400K-440K) were ~114-116 knots and 14-16 seconds. For a dry runway, the takeoff data is calculated using a 4000' decision distance. We don't go off of the distance, only S1 speed in XX time, but the decision to abort or continue will be made very close to 4000' after starting the takeoff roll (again, on a dry runway).

The takeoff data is calculated assuming no drag chute (worst case). If the drag chute deploys, then all the better. The max airspeed for drag chute deployment is 135 knots. If they aborted above 135 and the co-pilot panicked and deployed the chute before they got below 135, then the chute likely failed/sheared.

I'm assuming this was a very high speed abort well beyond S1. We've had a couple of those where the pilot felt for some reason that the plane just wasn't going to make it off the ground. IIRC, one ran off the end of the runway at Castle AFB in the mid-early 80's after rejecting the takeoff well beyond S1. I believe in that case that they were almost to S2 (unstick) speed when the decision to abort was made.