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
8
<< 1  2  3    5 >>

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.



posted on Dec, 21 2018 @ 02:34 PM
link   
AMARG is currently working on returning 60-0034 to flyable condition, upon which it will head to Tinker to undergo modernization and upgrades to return it to service to replace the aircraft destroyed here. It's a former 5th Bomb Wing, 23rd Bomb Squadron aircraft, that was based at Minot when it was retired. It's been in the Boneyard just over 10 years, with its retirement date being 14 Aug 2008.



posted on Dec, 21 2018 @ 03:16 PM
link   
a reply to: Zaphod58

If they can make 0054 flyable they can get any jet flyable.



posted on Jan, 10 2019 @ 11:30 PM
link   


She's about ready to head to Tinker.



posted on Jan, 11 2019 @ 02:27 AM
link   
Almost like old battleships.



posted on Apr, 14 2019 @ 02:25 PM
link   
They've gotten to engines running on 0034. She's been moved around, but I haven't heard if it was under her own power, ot towed.



posted on Apr, 19 2019 @ 08:43 AM
link   

originally posted by: Zaphod58
They've gotten to engines running on 0034. She's been moved around, but I haven't heard if it was under her own power, ot towed.


Already at Minot or still at BY? I live 5 min from BY.



posted on Apr, 19 2019 @ 09:27 AM
link   
a reply to: PilSungMtnMan

She'll go to Tinker first, but she hasn't left DM yet.



posted on May, 13 2019 @ 08:08 PM
link   
Aircraft 034 flies from the Boneyard Tuesday, May 14th. She goes to Barksdale, with three senior crew members on board. She'll fly VFR with the gear locked down, below 10,000 feet. Once at Barksdale, she gets field level modifications done. Once those are completed, she goes to Tinker for PDM and Depot level modifications.



posted on May, 13 2019 @ 10:38 PM
link   
a reply to: Zaphod58

Why not fly directly to Tinker? Is Barksdale not further? Let me go ahead and drive my beat-up old car to my buddy in another state so he can fix my tires, then i'm going to drive back the way I came to have the mechanic fix the engine...



posted on May, 14 2019 @ 12:55 AM
link   
a reply to: Bfirez

Because overall it's less time required to return it to service to go to Barksdale first. The guys there can do required upgrades that can be done at the unit level. If you go to the Depot to do all of it, you either have to tie up a slot that's already needed by a currently active aircraft, or you have to slot it in as best you can between aircraft. You're already looking at 18-19 months at Tinker minimum. Going straight there, that could be pushed out to 24-30.



new topics

top topics



 
8
<< 1  2  3    5 >>

log in

join