previous post next post  

Speaking of the Air Force...

...not meaning to pile on, but the report is out about the B2 crash in Guam earlier this year. The video keeps your heart in your throat - but the pilots do punch out at pretty much the last second.

Depending on whose cost figures you accept (1.4 - 2.5 billion per aircraft) you are watching 1/4 to 1/2 of a Nimitiz-class carrier turn into a yard dart at Andersen AFB on Guam.

The cause, according to the AF report (as reported by the AP):

The Air Force on Thursday said the first crash of a B-2 stealth bomber was caused by moisture in sensors and estimated the loss of the aircraft at $1.4 billion.

The crash probably could have been avoided if knowledge of a technique to evaporate the moisture had been disseminated throughout the B-2 program, said Maj. Gen. Floyd L. Carpenter, who headed an accident investigation board.

The "Spirit of Kansas" abruptly pitched up, rolled and yawed to the left Feb. 23 before plunging to the ground at Andersen Air Force Base on the island of Guam. Both pilots ejected safely just after the left wing made contact with the ground in the first crash since the maiden B-2 flights nearly 20 years ago.

Got to give the AF credit - 20 years without a total pranging isn't too bad.

Heh. Of course it had to be the aircraft named after a square state in the flyover... I assure you, as a resident of Kansas, that is *not* our Spirit, no matter what Thomas Franks thinks.

What we had here, was a failure to communicate:

The crash probably could have been avoided if knowledge of a technique to evaporate the moisture had been disseminated throughout the B-2 program, said Maj. Gen. Floyd L. Carpenter, who headed an accident investigation board.

Almost makes a taxpayer want to go out, get drunk, and cut the heads off of some parking meters.

The report said, "The human factor of communicating critical information was a contributing factor to this mishap."

One hopes the proponents of automating away the pilots in commercial aircraft are taking notes. They'll be awfully expensive if you have to equip them with ejection seats.

Heh.

"It's fortunate the crew was able to safely eject. It's unfortunate, however, that we lost one of our nation's penetrating bombers," said Gen. Carrol H. Chandler, commander of Pacific Air Forces.

It's really unfortunate that a communications error cost 1.4 billion dollars.

10 Comments

Has it taken forty years for the Air Force to figure out you can't get a computer wet and still expect it to work?
 
Nice of them to keep the wreckage clear of the runway. Were the pilots ok? I understand ejecting that low to the ground can be hazardous to your health.
 
I know they survived, I do not know if they were folded, spindled, or otherwise mauled. I know one problem with zero-zero or near zero ejections is landing in the flaming wreck, which did not happen here. Long time no read, dude!
 
I found one reference that they both survived, although no real details on the injuries : "The two pilots ejected. One was in stable condition with unspecified injuries at a naval hospital in Guam, while the other was released after a medical evaluation, ..." I'm glad we didn't lose them, at least.
 
Yea, and sometime back a F-117 was lost at an airshow because of a maintance failure. I can't say for sure but it's less likely things like this would happen if Curtis LeMay was still around. He was one ruthless SOB and didn't mind taking heads if there was a slip in combat efficiency. Too many of the Air Force brass today act more like CEO's of Starbucks than warfighters.
 
All that technology, all that money... and all gone for a departure stall. Sheesh.
 
As a 30+ year veteran of military and civilian flying, a grad of the USAF Mishap Investigation course, having been up close nad personal with F-117s and the maintainers and operators therein, not to mention talking to aerodynamic engineers, electrical engineers and the 4-stars who have seen everything from tracers coming up from the trees in Vietnam to JDAMs on 1x1 foot targets, etc., etc., etc., I find these comments... amusing. Heh.
 
Sometimes, despite all the maintenance, all the planning, all the pre-flights, $#it just breaks anyway...it's that Murphy guy I tell ya...
 
Instapilot, in a million words or less, how do we prevent this from happening again?
 
Communication - from the bottom up or top down? I say blame it on some AF brass who thinks "I should know that, I'm in charge. If I didn't come up with it then it's probably just another crew chief trying to make a name for himself and make me look bad". I say, fire the MotherF&*%er like they did with the other incompetants in the nuke flyover fiasco.