It looks like you're using an Ad Blocker.

Please white-list or disable AboveTopSecret.com in your ad-blocking tool.

Thank you.

 

Some features of ATS will be disabled while you continue to use an ad-blocker.

 

B-52 crash on Guam-May 2016

page: 4
7
<< 1  2  3   >>

log in

join
share:

posted on May, 21 2016 @ 10:47 AM
link   
a reply to: Bfirez

Only when they're doing some check rides. After one of the B-1 crashes where an IP was killed because he didn't have an ejection seat they limit extra crew on bombers as much as possible.




posted on May, 21 2016 @ 12:11 PM
link   


found a page with a few pics of 0047

www.touchdown-aviation.com...
edit on 21-5-2016 by grey580 because: (no reason given)



posted on May, 21 2016 @ 02:25 PM
link   
a reply to: grey580

Any updates yet on the ejection vs. skid and egress escape part?



posted on May, 21 2016 @ 02:28 PM
link   
a reply to: Bfirez

No, probably won't be for a week or two when they release preliminary information.



posted on Dec, 15 2016 @ 08:42 PM
link   
I haven't seen the AIB report yet, but I heard it was a high speed abort, that went off the end of the runway and caught fire.



posted on Dec, 16 2016 @ 02:17 PM
link   

originally posted by: Zaphod58
I'm starting to think that bombers might want to stay away from Guam. A B-52 crashed in 2008 killing all six on board while practicing for an air parade. A B-2 crashed on Guam in 2008, and another was almost destroyed by an engine fire. A B-1 suffered significant damage after making an emergency landing and rolling into parked fire trucks, also in 2008.


Crew sleep deprivation and time change?



posted on Dec, 16 2016 @ 02:40 PM
link   
a reply to: mbkennel

No, all but the B-2 crash had mechanical causes. The B-52 had a trim tab shift on them they think. The B-2 that crashed was due to not following checklists. The other B-2 was an engine fire, exacerbated by fire department inexperience. The B-1 was a hydraulic problem.



posted on Apr, 19 2017 @ 06:20 PM
link   
A combination of factors led to this accident. It was actually a runway overrun, not a crash as first reported.

The aircraft was performing a "high speed, heavyweight takeoff" when the pilot noticed birds near the end of the runway. There were also indications they weren't generating the required thrust to takeoff, so the pilot declared an abort. During the abort the drag chute failed, probably due to the speed, and the brakes overheated as they tried to stop. This resulted in the aircraft departing the runway and catching fire.

www.airforcetimes.com...



posted on Apr, 19 2017 @ 06:49 PM
link   
Might have to use an anchor next time..Very lucky no casualties..



posted on Apr, 19 2017 @ 08:12 PM
link   
Ugh... that is a gawd awful sequence of events..

Oh and as far as egress with a full crew + a couple... when I flew on a buff to an island in the indian ocean... if we had to bail I had to wait for the nav and radar nav to eject, toss the tool box out and hope it cleared the antenna... then jump and drop out the hole in the bottom and hope for the best.




top topics



 
7
<< 1  2  3   >>

log in

join