Air Force fighters now and into the future with Mike Benitez
Mike Benitez joined me on the Acquisition Talk podcast to talk about the current state and future of the Air Force fighter inventory. He discusses the rationale behind the recent announcement from Chief of Staff CQ Brown that the USAF will neck down it's inventory from seven systems to "four plus one." Mike explains how the NGAD will replace the F-22, the logic behind buying both the F-35 and F-15EX, and the options for replacing the F-16. We also play a round of "retire it or not" for the A-10, RQ-4 Global Hawk, and the KC-135 tanker.
During the episode, Mike argues that laying in several major advances in the same clean-sheet development leads to poor outcomes -- not only for the systems themselves but the industrial base. Shifting to a government reference architecture can help open up competition and even change business models. Rather than companies making their profits in sustainment, which represents 70% of lifecycle costs, the Air Force could change the paradigm by making development pay and potentially even breaking the link between development and production.
The F-117 was a great example of tackling one hard problem (low observability) while leveraging existing components everywhere else. While making a slightly different case, Mike points to Boeing's T-7A which used digital engineering and parts commonality. "The T-7 was engineered from the ground up for commonality within its parts," Mike said. "So the the left horizontal stabilizer is the same exact part as the right is just put in upside down... they've built an aircraft that has such a skinny supply chain that you're able to actually operate... but the point is that most of the fighters right now are not developed like that."
Mike discusses a more agile approach to fighter development, opportunities for test and evaluation techniques, the challenges presented by the budget process, the need to increase emphasis on logistics and communications, and much more.
You can find more from Mike Benitez by signing up for his weekly newsletter The Merge at https://themerge.co
This podcast was produced by Eric Lofgren. Soundtrack by urmymuse: "reflections of u". You can follow us on Twitter @AcqTalk and find more information at AcquisitionTalk.com.
During the episode, Mike argues that laying in several major advances in the same clean-sheet development leads to poor outcomes -- not only for the systems themselves but the industrial base. Shifting to a government reference architecture can help open up competition and even change business models. Rather than companies making their profits in sustainment, which represents 70% of lifecycle costs, the Air Force could change the paradigm by making development pay and potentially even breaking the link between development and production.
The F-117 was a great example of tackling one hard problem (low observability) while leveraging existing components everywhere else. While making a slightly different case, Mike points to Boeing's T-7A which used digital engineering and parts commonality. "The T-7 was engineered from the ground up for commonality within its parts," Mike said. "So the the left horizontal stabilizer is the same exact part as the right is just put in upside down... they've built an aircraft that has such a skinny supply chain that you're able to actually operate... but the point is that most of the fighters right now are not developed like that."
Mike discusses a more agile approach to fighter development, opportunities for test and evaluation techniques, the challenges presented by the budget process, the need to increase emphasis on logistics and communications, and much more.
You can find more from Mike Benitez by signing up for his weekly newsletter The Merge at https://themerge.co
This podcast was produced by Eric Lofgren. Soundtrack by urmymuse: "reflections of u". You can follow us on Twitter @AcqTalk and find more information at AcquisitionTalk.com.
The podcast Acquisition Talk is embedded on this page from an open RSS feed. All files, descriptions, artwork and other metadata from the RSS-feed is the property of the podcast owner and not affiliated with or validated by Podplay.