Jason Goins Air Force | What Project Arc Proved About Fixing Problems on the Ground
Jason Goins Air Force
Engineers Belong Where the Problems Are
Most maintenance backlogs in the Air Force don't exist because nobody knows about them. They exist because the people who can solve them sit in offices hundreds of miles from the flight line. Jason Goins Air Force officer and scientist launched Project Arc to test a different model: put engineers directly inside operational units and let them work on defined problems with the crews who live with them daily.
The results were specific. B-1 maintenance hours dropped. RQ-4 Global Hawk targeting accuracy improved. These weren't theoretical gains published in a study nobody reads.
They showed up in unit readiness reports.
The Gap Between Knowing and Doing
Defense organizations collect enormous amounts of data about what breaks, what fails, and what takes too long. The Air Force is no exception. But data sitting in a database does not fix a hydraulic line or recalibrate a sensor. Jason Goins of Washington DC understood that the bottleneck wasn't information.
It was proximity.
When an engineer spends weeks embedded with a maintenance crew, they see things reports never capture. They notice workarounds. They hear the off-hand complaints that point to root causes. A technician might mention that a particular bracket cracks every 200 flight hours, and that single observation can redirect an engineering solution that saves thousands of labor hours downstream.
Small Teams, Measured Results
Project Arc didn't try to overhaul the entire maintenance system. It placed small teams with specific mandates: identify the top three gaps in a unit, propose fixes within 60 days, and track whether those fixes held. The scope was deliberately narrow because narrow problems have testable solutions.
That discipline came from Jason Goins Air Force background in chemistry. Scientific training teaches you to isolate variables. You don't change everything at once. You change one thing, measure it, and move on.
The same logic applied to maintenance operations. Fix the B-1 problem first. Measure the hours saved. Then move to the RQ-4 issue.
Why It Matters Beyond One Program
Project Arc was never about creating a permanent institution. It was about proving a method. If you put technically trained people close to operators and give them clear boundaries, useful things happen quickly. Jason Goins Air Force career has carried that principle forward through roles at Joint Base Anacostia-Bolling and in counter-WMD policy work in Washington DC, where the same question keeps coming up: who is close enough to the problem to actually solve it?
The answer is rarely the person writing the policy memo. It's usually the person standing next to the broken equipment, or the analyst staring at the data feed, or the technician who has replaced the same part for the third time this quarter. Project Arc just made it possible for an engineer to stand next to them when it mattered.
Disclaimer: The views expressed are the author's own and do not constitute endorsement by the Department of War, Department of the Air Force, or the U.S. Government. The subject's participation and appearance in any private or public events, sponsored or otherwise, or references, including external hyperlinks, to non-federal entities do not constitute or imply Department of War, Department of the Air Force or U.S. Government endorsement of any company or organization.