Wednesday, May 9, 2012

Did I say $114 million mistake? I meant $351 million.

Hopefully these sorts of updates don't become a regular thing, it's awfully distressing. Anyways, once again we see more money vanish into the rabbit hole that is the F-35 Lightening II Joint Strike Fighter Program (JSF) program. It's more of the same, a $237.7 million contract "for changes to the configuration baseline hardware or software resulting from the JSF development effort."

But wait, there's more. This time the concurrency cap is getting increased, the concurrency cap being the threshold at or under which the contract has to incorporate government authorized changes. Yep, that's more leeway. I don't think Lockheed Martin is to blame by any means, so the cap should be raised, but it's awfully disheartening to see something written into the contract just in case it costs even more than it already has.

I'm really hoping this doesn't become a recurring theme with the F-35 program.

One thing worth noting about this particular modification is that $222.6 million of these funds will expire at the end of the current fiscal year. These mistakes have already cost a whooping $351 million, is taking away money if it takes a long time really worth it? Could rushing not be a problem that's making these changes necessary?

Interestingly enough, the F-35 JSF program has seen quite a bit of testing done. The F-35 has completed night flights, night refueling, conventional takeoffs and landings, formation flights, the whole 9 yards. There have been hundreds of flights, so what is going wrong that is costing this much extra money?

Well, I've got my abacus ready for if there are any more contracts, and I'll keep on calling program officials until they let me in on what's going on. Check back often for more updates!

No comments:

Post a Comment