A 22-Day PAC-3 Delivery Measures the Handoff, Not the Factory

Suppose a headline appeared tomorrow claiming twenty-two days from signed production agreement to delivered PAC-3 missile housing. A number like that would immediately be read as proof that missile-production capacity can be created in three weeks. It cannot, and the number would never have claimed it could.

I want to be precise about what such a number would measure, because read correctly it would be genuinely good news, and read the way excitement usually runs, it would become a dangerous planning assumption. Read correctly, it is a supplier-handoff metric: the time it takes a prepared industrial organization to accept a transferred work package and produce a conforming article for a demanding customer. Read wrongly, it becomes evidence that capacity is a faucet you open when demand arrives, and planners who believe in faucets buy too little capacity too late, at the worst possible prices.

The distinction matters because PAC-3 supply is exactly where wishful assumptions are about to get bought.

What Day Zero Would Actually Be

Day zero on such a clock would be a production agreement, not an empty lot. For the clock to run that fast, there would already have to exist a company with casting and machining capability, a trained workforce, calibrated inspection equipment, and quality systems mature enough to satisfy a missile prime's acceptance criteria. There would have to be a technical data package and a tooling plan ready to transfer, because nobody signs up to a 22-day commitment against a blank sheet. The clock would measure how fast a prepared receiver caught a prepared throw. It would exclude the years and the capital that built the receiver.

That would not be a criticism of the delivery. Executing a transfer in 22 days is hard, and any team that did it would have earned the result. My criticism is aimed at the pattern that follows every impressive schedule number in this industry: an outcome achieved under specific enabling conditions gets restated as a general capability, and the enabling conditions quietly drop out of the sentence. It is the same pattern that turns a capability demonstrated once, under favorable conditions, into a capability described as fielded.

Honest timelines carry their denominators. Lockheed Martin signed a framework agreement with the U.S. Department of Defense to accelerate production and delivery of the AIM-260 Joint Advanced Tactical Missile. That agreement builds on years of collaboration. Years is the honest denominator. Twenty-two days would be a numerator sitting on top of a denominator someone else already paid for.

The Shortage Such A Number Would Be Read Against

The context makes the misreading tempting. Insufficient production capacity is the primary challenge in supplying Ukraine with PAC-3 interceptors for its Patriot systems. Global demand for those interceptors currently exceeds supply, and existing stockpiles are inadequate. Separately, PAC-3 interceptor production is being considered for expansion through joint projects involving the United States, Ukraine and NATO partners. That means real money is about to move on the strength of somebody's assumptions about how fast capacity appears.

Against that backdrop, a 22-day story would be exactly what a stressed planner wants to believe. But a magazine depth problem is not closed by first articles. It is closed by accepted rounds per month, sustained for years through every line item in the bill of materials. A housing is one item on that bill, and a fast housing does nothing for whichever subsystem is actually pacing the line, which is usually the one nobody is tracking.

There is also a second-order risk. Numbers like 22 days get lifted into requirements documents as planning factors, the way wish-list requirements get written with no cost basis and no exchange arithmetic behind them. Once a schedule assumption is embedded in a program baseline, unwinding it costs political capital nobody wants to spend, so the assumption survives until reality invoices it. Better to interrogate such a number while it is still a headline and not a milestone.

What Clocks Look Like When They Start Closer To Zero

Compare the timescales when a program clock includes more of the real work. The Navy awarded Boeing a $562 million fixed-price incentive contract on September 14, 2026, to initiate Lot 1 low-rate initial production of the MQ-25A Stingray. The contract covers three Lot 1 aircraft and long-lead components for three additional Lot 2 aircraft. Initial deliveries are expected to begin in 2029. That is roughly three years from contract to first delivery, on a program mature enough to be in LRIP, and the contract buys long-lead parts now because that is where the time actually goes.

Go heavier and the clock reads in decades. Defence Secretary Wes Streeting said BAE Systems would manufacture the AUKUS submarines in Barrow-in-Furness and that steel cutting should begin in 2027. That steel cutting in 2027 is expected to mark the start of production, with the first submarine entering service in the late 2030s. Different product and scale, same shape: when little is pre-built, first delivery sits years past signature, not weeks.

Even the industrial base underneath castings tells the same story. MxD has received two U.S. Department of War grants totaling $2.4 million to accelerate digital modernization of the American casting and forging sector. The awards build on MxD's casting and forging initiative, which convened government, industry and technology leaders for workshops that produced a Casting & Forging Digital Fabric Roadmap. Sector-wide modernization begins with a roadmap, and the distance from roadmap to running foundry is measured in years, not weeks.

Measure Accepted Parts At Rate, Not Days To First Delivery

So here is the metric I would substitute. Not days from signature to first delivery, but accepted parts per month, at stated yield, through the customer's quality gate, sustained across enough months to prove the tooling, the workforce, the input supply and the quality system all hold under load. First-article speed is a leading indicator with a terrible false-positive rate: it confirms the transfer worked and says nothing about whether month twenty looks like month two. Rate is the only number a magazine responds to.

The funding implication follows directly. A 22-day result would be possible only because someone had already paid for the receiver, over years, before the demand spike arrived. If we want results like that, the move is to fund and exercise supplier handoffs now, at suppliers who have not yet been asked, while finding the gaps is still cheap. There is a model for this in a different domain: defense and technology companies take part in annual exercises in Norway aimed at countering satellite-signal jamming, rehearsing against the threat before it is the only thing that matters. Supplier handoffs deserve the same treatment: rehearse the transfer of a real work package to a qualified second source, then time it honestly and fix the data-package and quality gaps the rehearsal exposes.

Capacity is a mortgage, not a faucet.

Pay For The Receiver Before You Need The Throw

None of this diminishes what a fast handoff achieves. It relabels it, and labels matter because budgets follow labels. If program offices read 22 days as elastic capacity, they will fund too little and too late, and discover the real lead time at the worst possible moment. If they read it as a handoff metric, the same number argues for the opposite: pre-qualified second sources and exercised data packages, along with standing investment in casting, machining, workforce and quality systems that are ready before any signature exists.

That labeling discipline is one I try to hold my own work to. Kibernan has produced six complete, costed engineering programs, among them an AI Managed Missile Factory, and every published figure in those programs carries its maturity: modeled, specified, calculated or objective. They are proposals, and we say in writing that no Kibernan hardware has been built or fielded, because the distance between a modeled number and an objective one is exactly the distance between a 22-day handoff and a 22-day factory.

A delivery like that would be good news. The team that executed it would have done something genuinely hard, and done it fast. File it under handoffs executed, not capacity created, and then go fund the next receiver before anyone needs the throw.